Bug 1421746
| Summary: | [RFE] add nested virtualization hook vdsm-hook-nestedvt | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Jiri Belka <jbelka> | |
| Component: | vdsm | Assignee: | Michal Skrivanek <michal.skrivanek> | |
| Status: | CLOSED ERRATA | QA Contact: | Jiri Belka <jbelka> | |
| Severity: | medium | Docs Contact: | ||
| Priority: | medium | |||
| Version: | 4.1.0 | CC: | bcholler, eheftman, fgarciad, gveitmic, jcall, lsurette, lsvaty, michal.skrivanek, rbalakri, rheron, Rhev-m-bugs, rlondhe, srevivo, ycui, ykaul, ylavi | |
| Target Milestone: | ovirt-4.2.0 | Keywords: | FutureFeature, ZStream | |
| Target Release: | --- | Flags: | jbelka:
testing_plan_complete-
|
|
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Technology Preview | ||
| Doc Text: |
In this release, a new VDSM hook that configures nested virtualization, has been introduced as a Technology Preview. Support for nested virtualization was introduced in Red Hat Enterprise Linux 7 and it enables a virtual machine to serve as a host.
VDSM hooks are a means to insert code, commands, or scripts into a point in the lifecycle of a virtual machine or the VDSM daemon.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1481150 (view as bug list) | Environment: | ||
| Last Closed: | 2018-05-15 17:50:23 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | Virt | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1481150, 1513039 | |||
|
Description
Jiri Belka
2017-02-13 15:12:59 UTC
Event if it is tech preview, it's odd to have ability to configure Nested Virtualization in UI but to be forgotten to provide required rpm for customers. Changing to RFE, it's not missing, it was intentionally left out. other than the doc text we should likely describe how exactly it is installed and used. should be: yum install vdsm-hook-nestedvt enable nested in Edit Host -> Kernel -> Nested Virtualization reboot host now you can use VMs as virtualization hosts (In reply to Michal Skrivanek from comment #13) > other than the doc text we should likely describe how exactly it is > installed and used. > should be: > yum install vdsm-hook-nestedvt > enable nested in Edit Host -> Kernel -> Nested Virtualization > reboot host > now you can use VMs as virtualization hosts Is there a feature page? And if not what is the impact on the rest of the system if a VM is used as a virtualization host? Why is the feature needed? Can any VM become a virtualization host? Is the hook installed automatically on new systems? Can Nested Virtualization be enabled when creating Hosts as well as Editing? Is something else in the UI disabled when this is selected? Or does something need to be selected to activate this? Thanks Emma ok, installable, virt-host can host another vms vdsm-4.20.6-1.el7ev.x86_64 vdsm-hook-nestedvt-4.20.6-1.el7ev.noarch (In reply to Emma Heftman from comment #14) > Is there a feature page? nope, it's there for quite some time, only now enabled d/s > And if not what is the impact on the rest of the system if a VM is used as a > virtualization host? there are no guarantees on performance of that nested host. Otherwise there should be no impact on the L0 host, it's "just a VM" from its perspective > Why is the feature needed? testing,demos mostly, I suppose > Can any VM become a virtualization host? yes, as long as the L0 has nested support enabled. > Is the hook installed automatically on new systems? it's not automatically installed, it's just available for installation now as a vdsm hook > Can Nested Virtualization be enabled when creating Hosts as well as Editing? yes. Though it requires the hook installation step, and a reboot of the host to apply the kernel parameter. > Is something else in the UI disabled when this is selected? Or does > something need to be selected to activate this? nope. Just some of the host hw reporting is not accurate/real INFO: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason: [No relevant external trackers attached] For more info please contact: rhv-devops INFO: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason: [No relevant external trackers attached] For more info please contact: rhv-devops 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://access.redhat.com/errata/RHEA-2018:1489 BZ<2>Jira Resync |