Chapter 19. Correcting over-reporting of virtualized RHEL

So that subscription watch can accurately report Red Hat Enterprise Linux in virtualized environments such as virtual data center (VDC) subscriptions, the Satellite inventory upload plugin and the virt-who tool must be correctly configured.

Host-guest mappings must be present in the data that subscription watch analyzes to accurately report virtualized RHEL usage. The Satellite inventory upload plugin and the virt-who tool gather these mappings for subscription watch.

If these tools are not used, virtualized usage data cannot be correctly calculated. In that type of scenario, guests are counted, not ignored. Each guest is counted as an individual virtual machine, leading to a rapid escalation of virtualized socket count and unusual deployment over capacity. When multiplied over numerous VDC subscriptions, all running multiple guests, subscription watch could easily show RHEL overdeployment that significantly exceeds your subscription threshold.

The following example contains an isolated usage and utilization graph view from the subscription watch interface. It shows a substantial drop in the reporting of virtualized usage after the correct configuration of the Satellite inventory upload plugin and virt-who. Throughout the time period displayed, the subscription threshold remains constant, at 904 sockets. Before correction, total RHEL usage is reported as approximately 2,250 sockets. This count far exceeds the subscription threshold. After correction, virtualized usage is considerably reduced, with total RHEL usage at 768 sockets. This count falls below the subscription threshold of 904 sockets.

Figure 19.1. Corrected virtualized RHEL with virt-who and Satellite data

Corrected virtualized RHEL with virt-who and Satellite data

Procedure

To correct over-reporting of virtualized RHEL usage in subscription watch, make sure that you have completed the following steps:

  1. Review your RHEL subscription profile in Red Hat Satellite and determine which subscriptions require virt-who.
  2. Confirm that the virt-who tool is deployed on your hypervisors so that host-guest mappings can be communicated to Satellite. For more information, see the virtualization documentation that is appropriate for your version (for example, Configuring Virtual Machine Subscriptions in Red Hat Satellite) from the Product Documentation for Red Hat Satellite page.

    Note

    If you are also using simple content access, the workflows for some of the subscription management tools such as virt-who are altered. In addition to reviewing the information in the Satellite documentation, see also the information in the Simple Content Access article.

  3. Make sure that the Satellite inventory upload plugin is installed and configured to supply data to subscription watch. If needed, review the information in the "Installing the Satellite inventory upload plugin" topic in this guide for additional information.