Chapter 7. Upgrading Red Hat Enterprise Virtualization Hypervisors

Red Hat Enterprise Virtualization (RHEV) Hypervisors can be updated to get the latest features, bug fixes and security patches.

7.1. Upgrading a RHEV Hypervisor with a RHEV Manager

You can upgrade and reinstall a Red Hat Enterprise Virtualization Hypervisor host from an ISO stored on the RHEV Manager. Upgrading and reinstalling means that you are stopping and restarting the host. Virtual machines are automatically migrated to a different host, however it is recommended that the upgrade is performed at a time when usage of the system is at its lowest. Ensure that the cluster contains more than one host before performing an upgrade.
It is recommended that administrators update Red Hat Enterprise Virtualization Hypervisors regularly. Important bug fixes and security updates are included in updates. Hypervisors which are not up to date may be a security risk.

Warning

Upgrading hosts involves shutting down, deactivating virtual machines and restarting the physical server. If any virtual machines are running on the Hypervisor, all data and configuration details may be destroyed if they are not shut down correctly. Upgrading Hypervisors must be carefully planned and executed with care and consideration.

7.1.1. Prerequisites

Before upgrading a Hypervisor:
  1. Download the latest RHEV Hypervisor RPM package from Red Hat Network.
    Or, download the latest RHEV Hypervisor ISO image from Red Hat Network
  2. Copy the ISO image file to the C:\Program Files\RedHat\RHEVManager\Service\RHEV-H Installer folder on the Red Hat Enterprise Virtualization Manager server.
  3. Change the file permissions so that NETWORK SERVICE has full control of the iso file.
    1. Use Windows Explorer to navigate to C:\Program Files\RedHat\RHEVManager\Service\.
    2. Right-click on the updated file, for example, rhev-hypervisor.iso, and select the Properties option. The Properties dialog displays.
    3. Click the Security tab, and select NETWORK SERVICE from the Group or user names panel.
    4. In the Permissions panel, click the Allow Full Control check box.
    5. Click OK.

Important

Ensure that the cluster contains more than one host before performing an upgrade. Do not attempt to re-install or upgrade all hosts at the same time, as one host must remain available to perform Storage Pool Manager (SPM) tasks.

7.1.2. Upgrading a RHEV Hypervisor

  1. Click the Hosts tab.
    A list of hosts displays. Select the host that you intend to upgrade.
    If the host is not displayed, perform a search.
  2. On the Details pane, click the General Tab.
    General Pane with Upgrade Button

    Figure 7.1. General Pane with Upgrade Button

    An Alert Message indicates that a new version of the RHEV Hypervisor is available. The Upgrade link is disabled if the host is has a status of Up. A tooltip directs you to switch to maintenance mode to enable upgrade.
    Upgrade Button

    Figure 7.2. Upgrade Button

  3. Select the host and click the Maintenance button. This will cause any virtual machines running on the host to be migrated to other hosts. If the host is the SPM, this function will be moved to another host. The status of the host changes as it enters maintenance mode. When the host status is Maintenance, the message in the general tab changes, providing you with a selectable link to re-install or upgrade the host.
  4. Click the link. The Install Host dialog displays.
    Install Host Dialog

    Figure 7.3. Install Host Dialog

  5. Select the appropriate file from the list of available ISOs to upgrade the host. This is usually rhev-hypervisor.iso.
  6. Click OK to upgrade and re-install the host. The dialog closes, the details of the host are updated in the Hosts tab, and the status changes appropriately.
    The host status transitions through the following stages: Installing, Reboot, Non Responsive, and Up. These are all normal, and may take some time.
  7. Once successfully upgraded, the host displays a status of Up. Any virtual machines that were migrated off the host, may be migrated back onto the upgraded host.