[ovirt-devel] libvirtError: unsupported configuration: timer hypervclock doesn't support setting of timer tickpolicy
Francesco Romani
fromani at redhat.com
Wed Apr 29 10:12:02 UTC 2015
Hi,
----- Original Message -----
> From: "Christopher Pereira" <kripper at imatronix.cl>
> To: "Francesco Romani" <fromani at redhat.com>
> Cc: devel at ovirt.org
> Sent: Wednesday, April 29, 2015 11:43:43 AM
> Subject: Re: [ovirt-devel] libvirtError: unsupported configuration: timer hypervclock doesn't support setting of
> timer tickpolicy
> > 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
Then I'm afraid is just a bug, and this patch should help:
https://gerrit.ovirt.org/#/c/40387/
--
Francesco Romani
RedHat Engineering Virtualization R & D
Phone: 8261328
IRC: fromani
More information about the Devel
mailing list