[ovirt-devel] libvirtError: unsupported configuration: timer hypervclock doesn't support setting of timer tickpolicy

[Christopher Pereira]

On 29-04-2015 6:40, Francesco Romani wrote:
> Hi,
>
>
> ------------------------------------------------------------------------
>
>     *From: *"Christopher Pereira" <kripper at imatronix.cl>
>     *To: *devel at ovirt.org
>     *Sent: *Wednesday, April 29, 2015 11:33:55 AM
>     *Subject: *[ovirt-devel] libvirtError: unsupported configuration:
>     timer hypervclock doesn't support setting of timer tickpolicy
>
>     It seems like we need to upgrade libvirt dependencies in master repo:
>
>         Thread-78::ERROR::2015-04-29
>         06:23:04,584::vm::741::vm.Vm::(_startUnderlyingVm)
>         vmId=`6ec9c0a0-2879-4bfe-
>         9a79-92471881ebfe`::The vm start process failed
>         Traceback (most recent call last):
>           File "/usr/share/vdsm/virt/vm.py", line 689, in
>         _startUnderlyingVm
>             self._run()
>           File "/usr/share/vdsm/virt/vm.py", line 1800, in _run
>             self._connection.createXML(domxml, flags),
>           File
>         "/usr/lib/python2.7/site-packages/vdsm/libvirtconnection.py",
>         line 126, in wrapper
>             ret = f(*args, **kwargs)
>           File "/usr/lib64/python2.7/site-packages/libvirt.py", line
>         3427, in createXML
>             if ret is None:raise libvirtError('virDomainCreateXML()
>         failed', conn=self)
>         libvirtError: unsupported configuration: timer hypervclock
>         doesn't support setting of timer tickpolicy
>
>     To reproduce, start a "Windows 2008 R2 x64" VM (no problem with
>     Windows 2012).
>     Glad to see that hv_ optimization flags are being supported, since
>     they boost Windows VM performance using inhouse MS Hypervisor
>     optimizations.
>
>
> Deps should have been fixed already; can you share the versions of the 
> stack components you're running?
> VDSM from master I guess
> libvirt?
> qemu?
> OS?
>
CentOS Linux release 7.1.1503 (Core)

# yum update
No packages marked for update

qemu-kvm-ev-2.1.2-23.el7.1.x86_64
qemu-img-ev-2.1.2-23.el7.1.x86_64
ipxe-roms-qemu-20130517-6.gitc4bce43.el7.noarch
libvirt-daemon-driver-qemu-1.2.8-16.el7_1.2.x86_64
qemu-kvm-tools-ev-2.1.2-23.el7.1.x86_64
qemu-kvm-common-ev-2.1.2-23.el7.1.x86_64

libvirt-daemon-config-network-1.2.8-16.el7_1.2.x86_64
libvirt-daemon-1.2.8-16.el7_1.2.x86_64
libvirt-lock-sanlock-1.2.8-16.el7_1.2.x86_64
libvirt-daemon-driver-secret-1.2.8-16.el7_1.2.x86_64
libvirt-daemon-driver-lxc-1.2.8-16.el7_1.2.x86_64
libvirt-1.2.8-16.el7_1.2.x86_64
libvirt-client-1.2.8-16.el7_1.2.x86_64
libvirt-daemon-driver-nwfilter-1.2.8-16.el7_1.2.x86_64
libvirt-daemon-config-nwfilter-1.2.8-16.el7_1.2.x86_64
libvirt-daemon-driver-interface-1.2.8-16.el7_1.2.x86_64
libvirt-daemon-driver-storage-1.2.8-16.el7_1.2.x86_64
libvirt-daemon-driver-qemu-1.2.8-16.el7_1.2.x86_64
libvirt-daemon-kvm-1.2.8-16.el7_1.2.x86_64
libvirt-python-1.2.8-7.el7_1.1.x86_64
libvirt-daemon-driver-nodedev-1.2.8-16.el7_1.2.x86_64
libvirt-daemon-driver-network-1.2.8-16.el7_1.2.x86_64
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/devel/attachments/20150429/5378f184/attachment.html>