7.5. Configuring the Red Hat Enterprise Virtualization Hypervisor

7.5.1. Configuring Networking on the Hypervisor

The Network screen is used to configure the host name of the Hypervisor and the DNS servers, NTP servers, and network interfaces that the Hypervisor will use.
<Ping>: Allows you to ping a given IP address by specifying the address to ping and the number of times to ping that address.
<Create Bond>: Allows you to create bonds between network interfaces.

Procedure 7.7. Configuring the Host Name, DNS, and NTP

  1. In the text user interface, select the Network screen, press the right arrow key and enter a new host name in the Hostname field.
  2. Select the DNS Server 1 field and enter the IP address of the primary DNS server. Optionally set a secondary DNS server.
  3. Select the NTP Server 1 field and enter the IP address or host name of the primary NTP server. Optionally set a secondary NTP server.
  4. Select <Save> and press Enter to save the changes. You must save before you proceed to edit the network interfaces.
All network interface cards attached to the Hypervisor are initially in an unconfigured state. You must configure at least one network interface to connect it to a Red Hat Enterprise Virtualization environment.

Procedure 7.8. Configuring Network Interfaces

  1. Select a network interface from the list beneath Available System NICs and press Enter to configure that network interface.

    Note

    To identify the physical network interface card associated with the selected network interface, select <Flash Lights to Identify> and press Enter.
  2. Choose to configure IPv4 or IPv6.
    • Configure a dynamic or static IP address for IPv4:
      • Select DHCP under IPv4 Settings and press the space bar to configure a dynamic IP address.
      • Select Static under IPv4 Settings, press the space bar, and input the IP Address, Netmask, and Gateway that the Hypervisor will use to configure a static IP address.

        Example 7.17. Static IPv4 Networking Configuration

        IPv4 Settings
        ( ) Disabled     ( ) DHCP     (*) Static
        IP Address: 192.168.122.100_  Netmask: 255.255.255.0___
        Gateway     192.168.1.1_____
        
    • Configure a stateless, dynamic, or static IP for IPv6:
      • Select Auto under IPv6 Settings and press the space bar to configure stateless auto configuration.
      • Select DHCP under IPv6 Settings and press the space bar to configure a dynamic IP address.
      • Select Static under IPv6 Settings, press the space bar, and input the IP Address, Prefix Length, and Gateway that the Hypervisor will use to configure a static IP address.

        Example 7.18. Static IPv6 Networking Configuration

        IPv6 Settings
        ( ) Disabled     ( ) Auto     ( ) DHCP     (*) Static
        IP Address: 2001:db8:1::ab9:C0A8:103_  Prefix Length: 64______
        Gateway     2001:db8:1::ab9:1________
        
  3. Enter a VLAN identifier in the VLAN ID field to configure a VLAN for the device.
  4. Select the <Save> button and press Enter to save the network configuration.

7.5.2. Configuring Remote Storage

Use the Remote Storage screen to specify a remote iSCSI initiator or NFS share to use as storage.

Procedure 7.9. Configuring Remote Storage

  1. Enter an initiator name in the iSCSI Initiator Name field or the path to the NFS share in the NFSv4 Domain (example.redhat.com) field.

    Example 7.19. iSCSI Initiator Name

    iSCSI Initiator Name:
    iqn.1994-05.com.redhat:5189835eeb40_____

    Example 7.20. NFS Path

    NFSv4 Domain (example.redhat.com):
    example.redhat.com_____________________
  2. Select <Save> and press Enter.

7.5.3. Connecting the Hypervisor to the Red Hat Enterprise Virtualization Manager

You can attach the Hypervisor to the Red Hat Enterprise Virtualization Manager immediately if the address of the Manager is available. If the Manager has not yet been installed, you must instead set a password. This allows the Hypervisor to be added from the Administration Portal once the Manager has been installed. Both modes of configuration are supported from the RHEV-M screen in the Hypervisor user interface. However, adding the Hypervisor from the Administration Portal is the recommended option.

Important

Setting a password on the RHEV-M configuration screen sets the root password on the Hypervisor and enables SSH password authentication. Once the Hypervisor has successfully been added to the Manager, disabling SSH password authentication is recommended.

Important

If you are configuring the Hypervisor to use a bond or bridge device, add it manually from the Red Hat Enterprise Virtualization Manager instead of registering it with the Manager during setup to avoid unexpected errors.

Procedure 7.10. Configuring a Hypervisor Management Server

    • Configure the Hypervisor Management Server using the address of the Manager.
      1. Enter the IP address or fully qualified domain name of the Manager in the Management Server field.
      2. Enter the management server port in the Management Server Port field. The default value is 443. If a different port was selected during Red Hat Enterprise Virtualization Manager installation, specify it here, replacing the default value.
      3. Leave the Password and Confirm Password fields blank. These fields are not required if the address of the management server is known.
      4. Select <Save & Register> and press Enter.
      After a few minutes, the Hypervisor is displayed under the Hosts tab in the Administration Portal. You must approve it to use the Hypervisor in your Red Hat Enterprise Virtualization environment. See Section 7.6, “Approving a Registered Hypervisor” for more information.
    • Configure the Hypervisor Management Server using a password.
      1. Enter a password in the Password field. Although the Hypervisor will accept a weak password, it is recommended that you use a strong password. Strong passwords contain a mix of uppercase, lowercase, numeric and punctuation characters. They are six or more characters long and do not contain dictionary words.
      2. Re-enter the password in the Confirm Password field.
      3. Leave the Management Server and Management Server Port fields blank. As long as a password is set, allowing the Hypervisor to be added to the Manager later, these fields are not required.
      4. Select <Save & Register> and press Enter.
      After the password is set, manually add the Hypervisor from the Administration Portal. See Section 9.4, “Manually Adding a Hypervisor from the Administration Portal” for more information.

7.5.4. Registering the Hypervisor

Registration is only required if virtual machines running on the Hypervisor need to consume Red Hat Enterprise Linux virtualization entitlements. You can choose to register the Hypervisor to Red Hat Subscription Manager, a Satellite server, or Subscription Asset Manager from the RHSM Registration screen. The Hypervisor can also connect to these services via a proxy server.
You do not need to register the Hypervisor to receive updates to the Hypervisor image itself; new versions of the Hypervisor image are made available through the Red Hat Enterprise Virtualization Manager.

Procedure 7.11. Registering the Hypervisor

  1. Enter your Customer Portal user name in the Login field.
  2. Enter your Customer Portal password in the Password field.
  3. Enter a profile name to be used for the system in the Profile Name (optional) field. This is the name under which the system will appear when viewed in the Customer Portal.
  4. Select the method by which to register the Hypervisor:
    • Red Hat Subscription Manager

      1. Select the RHSM option and press the space bar.
      2. You do not need to enter values in the URL and CA URL fields.
      3. Optionally enter an organization name in the Organization field.

      Example 7.21. Red Hat Subscription Manager Configuration

      (X) RHSM     ( ) Satellite     ( ) SAM
      URL:          _________________________________________________
      CA URL:       _________________________________________________
      Organization: Organization_Name________________________________
    • Red Hat Satellite 5

      1. Select the Satellite option and press the space bar.
      2. Enter the URL of the Satellite server in the URL field.
      3. Enter the URL of the certificate authority for the Satellite server in the CA URL field.
      4. Optionally enter an organization name in the Organization field.
      5. Optionally enter a life cycle environment name in the Environment field.

      Example 7.22. Satellite 5 Configuration

      ( ) RHSM     (X) Satellite     ( ) SAM
      URL:          https://sat.example.com____________________________
      CA URL:       http://sat.example.com/pub/RHN-ORG-TRUSTED-SSL-CERT
      Organization: Organization_Name__________________________________
      Environment:  Library____________________________________________
    • Red Hat Satellite 6.0 or 6.1

      1. On the Satellite server, extract the certificate:
        # cd /tmp
        # rpm2cpio /var/www/html/pub/katello-ca-consumer-latest.noarch.rpm | cpio -idmv
        # cat etc/rhsm/ca/candlepin-local.pem etc/rhsm/ca/katello-server-ca.pem >> /var/www/html/pub/katello-server-ca.crt
        # restorecon -Rv /var/www/html/pub/katello-server-ca.crt
        # chmod 644 /var/www/html/pub/katello-server-ca.crt
      2. On the Hypervisor, select the Satellite option and press the space bar.
      3. Enter the URL of the Satellite server in the URL field.
      4. Enter the URL of the certificate authority for the Satellite server in the CA URL field.
      5. Enter an organization name in the Organization field.
      6. Enter a life cycle environment name in the Environment field.

      Example 7.23. Satellite 6 Configuration

      ( ) RHSM     (X) Satellite     ( ) SAM
      URL:          https://sat.example.com____________________________
      CA URL:       http://sat.example.com/pub/katello-server-ca.crt___
      Organization: Organization_Name__________________________________
      Environment:  Library____________________________________________
    • Red Hat Satellite 6.2

      1. Select the Satellite option and press the space bar.
      2. Enter the URL of the Satellite server in the URL field.
      3. Enter the URL of the certificate authority for the Satellite server in the CA URL field.
      4. Enter an organization name in the Organization field.
      5. Enter a life cycle environment name in the Environment field.

      Example 7.24. Satellite 6 Configuration

      ( ) RHSM     (X) Satellite     ( ) SAM
      URL:          https://sat.example.com____________________________
      CA URL:       http://sat.example.com/pub/katello-server-ca.crt___
      Organization: Organization_Name__________________________________
      Environment:  Library____________________________________________
    • Subscription Asset Manager

      1. Select the SAM option and press the space bar.
      2. Enter the URL of the Subscription Asset Manager server in the URL field.
      3. Enter the URL of the certificate authority for the Subscription Asset Manager server in the CA URL field.
      4. Optionally enter an organization name in the Organization field.

      Example 7.25. Subscription Asset Manager Configuration

      ( ) RHSM     ( ) Satellite     (X) SAM
      URL:          https://sam.example.com____________________________
      CA URL:       http://sam.example.com/sam/candlepin-local.pem_____
      Organization: Your_Organization__________________________________
  5. If you are using a proxy server, you must also specify the details of that server:
    1. Select <HTTP Proxy Configuration> and press Enter.
    2. Enter the IP address or fully qualified domain name of the proxy server in the Server field.
    3. Enter the port by which to attempt a connection to the proxy server in the Port field.
    4. Enter the user name by which to attempt a connection to the proxy server in the Username field.
    5. Enter the password by which to authenticate the user name specified above in the Password field.
    6. Select <Save> and press Enter to save the configuration and return to the RHSM Registration screen.
  6. Select <Save> and press Enter.

7.5.5. Changing the Admin User Password and Other Security-Related Tasks

You can configure security-related options for the Hypervisor such as SSH password authentication, AES-NI encryption, and the password of the admin user.

Procedure 7.12. Configuring Security-Related Tasks

  1. To enable SSH authentication, select the Enable SSH password authentication option and press the space bar. SSH authentication can also be enabled in the RHEV-M screen. Leave the option disabled if the function is not required.
  2. AES-NI encryption is enabled by default.
    • If you need to disable it, select the Disable AES-NI option and press the space bar.
    • If AES-NI encryption is enabled, you can optionally set the number of bytes by which to pad blocks in AES-NI encryption
  3. Enter a new password for the admin user in the Password field and Confirm Password to change the password used to log into the Hypervisor console.
  4. Select <Save> and press Enter.

7.5.6. Changing the Keyboard Layout on the Hypervisor

The Keyboard screen allows you to configure the keyboard layout used inside the Hypervisor console.

Procedure 7.13. Configuring the Hypervisor Keyboard Layout

  1. Select a keyboard layout from the list provided.
    Keyboard Layout Selection
    	
    Choose the Keyboard Layout you would like to apply to this system.
    
    Current Active Keyboard Layout: U.S. English
    Available Keyboard Layouts
    Swiss German (latin1)
    Turkish
    U.S. English
    U.S. International
    Ukranian
    ...
    
    <Save>
  2. Select <Save> and press Enter to save the selection.

7.5.7. Enabling the SNMP Agent on the Hypervisor

The SNMP screen allows you to enable and configure a password for simple network management protocol.
Enable SNMP       [ ]

SNMP Password
Password:          _______________
Confirm Password:  _______________


<Save>     <Reset>

Procedure 7.14. Enabling the SNMP Agent on the Hypervisor

  1. Select the Enable SNMP option and press the space bar to enable SNMP.
  2. Enter a password in the Password and Confirm Password fields.
  3. Select <Save> and press Enter.
You have enabled SNMP and configured a password that the Hypervisor will use in SNMP communication.

7.5.8. Enabling CIM Monitoring Connections on the Hypervisor

The CIM screen allows you to configure a common information model for attaching the Hypervisor to a pre-existing CIM management infrastructure and monitor virtual machines that are running on the Hypervisor.

Procedure 7.15. Enabling CIM Monitoring Connections on the Hypervisor

  1. Select the Enable CIM option and press the space bar to enable CIM.
    Enable CIM     [ ]
  2. Enter a password in the Password field and Confirm Password field.
  3. Select <Save> and press Enter.
You have configured the Hypervisor to accept CIM connections authenticated using a password. Use this password when adding the Hypervisor to your common information model object manager.

7.5.9. Configuring Logging

The Logging screen allows you to configure logging-related options such as a daemon for automatically exporting log files generated by the Hypervisor to a remote server.
Press F8 to see the available log files. To view the content of a log file, press the right arrow key, select a log file and press Enter.
  • /var/log/ovirt.log
  • /var/log/ovirt-node.log
  • /var/log/audit/audit.log
  • /var/log/messages
  • dmesg

Procedure 7.16. Configuring Logging using the Logging Screen

  1. In the Logrotate Max Log Size field, enter the maximum size in kilobytes that log files can reach before they are rotated by logrotate. The default value is 1024.
  2. Select an Interval to configure logrotate to run Daily, Weekly, or Monthly. The default value is Daily.
  3. Optionally configure rsyslog to transmit log files to a remote syslog daemon:
    1. Enter the remote rsyslog server address in the Server Address field.
    2. Enter the remote rsyslog server port in the Server Port field. The default port is 514.
  4. Optionally configure netconsole to transmit kernel messages to a remote destination:
    1. Enter the Server Address.
    2. Enter the Server Port. The default port is 6666.
  5. Select <Save> and press Enter.

7.5.10. Configuring Kernel Dumps

The Kdump screen allows you to specify a location in which kernel dumps will be stored in the event of a system failure.

Table 7.1. The Kdump Screen

Kdump Options Description
Disable
Disables kernel dumping.
Local
Stores kernel dumps on the local system.
SSH
Exports kernel dumps via SSH to the specified remote location.
NFS
Exports kernel dumps to the specified NFS share.

Procedure 7.17. Configuring Kernel Dumps

  1. Select an option for storing kernel dumps:
    • Disable

      To disable kernel dumps, select Disable, and press the space bar.
    • Local

      Select the Local option and press the space bar to store kernel dumps on the local system. This is the default option.
    • SSH

      1. Select the SSH option and press the space bar to export kernel dumps via SSH.
      2. Enter the location in which kernel dumps will be stored in the SSH Location (root@example.com) field.
      3. Enter an SSH Key URL (optional).
    • NFS

      1. Select the NFS option and press the space bar to export kernel dumps to an NFS share.
      2. Enter the location in which kernel dumps will be stored in the NFS Location (example.com:/var/crash) field.
  2. Select <Save> and press Enter.

7.5.11. The Diagnostics Screen

The Diagnostics screen allows you to select one of the diagnostic tools from the following list:
  • multipath -ll: Shows the current multipath topology from all available information.
  • fdisk -l: Lists the partition tables.
  • parted -s -l: Lists partition layout on all block devices.
  • lsblk: Lists information on all block devices.

7.5.12. The Performance Screen

The Performance screen allows you to select and apply a tuned profile to your system from the following list. The virtual-host profile is used by default. For Red Hat Enterprise Linux 7 profiles, see Tuned-adm in the Red Hat Enterprise Linux 7 Power Management Guide for more information.

Table 7.2. Tuned Profiles available in Red Hat Enterprise Virtualization

Tuned Profile Description
None
The system is disabled from using any tuned profile.
virtual-host
Based on the enterprise-storage profile, virtual-host decreases the swappiness of virtual memory and enables more aggressive writeback of dirty pages.
virtual-guest
A profile optimized for virtual machines.
throughput-performance
A server profile for typical throughput performance tuning.
spindown-disk
A strong power-saving profile directed at machines with classic hard disks.
server-powersave
A power-saving profile directed at server systems.
latency-performance
A server profile for typical latency performance tuning.
laptop-battery-powersave
A high-impact power-saving profile directed at laptops running on battery.
laptop-ac-powersave
A medium-impact power-saving profile directed at laptops running on AC.
enteprise-storage
A server profile to improve throughput performance for enterprise-sized server configurations.
desktop-powersave
A power-saving profile directed at desktop systems.
default
The default power-saving profile. This is the most basic power-saving profile. It only enables the disk and CPU plug-ins.

7.5.13. The Plugins Screen

The Plugins screen provides an overview of the installed plug-ins and allows you to view package differences if you have used the edit-node tool to update or add new packages. The Plugins screen also provides the following buttons:
  • <RPM Diff>: Allows you to view RPM differences.
  • <SRPM Diff>: Allows you to view SRPM differences.
  • <File Diff>: Allows you to view file differences.

7.5.14. The Hosted Engine Screen

To configure self-hosted engine on the Hypervisor, configure the Network screen before proceeding to configure the Hosted Engine screen. Do not configure the RHEV-M screen if you intend to configure the Hypervisor for self-hosted engine.
For more information on configuring networking, see Section 7.5.1, “Configuring Networking on the Hypervisor”.
For more information on configuring self-hosted engine, see Configuring Self-Hosted Engine on Red Hat Enterprise Virtualization Hypervisor in the Self-Hosted Engine Guide.