+++ This bug is a downstream clone. The original bug is: +++ +++ bug 1421746 +++ ====================================================================== Description of problem: ydary@: There is tech-preview support of nested in RHEL7 we should probably provide this hook as tech-preview as well. ~~~ It did not reach any official EL7 channel: - rpm search in customer portal https://rhn.redhat.com/rhn/channels/software/Search.do - my 4.0-beta hosts: [root@slot-2 ~]# yum repolist -v | grep -i baseurl Repo-baseurl : http://pulp-read.dist.prod.ext.phx2.redhat.com/content/dist/rhel/server/7/7Server/x86_64/rhv-mgmt-agent/4/os/ Repo-baseurl : http://pulp-read.dist.prod.ext.phx2.redhat.com/content/beta/rhel/server/7/x86_64/rhv-mgmt-agent/4/os/ Repo-baseurl : http://pulp-read.dist.prod.ext.phx2.redhat.com/content/dist/rhel/server/7/7Server/x86_64/os/ [root@slot-2 ~]# yum search vdsm-hook Loaded plugins: product-id, search-disabled-repos ============================================================================================== N/S matched: vdsm-hook ============================================================================================== vdsm-hook-ethtool-options.noarch : Allow setting custom ethtool options for vdsm controlled nics vdsm-hook-fcoe.noarch : Hook to enable FCoE support vdsm-hook-macspoof.noarch : Disables MAC spoofing filtering vdsm-hook-openstacknet.noarch : OpenStack Network vNICs support for VDSM vdsm-hook-vhostmd.noarch : VDSM hook set for interaction with vhostmd vdsm-hook-vmfex-dev.noarch : VM-FEX vNIC support for VDSM Name and summary matches only, use "search all" for everything. ~~~ Version-Release number of selected component (if applicable): 4.0-beta (Originally by Jiri Belka)
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. (Originally by Jiri Belka)
Changing to RFE, it's not missing, it was intentionally left out. (Originally by michal.skrivanek)
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-2017:2750