Re: [ovirt-devel] libvirtError: unsupported configuration: timer hypervclock doesn't support setting of timer tickpolicy
----- Original Message -----
From: "Christopher Pereira" <kripper(a)imatronix.cl>
To: "Francesco Romani" <fromani(a)redhat.com>
Cc: devel(a)ovirt.org
Sent: Wednesday, April 29, 2015 12:21:25 PM
Subject: Re: [ovirt-devel] libvirtError: unsupported configuration: timer hypervclock
doesn't support setting of
timer tickpolicy
[...]
>>> Glad to see that hv_ optimization flags are being
supported, since
>>> they boost Windows VM performance using inhouse MS Hypervisor
>>> optimizations.
[...]
> Then I'm afraid is just a bug, and this patch should help:
>
> https://gerrit.ovirt.org/#/c/40387/
>
Ok. Any news about turning on all the "hv_*" flags [1] for Windows guests?
[1] : https://bugzilla.redhat.com/show_bug.cgi?id=1083529
Except for the bug you hit, VDSM side is done.
To trigger all the optimization, Engine needs to send the 'hypervEnable' config
item set to 'true'.
Because of this bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1163828
this was disabled on Engine side for 3.5.x as workaround for an actual QEMU bug for window
>= 8 (64 bit)
and for windows server >= 2012 (64 bit).
For 3.6.x we'll need to revert that patch.
Meantime, you can just tune osinfo.properties locally and have the same result.
Bests,
--
Francesco Romani
RedHat Engineering Virtualization R & D
Phone: 8261328
IRC: fromani