Red Hat Enterprise Virtualization for Servers-2.1-Installation Guide-En-US

8/2/2019 Red Hat Enterprise Virtualization for Servers-2.1-Installation Guide-En-US

1/70

Red Hat Enterprise

Virtualizationfor Servers 2.1

Installation Guide

A guide to the installation of Red Hat

Enterprise Virtualization for Servers

Susan Burgess

Chris Curran

David Jorm


2/70

Installation Guide

Red Hat Enterprise Virtualization for Servers 2.1 Installation Guide

A guide to the installation of Red Hat Enterprise Virtualization for

Servers

Edition 1.1

Author Susan Burgess [email protected]

Author Chris Curran [email protected]

Author David Jorm [email protected]

Copyright 2010 Red Hat, Inc

Copyright 2010 Red Hat, Inc.

The text of and illustrations in this document are licensed by Red Hat under a Creative Commons

AttributionShare Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available

at http://creativecommons.org/licenses/by-sa/3.0/. In accordance with CC-BY-SA, if you distribute thisdocument or an adaptation of it, you must provide the URL for the original version.

Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert,

Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.

Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, MetaMatrix, Fedora, the Infinity

Logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.

Linux is the registered trademark of Linus Torvalds in the United States and other countries.

Java is a registered trademark of Oracle and/or its affiliates.

XFS is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United Statesand/or other countries.

MySQL is a registered trademark of MySQL AB in the United States, the European Union and other

countries.

All other trademarks are the property of their respective owners.

1801 Varsity Drive

Raleigh, NC 27606-2072 USA

Phone: +1 919 754 3700

Phone: 888 733 4281Fax: +1 919 754 3701

This document describes the installation of Red Hat Enterprise Virtualization for Servers.
http://creativecommons.org/licenses/by-sa/3.0/mailto:[email protected]:[email protected]:[email protected]


3/70

iii

Preface v

1. About this Guide ............................................................................................................. v

1.1. The Red Hat Enterprise Virtualization Manager Documentation Suite ............. ........ .. v

1.2. Audience .............................................................................................................. v

2. Document Conventions ................................................................................................... v

2.1. Typographic Conventions ..................................................................................... vi2.2. Pull-quote Conventions ........................................................................................ vii

2.3. Notes and Warnings ............................................................................................ vii

3. We Need Feedback! ..................................................................................................... viii

1. Overview 1

1.1. System architecture ...................................................................................................... 1

1.2. How the management system works ............................................................................. 2

1.2.1. About the servers .............................................................................................. 2

1.2.2. About the virtual machines ................................................................................. 2

1.3. About the installation process ....................................................................................... 2

2. System Requirements 5

2.1. Prerequisites ................................................................................................................ 5

2.2. Hardware requirements ................................................................................................ 5

2.3. Software requirements .................................................................................................. 6

3. Installing the Red Hat Enterprise Virtualization Manager Manager 7

3.1. Installing the Operating System ..................................................................................... 7

3.1.1. Configure DNS server ........................................................................................ 9

3.1.2. Connect to domain controller ............................................................................. 9

3.1.3. Add components ............................................................................................... 9

3.2. Installing RHEV Manager ............................................................................................ 13

3.2.1. Run the installation wizard ............................................................................... 13

3.2.2. Accept license agreement ................................................................................ 143.2.3. Select features ................................................................................................ 14

3.2.4. Setup the database ......................................................................................... 15

3.2.5. Choose installation location .............................................................................. 16

3.2.6. Select website ................................................................................................. 17

3.2.7. Select RHEV Manager domain and user ........................................................... 18

3.2.8. Enter certification details .................................................................................. 19

3.2.9. Enter net console port ..................................................................................... 20

3.2.10. Confirm settings ............................................................................................. 21

3.2.11. Add external packages ................................................................................... 23

3.2.12. Login to the administrator portal ........ ........ ........ ........ ........ ......... ........ ........ .... 24

4. Installing the Red Hat Enterprise Virtualization Manager Hypervisor 274.1. Preparing an installation disc ...................................................................................... 27

4.2. Confirm hardware virtualization support ....................................................................... 28

4.3. Boot the Hypervisor .................................................................................................... 29

4.4. The RHEV Hypervisor Configuration Menu .................................................................. 29

4.5. Remove existing RHEV Hypervisor installations ........................................................... 30

4.6. Partitioning the disk .................................................................................................... 30

4.7. Set the administrator password ................................................................................... 32

4.8. Set the hostname ....................................................................................................... 33

4.9. Setup Networking ....................................................................................................... 34

4.10. Connect to the RHEV Manager ................................................................................. 36

4.11. Installation ................................................................................................................ 37

4.12. Using the hypervisor ................................................................................................. 38

5. Using Red Hat Enterprise Linux Hosts 39


4/70

Installation Guide

iv

5.1. Adding Red Hat Enterprise Linux Hosts ....................................................................... 39

5.1.1. Preparing Red Hat Enterprise Linux Hosts ........ ......... ........ ........ ........ ........ ....... 39

5.1.2. To Add a Host ................................................................................................. 41

5.2. Activating a Host ........................................................................................................ 43

6. Setting Up Storage 45

6.1. Adding NFS Storage .................................................................................................. 456.2. Adding iSCSI Storage ................................................................................................. 46

6.3. Adding FCP Storage .................................................................................................. 49

7. Configuring the System 53

A. Planning the System Architecture 55

B. Using Active Directory 57

B.1. Installing Active Directory ......... ........ ........ ........ ........ ........ ........ ........ ........ ......... ........ . 57

B.2. Creating the RHEV admin user in Active Directory .............. ........ ........ ........ ........ ........ . 57

C. Additional Reading 59

D. Revision History 61


5/70

v

PrefaceThe Red Hat Enterprise Virtualization platform is a richly featured virtualization management solution

providing fully integrated management across virtual machines. It is based on the leading open source

virtualization platform and provides superior technical capabilities. The platform offers scalability in the

management of large numbers of virtual machines.

1. About this GuideThis guide describes how to install the Red Hat Enterprise Virtualization platform.

1.1. The Red Hat Enterprise Virtualization Manager Documentation

SuiteRed Hat Enterprise Virtualization Manager documentation suite provides information on installation,

development of applications, configuration and usage of the Red Hat Enterprise VirtualizationManager platform and its related products.

Red Hat Enterprise Virtualization Manager Release Notes: contains release-specific information and

known issues.

Red Hat Enterprise Virtualization Administration Guide: describes how to setup, configure and

manage the virtualized environment.

Red Hat Enterprise Virtualization Installation Guide: describes how to install the virtualized

environment.

Red Hat Enterprise Virtualization Hypervisor Deployment Guide: describes how to deploy and install

the hypervisor.

Red Hat Enterprise Virtualization Manager API Guide describes how to use the command line

functions to set up and manage virtualization tasks. Use this guide of you do not wish to use the

graphical user interface, and prefer using the command line.

1.2. AudienceThis documentation suite is intended for system administrators installing a virtual environment

based on the specifications provided to them by their solution architect. An advanced level of system

administration, preferably including familiarity with virtual machine data center operations, is assumed.

This document is not intended for beginners.

2. Document ConventionsThis manual uses several conventions to highlight certain words and phrases and draw attention to

specific pieces of information.

In PDF and paper editions, this manual uses typefaces drawn from the Liberation Fonts1

set. The

Liberation Fonts set is also used in HTML editions if the set is installed on your system. If not,

alternative but equivalent typefaces are displayed. Note: Red Hat Enterprise Linux 5 and later includes

the Liberation Fonts set by default.

1https://fedorahosted.org/liberation-fonts/
https://fedorahosted.org/liberation-fonts/https://fedorahosted.org/liberation-fonts/https://fedorahosted.org/liberation-fonts/


6/70

Preface

vi

2.1. Typographic ConventionsFour typographic conventions are used to call attention to specific words and phrases. These

conventions, and the circumstances they apply to, are as follows.

Mono-spaced Bold

Used to highlight system input, including shell commands, file names and paths. Also used to highlight

keycaps and key combinations. For example:

To see the contents of the file my_next_bestselling_novel in your current

working directory, enter the cat my_next_bestselling_novel command at the

shell prompt and press Enter to execute the command.

The above includes a file name, a shell command and a keycap, all presented in mono-spaced bold

and all distinguishable thanks to context.

Key combinations can be distinguished from keycaps by the hyphen connecting each part of a key

combination. For example:

Press Enter to execute the command.

Press Ctrl+Alt+F2 to switch to the first virtual terminal. Press Ctrl+Alt+F1 to

return to your X-Windows session.

The first paragraph highlights the particular keycap to press. The second highlights two key

combinations (each a set of three keycaps with each set pressed simultaneously).

If source code is discussed, class names, methods, functions, variable names and returned values

mentioned within a paragraph will be presented as above, in mono-spaced bold. For example:

File-related classes include filesystem for file systems, file for files, and dir fordirectories. Each class has its own associated set of permissions.

Proportional Bold

This denotes words or phrases encountered on a system, including application names; dialog box text;

labeled buttons; check-box and radio button labels; menu titles and sub-menu titles. For example:

Choose System PreferencesMouse from the main menu bar to launch Mouse

Preferences. In the Buttons tab, click the Left-handed mouse check box and click

Close to switch the primary mouse button from the left to the right (making the mouse

suitable for use in the left hand).

To insert a special character into a gedit file, choose Applications Accessories

Character Map from the main menu bar. Next, choose Search Find from the

Character Map menu bar, type the name of the character in the Search field and click

Next. The character you sought will be highlighted in the Character Table. Double-

click this highlighted character to place it in the Text to copy field and then click the

Copy button. Now switch back to your document and choose Edit Paste from the

gedit menu bar.

The above text includes application names; system-wide menu names and items; application-specific

menu names; and buttons and text found within a GUI interface, all presented in proportional bold and

all distinguishable by context.

Mono-spaced Bold Italic or Proportional Bold Italic


7/70

Pull-quote Conventions

vii

Whether mono-spaced bold or proportional bold, the addition of italics indicates replaceable or

variable text. Italics denotes text you do not input literally or displayed text that changes depending on

circumstance. For example:

To connect to a remote machine using ssh, type ssh [email protected] at

a shell prompt. If the remote machine is example.com and your username on that

machine is john, type ssh [email protected].

The mount -o remount file-system command remounts the named file

system. For example, to remount the /home file system, the command is mount -o

remount /home.

To see the version of a currently installed package, use the rpm -qpackage

command. It will return a result as follows:package-version-release.

Note the words in bold italics above username, domain.name, file-system, package, version and

release. Each word is a placeholder, either for text you enter when issuing a command or for text

displayed by the system.

Aside from standard usage for presenting the title of a work, italics denotes the first use of a new and

important term. For example:

Publican is a DocBookpublishing system.

2.2. Pull-quote ConventionsTerminal output and source code listings are set off visually from the surrounding text.

Output sent to a terminal is set in mono-spaced roman and presented thus:

books Desktop documentation drafts mss photos stuff svn

books_tests Desktop1 downloads images notes scripts svgs

Source-code listings are also set in mono-spaced roman but add syntax highlighting as follows:

package org.jboss.book.jca.ex1;

import javax.naming.InitialContext;

publicclass ExClient

{

publicstaticvoidmain(String args[])

throws Exception{

InitialContext iniCtx = new InitialContext();

Object ref = iniCtx.lookup("EchoBean");

EchoHome home = (EchoHome) ref;

Echo echo = home.create();

System.out.println("Created Echo");

System.out.println("Echo.echo('Hello') = " + echo.echo("Hello"));

}

}

2.3. Notes and WarningsFinally, we use three visual styles to draw attention to information that might otherwise be overlooked.


8/70

Preface

viii

Note

Notes are tips, shortcuts or alternative approaches to the task at hand. Ignoring a note should

have no negative consequences, but you might miss out on a trick that makes your life easier.

Important

Important boxes detail things that are easily missed: configuration changes that only apply to

the current session, or services that need restarting before an update will apply. Ignoring a box

labeled 'Important' will not cause data loss but may cause irritation and frustration.

Warning

Warnings should not be ignored. Ignoring warnings will most likely cause data loss.

3. We Need Feedback!If you find a typographical error in this manual, or if you have thought of a way to make this manual

better, we would love to hear from you! Please submit a report by email to the author of the manual,

Susan Burgess ([email protected] ). When submitting a bug report, be sure to mention the

manual's identifier: Server_Install_Guide.

If you have a suggestion for improving the documentation, try to be as specific as possible when

describing it. If you have found an error, include the section number and some of the surrounding text

so we can find it easily.
mailto:[email protected]:[email protected]


9/70

Chapter 1.

1

OverviewThis document describes how to install Red Hat Enterprise Virtualization Manager platform for the first

time. It contains information on hardware and software prerequisites, installation procedures and initial

configuration.

1.1. System architectureThe Red Hat Enterprise Virtualization Manager (RHEV) platform consists of:

Red Hat Enterprise Virtualization Manager Manager (RHEV Manager) acts as a centralized

management system that allows system administrators to view and manage virtual machines and

images. The Red Hat Enterprise Virtualization Manager Manager provides a comprehensive range

of features including search capabilities, resource management, live migrations and provisioning.

The RHEV Manager is able to manage hosts running Red Hat Enterprise Virtualization Hypervisor

or Red Hat Enterprise Linux 5.4.

Red Hat Enterprise Virtualization Manager Hypervisor (RHEV Hypervisor) is a thin virtualization

layer deployed across the server infrastructure. It is based on Kernel-based Virtual Machine (KVM),

which is a core component of the Linux kernel.

The RHEV Hypervisor is a stand-alone Red Hat Enterprise Linux installation developed specifically

for use with Red Hat Enterprise Virtualization. It is also possible to configure Red Hat Enterprise

Linux 5.4 to be used as a host. Red Hat Enterprise Linux hosts can be used concurrently with RHEV

Hypervisors.

The descriptions in this guide provide sufficient knowledge for performing a basic installation of the

system. For a more thorough description, refer to the Red Hat Enterprise Virtualization Manager forServers Administration Guide.

Figure 1.1. Red Hat Enterprise Virtualization Manager Components


10/70

Chapter 1. Overview

2

1.2. How the management system worksThe following components combine to enable system administrators to setup, configure and maintain

the virtualized environment by using a graphical interface.

1.2.1. About the serversThe Red Hat Enterprise Virtualization Manager platform consists of one or more Hypervisors (or hosts)

and at least one Manager. The virtual machines (or guests) are hosted on the Hypervisor. The system

and all of its components are managed through Red Hat Enterprise Virtualization Manager Manager.

Red Hat Enterprise Virtualization Manager Manager provides a graphical user interface to

administer the physical and logical resources within the virtual environment infrastructure. It can be

used to manage provisioning, connection protocols, user sessions, virtual machine pools, images and

high availability/clustering. The Red Hat Enterprise Virtualization Manager Manager runs on Windows

2003 server in clustered mode, with active-standby configuration.

Red Hat Enterprise Virtualization Manager Hypervisor or Red Hat Enterprise Linux Host runs

the virtual machines on Red Hat Enterprise Linux with KVM virtualization technology. It also includes a

resource optimization layer that allows for improved virtual machine interactivity and management.

1.2.2. About the virtual machinesRed Hat Enterprise Virtualization Manager enables a thin client or personal computer to access virtual

machines with minimal local resources, using a standard web browser.

The following operating systems are currently supported on virtual machines:

Red Hat Enterprise Linux 3 (32 bit only)

Red Hat Enterprise Linux 4 (32 bit and 64 bit)

Red Hat Enterprise Linux 5 (32 bit and 64 bit)

Windows Server 2003 with Service Pack 2 (32 bit and 64 bit)

Windows Server 2008 with Service Pack 2 (32 bit and 64 bit)

Windows XP (32 bit only)

1.3. About the installation processRed Hat Enterprise Virtualization Manager is installed using the following steps:

1. Check that you have the necessary prerequisites, hardware and software specified in Chapter 2,

System Requirements.

2. Install the Red Hat Enterprise Virtualization Manager Manager according to Chapter 3, Installing

the Red Hat Enterprise Virtualization Manager Manager. This requires the installation and

configuration of Windows 2003 Server 32-bit (or R2) with Service Pack 2, followed by the

installation of the Red Hat Enterprise Virtualization Manager Manager application.

3. Install the Red Hat Enterprise Virtualization Manager Hypervisors and Red Hat Enterprise Linux

hosts according to Chapter 4, Installing the Red Hat Enterprise Virtualization Manager Hypervisor

and Chapter 5, Using Red Hat Enterprise Linux Hosts.

4. Configure and attach storage, according to Chapter 6, Setting Up Storage.


11/70

About the installation process

3

5. Configure the Red Hat Enterprise Virtualization Manager Manager for use, according to Chapter 7,

Configuring the System.


12/70

4


13/70

Chapter 2.

5

System RequirementsThis section describes the basic hardware and software prerequisites required for installing the Red

Hat Enterprise Virtualization platform.

It is assumed that the requirements for your specific implementation of the Red Hat EnterpriseVirtualization Manager system have been defined by your solution architect. Therefore, the solution

planning stage is not covered by this document. However, be aware that the following must be

considered when designing the system: total number of virtual machines to be used, storage

requirements, network capacity, total CPU and memory requirements. Additional notes regarding

system planning are provided inAppendix A, Planning the System Architecture.

Ensure that the listed requirements are ready before attempting installation.

2.1. Prerequisites

Latest Red Hat Enterprise Virtualization Manager Release Notes.

A client with Windows XP and .NET Framework 3.1 with Service Pack 1 is required to access the

web-based administration portal. The web-based administration portal can be used as an alternative

to the administration portal available on the RHEV Manager server.

2.2. Hardware requirements One or more physical servers to act as the Red Hat Enterprise Virtualization Manager Hypervisors

or Red Hat Enterprise Linux Hosts, each with:

Hardware virtualization support:

a. AMD system with AMD-V enabled in the BIOS and AMD64 CPU extension; or

b. Intel system with Intel VT enabled in the BIOS and Intel 64 CPU extensions.

Minimum 512MB of RAM.

Minimum 512MB of additional RAM for each virtual machine. The amount of RAM allocated to

each virtual machine is dependent on the guest operating system.

Minimum 750MB storage for installation of the Hypervisor on hard disk drive, plus additional

storage for swap. Refer to Red Hat Knowledgebase1

for more information on recommended swap

sizes.

Ensure that all Hypervisor or host servers to be used within a single cluster have the same CPU

type. This enables virtual machines to reside on any host within the cluster and to be migrated

between hosts. For further information, refer to the Red Hat Enterprise Virtualization Manager for

Servers Administration Guide.

One server to act as the Red Hat Enterprise Virtualization Manager Manager, with:

Minimum 1 GB of memory.

Minimum 20 GB of local disk space.

Server to provide storage for virtual machine and ISO images. Storage networking can beimplemented using Network File System (NFS), Internet Small Computer System Interface (iSCSI)

or Fibre Channel Protocol (FCP).
http://kbase.redhat.com/faq/docs/DOC-15252


14/70

Chapter 2. System Requirements

6

At least one network controller with a minimum bandwidth of 100 Mbps.

2.3. Software requirements Red Hat Enterprise Virtualization Manager Hypervisor installation software; and/or

A Red Hat Enterprise Linux 5.4 AMD64/Intel 64 system.

Red Hat Enterprise Virtualization Manager Manager installation software.

Microsoft Windows Server 2003 (or R2) 32-bit edition, with:

1. Windows Server 2003 Service Pack 2.

It is possible to create installation media that has the Service Pack files integrated into

the Windows Server 2003 installation folder. This allows the Service Pack to be installed

simultaneously with the operating system. For instructions, refer to http://support.microsoft.com/

kb/950349.

2. Valid Microsoft Windows Server 2003 product key.

The following Windows components:

Microsoft .NET Framework 3.5 Service Pack 1.

Available from: http://download.microsoft.com/download/2/0/e/20e90413-712f-438c-988e-

fdaa79a8ac3d/dotnetfx35.exe

Microsoft .NET Framework 3.5 Family Update for Windows Server 2003.

Filename: NDP35SP1-KB958484-x86.exe

Available from: http://www.microsoft.com/downloads/details.aspx?

familyid=6c095bba-6100-4ec9-9c54-6450b0212565&displaylang=en&displaylang=en

Windows Power Shell 1.0

Filename: WindowsServer2003-KB926139-v2-x86-ENU.exe

Available from: http://www.microsoft.com/downloads/details.aspx?

FamilyId=10EE29AF-7C3A-4057-8367-C9C1DAB6E2BF&displaylang=en

Recommended utilities for transferring files between RHEV Manager and RHEV Hypervisor:

WinSCP: open source Secure Copy (SCP) client for Windows.

PuTTY: open source Secure Shell (SSH) client for Windows and Unix platforms.
http://www.microsoft.com/downloads/details.aspx?FamilyId=10EE29AF-7C3A-4057-8367-C9C1DAB6E2BF&displaylang=enhttp://www.microsoft.com/downloads/details.aspx?familyid=6c095bba-6100-4ec9-9c54-6450b0212565&displaylang=en&displaylang=enhttp://download.microsoft.com/download/2/0/e/20e90413-712f-438c-988e-fdaa79a8ac3d/dotnetfx35.exehttp://support.microsoft.com/kb/950349http://www.microsoft.com/downloads/details.aspx?FamilyId=10EE29AF-7C3A-4057-8367-C9C1DAB6E2BF&displaylang=enhttp://www.microsoft.com/downloads/details.aspx?FamilyId=10EE29AF-7C3A-4057-8367-C9C1DAB6E2BF&displaylang=enhttp://www.microsoft.com/downloads/details.aspx?familyid=6c095bba-6100-4ec9-9c54-6450b0212565&displaylang=en&displaylang=enhttp://www.microsoft.com/downloads/details.aspx?familyid=6c095bba-6100-4ec9-9c54-6450b0212565&displaylang=en&displaylang=enhttp://download.microsoft.com/download/2/0/e/20e90413-712f-438c-988e-fdaa79a8ac3d/dotnetfx35.exehttp://download.microsoft.com/download/2/0/e/20e90413-712f-438c-988e-fdaa79a8ac3d/dotnetfx35.exehttp://support.microsoft.com/kb/950349http://support.microsoft.com/kb/950349


15/70

Chapter 3.

7

Installing the Red Hat Enterprise

Virtualization Manager ManagerThe installation of Red Hat Enterprise Virtualization Manager Manager is performed in two phases.

The first phase is the installation and configuration of Windows Server 2003 (or R2) 32-bit edition

with Service Pack 2, and the second phase is the installation of the Red Hat Enterprise Virtualization

Manager Manager (RHEVM).

3.1. Installing the Operating System

1. Install Windows Server 2003 32-bit (or R2) with Service Pack 2 by booting from the installation

media and following the on-screen instructions. When formatting the hard disk using Windows

Setup, select Format the partition by using the NTFS file system (Quick) option.

Note

Only the English locale is supported when installing the RHEV Manager on Windows Server

2003.

2. Once the installation of Windows Server 2003 (or R2) 32-bit edition is complete, confirm that

Service Pack 2 was included in the initial installation of Windows Server 2003 before proceeding.

a. Open the System Properties dialog box using one of the following methods:

Open the System applet in Control Panel; or

Right-click on My Computer and choose Properties.


16/70

Chapter 3. Installing the Red Hat Enterprise Virtualization Manager Manager

8

b. Confirm that Service Pack 2 is listed under the System information.

Figure 3.1. System Properties

Note

If Service Pack 2 is not installed, use Windows Update to add Service Pack 2 before

proceeding.

3. Check that the i386 directory contained on the installation CD was copied to the C: drive. If not,

copy it to the hard drive manually, as it is required when adding the Windows components.


17/70

Configure DNS server

9

3.1.1. Configure DNS serverThe RHEV Manager server must be configured with a fully qualified name that is resolvable

throughout the system by the host and clients.

1. Configure TCP/IP for static addressing.

2. Configure DNS server role.

For instructions, refer to http://technet.microsoft.com/en-us/library/cc738344(WS.10).aspx.

3.1.2. Connect to domain controllerActive Directory acts as the domain controller for the Windows Server 2003 installation. Therefore,

Active Directory must be installed and configured before joining RHEV Manager to the domain. For

information about Active Directory, refer toAppendix B, Using Active Directory.

Procedure 3.1. To join an Active Directory domain from Windows Server 2003:

1. Go to Start, right-click My Computer and select Properties.

2. Select the Computer Name tab.

3. Ensure that the Computer description field contains the fully qualified computer name. If not,

enter it now.

4. Click Change....

5. Enter the domain information and click Ok.

6. When prompted for the credentials of a user that can join machines to the domain, enter the

RHEV administrator user credentials created as per Section B.2, Creating the RHEV admin userin Active Directory. Then click Ok.

7. If successful, a message will be displayed confirming that the computer has been joined to the

domain. Click Ok to continue.

If a confirmation message was not received, this is likely to be due to one of the following:

Domain specified is incorrect.

User credentials specified are incorrect.

User credentials provided do not have the necessary permissions to join a machine to the

domain.

Check your Active Directory configuration and credentials and try again.

8. Reboot the machine to complete the process.

3.1.3. Add componentsIt is necessary to install additional Windows components and perform updates before installing Red

Hat Enterprise Virtualization Manager Manager application.

1. a. Install .NET Framework 3.5 Service Pack 1
http://technet.microsoft.com/en-us/library/cc738344(WS.10).aspx


18/70


10

b. Verify that .NET Framework 3.5 Service Pack 1 was installed by going to Start > Control

Panel > Add or Remove Programs and checking that it is listed, as in Figure 3.2, Add or

Remove Programs.

Figure 3.2. Add or Remove Programs

2. From Add/Remove Programs, click on Add/Remove Windows Components.


19/70

Add components

11

3. From the Windows Components Wizard, select the Application Server checkbox and click

Details.

Figure 3.3. Windows component wizard

4. From the Application Server window, check the following options:

Application Server Console

ASP.NET

Enable network COM+ access

Enable network DTC access

Internet Information Services (IIS)


20/70


12

Figure 3.4. Application Server

5. Click OK to add the selected components.

a. If the required files are not found, an error message displays.

Figure 3.5. Copy Error

The error message indicates that the Windows installation CD or the i386 directory was not

found.


21/70

Installing RHEV Manager

13

b. Click Browse... to navigate to the location of the i386 directory.

c. Click Retry to continue.

6. Click Next to install the selected components.

7. Install Windows PowerShell 1.0

Verify PowerShell installed successfully by going to Start > All Programs > Windows

PowerShell 1.0.

8. Use Microsoft Windows Update to install all available updates.

3.2. Installing RHEV ManagerThis section describes the installation of the RHEV Manager application.

It is expected that the installation wizard will minimize at times throughout the installation process. The

wizard will reappear when ready to proceed with the next step.

3.2.1. Run the installation wizard

1. Double-click the RHEV Manager installation file to execute the installation wizard. You may need

to wait while the wizard prepares for installation.

2. When presented with the welcome screen, click Next.

Figure 3.6. Welcome screen


22/70


14

3.2.2. Accept license agreement

You are asked to read the End User License Agreement.

Figure 3.7. Import license file

To continue with the installation you must accept the terms of the License Agreement by

clicking Yes. The wizard will proceed to the next step.

If you do not agree to the License Agreement, click No. The installation process will be

canceled.

3.2.3. Select featuresA typical installation includes the following features:

RHEVM Admin Portal: used to manage the RHEV system and perform associated tasks.

RHEVM Database: holds RHEV system information regarding created objects, configuration and

logging history.

RHEVM Service: the core RHEV Manager application.

RHEVM Scripting Library: PowerShell scripting library and documentation.

RHEVM Net Console: remote console service used for logging purposes.

RHEVM Web Admin: web-based administrator portal.


23/70

Setup the database

15

Figure 3.8. Select components

1. Select the features to be installed. If a checkbox is gray, this indicates that the feature is required

for installation.

Note

It is recommended that all features are installed by default.

Although installation of a local RHEV Manager database is recommended, the Database

checkbox can be unmarked to use an existing database.

2. Once the selection is complete, click Next to continue.

3.2.4. Setup the databaseSpecify whether an existing SQL Server database is to be used or if the installation wizard should

create a local database instance.

It is recommended that a new database instance is created.


24/70


16

Procedure 3.2. Create a new database instance:

1. Select the Install a SQL Server 2005 Express Locally option.

Figure 3.9. RHEVM Database

2. Set the password for the database sa user.

To change the default password for the SQLExpress sa user:

Enter the preferred administrator password in the Password and Confirm Password

fields.

3.2.5. Choose installation location

Select the location for the RHEV Manager installation.

Note

It is recommended that the default installation path is used.


25/70

Select website

17

Procedure 3.3. Change the installation location

1. Click Browse... and select the required destination folder.

Figure 3.10. Set installation folder

2. Click Next to accept the installation location.

3.2.6. Select websiteThe installation wizard will create a website for users with automatic URL redirection.


26/70


18

1. Either select the desired website from the drop-down menu or create a new site.

Figure 3.11. Select or create website

To use the default website, keep the default values.

To set a custom name:

a. Click Create a new site.

b. Enter the desired site name in the New site name field.

c. Enter the site port in the Port field.

d. Leave the Force SSL checkbox selected.

2. Once the default or custom selection has been made, click Next to continue.

3.2.7. Select RHEV Manager domain and userProvide the Active Directory domain and user details to be used by RHEV Manager.

The User details section requires the Active Directory user details that were setup according to

Section 2.1, Prerequisites. These credentials will be used on the first run of template-created servers

to associate users and groups with specific virtual servers within the system. Therefore, this user

requires permissions to create computer objects within Active Directory.


27/70

Enter certification details

19

Figure 3.12. Enter domain and user details

The RHEV Manager filters users that do not have a User Principal Name (UPN, e.g. user@domain)

configured in Active Directory. Therefore, ensure that the user is correctly configured before

proceeding.

Domain details

1. From the Select Local or Domain drop-down menu, choose the Domain option.

2. Enter the domain name to be used in the Domain Name field.

User details

1. Enter the Active Directory username in the User Name field.

2. Enter the Active Directory password in the Password field.

Once it has been confirmed that the domain and user details have been correctly entered, click Next

to continue.

3.2.8. Enter certification detailsAt the Certification details screen:

1. Enter the name of your organization in the Organization name field.

2. Enter the fully qualified name for the RHEV Manager server in the Fully qualified computer

name field.


28/70


20

Note

It is recommended that the fully qualified computer name is resolvable. If not, select the Do

not validate fully qualified computer name checkbox. This option is useful during testing or

when the Domain Name Server is not configured.

Figure 3.13. Certification Details

3. Confirm that the information entered is correct and click Next to proceed.

3.2.9. Enter net console portA default net console port will be supplied by the installation wizard.


29/70

Confirm settings

21

Accept the default value by clicking Next.

Figure 3.14. Net Console Port

3.2.10. Confirm settingsThe installation wizard will present a summary of the installation information entered.

1. Confirm that the information entered is correct.

To alter any details, use the Back button to navigate to the relevant screen and make the

necessary changes.


30/70


22

2. Once all details are correct, click Next to continue.

Figure 3.15. Confirm settings

3. The installation wizard will begin configuring the installation.

If there are any running applications using files that require updating, you are notified to close

these before proceeding. Once this is done, click Retry to continue.


31/70

Add external packages

23

Figure 3.16. Close applications

3.2.11. Add external packagesInstall the following external packages when prompted.

Note

The installation window may minimize during the installation process.

OpenSSL Setup Wizard

1. Click Next to begin installation.

2. Read the License Agreement. To accept the license agreement, select the I accept the

agreement option and click Next.

3. It is recommended that OpenSSL is installed in the default location provided. Click Next to

continue.

4. The installation wizard will create shortcuts in the specified Start Menu folder specified. To change

the specified folder, click Browse and select the desired Start Menu folder.

5. Check the settings and confirm that the installation should proceed by clicking Install.

6. Click Finish.


32/70


24

Python Extensions for Microsoft Windows

1. At the Setup screen, click Next to proceed.

2. It is recommended that the installation uses the default settings provided, including the python and

installation directories. Click Next to continue.

3. The Python installation process begins. Once complete, click Finish to exit the setup wizard.

The RHEV Manager installation will continue and may take some time to complete. When finished, the

installation wizard will confirm that that it has completed the installation. Click Finish to exit.

3.2.12. Login to the administrator portalAccessing the administrator portal requires a client with Windows XP and .NET Framework 3.5

Service Pack 1 installed.

1. Open the administrator portal login screen by clicking on Start > All Programs > Red Hat >

RHEV Manager > RHEVManager.

Figure 3.17. Administrator portal login

Alternatively, if the RHEVManager shortcut is not present, open a web browser and navigate to

http://localhost/RHEVmanager .

2. Enter the RHEV Manager administrator credentials, as configured in Section 3.2.7, Select RHEV

Manager domain and user. Please wait while the application information is downloaded.

3. Allow the ActiveX component to be installed.


33/70

Login to the administrator portal

25

4. Once the installation process is complete, you will be presented with the RHEV Manager

interface.

Figure 3.18. RHEV Manager interface


34/70

26


35/70

Chapter 4.

27

Installing the Red Hat Enterprise

Virtualization Manager HypervisorThis chapter covers installing and integrating Red Hat Enterprise Virtualization Hypervisors with a Red

Hat Enterprise Virtualization Manager.

The RHEV Hypervisor mustbe installed on a physical server and cannot be installed on a virtual

machine.

The installation process will reconfigure the selected storage device and destroy all data. Therefore,

ensure that any data to be retained is successfully backed up before proceeding.

The following method can be used when installing multiple servers. However, ensure that unique

hostnames and IP addresses are used for each Hypervisor installation, in order to avoid network

conflicts.

The following procedure provides installation instructions for using a CD-ROM created using theRHEV Hypervisor ISO image available from Red Hat. For alternative installation methods using USB

Flash Drive or Network (PXE) Boot, refer to the Red Hat Enterprise Virtualization Hypervisor

Deployment Guide available at http://www.redhat.com/docs/.

RHEV Hypervisors can use Storage Attached Networks (SANs) and other network storage for

storing virtualized guest images. However, a local storage device is required for installing and

booting the Hypervisor.

Automated Installations

RHEV Hypervisor installations can be automated or conducted without interaction. This typeof installation is only recommended for advanced users. Refer to the Red Hat Enterprise

Virtualization Hypervisor Deployment Guide for more information.

4.1. Preparing an installation discRHEV Hypervisors can be installed using an optical disc on systems with a functional CD-ROM or

DVD drive.

These procedures require a Red Hat Enterprise Linux 5 system with RHN entitlements for the RHEV

channels.

Note

Access to a working system with an optical recorder drive and optical disk recording software

is required for creation of the installation disc. The instructions in this guide use the cdrecord

package, which is installed by default on Red Hat Enterprise Linux.

Procedure 4.1. Confirm recording software is present on Red Hat Enterprise Linux

1. To verify that the cdrecord package is present on the system, perform a query using the rpm

package manager by entering the command:

# rpm -q cdrecord
http://www.redhat.com/docs/


36/70

Chapter 4. Installing the Red Hat Enterprise Virtualization Manager Hypervisor

28

2. If the cdrecord package is installed, the package name will be displayed in the system

output.

If notification is displayed that the cdrecord package is not installed, it can be installed using

the command:

# yum install cdrecord

Once the cdrecord package is verified as being present, the installation media can be created.

Procedure 4.2. Create an installation disc

1. Enable the Red Hat Enterprise Virtualization Hypervisor 5 channel on RHN.

2. Install the RHEV Hypervisor ISO image package.

# yum -y install rhev-hypervisor

Alternatively, download the RHEV Hypervisor CD-ROM image from Red Hat Network1.

3. Insert a blank CD-ROM or DVD into your CD/DVD recorder drive.

4. Record the ISO file to disc using the cdrecord command in the format:

# cdrecord dev=device[iso file path]

For example, if using the first CD-RW device (/dev/cdrw) available and the Hypervisor ISO file

located at /usr/share/rhev-hypervisor/rhev-hypervisor.iso the command used is:

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

5. If an error occurs during the recording process, try inserting a new writable disc and repeat the

previous command.

Once the record process has completed without any errors occurring, the installation media is

ready to use. The RHEV Hypervisor uses the isomd5sum to verify the integrity of the installation

media each time the Hypervisor is booted. If media errors are reported during the boot sequence,

a new installation disc will need to be created.

4.2. Confirm hardware virtualization supportIf unsure, verify that the virtualization extensions are present and enabled in the BIOS before installing

the Hypervisor.

1. Insert the RHEV Hypervisor installation CD-ROM into the CD-ROM drive of the server.

2. Power on the system and ensure it boots from the CD.

3. Once the Hypervisor has completed the boot phase and the boot prompt is displayed, enter the

command:

: linux rescue

4. To verify that your CPU contains the virtualization extensions, enter the command:
https://rhn.redhat.com/network/software/channels/details.pxt?cid=9462


37/70

Boot the Hypervisor

29

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

The processor is hardware virtualization capable if output is displayed.

5. To verify that the virtualization extensions are enabled in the BIOS, check that the kvm modules

are loaded in the kernel by entering:

# lsmod | grep kvm

If the output includes kvm_intel or kvm_amd then the kvm hardware virtualization modules are

loaded and the system meets requirements.

Note

If hardware virtualization support is not present and enabled, it is not possible to install the RHEV

Hypervisor.

4.3. Boot the Hypervisor

1. Insert the RHEV Hypervisor installation CD-ROM into the CD-ROM drive of the server.

2. Power on the system and ensure the system boots from CD.

3. Once the Hypervisor has completed the boot phase and the boot prompt is displayed, press

Enter to continue.

If the Hypervisor has been previously installed, you may need to provide additional parameters to

cause the server to boot to the configuration setup menu. For further information, refer to the Red

Hat Enterprise Virtualization Hypervisor Deployment Guide.

4.4. The RHEV Hypervisor Configuration MenuOnce the RHEV Hypervisor boots you will see the Hypervisor Configuration Menu.

The Hypervisor Configuration Menu is an interactive tool for installing Red Hat Enterprise Virtualization

Hypervisors. The Hypervisor Configuration Menu resembles Example 4.1, Red Hat EnterpriseVirtualization Hypervisor Configuration Menu. Throughout this chapter it will be referred to as the

main menu.

Example 4.1. Red Hat Enterprise Virtualization Hypervisor Configuration Menu

Red Hat Enterprise Virtualization Hypervisor release 5.4-2.1

Hypervisor Configuration Menu

1) Configure storage partitions 5) Configure the RHEV Manager

2) Configure authentication 6) Install locally and reboot

3) Set the hostname 7) Uninstall an existing Hypervisor

4) Networking setup 8) Support menuChoose an option to configure:


38/70


30

Configuration menu options

Configure storage partitions: prepares the local storage device for installation. Refer to

Section 4.6, Partitioning the disk.

Configure authentication: sets the root password for administration and SSH access. Refer to

Section 4.7, Set the administrator password.

Set the hostname: sets the hostname manually instead of using DHCP. Refer to Section 4.8, Set

the hostname.

Networking setup: configures network settings and services (DHCP, IPv4 and/or IPv6, and DNS).

Refer to Section 4.9, Setup Networking.

Configure the RHEV Manager: enter IP address of the RHEV Manager server. Refer to

Section 4.10, Connect to the RHEV Manager.

Install locally and reboot: install the Hypervisor to the storage device and reboot. Refer to

Section 4.11, Installation.

Uninstall an existing Hypervisor: removes all existing RHEV Hypervisor installations and data.

Refer to Section 4.5, Remove existing RHEV Hypervisor installations.

Support menu: contains options for continuing stateless boot and exiting to a shell prompt. This

menu is not supported except when working with Red Hat support.

4.5. Remove existing RHEV Hypervisor installationsIf the Hypervisor was previously installed on the local system, remove the existing installation by

selecting Uninstall an existing Hypervisor option from the main menu.

For further information on removing previous versions of the RHEV Hypervisor, refer to the Red Hat

Enterprise Virtualization Manager Hypervisor Deployment Guide.

4.6. Partitioning the diskThe partitions used by the RHEV Hypervisor are configured from this menu. For most installations the

default partition layout is optimal.

Warning

Running this procedure will destroy all data on the local storage device selected with the

storage_init parameter.

Procedure 4.3. The Storage Configuration menu

1. Select theConfigure storage partitions option from the main menu to open the Configure

storage partitions menu.

Example 4.2. The Configure storage partitions menu

Configure storage partitions

1) Configure 3) Commit configuration

2) Review 4) Return to the Hypervisor Configuration Menu

Choose an option:


39/70

Partitioning the disk

31

2. Choose partition sizes

Select Configure.

You are prompted to set the size of swap, root, config, logging and data partitions. The value is

accepted in megabytes (MB).

Setting a size value of -1 sets the partition to take up all remaining disk space. Note that this can

only be used with the Data partition.

Pressing Enter without any value sets the partition to the default size.

Important

Do not append units onto the end of the partition size values. Using MB or similar unit on the

end of a value may have adverse effects. For example, use the value 5 instead of 5MB.

a. The boot partition contains the boot loader, kernel and initramfs.

The default and only supported size for the boot partition is 50MB.

b. The swap partition is used for swapping underused memory to the hard drive to speed up

memory performance. The default size of the swap partition is calculated from amount of

RAM and overcommit ratio (default is 0.5). RHEV Hypervisors must have a swap partition

and the swap partition cannot be disabled by setting its size to 0. The minimum size for the

swap partition is 5MB.

Red Hat Knowledgebase2

has an article on determining the size of the swap partition.

Use the formula from the Red Hat Knowledgebase and add storage for the overcommit ratio

(RAM multiplied by the overcommit ratio).

Recommended swap + (RAM * overcommit) = swap partition size

Pressing Enter during the installation sequence sets a recommended value for the swap

partition.

c. The root partition contains the core files for the Hypervisor and the LiveOS directory from

the installation media. The default total size of the root file system partitions is 512MB. Thatis broken up into 256MB for one root partition and an additional 256MB for a backup root

partition.

The default and only supported size for the root partition is 256MB. The size entered is per

partition, with the total size of the root partitions double what is entered.

d. The config partition stores configuration files for the Hypervisor.

The default and minimum size for the configuration partition is 5MB.

e. The logging partition stores all logs for the Hypervisor.

The default size for the logging partition is 2048MB, the minimum size is 256MB.

f. The data partition stores core files and kdump files and acts as temporary storage for ISO

files. The default size of the data partition is the remaining available disk space (labeled as

-1).
http://kbase.redhat.com/faq/docs/DOC-15252http://kbase.redhat.com/faq/docs/DOC-15252


40/70


32

When ISO files are uploaded using the ISO Uploader tool, they are temporarily stored on the

data partition of a RHEV Hypervisor host, before being moved to the shared ISO Library. The

data partition must include sufficient space to store these ISO files, which can be over 4GB in

size for modern operating systems.

The data partition should be at least 1.5x as large as the RAM on the host system plus an

additional 512MB in size. The minimum size is 256MB.

3. Review

Select the Review menu option. The review menu output similar to the screenshot below:

4. Select Commit configuration to accept the partitions. The following warning displays:

5.!!WARNING!!WARNING!!WARNING!!WARNING!!WARNING!!WARNING!!WARNING!!WARNING!!

!!WARNING!!WARNING!!WARNING!!WARNING!!WARNING!!WARNING!!WARNING!!WARNING!!

!!WARNING!! !!WARNING!!!!WARNING!! !!WARNING!!

!!WARNING!! If you proceed, all data on your local storage !!WARNING!!

!!WARNING!! device will be destroyed and your hard disk !!WARNING!!

!!WARNING!! will be irreversibly reconfigured. !!WARNING!!

!!WARNING!! !!WARNING!!

!!WARNING!! !!WARNING!!



Continue? (Y/n)

6. Press Y to proceed and format the partitions.

Partitions are created and file systems are formatted. Once complete, the main menu reappears.

4.7. Set the administrator passwordSetting a strong and easy to remember administrator password is an essential part of securing your

infrastructure.

Procedure 4.4. Set the administrator password

1. Select Configure authentication from the main configuration menu.

Example 4.3. The Configure authentication menu

SSH password and authentication is currently disabled


41/70

Set the hostname

33

1) Set administrator password 3) Return to the Hypervisor Configuration Menu

2) Toggle SSH password authentication

Choose an option to configure:

2. Select the Set administrator password.

3. The password prompt displays.

Set the system administrator's (root) password:

New UNIX password:

Enter the preferred password. You will be prompted to retype the password.

4.Changing password for user root.

passwd: all authentication tokens updated successfully.

storing to /config :

/etc/shadow File persisted

This message indicates that the password has been set and saved to local storage.

Configure SSH password authentication

SSH password authentication is required for accessing RHEV Hypervisors with the SSH protocol. By

default, SSH password authentication is disabled.

To enable SSH password authentication:

1. Select Toggle SSH password authentication from the Administrator password menu.

2.Enable SSH remote access ([Y]es or [N]o)?

Press y to enable SSH password authentication.

3. If successful, the following message is displayed:

SSH remote access is currently enabled.

Select Return to the Hypervisor Configuration Menu to continue the installation.

4.8. Set the hostnameThe Red Hat Enterprise Virtualization Manager requires a fully resolvable hostname for each RHEV

Hypervisor. If you are using DHCP and DNS a hostname can be assigned to the Hypervisor at boot

time.

If the DHCP server does not set hostnames, the hostname must be specified manually (with the

process below). This hostname must resolve to the assigned IP address located with a DNS lookup

request.

1. Select the Set the hostname option from the main menu.

2.What is this Hypervisor's hostname?

Enter the hostname in the following format: anyname.domain.example.com . Where anyname

is the individual name for the host on the specified domain.


42/70


34

3. Press Enter to set the hostname. If successful, this message is displayed:

The hostname is set.

You are returned to the Configuration menu.

Reseting hostnames

To reset a hostname:

1. Open the Set the hostname menu.

2. The specify a hostname prompt appears:

What is this Hypervisor's hostname?

Press the Enter key without typing anything else to reset the hostname.

The hostname is now reset to use DHCP.

4.9. Setup NetworkingConfigure your system's network settings.

1. Select the Networking setup option.

2. The network devices attached to your system are listed.

3.Choose an interface or a configuration option:

Select the network interface on the same network as the RHEV Manager. On systems with one

network interface there is only eth0 to choose from.

Device support

Wireless and logical network devices are presently unsupported.

4. Identifying the interface

Hypervisors include a tool to assist in physically identifying which network interface was selected.

Help identify eth0 by blinking the lights for 10 seconds ([Y]es or [N]o)?

Press y to identify which socket eth0 is. This is useful for systems with multiple network

interfaces.

If assistance is not required, continue by pressing n.

If the selected network interface does not support this feature, the system will display the following

message:


43/70

Setup Networking

35

Blinking is not supported by your network interface.

5. VLANs

A prompt will be displayed asking whether to include VLAN support:

Include VLAN support ([Y]es, [N]o or [A]bort)?

If VLAN support is not required, press n.

To enable VLAN support, enter y.

a.

What is the VLAN ID for this device (a=abort)

Enter the VLAN ID number when prompted.

b.Is this correct ([Y]es, [N]o or [A]bort)?

Confirm your VLAN choice if you selected a VLAN by pressing y.

6. IPv4

The IPv4 prompt appears.

Enable IPv4 support ([S]tatic IP, [D]HCP, [N]o or [A]bort)?

Select DHCP or Static IP depending on your networking environment.

To use DHCP, press D to enable IPv4 support with DHCP. It is recommended to statically map

all IP addresses for each RHEV Hypervisor on your DHCP server.

Alternatively, assign a static IP address by pressing S. You are then prompted for the IP

address, Netmask and gateway.

Confirm your settings.

Is this correct ([Y]es, [N]o or [A]bort)?

Press Y if correct to continue.

7. DNS

Configure DNS if required.

a. Enter the IP address of the first DNS gateway or press Enter to abort.

Enter the first DNS server (or press the Enter key to exit):

b. Enter the IP address of the second DNS gateway or press Enter to skip.

Enter the second DNS server (or press the Enter key to exit):

c. Confirm your settings.


44/70


36

Is this correct ([Y]es, [N]o or [A]bort)?

Press Y if correct to continue.

8. Network Time Protocol (NTP)

The Network Time Protocol (NTP) keeps system clocks in time with the rest of the world.NTP is crucial for some host systems with inconsistent clocks as hosts who are too far out of

synchronization cannot migrate.

a.Enter an NTP server:

Enter the IP address or hostname of an NTP server or press Enter to abort.

b. You will be prompted to enter additional NTP servers. Enter as many as required and press

Enter on a blank line to save your selection.

9. Select Return to the Hypervisor Configuration Menu to save the configuration.

10. If the network is configured correctly, the output should be similar to Figure 4.1, Working network

configuration.

Figure 4.1. Working network configuration

You are now returned to the main menu.

4.10. Connect to the RHEV ManagerThis procedure connects the RHEV Hypervisor to a RHEV Manager.

When specifying the address of the RHEV Manager, use the following format for IP addresses or

hostnames.

Table 4.1. Red Hat Enterprise Virtualization Manager addressing examples

Type Format Example

IP address IP[:port] 127.0.0.1:443

Host Name host.name.domain[:port] www.example.com:443


45/70

Installation

37

Important

Ensure that you have configured the local storage and networking correctly before proceeding. If

something is not correct change it now because you cannot change it after this point. To change

a setting after this point you must repeat the procedure from the beginning. The specified IP

addresses or host names used must be fully resolvable.

1. Select 5) Configure RHEV Host from the configuration menu.

2.Enter the RHEV Manager's hostname or IP address.

Optionally: append a port after the hostname or IP address

For example, 10.0.0.1:443 or rhev.example.com:443

a. Enter the Red Hat Enterprise Virtualization Manager hostname or IP address in the specified

format.

b. If the RHEV Manager is successfully found, the following output is displayed:

The RHEV Manager's address is set

The RHEV Manager's port is set.

3. Enter the address of the NetConsole manager for remote console output.

Enter the NetConsole manager's hostname or IP address.

Optionally: append a port after the hostname or IP address

For example, 10.0.0.1:25285 or rhev.redhat.com:25285

If you are unsure, use the RHEV Manager's address, without a port.

a. Enter the NetConsole server and port. In most cases, this server will be the RHEV Manager.

The NetConsole port is the same as the NetConsole port number specified during the

installation of the RHEV Manager in Section 3.2.9, Enter net console port.

b. If the NetConsole server is successfully found, the following output is displayed before being

returned to the configuration menu:

The NetConsole manager address is set.

The NetConsole manager port is set.

4.11. InstallationOnce all the previous steps are complete, the RHEV Hypervisor can be installed to the local storage

device.

Storage, networking and the RHEV Manager mustbe configured before continuing.

1. Select Install locally and reboot from the Hypervisor Configuration Menu.

2.This option exits the menu and requires a reboot.

Ensure local storage and networking is configured

correctly on the previous menu before continuing.

The current kernel boot parameters are

crashkernel=128M@16M elevator=deadline processor.max_cstate=1


46/70


38

Enter additional kernel boot parameters (press Enter to use the present arguments):

Press Enter to continue.

3.Do you wish to continue (Y/n)?

Press Y to continue.

The final installation sequence begins. Once the installation is complete the RHEV Hypervisor will

reboot.

After rebooting, the RHEV Hypervisor is installed and integrated with Red Hat Enterprise Virtualization

Manager for Servers. You should have a new host available in the Red Hat Enterprise Virtualization

Manager interface.

Note

You should remove the boot media and change the boot device order to prevent the installation

sequence restarting after the system reboots.

4.12. Using the hypervisorOnce the Hypervisor has finished rebooting, it is automatically registered with the Red Hat Enterprise

Virtualization Manager platform. The RHEV Manager interface displays the Hypervisor under the

Hosts tab. To prepare the Hypervisor for use, it must be approved using RHEV Manager.

Procedure 4.5. Approve the Hypervisor1. Login to the RHEV Manager admin portal (refer to Section 3.2.12, Login to the administrator

portal).

2. From the Hosts tab, click on the host to be approved. The host should currently be listed with the

status of Awaiting approval.

3. Click the Approve button. The Edit and Approve dialog displays. You can use the dialog to make

changes to the details

4. Click Save. The status in the Hosts tab changes to Installing, after a brief delay the host status

changes to Up.


47/70

Chapter 5.

39

Using Red Hat Enterprise Linux HostsVirtual machines on Red Hat Enterprise Linux can be managed by Red Hat Enterprise Virtualization

Manager. Red Hat Enterprise Linux hosts can be used concurrently with RHEV Hypervisors.

Important

Only the AMD64/Intel 64 version of Red Hat Enterprise Linux is compatible for use with Red Hat

Enterprise Virtualization Manager.

5.1. Adding Red Hat Enterprise Linux HostsRed Hat Enterprise Virtualization also supports hosts running Red Hat Enterprise Linux 5.4 AMD64/

Intel 64 version. This section describes the preparatory steps for installing the Red Hat Enterprise

Linux host, as well as the steps to manually add the host to the Red Hat Enterprise Virtualization

platform.

Adding a host can take some time, as the following steps are completed by the platform: virtualization

checks, installation of packages, creation of bridge and a reboot of the host. Use the Details pane to

monitor the hand-shake process as the host and management system establish a connection.

5.1.1. Preparing Red Hat Enterprise Linux HostsTo ensure a smooth and successful integration of Red Hat Enterprise Linux Hosts and Red Hat

Enterprise Virtualization platform, prepare the host carefully according to the instructions in this

section.

Ensure that Red Hat Enterprise Linux 5.4 is correctly installed and configured on the physical host.

Refer Red Hat Enterprise Linux Installation Guide.

Only the Base package group is required. All other packages can be removed or not selected.

Important note on fresh installations

Do not select the Virtualization or KVM package groups when installing Red Hat Enterprise

Linux, as they contain packages that are not compatible for use with Red Hat Enterprise

Virtualization.

Ensure that VLANs are configured for access to the Red Hat Enterprise Virtualization Manager.

Ensure the host is correctly subscribed to the appropriate Red Hat Network channels.

Red Hat Enterprise Virt Management Agent (v.5 for x86_64)

RHEL Virtualization (v. 5 for 64-bit x86_64)


48/70

Chapter 5. Using Red Hat Enterprise Linux Hosts

40

Note

If you do not have the appropriate subscription entitlements, contact Red Hat Customer

Service.

Install the fence-agents, kvm-qemu-imgbridge-utils packages required by Red Hat

Enterprise Virtualization Manager to manage Red Hat Enterprise Linux hosts. During installation if

the required additional packages are not found, they will be automatically installed by the Red Hat

Enterprise Virtualization Manager.

Install the required packages with yum:

# yum install bridge-utils fence-agents kvm-qemu-img

Uninstall incompatible packages.

The RHEV management daemon (vdsm) is currently incompatible with Xen and libvirt.

Therefore, both Xen and libvirt, including all dependencies, should be removed.

Warning

The following steps will destroy data on all existing virtual machines. It is strongly

recommended to back up or migrate existing virtual machines to other Red Hat Enterprise

Linux servers before proceeding. This process is not reversible.

Remove thexen, kernel-xen and libvirtpackages with the yum command:

# yum remove xen kernel-xen libvirt

This command removes several dependencies, libvirt configuration files and virtual machine

images stored in the /var/lib/libvirt/ directory.

Reboot the system. The reboot effects a return to the default kernel if the Xen kernel was in use;

and the reboot disables the default libvirt network bridge.

Add a manual host entry to the /etc/hosts file (on the Red Hat Enterprise Linux 5.4 host) for the

Red Hat Enterprise Virtualization Manager server to enable vdsm and other services to connect

properly to the host.

Because Active Directory uses layered domain names, the Active Directory instance takes the

domain name usually used by a Linux host. For example, if the server running the Red Hat

Enterprise Virtualization Manager has a hostname of server1.example.com, Active Directory

uses that address and creates a sub-address named rhev-manager.server1.example.com .

Edit the /etc/hosts file on the Red Hat Enterprise Linux Host. The following screen output sample

resembles the contents of the file:

127.0.0.1 localhost.localdomain localhost

::1 localhost6.localdomain6 localhost6


49/70

To Add a Host

41

Append a new line to /etc/hostswith the IP address and both variants of the RHEV Manager

domain names. The following screen output sample resembles the required contents of the file:

127.0.0.1 localhost.localdomain localhost

::1 localhost6.localdomain6 localhost6

10.0.0.1 server1.example.com rhev-manager.server1.example.com

Open firewall ports on the host.

Red Hat Enterprise Virtualization platform uses a number of network ports for management and

other virtualization features.

The following steps configure iptables to open the required ports.

Add the required ports as iptables rules. Advanced users can modify rules or use the

iptables -i option instead of iptables -A in order to integrate with existing rules.

# iptables -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT

# iptables -A INPUT -p icmp -j ACCEPT

# iptables -A INPUT -i lo -j ACCEPT

# iptables -A INPUT -p tcp --dport 54321 -j ACCEPT

# iptables -A INPUT -p tcp --dport 22 -j ACCEPT

# iptables -A INPUT -p tcp -m multiport --dports 5634:6166 -j ACCEPT

# iptables -A INPUT -p tcp -m multiport --dports 49152:49216 -j ACCEPT

# iptables -A INPUT -j REJECT --reject-with icmp-host-prohibited

# iptables -A FORWARD -m physdev ! --physdev-is-bridged -j REJECT --reject-

with icmp-host-prohibited

Save the modified rules.

# service iptables save

You can now add the correctly installed and configured Red Hat Enterprise Linux host to Red Hat

Enterprise Virtualization platform.

5.1.2. To Add a HostIn the process of adding a host, you will need to provide the IP and password of the host, and the

following steps are completed by the platform: virtualization checks, installation of packages, creation

of bridge and a reboot of the host. The process of adding a new host can take some time, the process

can be followed in the Details pane.

1. Click the Hosts tab. The Hosts tab displays a list of all hosts in the system.


50/70

Chapter 5. Using Red Hat Enterprise Linux Hosts

42

Figure 5.1. List of Hosts

2. Click the New button. The New Host dialog displays.

Figure 5.2. New Host Dialog

Enter the details of the new host.

3. Name: a descriptive name for the host.

4. Address: the IP address, or resolvable hostname of the host (provided during installation).

5. Port: the port used for internal communication control between the hosts. A default port is

displayed; change the default only if you are sure that another port can be used.

6. Host Cluster: the cluster to which the host belongs (select from the drop-down list).

7. Root password: the password of the designated host; used during installation of the host.

8. Enable Power Management: Select this checkbox to turn out-of-band (OOB) power management

on. If selected, the information for the following fields must also be provided.

The Address of the host. This is usually the address of the remote access card (RAC) on the

host.

A valid User Name for the OOB management.

A valid, robust Password for the OOB management.

The Type of the OOB management device. Select the appropriate device from the drop down

list.


51/70

Activating a Host

43

DRAC5 Dell Remote Access Controller for Dell

computers

ilo HP Integrated Lights Out standard

ipmilan Intelligent Platform Management Interface

rsa IBM Remote Supervisor Adaptor

bladecenter IBM Bladecentre Remote Supervisor Adapter

The Port to connect to OOB management.

Click the Test button to test the operation of the OOB management solution.

Red Hat Enterprise Virtualization recommends power management. Power management enables

the system to fence a troublesome host using an additional interface.

Note

If the host is required to be Highly Available, power management must be enabled and

configured.

9. Click OK.

The new host displays in the list of hosts with a status of "Installing". Once installation is complete,

the status of the newly added host isAwaiting. The host must be activated for the status to change

to Up.

Note:

View the process of the host installation on the Details pane.

5.2. Activating a HostAfter a host has been added, or an existing host has been taken down for maintenance, it needs to be

activated before it can be used. Red Hat Enterprise Linux 5.4 hosts need to be activated after being

added or upgraded.

To activate a host:

1. In the Hosts tab (see Figure 5.1, List of Hosts), select the host to be activated.

2. Click the Activate button.

The host status changes to Up. Virtual machines can now run on the host.


52/70

44


53/70

Chapter 6.

45

Setting Up StorageThis chapter provides a quick start guide to configuring storage for Red Hat Enterprise Virtualization.

For information about managing storage, including maintenance and removal, refer to the Red Hat

Enterprise Virtualization Manager Administration Guide.

Red Hat Enterprise Virtualization Manager uses a centralized storage system for maintaining ISO

files and virtual machine disk images, data and snapshots. Storage networking can be implemented

using Network File System (NFS), Internet Small Computer System Interface (iSCSI) or Fibre Channel

Protocol (FCP). Once storage has been configured, it must be attached to the RHEV Manager in order

to make it accessible to the system.

Before proceeding, ensure that you have:

A working RHEV Manager environment.

At least one RHEV Hypervisor attached to RHEV Manager. This is required as all communication

with the storage domain is performed via the configured Hypervisor.

6.1. Adding NFS StorageMount NFS shares by attaching them to the data center as a storage domain. Once attached, the

storage domains can be used to provide storage for virtualized guest images and ISO boot media. For

further information about using NFS, refer to the Red Hat Enterprise Linux Deployment Guide.

Preparing an NFS Share

This section outlines how to set up an NFS share with recommended settings.

Ensure NFS is installed.

rpm -q nfs-utils

If the package is not detected, install it using the following commands:

yum install nfs-utils

chkconfig --add nfs

chkconfig nfs on

Determine the NFS share directory. For example, if you intend to share /RHEV/Images, enter the

following line into the /etc/exports file.

/RHEV/Images *(rw,no_root_squash)

Restart the NFS service.

The NFS export directory must be configured for read write access and must be owned by

vdsm:kvm. If these users do not exist on your external NFS server use the following commands,

assuming that /RHEV/Images is the NFS share.


54/70

Chapter 6. Setting Up Storage

46

chown -R 36:36 /RHEV/Images

chmod g+s /exports/* -R

chmod u+s /exports/* -R

To Add NFS Storage:

1. Click the Storage tab. The Storage list and toolbar display.

2. Click New Storage. The New Storage dialog box displays.

Figure 6.1. NFS Storage

3. Enter the Name of the storage. For example, depending on its function, either Images or ISO. A

suitably descriptive name is recommended.

4. Select NFS as the storage Type.

5. Select a Config.Host. To attach a domain, the name of any configured (and activated) host must

be selected from the list of existing hosts.

Note

All communication to the storage domain is via the configured host and not from the Red

Hat Enterprise Virtualization Manager. At least one host must exist in the system before the

storage can be configured.

6. Enter the Export path of the storage. The export path can be either an IP address or a resolvable

hostname. For example, 192.168.0.10:/Images/ISO .

7. Click OK.

8. The name of the NFS storage domain is added to the Storage tab.

6.2. Adding iSCSI StorageRed Hat Enterprise Virtualization platform supports iSCSI storage at two levels:

VG level Volume Group Level associates a set of predefined Logical Unit Numbers (LUNs) to

a volume group that is assigned to a certain storage domain. Volume Groups cannot be shared

between storage domains.

LUN level allows an administrator to assign a set of LUNs to a storage domain. LUNs that are

attached to one storage domain cannot be attached to another storage domain.

For information regarding the setup and configuration of iSCSI on Red Hat Enterprise Linux, please

refer to the Online Storage Reconfiguration Guide.

To Add iSCSI Storage:

1. Click the Storage tab. The Storage list and toolbar display.


55/70

Adding iSCSI Storage

47

2. Click New Storage. The New Storage dialog box displays.

Figure 6.2. New Storage Dialog

3. Enter the Name of the storage.

4. Select iSCSI as the storage Type. The dialog box displays a set of fields appropriate to the iSCSI

Documents

Red Hat Enterprise Virtualization for Servers-2.1-Installation Guide-En-US