Bug 1614615 - "How to enable nested virtualization in KVM" page incorrectly describes sysfs nested parameter
Summary: "How to enable nested virtualization in KVM" page incorrectly describes sysfs...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora Documentation
Classification: Retired
Component: virtualization-guide
Version: devel
Hardware: Unspecified
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Petr Bokoc
QA Contact: Fedora Docs QA
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-08-10 04:11 UTC by Cel Skeggs
Modified: 2019-11-07 15:30 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-11-07 15:30:07 UTC
Embargoed:


Attachments (Terms of Use)

Description Cel Skeggs 2018-08-10 04:11:03 UTC
Description of problem:

The documentation at https://docs.fedoraproject.org/en-US/quick-docs/using-nested-virtualization-in-kvm/index.html states that /sys/module/kvm_intel/parameters/nested reports whether or not nested virtualization is supported. This is incorrect; it reports whether or not nested virtualization is enabled on the kvm_intel or kvm_amd kernel module.

How reproducible:

always.

Steps to Reproduce:

1) use an intel system that supports virtualization
2) load the kvm_intel module normally
3) cat /sys/module/kvm_intel/parameters/nested
4) unlock kvm_intel
5) load kvm_intel with nested=Y
6) cat /sys/module/kvm_intel/parameters/nested

Actual results:

The first 'cat' command displays 'N'. The second 'cat' command display 'Y'. The documentation says that 'N' as a result of the first 'cat' command implies that nested virtualization is not supported, but the second 'cat' command demonstrates that it is.

Expected results:

The documentation should correctly describe that, if the first 'cat' command produces 'N', it means that nested virtualization is disabled, not that nested virtualization is not supported.

Comment 1 Petr Bokoc 2019-11-07 15:30:07 UTC
I'm closing this bug as part of a Bugzilla cleanup effort. The most likely reason is that the bug has been opened either against a component we no longer publish, or against Release Notes for an EOL release.


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