Hi, ----- Original Message -----
> From: "Christopher Pereira" <[email protected]> > To: [email protected] > 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 [email protected] http://lists.ovirt.org/mailman/listinfo/devel
