Votre compte Red Hat vous permet d'accéder à votre profil, à vos préférences et aux services suivants en fonction de votre statut client :
Vous n'êtes pas encore inscrit ? Voici quelques bonnes raisons de le faire :
- Parcourez les articles de la base de connaissances, gérez les dossiers d'assistance et les abonnements, téléchargez des mises à jour et bien plus encore, le tout depuis un espace unique.
- Affichez la liste des utilisateurs de votre organisation et modifiez les informations, les préférences et les autorisations relatives à leur compte.
- Gérez vos certifications Red Hat, consultez l'historique de vos examens et téléchargez des logos et des documents relatifs à vos certifications.
Votre compte Red Hat vous permet d'accéder à votre profil, à vos préférences et à d'autres services en fonction de votre statut client.
Si vous utilisez un ordinateur public, déconnectez-vous de votre compte lorsque vous n'utilisez plus les services Red Hat afin de garantir votre sécurité.Déconnexion
If Red Hat Satellite is not part of your Red Hat Enterprise Linux (RHEL) management environment, you may still have the need to run virt-who to gather deployment information for RHEL VMs associated with your RHEL or Virtual Data Center (VDC) subscriptions when running in a virtualized environment.
If you have Simple Content Access (SCA) enabled on your customer portal, you would not need to attach a subscription to a RHEL VM. But with SCA enabled, you — as the consumer of Red Hat subscriptions — will need to track your subscription usage to be compliant with your Red Hat agreement, and virt-who can assist with providing data to link RHEL VMs to specific hypervisors.
In this tutorial we look at configuring virt-who to provide vSphere hypervisor host information when the RHEL VM is registered to the customer portal. We can see the hypervisor and RHEL VM information in the customer portal and on the Red Hat Hybrid Cloud Console.
For this tutorial I created a small RHEL VM (1 vCPU with 2 GB RAM) to host the virt-who daemon. This virt-who instance is gathering data from a 3 node EXSi cluster with local credentials.
Installing, configuring and enabling virt-who
I registered the system with an activation key to the Red Hat customer portal. Remember I have Simple Content Access (SCA) enabled on my Red Hat customer portal, so I won't be attaching a subscription to this RHEL instance after I register it.
# subscription-manager register --org=xxxxxxxxx --activationkey=your_key_here
When using SCA, I am not attaching a subscription to my RHEL VM. When you run subscription-manager status, you will see that SCA is enabled. To use specific content with your RHEL VM, you can enable any required content repositories.
# subscription-manager status +-------------------------------------------+ System Status Details +-------------------------------------------+ Overall Status: Disabled Content Access Mode is set to Simple Content Access. This host has access to content, regardless of subscription status. System Purpose Status: Disabled
I checked to make sure that the RHEL 8 repos are enabled on the VM. When creating the RHEL 8 VM from an ISO image on vSphere, the RHEL 8 repos are automatically enabled.
# subscription-manager repos --list-enabled +----------------------------------------------------------+ Available Repositories in /etc/yum.repos.d/redhat.repo +----------------------------------------------------------+ Repo ID: rhel-8-for-x86_64-appstream-rpms Repo Name: Red Hat Enterprise Linux 8 for x86_64 - AppStream (RPMs) Repo URL: https://cdn.redhat.com/content/dist/rhel8/$releasever/x86_64/appstream/os Enabled: 1 Repo ID: rhel-8-for-x86_64-baseos-rpms Repo Name: Red Hat Enterprise Linux 8 for x86_64 - BaseOS (RPMs) Repo URL: https://cdn.redhat.com/content/dist/rhel8/$releasever/x86_64/baseos/os Enabled: 1
Check to see if virt-who is installed.
# rpm -qa virt-who
If virt-who is not installed, let's install it.
# yum -y install virt-who ... Complete!
The virt-who installation creates a template configuration file that we can use to set up virt-who for our VMware cluster. The template configuration file is located under the /etc/virt-who.d/ directory.
We will create the virt-who.conf file. Before editing the file we need the organization id under which the RHEL VM is registered.
# subscription-manager identity system identity: 2278e9a5-...-2b605607f2ba name: virt-who.example.com org name: ####### org ID: #######
The vCenter user ID needs read-only access to all objects in the vCenter. See the troubleshooting section below if you need guidance in creating the vCenter user id for virt-who.
Now let's create and edit the virt-who.conf file in the /etc/virt-who.d/ directory. This configuration file is self-explanatory. The hypervisor_id setting is a default setting we need in the configuration file.
# vi virt-who.conf [vmware] type=esx server=vsca01.example.com firstname.lastname@example.org password=password owner=####### hypervisor_id=hostname
If you want to exclude EXSi hosts from virt-who reporting for a particular VMware cluster, add the filter hosts option to the virt-who.conf file. Use commas to separate host names. See the following example filter hosts line entry.
If you have more than one vCenter, simply create as many sections in the configuration file to match the number of vCenter clusters.
[vcenter01] type=esx server=vsca01.example.com email@example.com password=password owner=####### hypervisor_id=hostname [vcenter02] type=esx server=vsca02.example.com firstname.lastname@example.org password=password owner=####### hypervisor_id=hostname
Before starting virt-who you can manually test the configuration.
# virt-who --print
For an easier readout of the configuration test, try the following command.
# virt-who --print | jq
Let's start the virt-who daemon.
# systemctl start virt-who
Let's check the status of the virt-who daemon.
# systemctl status virt-who
Make virt-who startup automatically when the server is rebooted.
# systemctl enable virt-who Created symlink /etc/systemd/system/multi-user.target.wants/virt-who.service → /usr/lib/systemd/system/virt-who.service.
Let's encrypt the password contained in the virt-who.conf file.
To do that, run the virt-who-password command and supply the vCenter password.
# virt-who-password Password: Use following as value for encrypted_password key in the configuration file: 14809...98a885d4cecd
Change your virt-who.conf file to the following.
# vi virt-who.conf [vmware] type=esx server=vsca01.example.com email@example.com encrypted_password=14809...98a885d4cecd owner=####### hypervisor_id=hostname
You can test this new configuration using the same command above. Remember to restart the virt-who daemon.
# systemctl restart virt-who
Viewing the virt-who reporting in the Red Hat Customer Portal and the Red Hat Hybrid Cloud Console
Head over to the Red Hat customer portal and login.
In the Red Hat customer portal click on the "Subscriptions" link in the upper left-hand corner of the Red Hat customer portal landing page.
On the subscriptions page, click the "Systems" tab. On the systems page you will see the hypervisors that virt-who is aware of via the virt-who.conf file.
Click on a hypervisor link in the systems page to get to the "Details" information for a particular hypervisor.
From the systems page, if you choose a RHEL instance, you will also be able to see the hypervisor that the RHEL VM is running on in the RHEL VM's instance "Details" page.
Let's head over to the Red Hat Hybrid Cloud Console and login, then choose "Red Hat Enterprise Linux" from the side menu.
On the Red Hat Enterprise Linux page expand the "Subscriptions" option on the side menu and click the "All RHEL" link. Scroll down on the subscription page to Insights registered RHEL servers and VMware Hypervisors that are hosting RHEL VMs.
You can expand the "VMware Hypervisor" link to see what guest machines are running on a particular hypervisor. Note that when the VMware Hypervisor hostname first shows up in the All RHEL subscription section, it is listed as a UUID. We will change the UUID to the hypervisor name in the next steps.
To update the hypervisor name from the UUID to something more meaningful, click on the hypervisor link in the All RHEL page.
You will be taken to the inventory page of the hypervisor. On the inventory page, click the pencil icon next to the display name to change the display name to the hypervisor’s hostname.
A dialog box will open where you can edit the display name. After changing it, click the blue "Save" button. Repeat this step for the Ansible hostname.
Back on the inventory page, you will see the display name has been updated to the hypervisor’s hostname. The display name in the Subscriptions | All RHEL page will be updated after the next check in with the Red Hat Hybrid Cloud Console which typically happens within 24 hours.
Troubleshooting and additional notes
In this tutorial my vSphere Client version is 188.8.131.52000. I created the virt-who user id under the Administration - Single Sign-on - User and Groups menu. The user id "virt-who" is part of the vsphere.local domain. Under the Administration - Access Control - Global Permissions menu, I create a Read-only permission with virt-who as the user.
Test the virt-who VMware user id and password with a vSphere client.
Test virt-who VMware user id with the password unencrypted in the virt-who conf file. When the test is successful, encrypt the password and retest
If you test the virt-who command with the print option (or with any other command line options), make sure you are "running" as root (sudo or su).
Simple Content Access makes provisioning, migration and retirement of your RHEL VMs easier than ever. But you still want to know where those VMs are running to both optimize your RHEL environment and to ensure that you are staying within your Red Hat subscription entitlement. The Red Hat Hybrid Console along with virt-who are tools that can help you better manage your RHEL environment.
If you are not using Red Hat Insights in the Red Hat Hybrid Console, give it a try! Visit the Insights Getting Started page to learn more.
Please visit the Simple Content Access page for more information on enabling and using it.
About the author
Paul Lucas is a Chicagoland-based Red Hat Solutions Architect working with a variety of enterprise businesses. A 21 year technical sales veteran, Paul was previously a customer working at a benefits consulting firm, where he advised development teams on the use of Java and the then-emerging Java EE.