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.

Copying BZ for libvirt, as we need libvirt to support the new boolean flag once we implement it.

This bug was initially created as a copy of Bug #1877467


The set of available hyperv options depend on the host kernel, but this doesn't mean we can't provide a reasonable default set of hyperv features with a simple hyperv=on option.

The default set of hyperv features can depend on the machine type, so new upstream machine types can start enabling newer features, and downstream we can define the default set of hyperv features by just adding compat properties to the rhel machine types.

This way, we'll be able to provide a more reasonable interface for enabling hyperv features (just a boolean option) instead of the complex hyperv flag configuration interface we have today.

Bulk update: Move RHEL-AV bugs to RHEL9. If necessary to resolve in RHEL8, then clone to the current RHEL8 release.

Vitaly, since the qemu bug 1877467 is closed as wontfix, is there any sense in keeping the libvirt part open? Thanks.

(In reply to Jaroslav Suchanek from comment #5)
> Vitaly, since the qemu bug 1877467 is closed as wontfix, is there any sense
> in keeping the libvirt part open? Thanks.

No, I don't think so. Without a decision on how to do this feature in QEMU
(in a useful way), I don't think there's anything libvirt could do.

(In reply to Vitaly Kuznetsov from comment #6)
> (In reply to Jaroslav Suchanek from comment #5)
> > Vitaly, since the qemu bug 1877467 is closed as wontfix, is there any sense
> > in keeping the libvirt part open? Thanks.
> 
> No, I don't think so. Without a decision on how to do this feature in QEMU
> (in a useful way), I don't think there's anything libvirt could do.

Fine. Lets close it accordingly. It can be reopened if needed. Thanks.