1. At the Red Hat Enterprise Linux or Red Hat Enterprise Virtualization Hypervisor boot screen, press any key and select the Boot or Boot with serial console entry from the list.
2. Press Tab to edit the kernel parameters for the selected option.
3. Ensure there is a Space after the last kernel parameter listed, and append the rescue parameter.
4. Press Enter to boot into rescue mode.
5. At the prompt which appears, determine that your processor has the required extensions and that they are enabled by running this command:

   # grep -E 'svm|vmx' /proc/cpuinfo | grep nx

   If any output is shown, then the processor is hardware virtualization capable. If no output is shown, then it is still possible that your processor supports hardware virtualization. In some circumstances manufacturers disable the virtualization extensions in the BIOS. If you believe this to be the case, consult the system's BIOS and the motherboard manual provided by the manufacturer.
6. As an additional check, verify that the kvm modules are loaded in the kernel:

   # lsmod | grep kvm

   If the output includes kvm_intel or kvm_amd then the kvm hardware virtualization modules are loaded and your system meets requirements.

Procedure 2.1. Subscribing to the Red Hat Enterprise Virtualization Manager Channels using Subscription Manager

1. Register the System with Subscription Manager

   Run the following command and enter your Red Hat Network user name and password to register the system with the Red Hat Network:

   # subscription-manager register

2. Identify Available Entitlement Pools

   Run the following commands to find entitlement pools containing the channels required to install the Red Hat Enterprise Virtualization Manager:

   # subscription-manager list --available | grep -A8 "Red Hat Enterprise Linux Server"
   # subscription-manager list --available | grep -A8 "Red Hat Enterprise Virtualization"

3. Attach Entitlement Pools to the System

   Use the pool identifiers located in the previous step to attach the Red Hat Enterprise Linux Server and Red Hat Enterprise Virtualization entitlements to the system. Run the following command to attach the entitlements:

   # subscription-manager attach --pool=[POOLID]

4. Enable the Required Channels

   Run the following commands to enable the channels required to install Red Hat Enterprise Virtualization:

   # yum-config-manager --enable rhel-6-server-rpms
   # yum-config-manager --enable rhel-6-server-supplementary-rpms
   # yum-config-manager --enable rhel-6-server-rhevm-3.4-rpms
   # yum-config-manager --enable jb-eap-6-for-rhel-6-server-rpms
   

Procedure 2.2. Subscribing to the Red Hat Enterprise Virtualization Manager Channels using RHN Classic

1. Run the rhn_register command to register the system with Red Hat Network. To complete registration successfully you must supply your Red Hat Network user name and password. Follow the on-screen prompts to complete registration of the system.

   # rhn_register

2. Subscribe to Required Channels

   You must subscribe the system to the required channels using either the web interface to Red Hat Network or the command line rhn-channel command.

   • Using the rhn-channel Command

     Run the rhn-channel command to subscribe the system to each of the required channels. Run the following commands:

     # rhn-channel --add --channel=rhel-x86_64-server-6
     # rhn-channel --add --channel=rhel-x86_64-server-supplementary-6
     # rhn-channel --add --channel=rhel-x86_64-server-6-rhevm-3.4
     # rhn-channel --add --channel=jbappplatform-6-x86_64-server-6-rpm

     Important

     If you are not the administrator for the machine as defined in Red Hat Network, or the machine is not registered to Red Hat Network, then use of the rhn-channel command results in an error:

     Error communicating with server. The message was:
     Error Class Code: 37
     Error Class Info: You are not allowed to perform administrative tasks on this system.
     Explanation: 
          An error has occurred while processing your request. If this problem
          persists please enter a bug report at bugzilla.redhat.com.
          If you choose to submit the bug report, please be sure to include
          details of what you were trying to do when this error occurred and
          details on how to reproduce this problem.
     

     If you encounter this error when using rhn-channel, you must use the web user interface to add the channel.

   • Using the Web Interface to Red Hat Network

     To add a channel subscription to a system from the web interface:
     1. Log on to Red Hat Network (http://rhn.redhat.com).
     2. Move the mouse cursor over the Subscriptions link at the top of the screen, and then click the Registered Systems link in the menu that appears.
     3. Select the system to which you are adding channels from the list presented on the screen, by clicking the name of the system.
     4. Click Alter Channel Subscriptions in the Subscribed Channels section of the screen.
     5. Select the channels to be added from the list presented on the screen. Red Hat Enterprise Virtualization Manager requires:
        • The Red Hat Enterprise Linux Server (v. 6 for 64-bit x86_64) channel. This channel is located under the Release Channels for Red Hat Enterprise Linux 6 for x86_64 expandable menu.
        • The RHEL Server Supplementary (v. 6 64-bit x86_64) channel. This channel is located under the Release Channels for Red Hat Enterprise Linux 6 for x86_64 expandable menu.
        • The Red Hat Enterprise Virtualization Manager (v.3.4 x86_64) channel. This channel is located under the Additional Services Channels for Red Hat Enterprise Linux 6 for x86_64 expandable menu.
        • The Red Hat JBoss EAP (v 6) for 6Server x86_64 channel. This channel is located under the Additional Services Channels for Red Hat Enterprise Linux 6 for x86_64 expandable menu.
     6. Click the Change Subscription button to finalize the change.

1. Install Red Hat Enterprise Linux

   Install Red Hat Enterprise Linux 6 Server on a system that has access to Red Hat Network. This system downloads all required packages, and distribute them to your offline system(s).

   Important

   Ensure that the system used has a large amount of free disk space available. This procedure downloads a large number of packages, and requires up to 1.5 GB of free disk space.

2. Register Red Hat Enterprise Linux

   Register the system with Red Hat Network (RHN) using either Subscription Manager or RHN Classic.

   • Subscription Manager

     Use the subscription-manager command as root with the register parameter.

     # subscription-manager register

   • RHN Classic

     Use the rhn_register command as root.

     # rhn_register

3. Add required channel subscriptions

   Subscribe the system for all channels listed in the Red Hat Enterprise Virtualization - Installation Guide.

   • Subscription Manager

   • RHN Classic

4. Configure File Transfer Protocol (FTP) access

   Servers that are not connected to the Internet can access the software repository using File Transfer Protocol (FTP). To create the FTP repository you must install and configure vsftpd, while logged in to the system as the root user:

   1. Install vsftpd

      Install the vsftpd package.

      # yum install vsftpd

   2. Start vsftpd

      Start the vsftpd daemon.

      # chkconfig vsftpd on    service vsftpd start

   3. Create sub-directory

      Create a sub-directory inside the /var/ftp/pub/ directory. This is where the downloaded packages will be made available.

      # mkdir /var/ftp/pub/rhevrepo

5. Download packages

   Once the FTP server has been configured, you must use the reposync command to download the packages to be shared. It downloads all packages from all configured software repositories. This includes repositories for all Red Hat Network channels the system is subscribed to, and any locally configured repositories.
   1. As the root user, change into the /var/ftp/pub/rhevrepo directory.

      # cd /var/ftp/pub/rhevrepo

   2. Run the reposync command.

      # reposync --plugins .

6. Create local repository metadata

   Use the createrepo command to create repository metadata for each of the sub-directories where packages were downloaded under /var/ftp/pub/rhevrepo.

   # for DIR in `find /var/ftp/pub/rhevrepo -maxdepth 1 -mindepth 1 -type d`; do createrepo $DIR; done;

7. Create repository configuration files

   Create a yum configuration file, and copy it to the /etc/yum.repos.d/ directory on client systems that you want to connect to this software repository. Ensure that the system hosting the repository is connected to the same network as the client systems where the packages are to be installed.
   The configuration file can be created manually, or using a script. If using a script, then before running it you must replace ADDRESS in the baseurl with the IP address or Fully Qualified Domain Name (FQDN) of the system hosting the repository. The script must be run on this system and then distributed to the client machines. For example:

   #!/bin/sh
   
   REPOFILE="/etc/yum.repos.d/rhev.repo"
   
   for DIR in `find /var/ftp/pub/rhevrepo -maxdepth 1 -mindepth 1 -type d`; do  
       echo -e "[`basename $DIR`]"	> $REPOFILE	
       echo -e "name=`basename $DIR`" >> $REPOFILE	
       echo -e "baseurl=ftp://ADDRESS/pub/rhevrepo/`basename $DIR`" >> $REPOFILE	
       echo -e "enabled=1" >> $REPOFILE	
       echo -e "gpgcheck=0" >> $REPOFILE	
       echo -e "\n" >> $REPOFILE
   done;
   

8. Copy the repository configuration file to client system

   Copy the repository configuration file to the /etc/yum.repos.d/ directory on every system that you want to connect to this software repository. For example: Red Hat Enterprise Virtualization Manager system(s), all Red Hat Enterprise Linux virtualization hosts, and all Red Hat Enterprise Linux virtual machines.

Procedure 2.3. Installing the Red Hat Enterprise Virtualization Manager Packages

1. To ensure all packages are up to date, run the following command on the machine where you are installing the Red Hat Enterprise Virtualization Manager:

   # yum update

2. Run the following command to install the rhevm package and dependencies.

   # yum install rhevm

   Note

   The rhevm-doc package is installed as a dependency of the rhevm package, and provides a local copy of the Red Hat Enterprise Virtualization documentation suite. This documentation is also used to provide context sensitive help links from the Administration and User Portals. You can run the following commands to search for translated versions of the documentation:

   # yum search rhevm-doc

Procedure 2.4. Configuring the Red Hat Enterprise Virtualization Manager

1. Packages

   The engine-setup command checks to see if it is performing an upgrade or an installation, and whether any updates are available for the packages linked to the Manager. No user input is required at this stage.

   [ INFO  ] Checking for product updates...
   [ INFO  ] No product updates found

2. Network Configuration

   A reverse lookup is performed on the host name of the machine on which the Red Hat Enterprise Virtualization Manager is being installed. The host name is detected automatically, but you can correct this host name if it is incorrect or if you are using virtual hosts. There must be forward and reverse lookup records for the provided host name in DNS, especially if you will also install the reports server.

   Host fully qualified DNS name of this server [autodetected host name]:

   The engine-setup command checks your firewall configuration and offers to modify that configuration for you to open the ports used by the Manager for external communication such as TCP ports 80 and 443. If you do not allow the engine-setup command to modify your firewall configuration, then you must manually open the ports used by the Red Hat Enterprise Virtualization Manager.

   Do you want Setup to configure the firewall? (Yes, No) [Yes]:

3. Database Configuration

   You can use either a local or remote PostgreSQL database. The engine-setup command can configure your database automatically (including adding a user and a database), or it can use values that you supply.

   Where is the database located? (Local, Remote) [Local]: 
   Setup can configure the local postgresql server automatically for the engine to run. This may conflict with existing applications.
   Would you like Setup to automatically configure postgresql and create Engine database, or prefer to perform that manually? (Automatic, Manual) [Automatic]:
   

4. oVirt Engine Configuration

   Select Gluster, Virt, or Both:

   Application mode (Both, Virt, Gluster) [Both]:

   Both offers the greatest flexibility.
   Set a password for the automatically created administrative user of the Red Hat Enterprise Virtualization Manager:

   Engine admin password:
   Confirm engine admin password:

5. PKI Configuration

   The Manager uses certificates to communicate securely with its hosts. You provide the organization name for the certificate. This certificate can also optionally be used to secure https communications with the Manager.

   Organization name for certificate [autodetected domain-based name]:

6. Apache Configuration

   By default, external SSL (HTTPS) communication with the Manager is secured with the self-signed certificate created in the PKI configuration stage to securely communicate with hosts. Another certificate may be chosen for external HTTPS connections, without affecting how the Manager communicates with hosts.

   Setup can configure apache to use SSL using a certificate issued from the internal CA.
   Do you wish Setup to configure that, or prefer to perform that manually? (Automatic, Manual) [Automatic]:

   The Red Hat Enterprise Virtualization Manager uses the Apache web server to present a landing page to users. The engine-setup command can make the landing page of the Manager the default page presented by Apache.

   Setup can configure the default page of the web server to present the application home page. This may conflict with existing applications.
   Do you wish to set the application as the default web page of the server? (Yes, No) [Yes]:

7. System Configuration

   The engine-setup command can create an NFS share on the Manager to use as an ISO storage domain. Hosting the ISO domain locally to the Manager simplifies keeping some elements of your environment up to date.

   Configure an NFS share on this server to be used as an ISO Domain? (Yes, No) [Yes]: 
   Local ISO domain path [/var/lib/exports/iso]: 
   Local ISO domain ACL [0.0.0.0/0.0.0.0(rw)]: 
   Local ISO domain name [ISO_DOMAIN]:

8. Websocket Proxy Server Configuration

   The engine-setup command can optionally configure a websocket proxy server for allowing users to connect to virtual machines via the noVNC or HTML 5 consoles.

   Configure WebSocket Proxy on this machine? (Yes, No) [Yes]:

9. Miscellaneous Configuration

   You can use the engine-setup command to allow a proxy server to broker transactions from the Red Hat Access plug-in.

   Would you like transactions from the Red Hat Access Plugin sent from the RHEV Manager to be brokered through a proxy server? (Yes, No) [No]:

   [ INFO  ] Stage: Setup validation

10. Configuration Preview

    Check the configuration preview to confirm the values you entered before they are applied. If you choose to proceed, engine-setup configures the Red Hat Enterprise Virtualization Manager using those values.

    Engine database name                    : engine
    Engine database secured connection      : False
    Engine database host                    : localhost
    Engine database user name               : engine
    Engine database host name validation    : False
    Engine database port                    : 5432
    NFS setup                               : True
    PKI organization                        : Your Org
    Application mode                        : both
    Firewall manager                        : iptables
    Update Firewall                         : True
    Configure WebSocket Proxy               : True
    Host FQDN                               : Your Manager's FQDN
    NFS export ACL                          : 0.0.0.0/0.0.0.0(rw)
    NFS mount point                         : /var/lib/exports/iso
    Datacenter storage type                 : nfs
    Configure local Engine database         : True
    Set application as default page         : True
    Configure Apache SSL                    : True
             
    Please confirm installation settings (OK, Cancel) [OK]:

    When your environment has been configured, the engine-setup command displays details about how to access your environment and related security details.

11. Clean Up and Termination

    The engine-setup command cleans up any temporary files created during the configuration process, and outputs the location of the log file for the Red Hat Enterprise Virtualization Manager configuration process.

    [ INFO  ] Stage: Clean up
              Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-installation-date.log
    [ INFO  ] Stage: Pre-termination
    [ INFO  ] Stage: Termination
    [ INFO  ] Execution of setup completed successfully
    

Procedure 2.5. Preparing a PostgreSQL Database for use with Red Hat Enterprise Virtualization Manager

1. Run the following commands to initialize the PostgreSQL database, start the postgresql service and ensure this service starts on boot:

   # service postgresql initdb
   # service postgresql start
   # chkconfig postgresql on

2. Create a user for the Red Hat Enterprise Virtualization Manager to use when it writes to and reads from the database, and a database in which to store data about the Red Hat Enterprise Virtualization environment. You must perform this step on both local and remote databases. Use the psql terminal as the postgres user.

   # su - postgres
   $ psql              
   postgres=# create role [user name] with login encrypted password '[password]';
   postgres=# create database [database name] owner [user name] template template0 encoding 'UTF8' lc_collate 'en_US.UTF-8' lc_ctype 'en_US.UTF-8';

3. Run the following commands to connect to the new database and add the plpgsql language:

   postgres=# \c [database name]
   CREATE LANGUAGE plpgsql;

4. Ensure the database can be accessed remotely by enabling client authentication. Edit the /var/lib/pgsql/data/pg_hba.conf file, and add the following in accordance with the location of the database:
   • For local databases, add the two following lines immediately underneath the line starting with Local at the bottom of the file:

     host    [database name]    [user name]    0.0.0.0/0  md5
     host    [database name]    [user name]    ::0/0      md5

   • For remote databases, add the following line immediately underneath the line starting with Local at the bottom of the file, replacing X.X.X.X with the IP address of the Manager:

     host    [database name]    [user name]    X.X.X.X/32   md5

5. Allow TCP/IP connections to the database. You must perform this step for remote databases. Edit the /var/lib/pgsql/data/postgresql.conf file and add the following line:

   listen_addresses='*'

   This example configures the postgresql service to listen for connections on all interfaces. You can specify an interface by giving its IP address.
6. Restart the postgresql service. This step is required on both local and remote manually configured database servers.

   # service postgresql restart

Procedure 2.6. Configuring the Manager to use a Manually Configured Local or Remote PostgreSQL Database

1. During configuration of the Red Hat Enterprise Virtualization Manager, the engine-setup command prompts you to decide where your database is located:

   Where is the database located? (Local, Remote) [Local]:

   The steps involved in manually configuring the Red Hat Enterprise Virtualization Manger to use local or remotely hosted databases are the same. However, to use a remotely hosted database you must provide the host name of the remote database server and the port on which it is listening.
2. When prompted, enter Manual to manually configure the database:

   Would you like Setup to automatically configure postgresql, or prefer to perform that manually? (Automatic, Manual) [Automatic]: Manual

3. If you are using a remotely hosted database, supply the engine-setup command with the host name of your database server and the port on which it is listening:

   Database host [localhost]:
   Database port [5432]:

4. For both local and remotely hosted databases, you must select whether or not your database uses a secured connection. You must also enter the name of the database you configured, the user the Manager can use to access the database, and the password of that user.

   Database secured connection (Yes, No) [No]: 
   Database name [engine]: 
   Database user [engine]: 
   Database password:

   Note

   Using a secured connection to your database requires you to also have manually configured secured database connections.

Procedure 2.7. Connecting to the Administration Portal

1. Open a supported web browser.
2. Navigate to https://[your-manager-fqdn]/ovirt-engine, replacing [your-manager-fqdn] with the fully qualified domain name that you provided during installation to open the login screen.

   Important

   The first time that you connect to the Administration Portal, you are prompted to trust the certificate being used to secure communications between your browser and the web server.
3. Enter your User Name and Password. If you are logging in for the first time, use the user name admin in conjunction with the administrator password that you specified during installation.
4. Select the domain against which to authenticate from the Domain drop-down list. If you are logging in using the internal admin user name, select the internal domain.
5. You can view the Administration Portal in multiple languages. The default selection will be chosen based on the locale settings of your web browser. If you would like to view the Administration Portal in a language other than the default, select your preferred language from the list.
6. Click Login.

Procedure 2.8. Removing Red Hat Enterprise Virtualization Manager

1. Run the following command on the machine on which the Red Hat Enterprise Virtualization Manager is installed:

   # engine-cleanup

2. You are prompted to confirm removal of all Red Hat Enterprise Virtualization Manager components. These components include PKI keys, the locally hosted ISO domain file system layout, PKI configuration, the local NFS exports configuration, and the engine database content.

   Do you want to remove all components? (Yes, No) [Yes]:

   Note

   A backup of the Engine database and a compressed archive of the PKI keys and configuration are always automatically created. These files are saved under /var/lib/ovirt-engine/backups/, and include the date and engine- and engine-pki- in their file names respectively.
3. You are given another opportunity to change your mind and cancel the removal of the Red Hat Enterprise Virtualization Manager. If you choose to proceed, the ovirt-engine service is stopped, and your environment's configuration is removed in accordance with the options you selected.

   During execution engine service will be stopped (OK, Cancel) [OK]:
   ovirt-engine is about to be removed, data will be lost (OK, Cancel) [Cancel]:OK

Procedure 3.6. Backing up the Original Red Hat Enterprise Virtualization Manager

1. Preparing the Failover Host

   A failover host, one of the hosted-engine hosts in the environment, must be placed into maintenance mode so that it has no virtual load at the time of the backup. This host can then later be used to deploy the restored self-hosted engine environment. Any of the hosted-engine hosts can be used as the failover host for this backup scenario, however the restore process is more straightforward if Host 1 is used. The default name for the Host 1 host is hosted_engine_1; this was set when the hosted-engine deployment script was initially run.
   1. Log in to one of the hosted-engine hosts.
   2. Confirm that the hosted_engine_1 host is Host 1:

       # hosted-engine --vm-status

   3. Log in to the Administration Portal.
   4. Select the Hosts tab.
   5. Select the hosted_engine_1 host in the results list, and click Maintenance.
   6. Click Ok.

2. Disabling the High-Availability Agents

   Disable the high-availability agents on the hosted-engine hosts to prevent migration of the Red Hat Enterprise Virtualization Manager virtual machine during the backup process. Connect to any of the hosted-engine hosts and place the high-availability agents on all hosts into global maintenance mode.

   # hosted-engine --set-maintenance --mode=global

3. Creating a Backup of the Manager

   On the Manager virtual machine, back up the configuration settings and database content, replacing [EngineBackupFile] with the file name for the backup file, and [LogFILE] with the file name for the backup log.

   # engine-backup --mode=backup --file=[EngineBackupFile] --log=[LogFILE]

4. Copying the Backup Files to an External Server

   Secure copy the backup files to an external server. In the following example, [Storage.example.com] is the fully qualified domain name of a network storage server that will store the backup until it is needed, and /backup/ is any designated folder or path. This step is not mandatory, but the backup files must be accessible to restore the configuration settings and database content.

   # scp -p [EngineBackupFiles] [Storage.example.com:/backup/EngineBackupFiles]

5. Enabling the High-Availability Agents

   Connect to any of the hosted-engine hosts and turn off global maintenance mode. This enables the high-availability agents.

   # hosted-engine --set-maintenance --none

6. Activating the Failover Host

   Bring the hosted_engine_1 host out of maintenance mode.
   1. Log in to the Administration Portal.
   2. Select the Hosts tab.
   3. Select hosted_engine_1 from the results list.
   4. Click Activate.

Procedure 3.7. Creating a New Self-Hosted Environment to be Used as the Restored Environment

1. Updating DNS

   Update your DNS so that the fully qualified domain name of the Red Hat Enterprise Virtualization environment correlates to the IP address of the new Manager. In this procedure, fully qualified domain name was set as Manager.example.com. The fully qualified domain name provided for the engine must be identical to that given in the engine setup of the original engine that was backed up.

2. Initiating Hosted Engine Deployment

   On the newly installed Red Hat Enterprise Linux host, run the hosted-engine deployment script. To escape the script at any time, use the CTRL+D keyboard combination to abort deployment.

   # hosted-engine --deploy

   If running the hosted-engine deployment script over a network, it is recommended to use the screen window manager to avoid losing the session in case of network or terminal disruption. Install the screen package first if not installed.

   # screen hosted-engine --deploy

3. Configuring Storage

   Select the type of storage to use.

   During customization use CTRL-D to abort.
   Please specify the storage you would like to use (iscsi, nfs3, nfs4)[nfs3]:

   • For NFS storage types, specify the full address, using either the fully qualified domain name or IP address, and path name of the shared storage domain.

     Please specify the full shared storage connection path to use (example: host:/path): storage.example.com:/hosted_engine/nfs

   • For iSCSI, specify the iSCSI portal IP address, port, user name and password, and select a target name from the auto-detected list:

     Please specify the iSCSI portal IP address:           
     Please specify the iSCSI portal port [3260]:           
     Please specify the iSCSI portal user:           
     Please specify the iSCSI portal password:
     Please specify the target name (auto-detected values) [default]:

   Choose the storage domain and storage data center names to be used in the environment.

   [ INFO  ] Installing on first host
   Please provide storage domain name. [hosted_storage]: 
   Local storage datacenter name is an internal name and currently will not be shown in engine's admin UI.Please enter local datacenter name [hosted_datacenter]:

4. Configuring the Network

   The script detects possible network interface controllers (NICs) to use as a management bridge for the environment. It then checks your firewall configuration and offers to modify it for console (SPICE or VNC) access the Manager virtual machine. Provide a pingable gateway IP address, to be used by the ovirt-ha-agent, to help determine a host's suitability for running a Manager virtual machine.

   Please indicate a nic to set rhevm bridge on: (eth1, eth0) [eth1]:
   iptables was detected on your computer, do you wish setup to configure it? (Yes, No)[Yes]: 
   Please indicate a pingable gateway IP address [X.X.X.X]:
   

5. Configuring the New Manager Virtual Machine

   The script creates a virtual machine to be configured as the new Manager virtual machine. Specify the boot device and, if applicable, the path name of the installation media, the CPU type, the number of virtual CPUs, and the disk size. Specify a MAC address for the Manager virtual machine, or accept a randomly generated one. The MAC address can be used to update your DHCP server prior to installing the operating system on the Manager virtual machine. Specify memory size and console connection type for the creation of Manager virtual machine.

   Please specify the device to boot the VM from (cdrom, disk, pxe) [cdrom]: 
   The following CPU types are supported by this host:
             - model_Penryn: Intel Penryn Family
             - model_Conroe: Intel Conroe Family
   Please specify the CPU type to be used by the VM [model_Penryn]: 
   Please specify the number of virtual CPUs for the VM [Defaults to minimum requirement: 2]: 
   Please specify the disk size of the VM in GB [Defaults to minimum requirement: 25]: 
   You may specify a MAC address for the VM or accept a randomly generated default [00:16:3e:77:b2:a4]: 
   Please specify the memory size of the VM in MB [Defaults to minimum requirement: 4096]: 
   Please specify the console type you want to use to connect to the VM (vnc, spice) [vnc]:
   

6. Identifying the Name of the Host

   A unique name must be provided for the name of the host, to ensure that it does not conflict with other resources that will be present when the engine has been restored from the backup. The name hosted_engine_1 can be used in this procedure because this host was placed into maintenance mode before the environment was backed up, enabling removal of this host between the restoring of the engine and the final synchronization of the host and the engine.

   Enter the name which will be used to identify this host inside the Administrator Portal [hosted_engine_1]:

7. Configuring the Hosted Engine

   Specify a name for the self-hosted engine environment, and the password for the admin@internal user to access the Administrator Portal. Provide the fully qualified domain name for the new Manager virtual machine. This procedure uses the fully qualified domain name Manager.example.com. Provide the name and TCP port number of the SMTP server, the email address used to send email notifications, and a comma-separated list of email addresses to receive these notifications.

   Important

   The fully qualified domain name provided for the engine (Manager.example.com) must be the same fully qualified domain name provided when original Manager was initially set up.

   Enter 'admin@internal' user password that will be used for accessing the Administrator Portal: 
   Confirm 'admin@internal' user password: 
   Please provide the FQDN for the engine you want to use. This needs to match the FQDN that you will use for the engine installation within the VM: Manager.example.com
   Please provide the name of the SMTP server through which we will send notifications [localhost]: 
   Please provide the TCP port number of the SMTP server [25]: 
   Please provide the email address from which notifications will be sent [root@localhost]: 
   Please provide a comma-separated list of email addresses which will get notifications [root@localhost]:

8. Configuration Preview

   Before proceeding, the hosted-engine deployment script displays the configuration values you have entered, and prompts for confirmation to proceed with these values.

   Bridge interface                   : eth1
   Engine FQDN                        : Manager.example.com
   Bridge name                        : rhevm
   SSH daemon port                    : 22
   Firewall manager                   : iptables
   Gateway address                    : X.X.X.X
   Host name for web application      : hosted_engine_1
   Host ID                            : 1
   Image size GB                      : 25
   Storage connection                 : storage.example.com:/hosted_engine/nfs
   Console type                       : vnc
   Memory size MB                     : 4096
   MAC address                        : 00:16:3e:77:b2:a4
   Boot type                          : pxe
   Number of CPUs                     : 2
   CPU Type                           : model_Penryn
   
   Please confirm installation settings (Yes, No)[No]:
   

9. Creating the New Manager Virtual Machine

   The script creates the virtual machine to be configured as the Manager virtual machine and provides connection details. You must install an operating system on it before the hosted-engine deployment script can proceed on Hosted Engine configuration.

   [ INFO  ] Generating answer file '/etc/ovirt-hosted-engine/answers.conf'
   [ INFO  ] Stage: Transaction setup
   [ INFO  ] Stage: Misc configuration
   [ INFO  ] Stage: Package installation
   [ INFO  ] Stage: Misc configuration
   [ INFO  ] Configuring libvirt
   [ INFO  ] Generating VDSM certificates
   [ INFO  ] Configuring VDSM
   [ INFO  ] Starting vdsmd
   [ INFO  ] Waiting for VDSM hardware info
   [ INFO  ] Creating Storage Domain
   [ INFO  ] Creating Storage Pool
   [ INFO  ] Connecting Storage Pool
   [ INFO  ] Verifying sanlock lockspace initialization
   [ INFO  ] Initializing sanlock lockspace
   [ INFO  ] Initializing sanlock metadata
   [ INFO  ] Creating VM Image
   [ INFO  ] Disconnecting Storage Pool
   [ INFO  ] Start monitoring domain
   [ INFO  ] Configuring VM
   [ INFO  ] Updating hosted-engine configuration
   [ INFO  ] Stage: Transaction commit
   [ INFO  ] Stage: Closing up
   [ INFO  ] Creating VM
   You can now connect to the VM with the following command:
   	/usr/bin/remote-viewer vnc://localhost:5900
   Use temporary password "5379skAb" to connect to vnc console.
   Please note that in order to use remote-viewer you need to be able to run graphical applications.
   This means that if you are using ssh you have to supply the -Y flag (enables trusted X11 forwarding).
   Otherwise you can run the command from a terminal in your preferred desktop environment.
   If you cannot run graphical applications you can connect to the graphic console from another host or connect to the console using the following command:
   virsh -c qemu+tls://Test/system console HostedEngine
   If you need to reboot the VM you will need to start it manually using the command:
   hosted-engine --vm-start
   You can then set a temporary password using the command:
   hosted-engine --add-console-password
   The VM has been started.  Install the OS and shut down or reboot it.  To continue please make a selection:
            
             (1) Continue setup - VM installation is complete
             (2) Reboot the VM and restart installation
             (3) Abort setup
            
             (1, 2, 3)[1]:
   

   Using the naming convention of this procedure, connect to the virtual machine using VNC with the following command:

   /usr/bin/remote-viewer vnc://hosted_engine_1.example.com:5900

10. Installing the Virtual Machine Operating System

    Connect to Manager virtual machine and install a Red Hat Enterprise Linux 6.5 or 6.6 operating system.

11. Synchronizing the Host and the Manager

    Return to the host and continue the hosted-engine deployment script by selecting option 1:

    (1) Continue setup - VM installation is complete

     Waiting for VM to shut down...
    [ INFO  ] Creating VM
    You can now connect to the VM with the following command:
    	/usr/bin/remote-viewer vnc://localhost:5900
    Use temporary password "5379skAb" to connect to vnc console.
    Please note that in order to use remote-viewer you need to be able to run graphical applications.
    This means that if you are using ssh you have to supply the -Y flag (enables trusted X11 forwarding).
    Otherwise you can run the command from a terminal in your preferred desktop environment.
    If you cannot run graphical applications you can connect to the graphic console from another host or connect to the console using the following command:
    virsh -c qemu+tls://Test/system console HostedEngine
    If you need to reboot the VM you will need to start it manually using the command:
    hosted-engine --vm-start
    You can then set a temporary password using the command:
    hosted-engine --add-console-password
    Please install and setup the engine in the VM.
    You may also be interested in subscribing to "agent" RHN/Satellite channel and installing rhevm-guest-agent-common package in the VM.
    To continue make a selection from the options below:
              (1) Continue setup - engine installation is complete
              (2) Power off and restart the VM
              (3) Abort setup
    

12. Installing the Manager

    Connect to new Manager virtual machine, ensure the latest versions of all installed packages are in use, and install the rhevm packages.

    # yum upgrade

    # yum install rhevm

13. Install Reports and the Data Warehouse

    If you are also restoring Reports and the Data Warehouse, install the rhevm-reports-setup and rhevm-dwh-setup packages.

    # yum install rhevm-reports-setup rhevm-dwh-setup

Procedure 3.8. Restoring the Self-Hosted Engine Manager

1. Manually create an empty database to which the database content in the backup can be restored. The following steps must be performed on the machine where the database is to be hosted.
   1. If the database is to be hosted on a machine other than the Manager virtual machine, install the postgresql-server package. This step is not required if the database is to be hosted on the Manager virtual machine because this package is included with the rhevm package.

      # yum install postgesql-server

   2. Initialize the postgresql database, start the postgresql service, and ensure this service starts on boot:

      # service postgresql initdb
      # service postgresql start
      # chkconfig postgresql on

   3. Enter the postgresql command line:

      # su postgres
      $ psql

   4. Create the engine user:

      postgres=# create role engine with login encrypted password 'password';

      If you are also restoring the Reports and Data Warehouse, create the ovirt_engine_reports and ovirt_engine_history users on the relevant host:

      postgres=# create role ovirt_engine_reports with login encrypted password 'password';

      postgres=# create role ovirt_engine_history with login encrypted password 'password';

   5. Create the new database:

      postgres=# create database database_name owner engine template template0 encoding 'UTF8' lc_collate 'en_US.UTF-8' lc_ctype 'en_US.UTF-8';

      If you are also restoring the Reports and Data Warehouse, create the databases on the relevant host:

      postgres=# create database database_name owner ovirt_engine_reports template template0 encoding 'UTF8' lc_collate 'en_US.UTF-8' lc_ctype 'en_US.UTF-8';

      postgres=# create database database_name owner ovirt_engine_history template template0 encoding 'UTF8' lc_collate 'en_US.UTF-8' lc_ctype 'en_US.UTF-8';

   6. Exit the postgresql command line and log out of the postgres user:

      postgres=# \q
      $ exit

   7. Edit the /var/lib/pgsql/data/pg_hba.conf file as follows:
      • For each local database, replace the existing directives in the section starting with local at the bottom of the file with the following directives:

        host    database_name    user_name    0.0.0.0/0  md5
        host    database_name    user_name    ::0/0      md5

      • For each remote database:
        • Add the following line immediately underneath the line starting with Local at the bottom of the file, replacing X.X.X.X with the IP address of the Manager:

          host    database_name    user_name    X.X.X.X/32   md5

        • Allow TCP/IP connections to the database. Edit the /var/lib/pgsql/data/postgresql.conf file and add the following line:

          listen_addresses='*'

          This example configures the postgresql service to listen for connections on all interfaces. You can specify an interface by giving its IP address.
        • Open the default port used for PostgreSQL database connections, and save the updated firewall rules:

          # iptables -I INPUT 5 -p tcp -s Manager_IP_Address --dport 5432 -j ACCEPT
          # service iptables save

   8. Restart the postgresql service:

      # service postgresql restart

2. Copying the Backup Files to the New Manager

   Secure copy the backup files to the new Manager virtual machine. This example copies the files from an network storage server to which the files were copied as in Section 3.9.1, “Backing up the Self-Hosted Engine Manager Virtual Machine”. In this example, [Storage.example.com] is the fully qualified domain name of the storage server, [/backup/EngineBackupFiles] is the designated file path for the backup files on the storage server, and [/backup/] is the file path for the files to which the files will be copied on the new Manager.

   # scp -p [Storage.example.com:/backup/EngineBackupFiles] [/backup/]

3. Restore a complete backup or a database-only backup with the --change-db-credentials parameter to pass the credentials of the new database. The database_location for a database local to the Manager is localhost.

   Note

   The following examples use a --*password option for each database without specifying a password, which will prompt for a password for each database. Passwords can be supplied for these options in the command itself, however this is not recommended as the password will then be stored in the shell history. Alternatively, --*passfile=password_file options can be used for each database to securely pass the passwords to the engine-backup tool without the need for interactive prompts.
   • Restore a complete backup:

     # engine-backup --mode=restore --file=file_name --log=log_file_name --change-db-credentials --db-host=database_location --db-name=database_name --db-user=engine --db-password

     If Reports and Data Warehouse are also being restored as part of the complete backup, include the revised credentials for the two additional databases:

     engine-backup --mode=restore --file=file_name --log=log_file_name --change-db-credentials --db-host=database_location --db-name=database_name --db-user=engine --db-password --change-reports-db-credentials --reports-db-host=database_location --reports-db-name=database_name --reports-db-user=ovirt_engine_reports --reports-db-password --change-dwh-db-credentials --dwh-db-host=database_location --dwh-db-name=database_name --dwh-db-user=ovirt_engine_history --dwh-db-password

   • Restore a database-only backup by first restoring the configuration files backup and then restoring the database backup:

     # engine-backup --mode=restore --scope=files --file=file_name --log=log_file_name

     # engine-backup --mode=restore --scope=db --file=file_name --log=file_name --change-db-credentials --db-host=database_location --db-name=database_name --db-user=engine --db-password

     The example above restores a backup of the Manager database.

     # engine-backup --mode=restore --scope=reportsdb --file=file_name --log=file_name --change-reports-db-credentials --reports-db-host=database_location --reports-db-name=database_name --reports-db-user=ovirt_engine_reports --reports-db-password

     The example above restores a backup of the Reports database.

     # engine-backup --mode=restore --scope=dwhdb --file=file_name --log=file_name --change-dwh-db-credentials --dwh-db-host=database_location --dwh-db-name=database_name --dwh-db-user=ovirt_engine_history --dwh-db-password

     The example above restores a backup of the Data Warehouse database.
   If successful, the following output displays:

   You should now run engine-setup.
   Done.

4. Configuring the Manager

   Configure the restored Manager virtual machine. This process identifies the existing configuration settings and database content. Confirm the settings. Upon completion, the setup provides an SSH fingerprint and an internal Certificate Authority hash.

   # engine-setup

   [ INFO  ] Stage: Initializing
   [ INFO  ] Stage: Environment setup
   Configuration files: ['/etc/ovirt-engine-setup.conf.d/10-packaging.conf', '/etc/ovirt-engine-setup.conf.d/20-setup-ovirt-post.conf']
   Log file: /var/log/ovirt-engine/setup/ovirt-engine-setup-20140304075238.log
   Version: otopi-1.1.2 (otopi-1.1.2-1.el6ev)
   [ INFO  ] Stage: Environment packages setup
   [ INFO  ] Yum Downloading: rhel-65-zstream/primary_db 2.8 M(70%)
   [ INFO  ] Stage: Programs detection
   [ INFO  ] Stage: Environment setup
   [ INFO  ] Stage: Environment customization
            
             --== PACKAGES ==--
            
   [ INFO  ] Checking for product updates...
   [ INFO  ] No product updates found
            
             --== NETWORK CONFIGURATION ==--
            
   Setup can automatically configure the firewall on this system.
   Note: automatic configuration of the firewall may overwrite current settings.
   Do you want Setup to configure the firewall? (Yes, No) [Yes]: 
   [ INFO  ] iptables will be configured as firewall manager.
            
             --== DATABASE CONFIGURATION ==--
            
            
             --== OVIRT ENGINE CONFIGURATION ==--
            
             Skipping storing options as database already prepared
            
             --== PKI CONFIGURATION ==--
            
             PKI is already configured
            
             --== APACHE CONFIGURATION ==--
            
            
             --== SYSTEM CONFIGURATION ==--
            
            
             --== END OF CONFIGURATION ==--
            
   [ INFO  ] Stage: Setup validation
   [WARNING] Less than 16384MB of memory is available
   [ INFO  ] Cleaning stale zombie tasks
            
             --== CONFIGURATION PREVIEW ==--
            
             Database name                      : engine
             Database secured connection        : False
             Database host                      : X.X.X.X
             Database user name                 : engine
             Database host name validation      : False
             Database port                      : 5432
             NFS setup                          : True
             Firewall manager                   : iptables
             Update Firewall                    : True
             Configure WebSocket Proxy          : True
             Host FQDN                          : Manager.example.com
             NFS mount point                    : /var/lib/exports/iso
             Set application as default page    : True
             Configure Apache SSL               : True
            
             Please confirm installation settings (OK, Cancel) [OK]:

5. Removing the Host from the Restored Environment

   If the deployment of the restored self-hosted engine is on new hardware that has a unique name not present in the backed-up engine, skip this step. This step is only applicable to deployments occurring on the failover host, hosted_engine_1. Because this host was present in the environment at time the backup was created, it maintains a presence in the restored engine and must first be removed from the environment before final synchronization can take place.
   1. Log in to the Administration Portal.
   2. Click the Hosts tab. The failover host, hosted_engine_1, will be in maintenance mode and without a virtual load, as this was how it was prepared for the backup.
   3. Click Remove.
   4. Click Ok.

6. Synchronizing the Host and the Manager

   Return to the host and continue the hosted-engine deployment script by selecting option 1:

   (1) Continue setup - engine installation is complete

   [ INFO  ] Engine replied: DB Up!Welcome to Health Status!
   [ INFO  ] Waiting for the host to become operational in the engine. This may take several minutes...
   [ INFO  ] Still waiting for VDSM host to become operational...

   At this point, hosted_engine_1 will become visible in the Administration Portal with Installing and Initializing states before entering a Non Operational state. The host will continue to wait for VDSM host to become operational until it eventually times out. This happens because another host in the environment maintains the Storage Pool Manager (SPM) role and hosted_engine_1 cannot interact with the storage domain because the host with SPM is in a Non Responsive state. When this process times out, you are prompted to shut down the virtual machine to complete the deployment. When deployment is complete, the host can be manually placed into maintenance mode and activated through the Administration Portal.

   [ INFO  ] Still waiting for VDSM host to become operational...
   [ ERROR ] Timed out while waiting for host to start. Please check the logs.
   [ ERROR ] Unable to add hosted_engine_2 to the manager
             Please shutdown the VM allowing the system to launch it as a monitored service.
             The system will wait until the VM is down.

7. Shutting Down the Manager

   Shutdown the new Manager virtual machine.

   # shutdown -h now

8. Setup Confirmation

   Return to the host to confirm it has detected that the Manager virtual machine is down.

   [ INFO  ] Enabling and starting HA services
             Hosted Engine successfully set up
   [ INFO  ] Stage: Clean up
   [ INFO  ] Stage: Pre-termination
   [ INFO  ] Stage: Termination
   

9. Activating the Host

   1. Log in to the Administration Portal.
   2. Click the Hosts tab.
   3. Select hosted_engine_1 and click the Maintenance button. The host may take several maintenance before it enters maintenance mode.
   4. Click the Activate button.
   Once active, hosted_engine_1 immediately contends for SPM, and the storage domain and data center become active.

10. Migrating Virtual Machines to the Active Host

    Migrate virtual machines to the active host by manually fencing the Non Responsive hosts. In the Administration Portal, right-click the hosts and select Confirm 'Host has been Rebooted'.
    Any virtual machines that were running on that host at the time of the backup will now be removed from that host, and move from an Unknown state to a Down state. These virtual machines can now be run on hosted_engine_1. The host that was fenced can now be forcefully removed using the REST API.

1. Fencing the Non-Operational Host

   In the Administration Portal, right-click the hosts and select Confirm 'Host has been Rebooted'.
   Any virtual machines that were running on that host at the time of the backup will now be removed from that host, and move from an Unknown state to a Down state. The host that was fenced can now be forcefully removed using the REST API.

2. Retrieving the Manager Certificate Authority

   Connect to the Manager virtual machine and use the command line to perform the following requests with cURL.
   Use a GET request to retrieve the Manager Certificate Authority (CA) certificate for use in all future API requests. In the following example, the --output option is used to designate the file hosted-engine.ca as the output for the Manager CA certificate. The --insecure option means that this initial request will be without a certificate.

   # curl --output hosted-engine.ca --insecure https://[Manager.example.com]/ca.crt

3. Retrieving the GUID of the Host to be Removed

   Use a GET request on the hosts collection to retrieve the Global Unique Identifier (GUID) for the host to be removed. The following example specifies this as a GET request, and includes the Manager CA certificate file. The admin@internal user is used for authentication, the password for which will be prompted once the command is executed.

   # curl --request GET --cacert hosted-engine.ca --user admin@internal https://[Manager.example.com]/api/hosts

   This request will return information for all of the hosts in the environment. The host GUID is a hexidecimal string associated with the host name. For more information on the Red Hat Enterprise Virtualization REST API, see the Red Hat Enterprise Virtualization Technical Guide.

4. Removing the Fenced Host

   Use a DELETE request using the GUID of the fenced host to remove the host from the environment. In addition to the previously used options this example specifies headers to specify that the request is to be sent and returned using eXtensible Markup Language (XML), and the body in XML that sets the force action to be true.

   curl --request DELETE --cacert hosted-engine.ca --user admin@internal --header "Content-Type: application/xml" --header "Accept: application/xml" --data "<action><force>true</force></action>" https://[Manager.example.com]/api/hosts/ecde42b0-de2f-48fe-aa23-1ebd5196b4a5

   This DELETE request can be used to removed every fenced host in the self-hosted engine environment, as long as the appropriate GUID is specified.

Procedure 3.9. Adding the host

1. Install the ovirt-hosted-engine-setup package.

   # yum install ovirt-hosted-engine-setup

2. Configure the host with the deployment command.

   # hosted-engine --deploy

   If running the hosted-engine deployment script over a network, it is recommended to use the screen window manager to avoid losing the session in case of network or terminal disruption. Install the screen package first if not installed.

   # screen hosted-engine --deploy

3. Configuring Storage

   Select the type of storage to use.

   During customization use CTRL-D to abort.
   Please specify the storage you would like to use (iscsi, nfs3, nfs4)[nfs3]:

   • For NFS storage types, specify the full address, using either the FQDN or IP address, and path name of the shared storage domain.

     Please specify the full shared storage connection path to use (example: host:/path): storage.example.com:/hosted_engine/nfs

   • For iSCSI, specify the iSCSI portal IP address, port, user name and password, and select a target name from the auto-detected list:

     Please specify the iSCSI portal IP address:           
     Please specify the iSCSI portal port [3260]:           
     Please specify the iSCSI portal user:           
     Please specify the iSCSI portal password:
     Please specify the target name (auto-detected values) [default]:

4. Detecting the Self-Hosted Engine

   The hosted-engine script detects that the shared storage is being used and asks if this is an additional host setup. You are then prompted for the host ID, which must be an integer not already assigned to a host in the environment.

   The specified storage location already contains a data domain. Is this an additional host setup (Yes, No)[Yes]? 
   [ INFO  ] Installing on additional host
   Please specify the Host ID [Must be integer, default: 2]:
   

5. Configuring the System

   The hosted-engine script uses the answer file generated by the original hosted-engine setup. To achieve this, the script requires the FQDN or IP address and the password of the root user of that host so as to access and secure-copy the answer file to the additional host.

   [WARNING] A configuration file must be supplied to deploy Hosted Engine on an additional host.
   The answer file may be fetched from the first host using scp.
   If you do not want to download it automatically you can abort the setup answering no to the following question.
   Do you want to scp the answer file from the first host? (Yes, No)[Yes]:       
   Please provide the FQDN or IP of the first host:           
   Enter 'root' user password for host [hosted_engine_1.example.com]: 
   [ INFO  ] Answer file successfully downloaded
   

6. Configuring the Hosted Engine

   Specify the name for the additional host to be identified in the Red Hat Enterprise Virtualization environment, and the password for the admin@internal user. The name must not already be in use by a host in the environment.

   Enter the name which will be used to identify this host inside the Administrator Portal [hosted_engine_2]:           
   Enter 'admin@internal' user password that will be used for accessing the Administrator Portal: 
   Confirm 'admin@internal' user password:
   

7. Configuration Preview

   Before proceeding, the hosted-engine script displays the configuration values you have entered, and prompts for confirmation to proceed with these values.

   Bridge interface                   : eth1
   Engine FQDN                        : HostedEngine-VM.example.com
   Bridge name                        : rhevm
   SSH daemon port                    : 22
   Firewall manager                   : iptables
   Gateway address                    : X.X.X.X
   Host name for web application      : hosted_engine_2
   Host ID                            : 2
   Image size GB                      : 25
   Storage connection                 : storage.example.com:/hosted_engine/nfs
   Console type                       : vnc
   Memory size MB                     : 4096
   MAC address                        : 00:16:3e:05:95:50
   Boot type                          : disk
   Number of CPUs                     : 2
   CPU Type                           : model_Penryn
            
   Please confirm installation settings (Yes, No)[Yes]:
   

8. Confirming Engine Installation Complete

   The additional host will contact the Manager and hosted_engine_1, after which the script will prompt for a selection. Continue by selection option 1.

   [ INFO  ] Stage: Closing up
             To continue make a selection from the options below:
             (1) Continue setup - engine installation is complete
             (2) Power off and restart the VM
             (3) Abort setup
   
             (1, 2, 3)[1]:

9. [ INFO  ] Engine replied: DB Up!Welcome to Health Status!
   [ INFO  ] Waiting for the host to become operational in the engine. This may take several minutes...

   At this point, the host will become visible in the Administration Portal with Installing and Initializing states before entering a Non Operational state. The host will continue to wait for VDSM host to become operational until it eventually times out.

   [ INFO  ] Still waiting for VDSM host to become operational...
   [ INFO  ] Still waiting for VDSM host to become operational...
   [ ERROR ] Timed out while waiting for host to start. Please check the logs.
   [ ERROR ] Unable to add hosted_engine_1 to the manager
   [ INFO  ] Enabling and starting HA services
             Hosted Engine successfully set up
   [ INFO  ] Stage: Clean up
   [ INFO  ] Generating answer file '/etc/ovirt-hosted-engine/answers.conf'
   [ INFO  ] Stage: Pre-termination
   [ INFO  ] Stage: Termination

10. Activating the Host

    1. Log in to the Administration Portal.
    2. Click the Hosts tab and select the host to activate.
    3. Click the Activate button.

Procedure 5.1. Checking for Red Hat Enterprise Virtualization Manager Updates

1. Run the following command on the machine on which the Red Hat Enterprise Virtualization Manager is installed:

   # engine-upgrade-check

2. • If there are no updates are available, the command will output the text No upgrade:

     # engine-upgrade-check
     VERB: queue package rhevm-setup for update
     VERB: package rhevm-setup queued
     VERB: Building transaction
     VERB: Empty transaction
     VERB: Transaction Summary:
     No upgrade

   • If updates are available, the command will list the packages to be updated:

     # engine-upgrade-check
     VERB: queue package rhevm-setup for update
     VERB: package rhevm-setup queued
     VERB: Building transaction
     VERB: Transaction built
     VERB: Transaction Summary:
     VERB:     updated    - rhevm-lib-3.3.2-0.50.el6ev.noarch
     VERB:     update     - rhevm-lib-3.4.0-0.13.el6ev.noarch
     VERB:     updated    - rhevm-setup-3.3.2-0.50.el6ev.noarch
     VERB:     update     - rhevm-setup-3.4.0-0.13.el6ev.noarch
     VERB:     install    - rhevm-setup-base-3.4.0-0.13.el6ev.noarch
     VERB:     install    - rhevm-setup-plugin-ovirt-engine-3.4.0-0.13.el6ev.noarch
     VERB:     updated    - rhevm-setup-plugins-3.3.1-1.el6ev.noarch
     VERB:     update     - rhevm-setup-plugins-3.4.0-0.5.el6ev.noarch
     Upgrade available
     
     Upgrade available

Procedure 5.2. Updating Red Hat Enterprise Virtualization Manager

1. Run the following command to update the rhevm-setup package:

   # yum update rhevm-setup

2. Run the following command to update the Red Hat Enterprise Virtualization Manager:

   # engine-setup

Procedure 5.3. Updating Red Hat Enterprise Virtualization Hypervisors

1. Log in to the system hosting Red Hat Enterprise Virtualization Manager as the root user.
2. Enable the Red Hat Enterprise Virtualization Hypervisor (v.6 x86_64) repository:

   • With RHN Classic:

     # rhn-channel --add --channel=rhel-x86_64-server-6-rhevh

   • With Subscription Manager, attach a Red Hat Enterprise Virtualization entitlement and run the following command:

     # subscription-manager repos --enable=rhel-6-server-rhevh-rpms

3. Run the yum command with the update rhev-hypervisor6 parameters to ensure that you have the most recent version of the rhev-hypervisor6 package installed.

   # yum update rhev-hypervisor6

4. Use your web browser to log in to the Administration Portal as a Red Hat Enterprise Virtualization administrative user.
5. Click the Hosts tab, and then select the host that you intend to upgrade. If the host is not displayed, or the list of hosts is too long to filter visually, perform a search to locate the host.
6. With the host selected, click the General tab in the details pane.
   • If the host requires updating, an alert message indicates that a new version of the Red Hat Enterprise Virtualization Hypervisor is available.
   • If the host does not require updating, no alert message is displayed and no further action is required.
7. Ensure the host remains selected and click the Maintenance button, if the host is not already in maintenance mode. 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 link which when clicked will reinstall or upgrade the host.
8. Ensure that the host remains selected, and that you are on the General tab of the details pane. Click the Upgrade link to open the Install Host window.
9. Select rhev-hypervisor.iso, which is symbolically linked to the most recent hypervisor image.
10. Click OK to update and reinstall the host. The dialog closes, the details of the host are updated in the Hosts tab, and the status changes.
    The host status will transition through these stages:

    • Installing
    • Reboot
    • Non Responsive
    • Up.

    These are all expected, and each stage will take some time.
11. Once successfully updated, the host displays a status of Up. Any virtual machines that were migrated off the host, are at this point able to be migrated back to it.

    Important

    After a Red Hat Enterprise Virtualization Hypervisor is successfully registered to the Red Hat Enterprise Virtualization Manager and then upgraded, it may erroneously appear in the Administration Portal with the status of Install Failed. Click on the Activate button, and the hypervisor will change to an Up status and be ready for use.

Procedure 5.4. Updating Red Hat Enterprise Linux Hosts

1. From the Administration Portal, click the Hosts tab and select the host to be updated. Click Maintenance to place it into maintenance mode.
2. On the Red Hat Enterprise Linux host, run the following command:

   # yum update

3. Restart the host to ensure all updates are correctly applied.

Procedure 5.5. Updating the Red Hat Enterprise Virtualization Guest Tools

1. Run the following command on the machine on which the Red Hat Enterprise Virtualization Manager is installed:

   # yum update -y rhev-guest-tools-iso*
   

2. Run the following command to upload the ISO file to your ISO domain, replacing [ISODomain] with the name of your ISO domain:

   engine-iso-uploader --iso-domain=[ISODomain] upload /usr/share/rhev-guest-tools-iso/rhev-tools-setup.iso
   

   Note

   The rhev-tools-setup.iso file is a symbolic link to the most recently updated ISO file. The link is automatically changed to point to the newest ISO file every time you update the rhev-guest-tools-iso package.
3. Use the Administration Portal, User Portal, or REST API to attach the rhev-tools-setup.iso file to each of your virtual machines and upgrade the tools installed on each guest using the installation program on the ISO.

Procedure 5.6. Upgrading to Red Hat Enterprise Virtualization Manager 3.4

1. Subscribe the system on which the Red Hat Enterprise Virtualization Manager is installed to the required channels and entitlements for receiving Red Hat Enterprise Virtualization Manager 3.4 packages.
   • With RHN Classic:

     # rhn-channel --add --channel=rhel-x86_64-server-6-rhevm-3.4

   • With Subscription Manager:

     # yum-config-manager --enable rhel-6-server-rhevm-3.4-rpms

2. Run the following command to ensure you have the most recent version of engine-setup by updating the rhevm-setup package.

   # yum update rhevm-setup

3. If you have installed Reports and the Data Warehouse, run the following command to ensure you have the most recent version of the rhevm-reports-setup and rhevm-dwh-setup packages:

   # yum install rhevm-reports-setup rhevm-dwh-setup

4. Run the following command and follow the prompts to upgrade the Red Hat Enterprise Virtualization Manager:

   # engine-setup

5. Remove or disable the Red Hat Enterprise Virtualization Manager 3.3 channel to ensure the system does not use any Red Hat Enterprise Virtualization Manager 3.3 packages.
   • With RHN Classic:

     # rhn-channel --remove --channel=rhel-x86_64-server-6-rhevm-3.3

   • With Subscription Manager:

     # yum-config-manager --disable rhel-6-server-rhevm-3.3-rpms

6. Run the following command to ensure all packages are up to date:

   # yum update

Procedure 5.7. Upgrading to Red Hat Enterprise Virtualization Manager 3.3

1. Subscribe the system to the required channels and entitlements for receiving Red Hat Enterprise Virtualization Manager 3.3 packages.
   Subscription Manager

   Red Hat Enterprise Virtualization 3.3 packages are provided by the rhel-6-server-rhevm-3.3-rpms repository associated with the Red Hat Enterprise Virtualization entitlement. Use the yum-config-manager command to enable the repository in your yum configuration.

   # yum-config-manager --enable rhel-6-server-rhevm-3.3-rpms

   Red Hat Network Classic

   The Red Hat Enterprise Virtualization 3.3 packages are provided by the Red Hat Enterprise Virtualization Manager (v.3.3 x86_64) channel, also referred to as rhel-x86_64-server-6-rhevm-3.3 in Red Hat Network Classic. Use the rhn-channel command or the Red Hat Network web interface to subscribe to the Red Hat Enterprise Virtualization Manager (v.3.3 x86_64) channel:

   # rhn-channel --add --channel=rhel-x86_64-server-6-rhevm-3.3

2. Update the rhevm-setup package to ensure you have the most recent version of engine-setup.

   # yum update rhevm-setup

3. Run the engine-setup command and follow the prompts to upgrade Red Hat Enterprise Virtualization Manager.

   # engine-setup
   [ INFO  ] Stage: Initializing
             
             Welcome to the RHEV 3.3.0 upgrade.
             Please read the following knowledge article for known issues and
             updated instructions before proceeding with the upgrade.
             RHEV 3.3.0 Upgrade Guide: Tips, Considerations and Roll-back Issues
                 https://access.redhat.com/site/articles/408623
             Would you like to continue with the upgrade? (Yes, No) [Yes]:

4. Remove Red Hat Enterprise Virtualization Manager 3.2 channels and entitlements to ensure the system does not use any Red Hat Enterprise Virtualization Manager 3.2 packages.
   Subscription Manager

   Use the yum-config-manager command to disable the Red Hat Enterprise Virtualization 3.2 repository in your yum configuration.

   # yum-config-manager --disable rhel-6-server-rhevm-3.2-rpms

   Red Hat Network Classic

   Use the rhn-channel command or the Red Hat Network web interface to remove the Red Hat Enterprise Virtualization Manager (v.3.2 x86_64) channels.

   # rhn-channel --remove --channel=rhel-x86_64-server-6-rhevm-3.2

5. Run the following command to ensure all packages related to Red Hat Enterprise Virtualization are up to date:

   # yum update

   In particular, if you are using the JBoss Application Server from JBoss Enterprise Application Platform 6.0.1, you must run the above command to upgrade to Enterprise Application Platform 6.1.

Procedure 5.8. Upgrading to Red Hat Enterprise Virtualization Manager 3.2

1. Add Red Hat Enterprise Virtualization 3.2 Subscription

   Ensure that the system is subscribed to the required channels and entitlements to receive Red Hat Enterprise Virtualization Manager 3.2 packages. This procedure assumes that the system is already subscribed to required channels and entitlements to receive Red Hat Enterprise Virtualization 3.1 packages. These must also be available to complete the upgrade process.
   Certificate-based Red Hat Network

   The Red Hat Enterprise Virtualization 3.2 packages are provided by the rhel-6-server-rhevm-3.2-rpms repository associated with the Red Hat Enterprise Virtualization entitlement. Use the yum-config-manager command to enable the repository in your yum configuration. The yum-config-manager command must be run while logged in as the root user.

   # yum-config-manager --enable rhel-6-server-rhevm-3.2-rpms

   Red Hat Network Classic

   The Red Hat Enterprise Virtualization 3.2 packages are provided by the Red Hat Enterprise Virtualization Manager (v.3.2 x86_64) channel, also referred to as rhel-x86_64-server-6-rhevm-3.2 in Red Hat Network Classic.

   rhn-channel --add --channel=rhel-x86_64-server-6-rhevm-3.2

   Use the rhn-channel command, or the Red Hat Network Web Interface, to subscribe to the Red Hat Enterprise Virtualization Manager (v.3.2 x86_64) channel.

2. Remove Enterprise Virtualization 3.1 Subscription

   Ensure that the system does not use any Red Hat Enterprise Virtualization Manager 3.1 packages by removing the Red Hat Enterprise Vitulization Manager 3.1 channels and entitlements.
   Certificate-based Red Hat Network

   Use the yum-config-manager command to disable the Red Hat Enterprise Virtualization 3.1 repository in your yum configuration. The yum-config-manager command must be run while logged in as the root user.

   # yum-config-manager --disablerepo=rhel-6-server-rhevm-3.1-rpms

   Red Hat Network Classic

   Use the rhn-channel command, or the Red Hat Network Web Interface, to remove the Red Hat Enterprise Virtualization Manager (v.3.1 x86_64) channels.

   # rhn-channel --remove --channel=rhel-6-server-rhevm-3.1

3. Update the rhevm-setup Package

   To ensure that you have the most recent version of the rhevm-upgrade command installed you must update the rhevm-setup package. Log in as the root user and use yum to update the rhevm-setup package.

   # yum update rhevm-setup

4. Run the rhevm-upgrade Command

   To upgrade Red Hat Enterprise Virtualization Manager run the rhevm-upgrade command. You must be logged in as the root user to run this command.

   # rhevm-upgrade
   Loaded plugins: product-id, rhnplugin
   Info: RHEV Manager 3.1 to 3.2 upgrade detected
   Checking pre-upgrade conditions...(This may take several minutes)
   

5. If the ipa-server package is installed then an error message is displayed. Red Hat Enterprise Virtualization Manager 3.2 does not support installation on the same machine as Identity Management (IdM).

   Error: IPA was found to be installed on this machine. Red Hat Enterprise Virtualization Manager 3.2 does not support installing IPA on the same machine. Please remove ipa packages before you continue.
   

   To resolve this issue you must migrate the IdM configuration to another system before re-attempting the upgrade. For further information see https://access.redhat.com/knowledge/articles/233143.

Procedure 5.9. Upgrading to Red Hat Enterprise Virtualization Manager 3.1

1. Red Hat JBoss Enterprise Application Platform  6 Subscription

   Ensure that the system is subscribed to the required channels and entitlements to receive Red Hat JBoss Enterprise Application Platform  6 packages. Red Hat JBoss Enterprise Application Platform  6 is a required dependency of Red Hat Enterprise Virtualization Manager 3.1.
   Certificate-based Red Hat Network

   The Red Hat JBoss Enterprise Application Platform  6 packages are provided by the Red Hat JBoss Enterprise Application Platform entitlement in certificate-based Red Hat Network.

   Use the subscription-manager command to ensure that the system is subscribed to the Red Hat JBoss Enterprise Application Platform entitlement.

   # subscription-manager list

   Red Hat Network Classic

   The Red Hat JBoss Enterprise Application Platform  6 packages are provided by the Red Hat JBoss Application Platform (v 6) for 6Server x86_64 channel, also referred to as jbappplatform-6-x86_64-server-6-rpm, in Red Hat Network Classic. The Channel Entitlement Name for this channel is Red Hat JBoss Enterprise Application Platform (v 4, zip format).

   Use the rhn-channel command, or the Red Hat Network Web Interface, to subscribe to the Red Hat JBoss Application Platform (v 6) for 6Server x86_64 channel.

2. Add Red Hat Enterprise Virtualization 3.1 Subscription

   Ensure that the system is subscribed to the required channels and entitlements to receive Red Hat Enterprise Virtualization Manager 3.1 packages.
   Certificate-based Red Hat Network

   The Red Hat Enterprise Virtualization 3.1 packages are provided by the rhel-6-server-rhevm-3.1-rpms repository associated with the Red Hat Enterprise Virtualization entitlement. Use the yum-config-manager command to enable the repository in your yum configuration. The yum-config-manager command must be run while logged in as the root user.

   # yum-config-manager --enable rhel-6-server-rhevm-3.1-rpms

   Red Hat Network Classic

   The Red Hat Enterprise Virtualization 3.1 packages are provided by the Red Hat Enterprise Virtualization Manager (v.3.1 x86_64) channel, also referred to as rhel-x86_64-server-6-rhevm-3.1 in Red Hat Network Classic.

   Use the rhn-channel command, or the Red Hat Network Web Interface, to subscribe to the Red Hat Enterprise Virtualization Manager (v.3.1 x86_64) channel.

3. Remove Red Hat Enterprise Virtualization 3.0 Subscription

   Ensure that the system does not use any Red Hat Enterprise Virtualization Manager 3.0 packages by removing the Red Hat Enterprise Virtualization Manager 3.0 channels and entitlements.
   Certificate-based Red Hat Network

   Use the yum-config-manager command to disable the Red Hat Enterprise Virtualization 3.0 repositories in your yum configuration. The yum-config-manager command must be run while logged in as the root user.

   # yum-config-manager --disablerepo=rhel-6-server-rhevm-3-rpms

   # yum-config-manager --disablerepo=jb-eap-5-for-rhel-6-server-rpms

   Red Hat Network Classic

   Use the rhn-channel command, or the Red Hat Network Web Interface, to remove the Red Hat Enterprise Virtualization Manager (v.3.0 x86_64) channels.

   # rhn-channel --remove --channel=rhel-6-server-rhevm-3

   # rhn-channel --remove --channel=jbappplatform-5-x86_64-server-6-rpm

4. Update the rhevm-setup Package

   To ensure that you have the most recent version of the rhevm-upgrade command installed you must update the rhevm-setup package. Log in as the root user and use yum to update the rhevm-setup package.

   # yum update rhevm-setup

5. Run the rhevm-upgrade Command

   To upgrade Red Hat Enterprise Virtualization Manager run the rhevm-upgrade command. You must be logged in as the root user to run this command.

   # rhevm-upgrade
   Loaded plugins: product-id, rhnplugin
   Info: RHEV Manager 3.0 to 3.1 upgrade detected
   Checking pre-upgrade conditions...(This may take several minutes)
   

6. If the ipa-server package is installed then an error message is displayed. Red Hat Enterprise Virtualization Manager 3.1 does not support installation on the same machine as Identity Management (IdM).

   Error: IPA was found to be installed on this machine. Red Hat Enterprise Virtualization Manager 3.1 does not support installing IPA on the same machine. Please remove ipa packages before you continue.
   

   To resolve this issue you must migrate the IdM configuration to another system before re-attempting the upgrade. For further information see https://access.redhat.com/knowledge/articles/233143.
7. A list of packages that depend on Red Hat JBoss Enterprise Application Platform  5 is displayed. These packages must be removed to install Red Hat JBoss Enterprise Application Platform  6, required by Red Hat Enterprise Virtualization Manager  3.1.

    Warning: the following packages will be removed if you proceed with the upgrade:
   
       * objectweb-asm
   
    Would you like to proceed? (yes|no):
   

   You must enter yes to proceed with the upgrade, removing the listed packages.

Procedure 5.10. Changing the Cluster Compatibility Version

1. Log in to the Administration Portal as the administrative user. By default this is the admin user.
2. Click the Clusters tab.
3. Select the cluster to change from the list displayed. If the list of clusters is too long to filter visually then perform a search to locate the desired cluster.
4. Click the Edit button.
5. Change the Compatibility Version to the desired value.
6. Click OK to open the Change Cluster Compatibility Version confirmation window.
7. Click OK to confirm.

Procedure 5.11. Changing the Data Center Compatibility Version

1. Log in to the Administration Portal as the administrative user. By default this is the admin user.
2. Click the Data Centers tab.
3. Select the data center to change from the list displayed. If the list of data centers is too long to filter visually then perform a search to locate the desired data center.
4. Click the Edit button.
5. Change the Compatibility Version to the desired value.
6. Click OK.

Procedure 7.2. Preparing USB Installation Media Using livecd-iso-to-disk

1. Run the following command to ensure you have the latest version of the Red Hat Enterprise Virtualization Hypervisor disk image:

   # yum update rhev-hypervisor6

2. Use the livecd-iso-to-disk utility to write the disk image to a USB storage device.

   Example 7.1. Use of livecd-iso-to-disk

   This example demonstrates the use of livecd-iso-to-disk to write a Red Hat Enterprise Virtualization Hypervisor disk image to a USB storage device named /dev/sdc and make that USB storage device bootable.

   # livecd-iso-to-disk --format --reset-mbr /usr/share/rhev-hypervisor/rhev-hypervisor.iso /dev/sdc
   Verifying image...
   /usr/share/rhev-hypervisor/rhev-hypervisor.iso:   eccc12a0530b9f22e5ba62b848922309
   Fragment sums: 8688f5473e9c176a73f7a37499358557e6c397c9ce2dafb5eca5498fb586
   Fragment count: 20
   Press [Esc] to abort check.
   Checking: 100.0%
   
   The media check is complete, the result is: PASS.
   
   It is OK to use this media.
   
   WARNING: THIS WILL DESTROY ANY DATA ON /dev/sdc!!!
   Press Enter to continue or ctrl-c to abort
   
   /dev/sdc: 2 bytes were erased at offset 0x000001fe (dos): 55 aa
   Waiting for devices to settle...
   mke2fs 1.42.7 (21-Jan-2013)
   Filesystem label=LIVE
   OS type: Linux
   Block size=4096 (log=2)
   Fragment size=4096 (log=2)
   Stride=0 blocks, Stripe width=0 blocks
   488640 inodes, 1953280 blocks
   97664 blocks (5.00%) reserved for the super user
   First data block=0
   Maximum filesystem blocks=2000683008
   60 block groups
   32768 blocks per group, 32768 fragments per group
   8144 inodes per group
   Superblock backups stored on blocks: 
           32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632
   
   Allocating group tables: done                            
   Writing inode tables: done                            
   Creating journal (32768 blocks): done
   Writing superblocks and filesystem accounting information: done 
   
   Copying live image to target device.
   squashfs.img
      163360768 100%  184.33MB/s    0:00:00 (xfer#1, to-check=0/1)
   
   sent 163380785 bytes  received 31 bytes  108920544.00 bytes/sec
   total size is 163360768  speedup is 1.00
   osmin.img
           4096 100%    0.00kB/s    0:00:00 (xfer#1, to-check=0/1)
   
   sent 4169 bytes  received 31 bytes  8400.00 bytes/sec
   total size is 4096  speedup is 0.98
   Updating boot config file
   Installing boot loader
   /media/tgttmp.q6aZdS/syslinux is device /dev/sdc
   Target device is now set up with a Live image!
   

Procedure 7.3. Preparing USB Installation Media using dd on Linux Systems

1. Run the following command to ensure you have the latest version of the Red Hat Enterprise Virtualization Hypervisor disk image:

   # yum update rhev-hypervisor6

2. Use the dd utility to write the disk image to a USB storage device.

   Example 7.2. Use of dd

   This example uses a USB storage device named /dev/sdc.

   # dd if=/usr/share/rhev-hypervisor/rhev-hypervisor.iso of=/dev/sdc
   243712+0 records in
   243712+0 records out
   124780544 bytes (125 MB) copied, 56.3009 s, 2.2 MB/s
   

   Warning

   The dd utility will overwrite all data on the device specified by the of parameter. Ensure you have specified the correct device and that the device contains no valuable data before using the dd utility.

Procedure 7.4. Preparing USB Installation Media using dd on Windows Systems

1. Open http://www.redhat.com/services/custom/cygwin/ in a web browser and click 32-bit Cygwin to download the 32-bit version of Red Hat Cygwin, or 64-bit Cygwin to download the 64-bit version of Red Hat Cygwin.
2. Run the downloaded executable as a user with administrator privileges to open the Red Hat Cygwin installation program.
3. Follow the prompts to install Red Hat Cygwin. The Coreutils package in the Base package group provides the dd utility. This package is automatically selected for installation.
4. Copy the rhev-hypervisor.iso file downloaded from the Red Hat Network to C:\rhev-hypervisor.iso.
5. Run the Red Hat Cygwin application from the desktop as a user with administrative privileges.

   Important

   On the Windows 7 and Windows Server 2008, you must right-click the Red Hat Cygwin icon and select the Run as Administrator option to ensure the application runs with the correct permissions.
6. In the terminal, run the following command to view the drives and partitions currently visible to the system:

   $ cat /proc/partitions

   Example 7.3. View of Disk Partitions Attached to System

   Administrator@test /
   $ cat /proc/partitions
   major minor  #blocks  name
       8     0  15728640 sda
       8     1    102400 sda1
       8     2  15624192 sda2

7. Attach the USB storage device to which the Red Hat Enterprise Virtualization Hypervisor disk image will be written to the system. Run the cat /proc/partitions command again and compare the output to that of the previous output. A new entry will appear that designates the USB storage device.

   Example 7.4. View of Disk Partitions Attached to System

   Administrator@test /
   $ cat /proc/partitions
   major minor  #blocks  name
       8     0  15728640 sda
       8     1    102400 sda1
       8     2  15624192 sda2
       8    16    524288 sdb
   

8. Use the dd utility to write the rhev-hypervisor.iso file to the USB storage device. The following example uses a USB storage device named /dev/sdb. Replace sdb with the correct device name for the USB storage device to be used.

   Example 7.5. Use of dd Utility Under Red Hat Cygwin

   Administrator@test /
   $ dd if=/cygdrive/c/rhev-hypervisor.iso of=/dev/sdb& pid=$!
   

   Warning

   The dd utility will overwrite all data on the device specified by the of parameter. Ensure you have specified the correct device and that the device contains no valuable data before using the dd utility.

   Note

   Writing disk images to USB storage devices with the version of the dd utility included with Red Hat Cygwin can take significantly longer than the equivalent on other platforms. You can run the following command to view the progress of the operation:

   $ kill -USR1 $pid

Procedure 7.5. Preparing Optical Hypervisor Installation Media

1. Run the following command to install the wodim package and dependencies:

   # yum install wodim
   

2. Insert a blank CD-ROM or DVD into your CD or DVD writer.
3. Run the following command to write the Red Hat Enterprise Virtualization Hypervisor disk image to the disc:

   wodim dev=[device] [image]

   Example 7.6. Use of the wodim Utility

   This example uses the first CD-RW (/dev/cdrw) device available and the default hypervisor image location.

   # wodim dev=/dev/cdrw /usr/share/rhev-hypervisor/rhev-hypervisor.iso
   

Procedure 7.6. Booting the Hypervisor from USB Installation Media

1. Enter the BIOS menu to enable USB storage device booting if not already enabled.
   1. Enable USB booting if this feature is disabled.
   2. Set booting USB storage devices to be first boot device.
   3. Shut down the system.
2. Insert the USB storage device that contains the hypervisor boot image.
3. Restart the system.

Procedure 7.7. Booting the Hypervisor from Optical Installation Media

1. Ensure that the system's BIOS is configured to boot from the CD-ROM or DVD-ROM drive first. For many systems this the default.

   Note

   Refer to your manufacturer's manuals for further information on modifying the system's BIOS boot configuration.
2. Insert the Hypervisor CD-ROM in the CD-ROM or DVD-ROM drive.
3. Reboot the system.

Procedure 7.8. Starting the Installation Program

1. From the boot splash screen, press any key to open the boot menu.
   

   Figure 7.1. The boot splash screen

2. From the boot menu, use the directional keys to select Install or Upgrade, Install (Basic Video), or Install or Upgrade with Serial Console.
   

   Figure 7.2. The boot menu

   The full list of options in the boot menu is as follows:

   Install or Upgrade

   Install or upgrade the hypervisor.

   Install (Basic Video)

   Install or upgrade the Hypervisor in basic video mode.

   Install or Upgrade with Serial Console

   Install or upgrade the hypervisor while redirecting the console to a serial device attached to /dev/ttyS0.

   Reinstall

   Reinstall the hypervisor.

   Reinstall (Basic Video)

   Reinstall the hypervisor in basic video mode.

   Reinstall with Serial Console

   Reinstall the hypervisor while redirecting the console to a serial device attached to /dev/ttyS0.

   Uninstall

   Uninstall the hypervisor.

   Boot from Local Drive

   Boot the operating system installed on the first local drive.

3. Press the Enter key.

Procedure 7.9. Installing the Hypervisor Interactively

1. Use the prepared boot media to boot the machine on which the Hypervisor is to be installed.
2. Select Install Hypervisor and press Enter to begin the installation process.
3. The first screen that appears allows you to configure the appropriate keyboard layout for your locale. Use the arrow keys to highlight the appropriate option and press Enter to save your selection.

   Example 7.7. Keyboard Layout Configuration

   Keyboard Layout Selection
   				
   Available Keyboard Layouts
   Swiss German (latin1)
   Turkish
   U.S. English
   U.S. International
   ...
   
   (Hit enter to select a layout)
   
   <Quit>     <Back>     <Continue>

4. The installation script automatically detects all disks attached to the system. This information is used to assist with selection of the boot and installation disks that the Hypervisor will use. Each entry displayed on these screens indicates the Location, Device Name, and Size of the disks.

   1. Boot Disk

      The first disk selection screen is used to select the disk from which the Hypervisor will boot. The Hypervisor's boot loader will be installed to the Master Boot Record (MBR) of the disk that is selected on this screen. The Hypervisor attempts to automatically detect the disks attached to the system and presents the list from which to choose the boot device. Alternatively, you can manually select a device by specifying a block device name using the Other Device option.

      Important

      The selected disk must be identified as a boot device and appear in the boot order either in the system's BIOS or in a pre-existing boot loader.

      • Automatically Detected Device Selection

        1. Select the entry for the disk the Hypervisor is to boot from in the list and press Enter.
        2. Select the disk and press Enter. This action saves the boot device selection and starts the next step of installation.

      • Manual Device Selection

        1. Select Other device and press Enter.
        2. When prompted to Please select the disk to use for booting RHEV-H, enter the name of the block device from which the Hypervisor should boot.

           Example 7.8. Other Device Selection

           Please select the disk to use for booting RHEV-H
           /dev/sda
           

        3. Press Enter. This action saves the boot device selection and starts the next step of installation.
   2. The disk or disks selected for installation will be those to which the Hypervisor itself is installed. The Hypervisor attempts to automatically detect the disks attached to the system and presents the list from which installation devices are chosen.

      Warning

      All data on the selected storage devices will be destroyed.
      1. Select each disk on which the Hypervisor is to be installed and press Space to toggle it to enabled. Where other devices are to be used for installation, either solely or in addition to those which are listed automatically, use Other Device.
      2. Select the Continue button and press Enter to continue.
      3. Where the Other Device option was specified, a further prompt will appear. Enter the name of each additional block device to use for Hypervisor installation, separated by a comma. Once all required disks have been selected, select the <Continue> button and press Enter.

         Example 7.9. Other Device Selection

         Please enter one or more disks to use for installing RHEV-H. Multiple devices can be separated by comma.
         Device path:   /dev/mmcblk0,/dev/mmcblk1______________
         

      Once the installation disks have been selected, the next stage of the installation starts.
5. The next screen allows you to configure storage for the Hypervisor.
   1. Select or clear the Fill disk with Data partition check box. Clearing this text box displays a field showing the remaining space on the drive and allows you to specify the amount of space to be allocated to data storage.
   2. Enter the preferred values for Swap, Config, and Logging.
   3. If you selected the Fill disk with Data partition check box, the Data field is automatically set to 0. If the check box was cleared, you can enter a whole number up to the value of the Remaining Space field. Entering a value of -1 fills all remaining space.
6. The Hypervisor requires a password be set to protect local console access to the admin user. The installation script prompts you to enter the preferred password in both the Password and Confirm Password fields.
   Use a strong password. Strong passwords comprise a mix of uppercase, lowercase, numeric, and punctuation characters. They are six or more characters long and do not contain dictionary words.
   Once a strong password has been entered, select <Install> and press Enter to install the Hypervisor on the selected disks.

Procedure 7.10. Logging Into the Hypervisor

1. Start the machine on which the Red Hat Enterprise Virtualization Hypervisor operating system is installed.
2. Enter the user name admin and press Enter.
3. Enter the password you set during installation and press Enter.

Procedure 7.15. Configuring Security

1. Select the Enable SSH password authentication option and press the space bar to enable SSH authentication.
2. Select the Disable AES-NI option and press the space bar to disable the use of AES-NI for encryption.
3. Optionally, enter the number of bytes by which to pad blocks in AES-NI encryption if AES-NI encryption is enabled.
4. 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.
5. Select <Save> and press Enter.

Procedure 7.16. 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.

Procedure 7.17. Configuring Simple Network Management Protocol

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.

Procedure 7.18. Configuring Hypervisor Common Information Model

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.

Procedure 7.19. Configuring Logging

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. 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.
3. 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.
4. Select <Save> and press Enter.

Procedure 7.20. Configuring Kernel Dumps

1. Select an option for storing kernel dumps:

   • Local

     1. Select the Local option and press the space bar to store kernel dumps on the local system.

   • 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.

   • 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.

Procedure 7.21. 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.11. iSCSI Initiator Name

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

   Example 7.12. NFS Path

   NFSv4 Domain (example.redhat.com):
   example.redhat.com_____________________

2. Select <Save> and press Enter.

Procedure 7.22. 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.
    5. In the RHEV-M Fingerprint screen, review the SSL fingerprint retrieved from the Manager, select <Accept>, and press Enter. The Certificate Status in the RHEV-M screen changes from N/A to Verified.
  • 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.

Procedure 7.23. Registering the Hypervisor with the Red Hat Network

1. Enter your Red Hat Network user name in the Login field.
2. Enter your Red Hat Network 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 Red Hat Network.
4. Select the method by which to register the hypervisor:

   • The Red Hat Network

     Select the RHN option and press the space bar to register the hypervisor directly with the Red Hat Network. You do not need to enter values in the URL and CA URL fields.

     Example 7.13. Red Hat Network Configuration

     (X) RHN     ( ) Satellite     ( ) SAM
     URL:      _______________________________________________________________
     CA URL:   _______________________________________________________________

   • Satellite

     1. Select the Satellite option and press the space bar to register the hypervisor with a Satellite server.
     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.

     Example 7.14. Satellite Configuration

     ( ) RHN     (X) Satellite     ( ) SAM
     RHN URL:   https://your-satellite.example.com_____________________________
     CA URL:    https://your-satellite.example.com/pub/RHN-ORG-TRUSTED-SSL-CERT

   • Subscription Asset Manager

     1. Select the Subscription Asset Manager option and press Space to register the hypervisor via Subscription Asset Manager.
     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.

     Example 7.15. Subscription Asset Manager Configuration

     ( ) RHN     ( ) Satellite     (X) SAM
     URL:  https://subscription-asset-manager.example.com_____________________________
     CA :  https://subscription-asset-manager.example.com/pub/RHN-ORG-TRUSTED-SSL-CERT

5. If you are using a proxy server, you must also specify the details of that server:
   1. Enter the IP address or fully qualified domain name of the proxy server in the Server field.
   2. Enter the port by which to attempt a connection to the proxy server in the Port field.
   3. Enter the user name by which to attempt a connection to the proxy server in the Username field.
   4. Enter the password by which to authenticate the user name specified above in the Password field.
6. Select <Save> and press Enter.

Procedure 7.24. Approving a Hypervisor

1. Log in to the Red Hat Enterprise Virtualization Manager Administration Portal.
2. From the Hosts tab, click on the host to be approved. The host should currently be listed with the status of Pending Approval.
3. Click the Approve button. The Edit and Approve Hosts dialog displays. You can use the dialog to set a name for the host, fetch its SSH fingerprint before approving it, and configure power management, where the host has a supported power management card. For information on power management configuration, refer to Section 9.8.2, “Host Power Management Settings Explained”.
4. Click OK. If you have not configured power management you will be prompted to confirm that you wish to proceed without doing so, click OK.

Procedure 7.25. Installing the edit-node Tool

1. Log in to the system on which to modify the Red Hat Enterprise Virtualization Hypervisor ISO file.
2. Enable the Red Hat Enterprise Virtualization Hypervisor (v.6 x86_64) repository:

   • With RHN Classic:

     # rhn-channel --add --channel=rhel-x86_64-server-6-rhevh

   • With Subscription Manager, attach a Red Hat Enterprise Virtualization entitlement and run the following command:

     # subscription-manager repos --enable=rhel-6-server-rhevh-rpms

3. Install the ovirt-node-tools package:

   # yum install ovirt-node-tools