Bug 504111

Summary:	Installing KVM makes machine unable to resume from suspend
Product:	[Fedora] Fedora	Reporter:	Andrew Zabolotny <anpaza>
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	10	CC:	itamar, kernel-maint
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-12-18 09:32:14 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Andrew Zabolotny 2009-06-04 10:14:56 UTC

Description of problem:
When the KVM package is installed (which loads the kvm and kvm_intel modules) suspending the machine doesn't work anymore - you can't wake it up again - it locks up. This bug was always there - since the appearance of KVM in kernel, and is present both in fedora 9 and 10.

Version-Release number of selected component (if applicable):
kernel-2.6.27.23-78.2.50.fc9.x86_64
kernel-2.6.27.24-170.2.68.fc10.x86_64

How reproducible:
Quite often

Steps to Reproduce:
1. Install the kvm package
2. Reboot and log in to X11
2.5. (optional) launch some virtual machine with qemu-kvm, I have a feeling that this makes the probability of the bug higher.
3. System->Shutdown->Suspend or run pm-suspend
4. Try to wake up the computer
  
Actual results:
The computer turns on, but does not react to keyboard nor does not show anything on the monitor. Seldom it will wake up normally.

Expected results:
The computer should resume normally.

Additional info:
Tried this on two machines:
- One with a Core2 Duo E6400 CPU (2-cores)
- One with a Core2 Extreme CPU X9650 (4-cores)

Comment 1 Bug Zapper 2009-11-18 12:04:13 UTC

This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '10'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 10's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 10 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 2 Bug Zapper 2009-12-18 09:32:14 UTC

Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.