Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: Twice now I've created new guests on an F12 box and the guests have defaulted to QEMU instead of KVM, on a box with KVM-capable processors. There was nowhere I could see during the guest setup process to specify KVM and the guests are running with the '-no-kvm' switch. In fact, libvirt doesn't seem to see the host as KVM-capable, even though it is: virsh capabilities|grep -i kvm comes back with nothing. /proc/cpuinfo: processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 26 model name : Intel(R) Xeon(R) CPU E5540 @ 2.53GHz stepping : 5 cpu MHz : 2527.104 cache size : 8192 KB physical id : 1 siblings : 4 core id : 0 cpu cores : 4 apicid : 16 initial apicid : 16 fpu : yes fpu_exception : yes cpuid level : 11 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm dca sse4_1 sse4_2 popcnt lahf_lm ida tpr_shadow vnmi flexpriority ept vpid bogomips : 5054.20 clflush size : 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: Version-Release number of selected component (if applicable): virt-manager-0.8.2-3.fc12.noarch qemu-system-x86-0.11.0-13.fc12.x86_64 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
What do "modprobe | grep kvm" and "dmesg | grep kvm" tell you? Most likely you either don't have kvm loaded, or it tried to load and failed because virtualization is disabled in the BIOS. Chris Lalancette
Just an FYI, latest virt-manager in rawhide explictly handles this case, giving an info msg when launching the VM wizard and KVM isn't detected. In F12 it's pretty non-obvious when we fallback to qemu as you've seen. I'll take a look at backporting those changes.
Yes, you're right it's disabled in the BIOS - there's a message when the KVM module loads to that effect. I didn't setup this machine myself, which explains it, as I always enable virtualization. Many thanks for the swift response and glad to hear it's being addressed.
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. 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 '12'. 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 12'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 12 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
Not backporting to F12 at this point, so closing against F13 where this is currently fixed.