Red Hat Summit Red Hat SummitSuporteConsoleDesenvolvedoresComeçar um testeContato

Este conteúdo não está disponível no idioma selecionado.

Chapter 4. Configuring virt-who for Nutanix AHV

You create a virt-who configuration for Nutanix AHV by using the Satellite web UI or the CLI on Satellite Server.

Then, you deploy the generated script or Hammer command on the Satellite Server, Capsule Server, or on a dedicated Red Hat Enterprise Linux server.

4.1. Creating a virt-who configuration by using the Satellite web UI
Copiar o link

You can create a virt-who configuration for Nutanix AHV by using the Satellite web UI.

The virt-who configuration creates a virt_who_reporter_1 user with the Virt-who Reporter role, which provides minimal permissions for virt-who reporting to Satellite Server. This user cannot be manually configured or used to log in to Satellite Server.

Local configuration values are stored in the /etc/virt-who.d/conf_name.conf file. These values apply only to the hypervisor.

Global configuration values are stored in the /etc/sysconfig/virt-who file These values, which include Interval, Enable debugging output, HTTP Proxy, and Ignore Proxy, apply to all virt-who configurations on the same server. Redeploying a virt-who configuration on the same server overwrites these values.

Prerequisites

Procedure

  1. In the Satellite web UI, navigate to Infrastructure > Virt-who Configurations.
  2. Click Create Config.

  3. Complete the following fields:

    • Name: Configuration name.
    • Hypervisor Type: Select Nutanix AHV (ahv).
    • Interval: Virtual machine information reporting interval.
    • Satellite Server FQDN.
    • Hypervisor ID: Select Hostname or UUID.

  4. Optional: Filtering. Select one of the following options for querying hypervisors:

    • Unlimited (default): All hypervisors are queried.

    • Whitelist: Specific hypervisors are included.

      • Filter hosts: Comma-separated list of included hypervisors.

    • Blacklist: Specific hypervisors are excluded.

      • Exclude hosts: Comma-separated list of excluded hypervisors.

    In the Filtering fields, specify the host name or UUID according to the hypervisor ID you selected. Follow these guidelines for host names:

    • You can use wildcards, regular expressions, and special characters in the host name.
    • If you use regular expressions, you must escape the backslashes.
    • If you use special characters, you must enclose the host name in quotation marks.

    For more information, see Using the "Filter Host Parents" and "Exclude Host Parents" Attributes with VMware Clusters in the Red Hat Knowledgebase.

  5. You can configure the following logging and proxy options:

    • Enable debugging output: Enables debug logging for virt-who.

    • HTTP Proxy. Example: http://proxy.example.com:3128.

      To use no proxy, leave this field blank; this has the same result as entering * in the Ignore Proxy field.

    • Ignore Proxy: Comma-separated list of host names, IP addresses, or domains to bypass existing proxy settings.
  6. Select Prism Central or Prism Element from the Prism Flavor list.
  7. Optional: Enable AHV Debug: Enables AHV internal debugging. This option provides additional AHV information when you enable both debugging options.
  8. Click Submit.

4.2. Creating a virt-who configuration by using Hammer CLI
Copiar o link

You can create a virt-who configuration for Nutanix AHV by using Hammer CLI.

The virt-who configuration creates a virt_who_reporter_1 user with the Virt-who Reporter role, which provides minimal permissions for virt-who reporting to Satellite Server. This user cannot be manually configured or used to log in to Satellite Server.

Local configuration values are stored in the /etc/virt-who.d/conf_name.conf file. These values apply only to the hypervisor.

Global configuration values are stored in the /etc/sysconfig/virt-who file These values, which include Interval, Enable debugging output, HTTP Proxy, and Ignore Proxy, apply to all virt-who configurations on the same server. Redeploying a virt-who configuration on the same server overwrites these values.

Prerequisites

Procedure

  • On Satellite Server, enter the hammer virt-who-config create command: 

    $ hammer virt-who-config create \
--name My_virt-who_Configuration \
--organizations "My_Organization" \
--interval 720 \
--filtering-mode none \
--hypervisor-id hostname \
--hypervisor-type ahv \
--hypervisor-server prism.example.com \
--hypervisor-username virt_who_user \
--satellite-url satellite.example.com

In this command, use the following options:

  • In --filtering-mode, specify none for no filtering of hypervisors for virt-who queries. Specify whitelist or blacklist to include or exclude hypervisors for virt-who queries.

  • In --hypervisor-id, specify hostname, uuid, or hwuuid for the hypervisor ID format.

    • You can use uuid to avoid duplication if you rename a hypervisor.

    • You can use hwuuid for configurations that apply to a virtualization manager instead of an individual hypervisor.

      Note

      You cannot change hwuuid to another option after virt-who starts running because this might cause duplicate entries in Subscription Manager.

  • In --hypervisor-server, specify the FQDN or IP address of the hypervisor.
  • In --hypervisor-username, specify the name of the virt-who user you created on the hypervisor.
  • Optionally, in the --proxy option, specify the proxy address and port, for example, --proxy '\http://proxy.example.com:3128'.
  • Optionally, in the --interval option, specify the virtual machine information reporting interval in minutes.

Example 4.1. Nutanix AHV virt-who configuration

type=ahv
hypervisor_id=hostname
prism_central=true
owner=Default_Organization
env=Library
server=prism.example.com
username=prism_user
encrypted_password=$cr_password
rhsm_hostname=satellite.example.com
rhsm_username=virt_who_reporter_1
rhsm_encrypted_password=$user_password
rhsm_prefix=/rhsm

4.3. Deploying a virt-who configuration on Satellite Server
Copiar o link

You deploy a virt-who configuration on Satellite Server to enable virtual machine subscription tracking. You download a virt-who configuration script from the Satellite web UI and then you run the script on Satellite Server.

Global configuration values apply to all virt-who configurations on this server and are overwritten if you deploy a new virt-who configuration.

Procedure

  1. In the Satellite web UI, navigate to Infrastructure > Virt-who Configurations.
  2. Click a virt-who configuration.
  3. Click the Deploy tab.
  4. Under Hammer command, click Copy to clipboard.
  5. Log in to Satellite Server, paste the Hammer command into your terminal, and then run the command.

4.4. Deploying a virt-who configuration on Capsule Server
Copiar o link

You deploy a virt-who configuration on Capsule Server to enable virtual machine subscription tracking. You download a virt-who configuration script from the Satellite web UI and then you run the script on Capsule Server.

Global configuration values apply to all virt-who configurations on this server and are overwritten if you deploy a new virt-who configuration.

Procedure

  1. In the Satellite web UI, navigate to Infrastructure > Virt-who Configurations.
  2. Click a virt-who configuration.
  3. Click the Deploy tab.
  4. Under Configuration script, click Download the script.

  5. Copy the script from Satellite Server to Capsule Server: 

    $ scp deploy_virt_who_config_1.sh root@capsule.example.com:

  6. Log in to Capsule Server and make the script executable: 

    $ chmod +x deploy_virt_who_config_1.sh

  7. Run the script: 

    $ sh deploy_virt_who_config_1.sh

  8. After the deployment is complete, delete the script: 

    $ rm deploy_virt_who_config_1.sh

You deploy a virt-who configuration on a dedicated Red Hat Enterprise Linux server to enable virtual machine subscription tracking. You download a virt-who configuration script from the Satellite web UI and then you run the script on the Red Hat Enterprise Linux server.

The server can be physical or virtual.

Global configuration values apply to all virt-who configurations on this server and are overwritten if you deploy a new virt-who configuration.

Prerequisites

Procedure

  1. Log in to the Red Hat Enterprise Linux server.

  2. Add a TCP port for communication between virt-who and Satellite Server to the runtime configuration: 

    $ firewall-cmd --add-port="443/tcp"

  3. Add a TCP port for communication between virt-who and Satellite Server to the permanent configuration: 

    $ firewall-cmd --add-port="443/tcp" --permanent
  4. In the Satellite web UI, navigate to Infrastructure > Virt-who Configurations.
  5. Click a virt-who configuration.
  6. Click the Deploy tab.
  7. Under Configuration script, click Download the script.

  8. Copy the script from Satellite Server to the Red Hat Enterprise Linux server: 

    $ scp deploy_virt_who_config_1.sh root@server.example.com:

  9. Log in to the Red Hat Enterprise Linux server and make the script executable: 

    $ chmod +x deploy_virt_who_config_1.sh

  10. Run the script: 

    $ sh deploy_virt_who_config_1.sh

  11. After the deployment is complete, delete the script: 

    $ rm deploy_virt_who_config_1.sh
Red Hat logoGithubredditYoutubeTwitter

Aprender

Experimente, compre e venda

Comunidades

Sobre a documentação da Red Hat

Ajudamos os usuários da Red Hat a inovar e atingir seus objetivos com nossos produtos e serviços com conteúdo em que podem confiar. Explore nossas atualizações recentes.

Tornando o open source mais inclusivo

A Red Hat está comprometida em substituir a linguagem problemática em nosso código, documentação e propriedades da web. Para mais detalhes veja o Blog da Red Hat.

Sobre a Red Hat

Fornecemos soluções robustas que facilitam o trabalho das empresas em plataformas e ambientes, desde o data center principal até a borda da rede.

Theme

© 2026 Red HatVoltar ao topo