Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1096769

Summary:	[RFE] RHEV: Permit exposing "hv_relaxed" to RHEV Virtual Machines
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Evgheni Dereveanchin <ederevea>
Component:	ovirt-engine-webadmin-portal	Assignee:	Nobody <nobody>
Status:	CLOSED DUPLICATE	QA Contact:	Pavel Stehlik <pstehlik>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.3.0	CC:	acathrow, asegundo, dfediuck, ecohen, ederevea, iheim, nobody, Rhev-m-bugs, sherold, yeylon
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	virt
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-05-14 19:56:16 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:

Description Evgheni Dereveanchin 2014-05-12 12:05:48 UTC

Description of problem:

There is no possibility to present CPU flags to VMs (specifically "hv_relaxed" which Windows 7/2012 VMs use to disable timers and thus avoid BSoD)

Version-Release number of selected component (if applicable):
RHEV 3.3

Requested enhancement:
 Ability to pass hv_relaxed CPU flag to VM from the Administrator Portal in the VM settings page

Comment 2 Doron Fediuck 2014-05-13 05:22:33 UTC

RHEV supports qemu's flags passthrough using -cpu host, which
should resolve this issue.

Can you please verify using "Use Host CPU" in the host side-tab of
the edit VM dialog?

Comment 3 Evgheni Dereveanchin 2014-05-13 07:37:08 UTC

hv_relaxed is a virtual CPU flag, it is not present on the actual physical CPU. It is added just to "Enlighten" a Windoes VM that it is a guest. QEMU supports that flag since RHEL 6.4 as a result of BZ#801196.

Comment 6 Itamar Heim 2014-05-14 19:56:16 UTC


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