Chapter 5. Installing the Red Hat Virtualization Manager

5.1. Manually installing the RHV-M Appliance

When you deploy the self-hosted engine, the following sequence of events takes place:

  1. The installer installs the RHV-M Appliance to the deployment host.
  2. The appliance installs the Manager virtual machine.
  3. The appliance installs the Manager on the Manager virtual machine.

However, you can install the appliance manually on the deployment host beforehand if you need to. The appliance is large and network connectivity issues might cause the appliance installation to take a long time, or possibly fail.


  1. On Red Hat Enterprise Linux hosts:

    1. Reset the virt module:

      # dnf module reset virt

      If this module is already enabled in the Advanced Virtualization stream, this step is not necessary, but it has no negative impact.

      You can see the value of the stream by entering:

      # dnf module list virt
    2. Enable the virt module in the Advanced Virtualization stream with the following command:

      • For RHV 4.4.2:

        # dnf module enable virt:8.2
      • For RHV 4.4.3 to 4.4.5:

        # dnf module enable virt:8.3
      • For RHV 4.4.6 or later:

        # dnf module enable virt:av

        Starting with RHEL 8.4, only one Advanced Virtualization stream is used, rhel:av.

  2. Synchronize installed packages to update them to the latest available versions:

    # dnf distro-sync --nobest
  3. Install the RHV-M Appliance to the host manually:

    # dnf install rhvm-appliance

Now, when you deploy the self-hosted engine, the installer detects that the appliance is already installed.

5.2. Enabling and configuring the firewall

firewalld must be installed and running before you run the self-hosted deployment script. You must also have an active zone with an interface configured.


  • firewalld is installed. hosted-engine-setup requires the firewalld package, so you do not need to do any additional steps.


  1. Start firewalld:

    # systemctl unmask firewalld
    # systemctl start firewalld

    To ensure firewalld starts automatically at system start, enter the following command as root:

    # systemctl enable firewalld
  2. Ensure that firewalld is running:

    # systemctl status firewalld
  3. Ensure that your management interface is in a firewall zone via

    # firewall-cmd --get-active-zones

Now you are ready to deploy the self-hosted engine.

5.3. Deploying the self-hosted engine using Cockpit


Using Cockpit to install the self-hosted engine is deprecated. Support for this installation method will be removed in a later release.

Deploy a self-hosted engine, using Cockpit to collect the details of your environment. Cockpit is enabled by default on Red Hat Virtualization Hosts. You can manually install Cockpit on Red Hat Enterprise Linux hosts.

You can customize the Manager virtual machine during deployment, either manually, by pausing the deployment, or using automation.

  • Selecting the Pause Host check-box pauses deployment after installing the Manager and adding the deployment host to the Manager. It also creates a lock file at /tmp with the suffix _he_setup_lock on the deployment host, enabling you to manually customize the virtual machine as needed. The deployment continues after you delete the lock file, or after 24 hours, whichever comes first.
  • Adding an Ansible playbook to either the enginevm_before_engine_setup hook or the enginevm_after_engine_setup hook automatically runs the playbook.


  • FQDNs prepared for your Manager and the deployment host. Forward and reverse lookup records must both be set in the DNS.
  • When using a block storage domain, either FCP or iSCSI, a single target LUN is the only supported setup for a self-hosted engine.
  • (Optional) If you want to customize the Manager virtual machine during deployment using automation, an Ansible playbook must be added. See Appendix B, Customizing the Manager virtual machine using automation during deployment.


  1. Log in to Cockpit at https://HostIPorFQDN:9090 and click VirtualizationHosted Engine.
  2. Click Start under the Hosted Engine option.
  3. Enter the details for the Manager virtual machine:

    1. Enter the Engine VM FQDN. This is the FQDN for the Manager virtual machine, not the base host.
    2. Enter a MAC Address for the Manager virtual machine, or accept a randomly generated one.
    3. Choose either DHCP or Static from the Network Configuration drop-down list.


      For IPv6, Red Hat Virtualization supports only static addressing.

      • If you choose DHCP, you must have a DHCP reservation for the Manager virtual machine so that its host name resolves to the address received from DHCP. Specify its MAC address in the MAC Address field.
      • If you choose Static, enter the following details:

        • VM IP Address - The IP address must belong to the same subnet as the host. For example, if the host is in, the Manager virtual machine’s IP must be in the same subnet range (
        • Gateway Address
        • DNS Servers
    4. Select the Bridge Interface from the drop-down list.
    5. Enter and confirm the virtual machine’s Root Password.
    6. Specify whether to allow Root SSH Access.
    7. Enter the Number of Virtual CPUs for the virtual machine.
    8. Enter the Memory Size (MiB). The available memory is displayed next to the input field.
  4. Optionally expand the Advanced fields:

    1. Enter a Root SSH Public Key to use for root access to the Manager virtual machine.
    2. Select or clear the Edit Hosts File check box to specify whether to add entries for the Manager virtual machine and the base host to the virtual machine’s /etc/hosts file. You must ensure that the host names are resolvable.
    3. Change the management Bridge Name, or accept the default ovirtmgmt.
    4. Enter the Gateway Address for the management bridge.
    5. Enter the Host FQDN of the first host to add to the Manager. This is the FQDN of the base host you are running the deployment on.
    6. Select the Pause Host check-box to create a lock file, which pauses the deployment after adding the deployment host to the Manager. Pausing the deployment enables you to customize the virtual machine as needed.
    7. Specify how to check network connectivity by selecting one of the following options from the Network Test pop-up menu: DNS, Ping, TCP, None.

      Checks the connection to the DNS server.
      Attempts to ping the gateway.
      Creates a TCP connection to a host and port combination. Specify a destination IP address and port. Once the connection is successfully created, the network is considered to be alive. Ensure that the given host is able to accept incoming TCP connections on the given port.
      The network is always considered connected.
  5. Click Next.
  6. Enter and confirm the Admin Portal Password for the admin@internal user.
  7. Configure event notifications:

    1. Enter the Server Name and Server Port Number of the SMTP server.
    2. Enter the Sender E-Mail Address.
    3. Enter the Recipient E-Mail Addresses.
  8. Click Next.
  9. Review the configuration of the Manager and its virtual machine. If the details are correct, click Prepare VM.

    The deployment script begins installing and configuring the Manager virtual machine.

  10. (Optional) If you selected Pause Host, the deployment pauses after adding the deployment host to the Manager and displays a message on the Prepare VM screen similar to Pause execution until /tmp/ansible.<id>_he_setup_lock is removed, delete it once you are ready to proceed.

    You can now log in from the deployment host to the Manager virtual machine to customize it. You can log in with either the FQDN or the IP address of the Manager. For example, if the FQDN of the Manager is

    $ ssh

    In the installation log, the IP address is in local_vm_ip. The installation log is the most recent instance of /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-ansible-bootstrap_local_vm*.

    1. Customize the Manager virtual machine as needed.
    2. When you are done, log in to the Administration Portal using a browser with the Manager FQDN and make sure that the host’s state is Up.
    3. Delete the lock file and the deployment script automatically continues, configuring the Manager virtual machine.
  11. When the virtual machine and Manager installation is complete, click Next.
  12. Select the Storage Type from the drop-down list, and enter the details for the self-hosted engine storage domain:

    • For NFS:

      1. Enter the full address and path to the storage in the Storage Connection field.
      2. If required, enter any Mount Options.
      3. Enter the Disk Size (GiB).
      4. Select the NFS Version from the drop-down list.
      5. Enter the Storage Domain Name.
    • For iSCSI:

      1. Enter the Portal IP Address, Portal Port, Portal Username, and Portal Password.
      2. Click Retrieve Target List and select a target. You can only select one iSCSI target during the deployment, but multipathing is supported to connect all portals of the same portal group.


        To specify more than one iSCSI target, you must enable multipathing before deploying the self-hosted engine. See Red Hat Enterprise Linux DM Multipath for details. There is also a Multipath Helper tool that generates a script to install and configure multipath with different options.

      3. Enter the Disk Size (GiB).
      4. Enter the Discovery Username and Discovery Password.
    • For Fibre Channel:

      1. Enter the LUN ID. The host bus adapters must be configured and connected, and the LUN must not contain any existing data. To reuse an existing LUN, see Reusing LUNs in the Administration Guide.
      2. Enter the Disk Size (GiB).
    • For Red Hat Gluster Storage:

      1. Enter the full address and path to the storage in the Storage Connection field.
      2. If required, enter any Mount Options.
      3. Enter the Disk Size (GiB).
  13. Click Next.
  14. Review the storage configuration. If the details are correct, click Finish Deployment.
  15. When the deployment is complete, click Close.

    One data center, cluster, host, storage domain, and the Manager virtual machine are already running. You can log in to the Administration Portal to add further resources.

  16. Optionally, add a directory server using the ovirt-engine-extension-aaa-ldap-setup interactive setup script so you can add additional users to the environment. For more information, see Configuring an External LDAP Provider in the Administration Guide.
  17. Optionally, deploy Grafana so you can monitor and display reports from your RHV environment. For more information, see Configuring Grafana in the Administration Guide.

The self-hosted engine’s status is displayed in Cockpit’s VirtualizationHosted Engine tab. The Manager virtual machine, the host running it, and the self-hosted engine storage domain are flagged with a gold crown in the Administration Portal.


Both the Manager’s I/O scheduler and the hypervisor that hosts the Manager reorder I/O requests. This double reordering might delay I/O requests to the storage layer, impacting performance.

Depending on your data center, you might improve performance by changing the I/O scheduler to none. For more information, see Available disk schedulers in Monitoring and managing system status and performance for RHEL.

The next step is to enable the Red Hat Virtualization Manager repositories.

5.4. Enabling the Red Hat Virtualization Manager Repositories

You need to log in and register the Manager machine with Red Hat Subscription Manager, attach the Red Hat Virtualization Manager subscription, and enable the Manager repositories.


  1. Register your system with the Content Delivery Network, entering your Customer Portal user name and password when prompted:

    # subscription-manager register

    If you are using an IPv6 network, use an IPv6 transition mechanism to access the Content Delivery Network and subscription manager.

  2. Find the Red Hat Virtualization Manager subscription pool and record the pool ID:

    # subscription-manager list --available
  3. Use the pool ID to attach the subscription to the system:

    # subscription-manager attach --pool=pool_id

    To view currently attached subscriptions:

    # subscription-manager list --consumed

    To list all enabled repositories:

    # dnf repolist
  4. Configure the repositories:

    # subscription-manager repos \
        --disable='*' \
        --enable=rhel-8-for-x86_64-baseos-rpms \
        --enable=rhel-8-for-x86_64-appstream-rpms \
        --enable=rhv-4.4-manager-for-rhel-8-x86_64-rpms \
        --enable=fast-datapath-for-rhel-8-x86_64-rpms \
  5. Enable the pki-deps module.

    # dnf module -y enable pki-deps
  6. Enable version 12 of the postgresql module.

    # dnf module -y enable postgresql:12
  7. Synchronize installed packages to update them to the latest available versions.

    # dnf distro-sync --nobest

    Additional resources

    For information on modules and module streams, see the following sections in Installing, managing, and removing user-space components

Log in to the Administration Portal, where you can add hosts and storage to the environment:

5.5. Connecting to the Administration Portal

Access the Administration Portal using a web browser.

  1. In a web browser, navigate to https://manager-fqdn/ovirt-engine, replacing manager-fqdn with the FQDN that you provided during installation.


    You can access the Administration Portal using alternate host names or IP addresses. To do so, you need to add a configuration file under /etc/ovirt-engine/engine.conf.d/. For example:

    # vi /etc/ovirt-engine/engine.conf.d/99-custom-sso-setup.conf

    The list of alternate host names needs to be separated by spaces. You can also add the IP address of the Manager to the list, but using IP addresses instead of DNS-resolvable host names is not recommended.

  2. Click Administration Portal. An SSO login page displays. SSO login enables you to log in to the Administration and VM Portal at the same time.
  3. Enter your User Name and Password. If you are logging in for the first time, use the user name admin along with the password that you specified during installation.
  4. Select the Domain to authenticate against. If you are logging in using the internal admin user name, select the internal domain.
  5. Click Log In.
  6. You can view the Administration Portal in multiple languages. The default selection is chosen based on the locale settings of your web browser. If you want to view the Administration Portal in a language other than the default, select your preferred language from the drop-down list on the welcome page.

To log out of the Red Hat Virtualization Administration Portal, click your user name in the header bar and click Sign Out. You are logged out of all portals and the Manager welcome screen displays.