A.4. Virt-who Troubleshooting Scenarios

Virt-who fails to connect to the virtualization platform

If virt-who fails to connect to the hypervisor or virtualization manager, check the Red Hat Subscription Manager log file /var/log/rhsm/rhsm.log. If you find the message No route to host, the hypervisor might be listening on the wrong port. In this case, modify the virt-who configuration and append the correct port number to the Hypervisor Server value.

You must redeploy the virt-who configuration after modifying it.

Virt-who fails to connect to the virtualization platform through an HTTP proxy on the local network

If virt-who cannot connect to the hypervisor or virtualization manager through an HTTP proxy, either configure the proxy to allow local traffic to pass through, or modify the virt-who configuration to use no proxy.

You must redeploy the virt-who configuration after modifying it.

Virt-who fails to report back the host-guest mapping to Red Hat Satellite server

Virt-who fails to report back the host-guest mapping to Red Hat Satellite server in the following circumstances.

  1. virt-who is configured and deployed on Red Hat Satellite server.
  2. The rhsm.conf file of Red Hat Satellite server is configured to use a proxy server to talk to subscription.rhsm.redhat.com and cdn.redhat.com.
  3. The no_proxy=* setting in /etc/sysconfig/virt-who is present but being ignored by subscription-manager, and virt-who attempts to connect back to Satellite server through a proxy server but fails.

In this case, add the following parameter to the /etc/rhsm/rhsm.conf file. 

no_proxy = satellite.example.com