Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

The configuration of virt-who for RHEV is dependent on which type of hypervisor that is used:

- RHEV-H - As this hypervisor cannot be registered (to Satellite), rhevm mode is ideal here, as the hypervisor's Operating System never needs content (and thus won't need a subscription attached). This is effectively just like esx mode in virt-who. (One system polls the hypervisor management platform and gets host/guest mapping for ALL hypervisors)

- RVH-H and RHEL-Based Hypervisors - As these hypervisors can be registered (to Satellite) via subscription-manager, configuring virt-who in libvirt mode (on *each* hypervisor) makes the most sense here.

The virtual instance guide is unclear as to which configuration to use and why.

Assigning to Russell for review.