Created attachment 916052 [details] vdsm+engine logs Description of problem: Running a vm cause a libvirtError:"Failed to retrieve QoS metadata". vdsm's log: Thread-919::ERROR::2014-07-07 14:59:55,601::vm::319::vm.Vm::(_sampleCpuTune) vmId=`6eddfad3-b36c-4b7b-a9b1-ac5aaaf6f704`::Failed to retrieve QoS metadata Traceback (most recent call last): File "/usr/share/vdsm/virt/vm.py", line 316, in _sampleCpuTune libvirt.VIR_DOMAIN_METADATA_ELEMENT, METADATA_VM_TUNE_URI, 0) File "/usr/share/vdsm/virt/vm.py", line 604, in f ret = attr(*args, **kwargs) File "/usr/lib64/python2.6/site-packages/vdsm/libvirtconnection.py", line 111, in wrapper ret = f(*args, **kwargs) File "/usr/lib64/python2.6/site-packages/libvirt.py", line 904, in metadata if ret is None: raise libvirtError ('virDomainGetMetadata() failed', dom=self) libvirtError: argument unsupported: QEMU driver does not support <metadata> element Version-Release number of selected component (if applicable): ovirt-engine-3.5.0-0.0.master.20140629172257.git0b16ed7.el6.noarch vdsm-4.16.0-3.git601f786.el6.x86_64 How reproducible: 100% Steps to Reproduce: 1.create vm + disk 2.run vm Actual results: operation is successful but a fail appears on log Expected results: no fail should appear Additional info:
I set severity to urgent because it's might be the reason (or at least part of the reason) why getting a vm started on oVirt 3.5 takes so long
*** This bug has been marked as a duplicate of bug 1114968 ***