Bug 1393352

Summary: Corruption and instability on suspend and resume
Product: [Fedora] Fedora Reporter: cslee-redhat
Component: qemuAssignee: Fedora Virtualization Maintainers <virt-maint>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 24CC: amit, amit.shah, berrange, cfergeau, clalancette, crobinso, dwmw2, ehabkost, extras-orphan, itamar, markmc, pbonzini, quintela, rjones, virt-maint
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-02-23 01:52:39 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:

Description cslee-redhat 2016-11-09 11:42:17 UTC 
Description of problem:
On closing the lid of a laptop ~20% of opening the machine and resuming results in the VM running processor up to very high utilization and not responding to input.
Once in a while the VM will resume fine and operate, but on reboot the disk is found to be corrupt, this has happened twice.
I am not sure that resume is involved in the second issue.

Version-Release number of selected component (if applicable):


How reproducible:
random but fairly high chance of inactive after resume

Steps to Reproduce:
1. Create Fedora VM using virtual machine manager
2. Run machine
3. close laptop lid and wait for suspend
4. Open laptop lid
5. Virtual machine manager shows utilization on CPU go very high, fans start to run
6. Try access through Boxes or virtual Machine Manager, nothing works

Actual results:
VM is humg at high CPU use

Expected results:
VM resumes and runs as expected

Additional info:
Comment 1 Cole Robinson 2017-02-23 01:52:39 UTC 

*** This bug has been marked as a duplicate of bug 1352992 ***
Comment 2 Cole Robinson 2017-03-16 15:34:09 UTC 

*** This bug has been marked as a duplicate of bug 1380893 ***