Bug 539956

Summary: qemu-kvm can not boot guest
Product: [Fedora] Fedora Reporter: Sergei LITVINENKO <sergei.litvinenko>
Component: qemuAssignee: Glauber Costa <gcosta>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: berrange, dwmw2, gcosta, itamar, jaswinder, jforbes, markmc, quintela, sergei.litvinenko, virt-maint
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-11-22 10:11:59 EST Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Sergei LITVINENKO 2009-11-21 13:50:57 EST
Description of problem:
kvm: unhandled exit 7
kvm_run returned -22

Version-Release number of selected component (if applicable):
[sergeil@homedesk ~]$ rpm -qf `which qemu-kvm`

How reproducible:

Steps to Reproduce:
1. qemu-kvm -localtime -hda rawhide.img -boot c -m 1024
Actual results:
error message and stop guest booting after message
ata0 master ...

Expected results:
boot guest system and work

Additional info:

1. `qemu-kvm -no-kvm -hda fedora12.img -boot c` work as expected

2. [sergeil@homedesk ~]$ uname -r

3. [sergeil@homedesk ~]$ cat /proc/cpuinfo | grep "model name"
model name      : Intel(R) Core(TM)2 Duo CPU     E6850  @ 3.00GHz

4. Disk image is created and work OK under Fedora-11
Comment 1 Sergei LITVINENKO 2009-11-21 14:20:45 EST
rebuild and installing qemu-0.11.0-12.fc13.src.rpm from rawhide decided my problem.
Comment 2 Justin M. Forbes 2009-11-22 10:11:59 EST
This is actually a KSM issue that only appears when running on a 32bit host.  Using the kernel update from updates-testing will resolve the issue.  You can also 'service ksmtuned stop; service ksm stop' after the system has booted to temporarily restore functionality until the new kernel is shipping.

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