Bug 822613

Summary:	libvirt should use qemu "enforce" -cpu flag
Product:	Red Hat Enterprise Linux 6	Reporter:	Eduardo Habkost <ehabkost>
Component:	libvirt	Assignee:	Martin Kletzander <mkletzan>
Status:	CLOSED DUPLICATE	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.3	CC:	acathrow, dallan, dyasny, dyuan, mzhan, rwu, yupzhang
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	822148	Environment:
Last Closed:	2012-08-09 05:47:45 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	692374
Bug Blocks:

Description Eduardo Habkost 2012-05-17 15:41:21 UTC

Cloning bug for 6.4.

This depends on bug 692374, that is about making "-cpu enforce" work reliably.

+++ This bug was initially created as a clone of Bug #822148 +++

Description of problem:
To make sure libvirt is always getting exactly the CPU flags it asked qemu for, it has to use "-cpu <model>,enforce", so qemu won't start if the requested flags can't be exposed.

This may be a problem in case users have existing VMs that are working perfectly for them, but would fail to start if "enforce" is used. Maybe the new behavior could be enabled only for new machine-types?