Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1168881

Summary: When running a KVM Windows guest, need to turn on all the "hv_*" flags
Product: Red Hat Enterprise Linux 7 Reporter: Giuseppe Scrivano <gscrivan>
Component: libosinfoAssignee: Fabiano FidĂȘncio <fidencio>
Status: CLOSED UPSTREAM QA Contact: Desktop QE <desktop-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.2CC: cfergeau, dyuan, gscrivan, juzhang, knoel, mclasen, mzhan, tpelka, tzheng, virt-bugs
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1083537 Environment:
Last Closed: 2019-01-03 15:58:27 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 Giuseppe Scrivano 2014-11-28 10:05:02 UTC
+++ This bug was initially created as a clone of Bug #1083537 +++

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

Description of problem:
As of RHEL7.0 QEMU and Libvirt support several Hyper-V Enlightenment features, that need to be explicitly turned on for Windows guests. It is forbidden to turn them on for RHEL5 guests.
The QEMU flags are: "hv_relaxed,hv_spinlocks=0x1fff,hv_vapic,hv_time"

Additional info:
hv_relaxed turns off an internal Windows watchdog, and by doing so avoids some high load BSODs
hv_relaxed is also supported in RHEL6 as of RHEL6.4
All the other flags are performance optimization flags, that can improve the performance by 10% to much more (in extreme cases of resources overcommit).

Libvirt related bugs:
RHEL7
 Bug 1056205 - new cpu's flags, to control hyper-v related features - hv-time
 Bug 784836 - new cpu's flags, to control hyper-v related features
RHEL6
 Bug 864606 - [RFE] Enable Hyper-V Enlightenment for Windows guests

Note: You might want to duplicate this BZ to other RHEL7 based versions of RHOS.

--- Additional comment from Giuseppe Scrivano on 2014-11-28 05:04:12 EST ---

I think that this OS information should go into libosinfo first, and virt-manager just uses it.  Probably this requires a new API for libosinfo. 

Cloning there...

Comment 4 Fabiano FidĂȘncio 2019-01-03 15:58:27 UTC
This bug report can be considered part of https://gitlab.com/libosinfo/libosinfo/issues/9 and the progress will be tracked there.

I'm closing this one as UPSTREAM. Please, feel free to re-open it or directly comment in the upstream issue.