Red Hat Bugzilla – Bug 492178
virsh capabilities run w/ qemu driver does not show vmx flags in <host> section
Last modified: 2011-01-13 17:51:14 EST
Description of problem:
virsh capabilities should show presence of vmx flags in <host> section. Running virsh capabilities on a box with kvm and kvm_intel modules loaded results in:
vmx flag presence is not reported.
Version-Release number of selected component (if applicable):
Also reproduced w/
Steps to Reproduce:
vmx flag is not shown
vmx flag should be present
<danpb> oh hang on, i'm using xen here
<danpb> bet this is a QMEU driver bug
...but why is <cpu> not HV independent? Seems like a design issue.
True, seeing the same thing here. <vmx/> is present on Xen but missing
on KVM, with otherwise same stack, can't garantee it will be fixed for
5.4 though it should be relatively simple to fix,
Well there is various pieces of code doing this already but this need to be cleaned up, and I'm afraid the refactoring is too much change for 5.4 at this
point. So a priori postponed to a later release.
Upstream libvirt is working on exposing full host CPU flags data. In the meantime we should do a quick fix to expose vmx/svm flags so QEMU driver is on a par with the Xen driver.
I don't think we can cover this for 5.5 at this point, retargetting it for 5.6
Fixed in libvirt-0.8.2-1.el5
Verified on x86-64 kvm Intel and AMD
the steps on AMD
run virsh capabilities
<topology sockets='1' cores='4' threads='1'/>
Look at the file /usr/share/libvirt/cpu_map.xml
the svm is included in phenom model
So the bug is verified
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.