7.5. Host Tasks

Procedure 7.1. Adding a Host to the Red Hat Virtualization Manager

1. From the Administration Portal, click the Hosts resource tab.
2. Click New.
3. Use the drop-down list to select the Data Center and Host Cluster for the new host.
4. Enter the Name and the Address of the new host. The standard SSH port, port 22, is auto-filled in the SSH Port field.
5. Select an authentication method to use for the Manager to access the host.
   • Enter the root user's password to use password authentication.
   • Alternatively, copy the key displayed in the SSH PublicKey field to /root/.ssh/authorized_keys on the host to use public key authentication.
6. Click the Advanced Parameters button to expand the advanced host settings.
   1. Optionally disable automatic firewall configuration.
   2. Optionally add a host SSH fingerprint to increase security. You can add it manually, or fetch it automatically.
7. Optionally configure Power Management, SPM, Console, Network Provider, and Kernel. See Section 7.5.4, “Explanation of Settings and Controls in the New Host and Edit Host Windows” for more information. Hosted Engine is used when deploying or undeploying a host for a self-hosted engine deployment.
8. Click OK.

Procedure 7.2. Adding a Satellite Host Provider Host

1. Click the Hosts resource tab to list the hosts in the results list.
2. Click New to open the New Host window.
3. Use the drop-down menu to select the Host Cluster for the new host.
4. Select the Foreman/Satellite check box to display the options for adding a Satellite host provider host and select the provider from which the host is to be added.
5. Select either Discovered Hosts or Provisioned Hosts.
   • Discovered Hosts (default option): Select the host, host group, and compute resources from the drop-down lists.
   • Provisioned Hosts: Select a host from the Providers Hosts drop-down list.
   Any details regarding the host that can be retrieved from the external provider are automatically set, and can be edited as desired.
6. Enter the Name, Address, and SSH Port (Provisioned Hosts only) of the new host.
7. Select an authentication method to use with the host.
   • Enter the root user's password to use password authentication.
   • Copy the key displayed in the SSH PublicKey field to /root/.ssh/authorized_hosts on the host to use public key authentication (Provisioned Hosts only).
8. You have now completed the mandatory steps to add a Red Hat Enterprise Linux host. Click the Advanced Parameters drop-down button to show the advanced host settings.
   1. Optionally disable automatic firewall configuration.
   2. Optionally add a host SSH fingerprint to increase security. You can add it manually, or fetch it automatically.
9. You can configure the Power Management, SPM, Console, and Network Provider using the applicable tabs now; however, as these are not fundamental to adding a Red Hat Enterprise Linux host, they are not covered in this procedure.
10. Click OK to add the host and close the window.

Procedure 7.3. Configuring Satellite Errata Management for a Host

1. Add the Satellite server as an external provider. See Section 12.2.1, “Adding a Red Hat Satellite Instance for Host Provisioning” for more information.
2. Associate the required host with the Satellite server.

   Note

   The host must be registered to the Satellite server and have the katello-agent package installed.

   For more information on how to configure a host registration see Configuring a Host for Registration in the Red Hat Satellite User Guide and for more information on how to register a host and install the katello-agent package see Registration in the Red Hat Satellite User Guide
   1. In the Hosts tab, select the host in the results list.
   2. Click Edit to open the Edit Host window.
   3. Check the Use Foreman/Satellite checkbox.
   4. Select the required Satellite server from the drop-down list.
   5. Click OK.

Procedure 7.4. Configuring Power Management Settings

1. In the Hosts tab, select the host in the results list.
2. Click Edit to open the Edit Host window.
3. Click the Power Management tab to display the Power Management settings.
4. Select the Enable Power Management check box to enable the fields.
5. Select the Kdump integration check box to prevent the host from fencing while performing a kernel crash dump.

   Important

   When you enable Kdump integration on an existing host, the host must be reinstalled for kdump to be configured. See Section 7.5.11, “Reinstalling Hosts”.
6. Optionally, select the Disable policy control of power management check box if you do not want your host's power management to be controlled by the Scheduling Policy of the host's cluster.
7. Click the plus (+) button to add a new power management device. The Edit fence agent window opens.
8. Enter the Address, User Name, and Password of the power management device into the appropriate fields.
9. Select the power management device Type from the drop-down list.
10. Enter the SSH Port number used by the power management device to communicate with the host.
11. Enter the Slot number used to identify the blade of the power management device.
12. Enter the Options for the power management device. Use a comma-separated list of 'key=value' entries.
13. Select the Secure check box to enable the power management device to connect securely to the host.
14. Click Test to ensure the settings are correct. Test Succeeded, Host Status is: on will display upon successful verification.
15. Click OK to close the Edit fence agent window.
16. In the Power Management tab, optionally expand the Advanced Parameters and use the up and down buttons to specify the order in which the Manager will search the host's cluster and dc (datacenter) for a fencing proxy.
17. Click OK.

Procedure 7.5. Configuring SPM settings

1. Click the Hosts resource tab, and select a host from the results list.
2. Click Edit to open the Edit Host window.
3. Click the SPM tab to display the SPM Priority settings.
4. Use the radio buttons to select the appropriate SPM priority for the host.
5. Click OK to save the settings and close the window.

Procedure 7.6. Placing a Host into Maintenance Mode

1. Click the Hosts resource tab, and select the desired host.
2. Click Maintenance to open the Maintenance Host(s) confirmation window.
3. Optionally, enter a Reason for moving the host into maintenance mode in the Maintenance Host(s) confirmation window. This allows you to provide an explanation for the maintenance, which will appear in the logs and when the host is activated again.

   Note

   The host maintenance Reason field will only appear if it has been enabled in the cluster settings. See Section 5.2.2.1, “General Cluster Settings Explained” for more information.
4. Click OK to initiate maintenance mode.

Procedure 7.7. Activating a Host from Maintenance Mode

1. Click the Hosts resources tab and select the host.
2. Click Activate.

Procedure 7.8. Removing a host

1. In the Administration Portal, click the Hosts resource tab and select the host in the results list.
2. Place the host into maintenance mode.
3. Click Remove to open the Remove Host(s) confirmation window.
4. Select the Force Remove check box if the host is part of a Red Hat Gluster Storage cluster and has volume bricks on it, or if the host is non-responsive.
5. Click OK.

Procedure 7.9. Reinstalling Red Hat Virtualization Host or Red Hat Enterprise Linux hosts

1. Use the Hosts resource tab, tree mode, or the search function to find and select the host in the results list.
2. Click Maintenance. If migration is enabled at cluster level, any virtual machines running on the host are migrated to other hosts. If the host is the SPM, this function is moved to another host. The status of the host changes as it enters maintenance mode.
3. Click Reinstall to open the Install Host window.
4. Click OK to reinstall the host.

Procedure 7.10. Customizing hosts with tags

1. Use the Hosts resource tab, tree mode, or the search function to find and select the host in the results list.
2. Click Assign Tags to open the Assign Tags window.
   

   Figure 7.1. Assign Tags Window

3. The Assign Tags window lists all available tags. Select the check boxes of applicable tags.
4. Click OK to assign the tags and close the window.

Procedure 7.11. Viewing Host Errata

1. Click the Hosts resource tab, and select a host from the results list.
2. Click the General tab in the details pane.
3. Click the Errata sub-tab in the General tab.

Procedure 7.12. Viewing Host Devices

1. Use the Hosts resource tab, tree mode, or the search function to find and select a host from the results list.
2. Click the Host Devices tab in the details pane.

Procedure 7.13. Preparing a Host for GPU Passthrough

1. From the Administration Portal, select a host.
2. Click the General tab in the details pane, and click Hardware. Locate the GPU device vendor ID:product ID. In this example, the IDs are 10de:13ba and 10de:0fbc.
3. Right-click the host and select Edit. Click the Kernel tab.
4. In the Kernel command line free text entry field, enter the IDs located in the previous steps.

   pci-stub.ids=10de:13ba,10de:0fbc

5. Blacklist the corresponding drivers on the host. For example, to blacklist nVidia's nouveau driver, next to pci-stub.ids=xxxx:xxxx, enter rdblacklist=nouveau.

   pci-stub.ids=10de:13ba,10de:0fbc rdblacklist=nouveau

6. Click OK to save the changes.
7. Click Reinstall to commit the changes to the host.
8. Reboot the host after the reinstallation is complete.

Procedure 7.14. Preparing a Guest Virtual Machine for GPU Passthrough

• • For Linux
    1. Only proprietary GPU drivers are supported. Black list the corresponding open source driver in the grub configuration file. For example:

       $ vi /etc/default/grub
       ...
       GRUB_CMDLINE_LINUX="nofb splash=quiet console=tty0 ... rdblacklist=nouveau"
       ...

    2. Locate the GPU BusID. In this example, is BusID is 00:09.0.

       # lspci | grep VGA
       00:09.0 VGA compatible controller: NVIDIA Corporation GK106GL [Quadro K4000] (rev a1)

    3. Edit the /etc/X11/xorg.conf file and append the following content:

       Section "Device"
       Identifier "Device0"
       Driver "nvidia"
       VendorName "NVIDIA Corporation"
       BusID "PCI:0:9:0"
       EndSection

    4. Restart the virtual machine.
  • For Windows
    1. Download and install the corresponding drivers for the device. For example, for Nvidia drivers, go to NVIDIA Driver Downloads.
    2. Restart the virtual machine.

Procedure 7.15. Accessing Cockpit from the Administration Portal

1. Install the Cockpit UI plug-in on the Manager machine:

   # yum install cockpit-ovirt-uiplugin

2. Restart the ovirt-engine service:

   # systemctl restart ovirt-engine.service

3. In the Administration Portal, click the Hosts tab and select a host.
4. Open the Cockpit user interface in a new tab, or view it directly through the Administration Portal:
   • Right-click the host and select Cockpit to open the Cockpit user interface in a new browser tab.
   • Click the Cockpit sub-tab to view the Cockpit user interface in the details pane of the Hosts tab.

     Note

     If Cockpit is not available on the selected host, the Cockpit sub-tab shows basic troubleshooting steps.