Bug 705339

Summary:	virt-manager does not allow enabling x2apic flag for guest CPU
Product:	[Fedora] Fedora	Reporter:	Yaniv Kaul <ykaul>
Component:	virt-manager	Assignee:	Cole Robinson <crobinso>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	15	CC:	berrange, crobinso, dyuan, hbrock, jforbes, jkt, mzhan, rwu, virt-maint
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	virt-manager-0.9.1-1.fc15	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-02-14 08:56:19 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Yaniv Kaul 2011-05-17 12:21:54 UTC

Description of problem:
x2apic CPU flags should be unconditionally enabled (regardless of host CPU), and enabled by default (see http://fedoraproject.org/wiki/Features/Virtx2apic).
Regretfully, it can't be. I'm getting the following error;

Error starting domain: internal error guest CPU is not compatible with host CPU

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 45, in cb_wrapper
    callback(asyncjob, *args, **kwargs)
  File "/usr/share/virt-manager/virtManager/engine.py", line 959, in asyncfunc
    vm.startup()
  File "/usr/share/virt-manager/virtManager/domain.py", line 1128, in startup
    self._backend.create()
  File "/usr/lib64/python2.7/site-packages/libvirt.py", line 330, in create
    if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirtError: internal error guest CPU is not compatible with host CPU



Version-Release number of selected component (if applicable):
libvirt-client-0.8.8-4.fc15.x86_64
libvirt-python-0.8.8-4.fc15.x86_64
libvirt-0.8.8-4.fc15.x86_64
virt-manager-0.8.7-4.fc15.noarch

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Cole Robinson 2011-07-13 18:34:35 UTC

Thanks for the report, fixed upstream now:

http://git.fedorahosted.org/git?p=virt-manager.git;a=commit;h=cbaedd87bcfd44c3a8bdf99891c31ec9f41e3d0b

The CPU feature list now allows setting the actual feature 'policy' rather than hardcode 'require', which requires the host CPU to actually support the feature flag. For x2apic you'll want to select the 'force' policy

Comment 2 Fedora Update System 2012-02-01 18:23:58 UTC

virt-manager-0.9.1-1.fc15 has been submitted as an update for Fedora 15.
https://admin.fedoraproject.org/updates/virt-manager-0.9.1-1.fc15

Comment 3 Fedora Update System 2012-02-02 17:23:24 UTC

Package virt-manager-0.9.1-1.fc15:
* should fix your issue,
* was pushed to the Fedora 15 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing virt-manager-0.9.1-1.fc15'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-1173/virt-manager-0.9.1-1.fc15
then log in and leave karma (feedback).

Comment 4 Fedora Update System 2012-02-14 08:56:19 UTC

virt-manager-0.9.1-1.fc15 has been pushed to the Fedora 15 stable repository.  If problems still persist, please make note of it in this bug report.