Red Hat Bugzilla – Bug 1029792
VDSM does not report the qemu version in capabilities, if qemu-kvm-rhev is used
Last modified: 2013-12-02 12:52:06 EST
Created attachment 823293 [details]
Missing qemu version in webadmin
Description of problem:
When qemu-kvm-rhev is installed, vdsm does not report the used qemu version in its capabilities and the version of qemu as shown in webadmin stays empty. For live-snaphots (and probably other features, too) qemu-kvm-rhev is the preferred version over plain qemu-kvm. VDSM for RHEV has a patch, that changes detection of qemu-kvm to qemu-kvm-rhev (patch: 0069-VDSM-should-return-qemu-kvm-parameters-by-getCaps-AP.patch). For oVirt there probably should be a more robust solution, that is able to detect both variations.
Version-Release number of selected component (if applicable):
any ovirt vdsm release
Steps to Reproduce:
1. install new host with qemu-kvm-rhev and register it to the engine
qemu version is not reported in capabilties and not shown in webadmin
qemu version is reported in capabilties and shown in webadmin
Created attachment 823294 [details]
VDSM log (slightly sanitized)
Installed qemu packages on this host:
Could you give more details about your configuration?
Are you using oVirt's Vdsm with rhev's qemu-kvm? Why? Mixing ovirt and rhev may have other issues.
(In reply to Dan Kenigsberg from comment #3)
> Could you give more details about your configuration?
> Are you using oVirt's Vdsm with rhev's qemu-kvm? Why? Mixing ovirt and rhev
> may have other issues.
This is a CentOS 6.4 host with oVirt vdsm (latest 3.3.1 beta) and a rebuild of qemu-kvm (with rhev features enabled). RHEV qemu and base qemu are the basically same SRPM. They only differ in the way they are build. RHEV qemu has rhev=1 defined in its spec and enables more features. Lately there have been several discussions in the mailing list and the consensus was that qemu-kvm-rhev is preferred over the default qemu-kvm because it does not support e.g. live-snaphots.
It should be an easyfix. Could you verify the attached patch?
Tested on 3.3.1 with a respin of vdsm 4.13.0-11 and patch applied, but in vdsm.log I see:
Traceback (most recent call last):
File "/usr/share/vdsm/caps.py", line 342, in _getKeyPackages
mi = ts.dbMatch('name', KEY_PACKAGES[pkg]).next()
TypeError: unknown key type
http://gerrit.ovirt.org/#/c/19295/ is needed as a prerequisite. When applying gerrit 21226 together with 19295 it works fine.
Full patch that addresses this ticket is attached.
Created attachment 823536 [details]
should probably be delivered with 3.3.2