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 1851249 - Support hv-passthrough mode
Summary: Support hv-passthrough mode
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: libvirt
Version: 9.0
Hardware: x86_64
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Tim Wiederhake
QA Contact: Luyao Huang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-06-25 22:05 UTC by Eduardo Habkost
Modified: 2024-04-24 02:06 UTC (History)
9 users (show)

Fixed In Version: libvirt-8.0.0-0rc1.1.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-05-17 12:45:05 UTC
Type: Feature Request
Target Upstream Version: 8.0.0
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2022:2390 0 None None None 2022-05-17 12:45:31 UTC

Description Eduardo Habkost 2020-06-25 22:05:25 UTC
QEMU supports a convenient CPU option for enabling all supported hyperv flags (hv-passthrough=on).

libvirt could support that flags, so management software could easily enable all supported hyperv flags out of the box when live migration support isn't required by the user.

Comment 1 Vitaly Kuznetsov 2020-06-26 14:32:27 UTC
Libvirt could also leverage hv-passthrough to figure out which Hyper-V enlightenments
are supported (for https://bugzilla.redhat.com/show_bug.cgi?id=1717611) the same way
it does with host CPU features (running QEMU with "-cpu host" and querying all supported
CPUIDs).

Comment 3 John Ferlan 2021-09-08 13:30:05 UTC
Bulk update: Move RHEL-AV bugs to RHEL9. If necessary to resolve in RHEL8, then clone to the current RHEL8 release.

Comment 5 Tim Wiederhake 2021-11-26 14:36:01 UTC
Proposed patch: https://listman.redhat.com/archives/libvir-list/2021-November/msg00861.html

Comment 12 Luyao Huang 2022-01-17 06:38:02 UTC
Verify this bug with libvirt-8.0.0-1.el9.x86_64:

1. prepare a guest which have hv-passthrough element:

# virsh dumpxml vm1
...
  <features>
    <acpi/>
    <apic/>
    <hyperv mode='passthrough'>
    </hyperv>
  </features>
...

2. start guest

# virsh start vm1
Domain 'vm1' started


3. check qemu command line and make sure that libvirt add hv-passthrough=on in qemu command line 

# ps aux|grep qemu
... -cpu Skylake-Client-IBRS,...,hv-passthrough=on ...

Comment 14 errata-xmlrpc 2022-05-17 12:45:05 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (new packages: libvirt), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:2390


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