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.
Feature:
(Description from Paolo)
> After the "modprobe nested=1" it would be useful to explain that it only
> enables nesting until next reboot. Enable it forever requires adding
> something like
>
> options kvm_intel nested=1
> options kvm_amd nested=1
>
> to /etc/modprobe.d/kvm.conf (can use one file for both Intel and AMD).
>
> We probably should distribute such a file (with the options commented
> out) as part of the qemu-kvm package
Benefit:
Customers trying nested KVM (tech preview) will have an example of how to enable nested permanently.
Comment 1Miroslav Rezanina
2016-06-28 12:59:47 UTC
Verified this bug with qemu-kvm-rhev-2.6.0-22.el7.x86_64
1.Enable nested via kvm.conf
# cat /etc/modprobe.d/kvm.conf
# Setting modprobe kvm_intel/kvm_amd nested = 1
# only enables Nested Virtualization until the next reboot or
# module reload. Uncomment the option applicable
# to your system below to enable the feature permanently.
#
# User changes in this file are preserved across upgrades.
#
# For Intel
options kvm_intel nested=1
#
# For AMD
#options kvm_amd nested=1
2. reboot host
3. confirm nested if it is enabled
# cat /sys/module/kvm_intel/parameters/nested
Y
For AMD machine. It is the same result with Intel machine.
So, Base on this testing result. This bug is fixed.
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, 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://rhn.redhat.com/errata/RHBA-2016-2673.html
Feature: (Description from Paolo) > After the "modprobe nested=1" it would be useful to explain that it only > enables nesting until next reboot. Enable it forever requires adding > something like > > options kvm_intel nested=1 > options kvm_amd nested=1 > > to /etc/modprobe.d/kvm.conf (can use one file for both Intel and AMD). > > We probably should distribute such a file (with the options commented > out) as part of the qemu-kvm package Benefit: Customers trying nested KVM (tech preview) will have an example of how to enable nested permanently.