Bug 1243932 - cannot start VMs -- Error starting domain: unsupported configuration: host doesn't support invariant TSC
Summary: cannot start VMs -- Error starting domain: unsupported configuration: host do...
Keywords:
Status: CLOSED DUPLICATE of bug 1133155
Alias: None
Product: Virtualization Tools
Classification: Community
Component: virt-manager
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Cole Robinson
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-07-16 15:38 UTC by Greg Sheremeta
Modified: 2015-09-10 15:44 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-09-04 08:25:16 UTC
Embargoed:


Attachments (Terms of Use)

Description Greg Sheremeta 2015-07-16 15:38:34 UTC
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

Comment 1 Greg Sheremeta 2015-07-16 15:40:58 UTC
Could be related to bug 1133155

Comment 2 Dennis Jacobfeuerborn 2015-08-12 13:39:49 UTC
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.

Comment 3 Pavel Hrdina 2015-09-04 08:25:16 UTC
It's fixed in v1.2.0.

*** This bug has been marked as a duplicate of bug 1133155 ***

Comment 4 Laurie Barry 2015-09-10 15:44:25 UTC
Can RH please let us know the schedule for this v1.2.0 release?

thx
Laurie


Note You need to log in before you can comment on or make changes to this bug.