Bug 1138335
| Summary: | Suspending a vm with shared bootable disk will cause other vms that uses the bootable disk to enter into paused state due to storage I/O problem | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Retired] oVirt | Reporter: | Raz Tamir <ratamir> | ||||
| Component: | ovirt-engine-core | Assignee: | bugs <bugs> | ||||
| Status: | CLOSED WORKSFORME | QA Contact: | meital avital <mavital> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 3.5 | CC: | amureini, ecohen, gklein, iheim, michal.skrivanek, ratamir, rbalakri, yeylon | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 3.5.1 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | virt | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2014-11-07 10:37:35 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | Virt | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | 1084103 | ||||||
| Bug Blocks: | |||||||
| Attachments: |
|
||||||
Update: Also shutting down one of the vms will cause the same behaviour. Probably not an interesting usecase, but leaving the virt stakeholders to triage - not sure what the suspension does to this disk Raz, can we get the qemu and libvirt logs too please? so the disk is bootable in 2 VMs, shared&writeable in 2 VMs and you're running both at the same time? Hi Allon, I can't reproduce this. (In reply to ratamir from comment #5) > Hi Allon, > I can't reproduce this. Closing, based on this comment. Raz - if you're encounter/reproduce this again, please re-open the bug. Thanks! |
Created attachment 934446 [details] vdsm and engine logs Description of problem: 2 vms that shares the same bootable disk as their bootable disk can cause a situation that if one of the vms is suspended, the other vm will pause due to storage I/O problem. Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: setup: 2 vms, 1 bootable disk (shared) 1. run both of the vms 2. suspend one of them 3. Actual results: the second vm will enter into pause mode Expected results: Additional info: