How to configure virt-who in VDSM mode to work with RHEL-H or RHV-H?
Environment
- Red Hat Enterprise Virtualization 3.5, 3.6
- Red Hat Enterprise Linux 6.5+, 7.x as hypervisor (RHEL-H)
- Red Hat Virtualization 4.x
- Red Hat Enterprise Linux 7.x as hypervisor (RHEL-H)
- Red Hat Enterprise Virtualization Host as hypervisor (RHVH)
- Subscription
- Red Hat Enterprise Linux for Virtual Datacenters
- Red Hat Enterprise Linux with Smart Virtualization and Management
- Red Hat Satellite 6.1+
virt-who>=0.12-10
Issue
- How to install
virt-whoto work with RHEV 3.6 or earlier and RHEL-H (NOT RHEV-H)? - How to install
virt-whoto work with RHV 4.x and RHEL-H or RHV-H? - How to use single Red Hat Enterprise Linux Server (Unlimited Guests) for RHEL-H and for hypervisor profile?
- How to configure
virt-whoin the VDSM mode to avoid duplicate profiles of RHVH/RHEL-H on the Satellite server? - How to install and configure
virt-whoto subscribe both RHV-H 4.X and guests systems running underneath it ?
Resolution
Instructions for RHEL-H (RHEV 3.6 and earlier)
- See Configuring virt-who to Connect to a Red Hat Enterprise Linux Hypervisor for more information.
Instructions for RHVH 4.1
-
As RHVH is a read-write filesystem, RPM packages can be directly installed on it. Install consumer RPM (http://satellite.example.com/pub/katello-ca-consumer-latest.noarch.rpm) and register it with Red Hat Satellite 6 server.
-
Attach Red Hat Enterprise Linux Server (Unlimited Guests) or equivalent subscription which provides 1 Physical and Unlimited Guest subscription to the hypervisor profile.
-
By default,
virt-whois installed on RHVH 4.1 hypervisor, so directly follow the instructions for configuring listed below# rpm -qa |grep virt-who virt-who-0.12-10.el6.noarch -
Edit the
virt-whoconfiguration file and enable only the below parameters.# cat /etc/sysconfig/virt-who |grep -v ^# VIRTWHO_BACKGROUND=1 VIRTWHO_DEBUG=1 VIRTWHO_INTERVAL=15 <-- For test only! (optional, default value is 3600 (seconds) ) VIRTWHO_SATELLITE6=1 -
Create a new configuration file inside
/etc/virt-who.d/# cat /etc/virt-who.d/rhv.conf [FQDN of the hypervisor] type=vdsm hypervisor_id=hostname -
After completing the above steps, restart the
virt-whoservice.# systemctl restart virt-who -
Try to register guests created on the hypervisor and confirm whether they are using a subscription attached to the hypervisor or not.
# rpm -Uvh install http://satellite.example.com/pub/katello-ca-consumer-latest.noarch.rpm # subscription-manager register --org="Organization" --auto-attach
Instructions for RHVH 4.4 on RHEL 8.2
-
The support for
vdsmmode configuration has been removed from thevirt-whopackage that ships with RHVH 4.4 i.e.virt-who-0.27.6-1.el8.noarch. -
In this scenario, to achieve the desired outcome, all the steps for configuring virt-who should be the same as RHVH 4.1, except for one small change in the configuration file.
-
Ensure that the virt-who configuration looks as displayed below i.e. no specific
typeset so that It can use the default type aslibvirt.# cat /etc/virt-who.d/rhv.conf [FQDN of the hypervisor] hypervisor_id=hostname
-
For more KB articles/solutions related to Virt-who and Virtual Datacenter (VDC) Subscriptions Issues, please refer to the Consolidated Troubleshooting Article for Virt-who and Virtual Datacenter (VDC) Subscriptions Issues
This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.