Bug 1165352
| Summary: | qemu spins after host suspends/hibernates and resumes | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Dimitris <dimitris.on.linux> | ||||
| Component: | qemu | Assignee: | Fedora Virtualization Maintainers <virt-maint> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 21 | CC: | amit.shah, berrange, cfergeau, crobinso, dwmw2, itamar, pbonzini, rjones, scottt.tw, virt-maint | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2015-10-14 14:47:28 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
Update: This is still present in host F21, guest still F20, qemu 2:2.1.2-7.fc21. Also, I can reproduce with both host suspend and hibernate. Update: Guest also updated to F21, same behavior continues. Both host's and guest's packages up to date as of now. *** This bug has been marked as a duplicate of bug 1233568 *** *** This bug has been marked as a duplicate of bug 1380893 *** |
Created attachment 958741 [details] virsh dumpxml output Description of problem: Host and guest are both on F20. The guest is not configured/expected to suspend when the host hibernates; I just want to be able to suspend or hibernate the host without hacving to shutdown/boot the guest every time. Version-Release number of selected component (if applicable): 2:1.6.2-10.fc20 How reproducible: Every time Steps to Reproduce: 1. Start the guest 2. Hibernate the host 3. Resume the host Actual results: The guest is unresponsive, and the qemu process is using 100% of one core. Expected results: The guest should continue running. IIRC this used to be the case until a little while ago. Additional info: