Re: [ovirt-devel] libvirtError: unsupported configuration: timer hypervclock doesn't support setting of timer tickpolicy
On 29-04-2015 7:12, Francesco Romani wrote: Hi, - Original Message - From: Christopher Pereira krip...@imatronix.cl To: Francesco Romani from...@redhat.com Cc: devel@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 ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] libvirtError: unsupported configuration: timer hypervclock doesn't support setting of timer tickpolicy
- Original Message - From: Christopher Pereira krip...@imatronix.cl To: Francesco Romani from...@redhat.com Cc: devel@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 ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
[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.
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] libvirtError: unsupported configuration: timer hypervclock doesn't support setting of timer tickpolicy
On 29-04-2015 6:40, Francesco Romani wrote:
Hi,
*From: *Christopher Pereira krip...@imatronix.cl
*To: *devel@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
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] libvirtError: unsupported configuration: timer hypervclock doesn't support setting of timer tickpolicy
Hi,
- Original Message -
From: Christopher Pereira krip...@imatronix.cl
To: devel@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
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] libvirtError: unsupported configuration: timer hypervclock doesn't support setting of timer tickpolicy
Hi, - Original Message - From: Christopher Pereira krip...@imatronix.cl To: Francesco Romani from...@redhat.com Cc: devel@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 ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
