Red Hat Virtualization Agent (virt-who) Configuration Helper

Updated -

The virt-who daemon retrieves host-guest mapping information from one or more hypervisor management platforms. It can be run on one or more Red Hat Enterprise Linux systems and has two major functions:

  • Retrieve the mapping information of which virtual guest a hypervisor is running on in one of two ways:

    • By running locally on the hypervisor (RHEL+KVM, RHEL-OSP, or RHEL-H)
    • By using the hypervisor's management platform (RHEV with 2013 subs or RHEV-H, vSphere, Hyper-V)
  • Report the host-guest mapping to a subscription manager (Satellite 6, SAM or Red Hat Subscription Management (RHSM)) at a defined interval. The default interval value is 3600 seconds (one hour).

virt-who is required when working with any hypervisor if your subscription name includes the words "Virtual Datacenters", "4 Guests", or "Unlimited Guests". This app helps users configure virt-who.

When started, the app requests information about your virt-who usage and generates a configuration file based on the answers. It also provides instructions for updating your virt-who configuration.

The virt-who app reports to the following servers:

  • Satellite 6
  • Red Hat Customer Portal

The virt-who app retrieves host-guest mapping information from the following:

  • VMware vSphere/vCenter (esx)
  • Red Hat Virtualization Hypervisor (rhevm)
  • Red Hat Enterprise Linux Hypervisor (vdsm)
  • Microsoft Hyper-V (hyperv)
  • XenServer (xen)
  • libvirt

Was this helpful?

We appreciate your feedback. Leave a comment if you would like to provide more detail.
It looks like we have some work to do. Leave a comment to let us know how we could improve.

Get notified when this content is updated



Subscriber exclusive content

An active Red Hat subscription is required to participate.

Log In

This is great! It helped with a confusing multi esxi environment with hundreds of esx and thousands of hosts. Great Work!!!!!! Thank you to whomever wrote this little tool!

Great .....but.... Did run into some problems running it agains a RHV Manager 4.1 When using 'type=rhevm' the helper outputs the rhevm server to be 'server=fqdn'. This doesn't seem to work. I get 'Virt backend 'rhv' fails with error: Unable to connect to RHEV-M server' Got it fixed by using 'server=fqdn:443/ovirt-engine'

Hi Stig, Thank you very much for reporting the issue.
The app provides an example and explanation next to the "Server" input field. I will add a placeholder to the input field so customers can be noticed what they should input. Thanks.

Our Satellite 6.2 server and clients are both VMware virtual machines. Where do I need to install virt-who package, Satellite client, Satellite server or install virt-who on both Satellite server and client?

How about an update to support Red Hat Satellite 6.3?

Hi Jerry,

Red Hat Satellite 6.3 introduces two new methods of configuring virt-who: with the Satellite web UI and the hammer tool. These methods replace the previous method of manually creating and editing configuration files. Each method has the same outcome, so use whichever you are most comfortable with to create the configuration. Manual modification of pre-existing virt-who configuration files is supported, but deprecated.

You can check the details here:

SAM is EOL 31 oct 2018.

Hi Tom,

Thanks for reaching out us. I will fix this issue as soon as possible.


Hi Tom,

The issue has been fixed. Thanks.


This application appears to support only configuration of virt-who for Satellite. Can this be used to configure virt-who when using the Customer Portal?

Hi Bram,

Thank you for reaching out us.

This application can be used to configure virt-who when using the Customer Portal.

In "Virt-who Configuration" page, you can set the option of "Where does your virt-who report to?" to "Red Hat Customer Portal".



Thank you. I see it now. I was confused by the fact that the note on the first page listed only satellite versions.

The application did help to resolve the configuration issue that was blocking me so thanks!

However the app does not officially support RHEL8 yet. And the configuration it generates includes the env parameter that has been deprecated.

But luckily the help text for the user account helped me realize that I should NOT escape the backslash after the domain.



Simple and straightforward