Description of problem: Version-Release number of selected component (if applicable): virt-manager.noarch 1.1.0-12.el7 @base How reproducible: always Steps to Reproduce: 1. create a new VM 2. edit the Processor > check Copy host CPU configuration 3. start the VM Actual results: Error starting domain: unsupported configuration: host doesn't support invariant TSC Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 89, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/asyncjob.py", line 125, in tmpcb callback(*args, **kwargs) File "/usr/share/virt-manager/virtManager/domain.py", line 1393, in startup self._backend.create() File "/usr/lib64/python2.7/site-packages/libvirt.py", line 966, in create if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self) libvirtError: unsupported configuration: host doesn't support invariant TSC Expected results: a started VM Additional info: qemu.x86_64 2:2.0.0-1.el7.5 @epel libvirt.x86_64 1.2.8-16.el7_1.3 @updates virt-manager.noarch 1.1.0-12.el7 @base
Could be related to bug 1133155
I just ran into this problem as well and the workaround is to "virsh edit" after the flag is set and remove the line "<feature policy='require' name='invtsc'/>" from the xml. After that the guest boots normally.
It's fixed in v1.2.0. *** This bug has been marked as a duplicate of bug 1133155 ***
Can RH please let us know the schedule for this v1.2.0 release? thx Laurie