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 1888750 - Provide simple boolean hyperv=on option with reasonable defaults (libvirt)
Summary: Provide simple boolean hyperv=on option with reasonable defaults (libvirt)
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: libvirt
Version: 9.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Tim Wiederhake
QA Contact: Luyao Huang
URL:
Whiteboard:
Depends On: 1877467
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-10-15 16:47 UTC by Eduardo Habkost
Modified: 2022-09-05 15:06 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-09-05 15:06:04 UTC
Type: Feature Request
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Eduardo Habkost 2020-10-15 16:47:58 UTC
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.

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

Comment 5 Jaroslav Suchanek 2022-09-05 14:04:32 UTC
Vitaly, since the qemu bug 1877467 is closed as wontfix, is there any sense in keeping the libvirt part open? Thanks.

Comment 6 Vitaly Kuznetsov 2022-09-05 14:36:19 UTC
(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.

Comment 7 Jaroslav Suchanek 2022-09-05 15:06:04 UTC
(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.


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