Red Hat Bugzilla – Bug 487650
F10 virt-manager: only offers XEN & QEMU, no KVM => No Paravirt
Last modified: 2009-03-01 06:29:57 EST
Description of problem:
Although all the paravirt options are enabled in the current kernel .config,
the Virtual Machine Manager ( <- libvirt ) only offers connections to "XEN" and "QEMU", but not "KVM".
Selecting QEMU, trying to build a new VM, the Paravirt alternative keeps greyed out; only the Full_Virt alternative is offered.
Version-Release number of selected component (if applicable):
kernel 220.127.116.11 (amd64)
Steps to Reproduce:
1. Start the Virtual Machine Manager
3. Create a new VM
No Paravirt selectable
Be able to build paravirt. VM's
Cross-checking on my parallel Gentoo (18.104.22.168 ; gcc 4.3.3) installation,
paravirt KVMs work like a charme.
KVM guets run fullvirtualized kernels, with a number of paravirt drivers (clock, disk, network & balloon) - the kernel config options you enable for 'kvm paravirt' are just refering to turning on PV drivers - the core kernel is still fullvirtualizaed. The 'paravirt' option in virt manager refers to truely paravirt kernels like the Xen PV ABI
(In reply to comment #1)
> KVM guets run fullvirtualized kernels ...
> the core kernel is still fullvirtualizaed.
Thanks a lot for your speedy distinct clarification!
Is this decision due to KVM hanging on 'root mode',
thus creating an internal conflict
if the kernel is XEN-enabled at the same time?
Just for chance, do you happen to know if this will change in F11
(c.f. recent RedHat decisions to (Qumranet-acquired) KVM in favour over XEN) ?
(In reply to comment #2)
> (In reply to comment #1)
I mis-interpreted your answer. ;(
Forget about my questions !