Red Hat Bugzilla – Bug 1021742
Docs are unclear about using virt-who on RHEL based Hypervisors
Last modified: 2013-11-01 11:59:54 EDT
Description of problem:
In the newest release of documentation for SAM 1.3, the documentation is tremendously unclear about the usage of virt-who on RHEL based hypervisors
Version-Release number of selected component (if applicable):
Problematic Section: 7.1
Text in question:
"The hypervisor is registered first with Subscription Asset Manager, and then a related process on the system scans for any guests and submits the discovered UUIDs to the subscription service. For VMWare ESX hypervisors, this process is virt-who. For Red Hat Enterprise Linux hypervisors such as Xen and KVM, this is done through the libvirt process when the rhn-virtualization-host command is run."
Suggestion for improvement:
In the previous docs for 1.2, the following section goes into greater detail about using SAM in a virtualized environment and the role of virt-who on RHEL based Hypervisors:
The current docs should reflect this importance as well.
Could I get some clarification on why this was closed? The 'rhn-virtualization-host' package is only available for clients that subscribe to the RHN Tools channel. Which isn't an available repository when subscribed via RHSM.
[root@sat-montana ~]# yum repolist all | grep -i tool
This system is receiving updates from Red Hat Subscription Management.
This system is not registered with RHN Classic or RHN Satellite.
You can use rhn_register to register.
RHN Satellite or RHN Classic support will be disabled.
rhel-6-server-cf-tools-1-beta-debug-rpms Red Hat CloudForms disabled
rhel-6-server-cf-tools-1-beta-rpms Red Hat CloudForms disabled
rhel-6-server-cf-tools-1-beta-source-rpms Red Hat CloudForms disabled
rhel-6-server-cf-tools-1-debug-rpms Red Hat CloudForms disabled
rhel-6-server-cf-tools-1-rpms Red Hat CloudForms enabled: 31
rhel-6-server-cf-tools-1-source-rpms Red Hat CloudForms disabled
So RHSM, and SAM guests, could not use that package.