libvirtError: unsupported configuration: timer hypervclock doesn't support setting of timer tickpolicy
4:33 a.m.
This is a multi-part message in MIME format.
--------------050805010200030806000304
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
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.
--------------050805010200030806000304
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit
<html>
<head>
<meta http-equiv="content-type" content="text/html;
charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
It seems like we need to upgrade libvirt dependencies in master
repo:<br>
<blockquote>Thread-78::ERROR::2015-04-29
06:23:04,584::vm::741::vm.Vm::(_startUnderlyingVm)
vmId=`6ec9c0a0-2879-4bfe-<br>
9a79-92471881ebfe`::The vm start process failed<br>
Traceback (most recent call last):<br>
File "/usr/share/vdsm/virt/vm.py", line 689, in
_startUnderlyingVm<br>
self._run()<br>
File "/usr/share/vdsm/virt/vm.py", line 1800, in _run<br>
self._connection.createXML(domxml, flags),<br>
File
"/usr/lib/python2.7/site-packages/vdsm/libvirtconnection.py", line
126, in wrapper<br>
ret = f(*args, **kwargs)<br>
File "/usr/lib64/python2.7/site-packages/libvirt.py", line 3427,
in createXML<br>
if ret is None:raise libvirtError('virDomainCreateXML()
failed', conn=self)<br>
libvirtError: unsupported configuration: timer hypervclock doesn't
support setting of timer tickpolicy<br>
</blockquote>
To reproduce, start a "Windows 2008 R2 x64" VM (no problem with
Windows 2012).<br>
Glad to see that hv_ optimization flags are being supported, since
they boost Windows VM performance using inhouse MS Hypervisor
optimizations.<br>
<br>
</body>
</html>
--------------050805010200030806000304--
4:40 a.m.
------=_Part_7129509_1403561595.1430300416017
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Hi,
----- Original Message -----
From: "Christopher Pereira" <kripper(a)imatronix.cl>
To: devel(a)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?
Bests,
--
Francesco Romani
RedHat Engineering Virtualization R & D
Phone: 8261328
IRC: fromani
------=_Part_7129509_1403561595.1430300416017
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit
<html><body><div style="font-family: times new roman, new york, times,
serif; font-size: 12pt; color:
#000000"><div>Hi,</div><div><br></div><div><br></div><hr
id="zwchr"><blockquote style="border-left:2px solid
#1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><b>From:
</b>"Christopher Pereira"
&lt;kripper(a)imatronix.cl&gt;<br><b>To:
</b>devel(a)ovirt.org<br><b>Sent: </b>Wednesday, April 29, 2015
11:33:55 AM<br><b>Subject: </b>[ovirt-devel] libvirtError: unsupported
configuration: timer hypervclock doesn't support setting of timer
tickpolicy<br><div><br></div>
It seems like we need to upgrade libvirt dependencies in master
repo:<br><blockquote>Thread-78::ERROR::2015-04-29
06:23:04,584::vm::741::vm.Vm::(_startUnderlyingVm)
vmId=`6ec9c0a0-2879-4bfe-<br>
9a79-92471881ebfe`::The vm start process failed<br>
Traceback (most recent call last):<br>
File "/usr/share/vdsm/virt/vm.py", line 689, in
_startUnderlyingVm<br>
self._run()<br>
File "/usr/share/vdsm/virt/vm.py", line 1800, in
_run<br>
self._connection.createXML(domxml, flags),<br>
File
"/usr/lib/python2.7/site-packages/vdsm/libvirtconnection.py", line
126, in wrapper<br>
ret = f(*args, **kwargs)<br>
File "/usr/lib64/python2.7/site-packages/libvirt.py", line
3427,
in createXML<br>
if ret is None:raise
libvirtError('virDomainCreateXML()
failed', conn=self)<br>
libvirtError: unsupported configuration: timer hypervclock doesn't
support setting of timer tickpolicy<br></blockquote>
To reproduce, start a "Windows 2008 R2 x64" VM (no problem with
Windows 2012).<br>
Glad to see that hv_ optimization flags are being supported, since
they boost Windows VM performance using inhouse MS Hypervisor
optimizations.</blockquote><div><br></div><div>Deps
should have been fixed already; can you share the versions of the stack components
you're running?<br></div><div>VDSM from master I
guess<br></div><div>libvirt?<br></div><div>qemu?<br></div><div>OS?<br></div><div><br></div><div>Bests,<br></div><div><br></div><div>--
<br></div><div><span name="x"></span>Francesco
Romani<br>RedHat Engineering Virtualization R & D<br>Phone:
8261328<br>IRC: fromani<span
name="x"></span><br></div></div></body></html>
------=_Part_7129509_1403561595.1430300416017--
4:43 a.m.
This is a multi-part message in MIME format.
--------------070401030506090701070206
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
On 29-04-2015 6:40, Francesco Romani wrote:
Hi,
------------------------------------------------------------------------
*From: *"Christopher Pereira" <kripper(a)imatronix.cl>
*To: *devel(a)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
--------------070401030506090701070206
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit
<html>
<head>
<meta content="text/html; charset=utf-8"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 29-04-2015 6:40, Francesco Romani wrote:<br>
<blockquote
cite="mid:1699348517.7129510.1430300416019.JavaMail.zimbra@redhat.com"
type="cite">
<div style="font-family: times new roman, new york, times, serif;
font-size: 12pt; color: #000000">
<div>Hi,</div>
<div><br>
</div>
<div><br>
</div>
<hr id="zwchr">
<blockquote style="border-left:2px solid
#1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><b>From:
</b>"Christopher Pereira" <a
class="moz-txt-link-rfc2396E"
href="mailto:kripper@imatronix.cl"><kripper@imatronix.cl></a><br>
<b>To: </b><a class="moz-txt-link-abbreviated"
href="mailto:devel@ovirt.org">devel@ovirt.org</a><br>
<b>Sent: </b>Wednesday, April 29, 2015 11:33:55 AM<br>
<b>Subject: </b>[ovirt-devel] libvirtError: unsupported
configuration: timer hypervclock doesn't support setting of
timer tickpolicy<br>
<div><br>
</div>
It seems like we need to upgrade libvirt dependencies in
master repo:<br>
<blockquote>Thread-78::ERROR::2015-04-29
06:23:04,584::vm::741::vm.Vm::(_startUnderlyingVm)
vmId=`6ec9c0a0-2879-4bfe-<br>
9a79-92471881ebfe`::The vm start process failed<br>
Traceback (most recent call last):<br>
File "/usr/share/vdsm/virt/vm.py", line 689, in
_startUnderlyingVm<br>
self._run()<br>
File "/usr/share/vdsm/virt/vm.py", line 1800, in _run<br>
self._connection.createXML(domxml, flags),<br>
File
"/usr/lib/python2.7/site-packages/vdsm/libvirtconnection.py",
line 126, in wrapper<br>
ret = f(*args, **kwargs)<br>
File "/usr/lib64/python2.7/site-packages/libvirt.py", line
3427, in createXML<br>
if ret is None:raise libvirtError('virDomainCreateXML()
failed', conn=self)<br>
libvirtError: unsupported configuration: timer hypervclock
doesn't support setting of timer tickpolicy<br>
</blockquote>
To reproduce, start a "Windows 2008 R2 x64" VM (no problem
with Windows 2012).<br>
Glad to see that hv_ optimization flags are being supported,
since they boost Windows VM performance using inhouse MS
Hypervisor optimizations.</blockquote>
<div><br>
</div>
<div>Deps should have been fixed already; can you share the
versions of the stack components you're running?<br>
</div>
<div>VDSM from master I guess<br>
</div>
<div>libvirt?<br>
</div>
<div>qemu?<br>
</div>
<div>OS?<br>
</div>
<br>
</div>
</blockquote>
CentOS Linux release 7.1.1503 (Core)<br>
<br>
# yum update<br>
No packages marked for update<br>
<br>
qemu-kvm-ev-2.1.2-23.el7.1.x86_64<br>
qemu-img-ev-2.1.2-23.el7.1.x86_64<br>
ipxe-roms-qemu-20130517-6.gitc4bce43.el7.noarch<br>
libvirt-daemon-driver-qemu-1.2.8-16.el7_1.2.x86_64<br>
qemu-kvm-tools-ev-2.1.2-23.el7.1.x86_64<br>
qemu-kvm-common-ev-2.1.2-23.el7.1.x86_64<br>
<br>
libvirt-daemon-config-network-1.2.8-16.el7_1.2.x86_64<br>
libvirt-daemon-1.2.8-16.el7_1.2.x86_64<br>
libvirt-lock-sanlock-1.2.8-16.el7_1.2.x86_64<br>
libvirt-daemon-driver-secret-1.2.8-16.el7_1.2.x86_64<br>
libvirt-daemon-driver-lxc-1.2.8-16.el7_1.2.x86_64<br>
libvirt-1.2.8-16.el7_1.2.x86_64<br>
libvirt-client-1.2.8-16.el7_1.2.x86_64<br>
libvirt-daemon-driver-nwfilter-1.2.8-16.el7_1.2.x86_64<br>
libvirt-daemon-config-nwfilter-1.2.8-16.el7_1.2.x86_64<br>
libvirt-daemon-driver-interface-1.2.8-16.el7_1.2.x86_64<br>
libvirt-daemon-driver-storage-1.2.8-16.el7_1.2.x86_64<br>
libvirt-daemon-driver-qemu-1.2.8-16.el7_1.2.x86_64<br>
libvirt-daemon-kvm-1.2.8-16.el7_1.2.x86_64<br>
libvirt-python-1.2.8-7.el7_1.1.x86_64<br>
libvirt-daemon-driver-nodedev-1.2.8-16.el7_1.2.x86_64<br>
libvirt-daemon-driver-network-1.2.8-16.el7_1.2.x86_64
</body>
</html>
--------------070401030506090701070206--
5:12 a.m.
Hi,
----- 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 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
5:21 a.m.
On 29-04-2015 7:12, Francesco Romani wrote:
Hi,
----- 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 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)
> [...]
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
5:29 a.m.
----- 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
3283
days inactive
3283
days old
5 comments
2 participants
participants (2)
-
Christopher Pereira -
Francesco Romani