Red Hat Enterprise Virtualization 3.4 User Guide en US
Uploaded by
war_ningRed Hat Enterprise Virtualization 3.4 User Guide en US
Uploaded by
war_ningRed Hat Enterprise Virtualization
3.4
User Guide
Accessing and Using Virtual Machines From the User Portal
Jodi Biddle Lucinda Bopf Andrew Burden
Zac Dover Tim Hildred Dayle Parker
Cheryn Tan
Red Hat Enterprise Virtualization 3.4 User Guide
Accessing and Using Virtual Machines From the User Portal
Jo di Biddle
[email protected] m
Lucinda Bo pf
lbo [email protected] m
Andrew Burden
[email protected] m
Zac Do ver
zdo [email protected] m
Tim Hildred
[email protected] m
Dayle Parker
[email protected] m
Cheryn Tan
[email protected] m
Legal Notice
Copyright © 2014 Red Hat, Inc.
T his document is licensed by Red Hat under the Creative Commons Attribution-ShareAlike 3.0 Unported
License. If you distribute this document, or a modified version of it, you must provide attribution to Red
Hat, Inc. and provide a link to the original. If the document is modified, all Red Hat trademarks must be
removed.
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 T orvalds 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 States
and/or other countries.
MySQL ® is a registered trademark of MySQL AB in the United States, the European Union and other
countries.
Node.js ® is an official trademark of Joyent. Red Hat Software Collections is not formally related to or
endorsed by the official Joyent Node.js open source or commercial project.
T he OpenStack ® Word Mark and OpenStack Logo are either registered trademarks/service marks or
trademarks/service marks of the OpenStack Foundation, in the United States and other countries and
are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed or
sponsored by the OpenStack Foundation, or the OpenStack community.
All other trademarks are the property of their respective owners.
Abstract
T his document shows you how to use virtual machines from the Red Hat Enterprise Virtualization User
Portal.
Table of Contents
Table of Contents
.Preface
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4. . . . . . . . .
1. Document Conventions 4
1.1. T ypographic Conventions 4
1.2. Pull-quote Conventions 5
1.3. Notes and Warnings 6
2. Getting Help and Giving Feedback 6
2.1. Do You Need Help? 6
2.2. We Need Feedback! 7
P
. .art
. . .I.. Getting
. . . . . . . .Started
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8. . . . . . . . .
C
. .hapter
. . . . . . 1.
. . Accessing
. . . . . . . . . . the
. . . .User
. . . . Portal
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9. . . . . . . . .
1.1. Logging in to the User Portal 9
1.2. Logging out of the User Portal 12
1.3. Logging in for the First T ime: Installing the Engine Certificate 12
1.3.1. Installing the Red Hat Enterprise Virtualization Manager Certificate in Firefox 12
1.3.2. Installing the Red Hat Enterprise Virtualization Manager Certificate in Internet Explorer
13
C
. .hapter
. . . . . . 2. . . Installing
. . . . . . . . . Supporting
. . . . . . . . . . .Components
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
..........
2.1. Installing Console Components 15
2.1.1. Console Components 15
2.1.2. Installing Remote Viewer on Linux 15
2.1.3. Installing Remote Viewer for Internet Explorer on Windows 15
2.1.4. Installing Remote Viewer on Windows 16
2.1.5. Manually Associating console.vv Files with Remote Viewer 17
2.2. Installing USB Redirection Components 18
2.2.1. Installing USB Clerk on Windows 18
P
. .art
. . .II.. .Basic
. . . . . Usage
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
..........
C
. .hapter
. . . . . . 3.
. .T
. .he
. . Basic
. . . . . .T. ab
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
..........
3.1. Basic T ab Graphical Interface 20
3.2. Running Virtual Machines 21
3.2.1. Running Virtual Machines - Overview 21
3.2.2. T urning on a Virtual Machine 21
3.2.3. Connecting to a Powered-On Virtual Machine 23
3.2.4. Logging out of a Virtual Machine 24
C
. .hapter
. . . . . . 4. . .T.he . . .Extended
. . . . . . . . .T.ab
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
..........
4 .1. T he Extended T ab Graphical Interface 25
4 .2. Running Virtual machines 27
4 .2.1. Running Virtual Machines Introduction 27
4 .2.2. Connecting to Virtual Machines 27
4 .2.3. T urning Off a Virtual Machine from the User Portal 28
4 .2.4. Rebooting a Virtual Machine from the User Portal 29
4 .3. Creating Virtual Machines 29
4 .3.1. Creating a Virtual Machine 29
4 .3.2. Creating a Virtual Machine Based on a T emplate 31
4 .3.3. Creating a Cloned Virtual Machine Based on a T emplate 33
4 .4. Explanation of Settings and Controls in the New Virtual Machine and Edit Virtual Machine
Windows 35
4 .4.1. Virtual Machine General Settings Explained 35
4 .4.2. Virtual Machine System Settings Explained 36
4 .4.3. Virtual Machine Initial Run Settings Explained 37
4 .4.4. Virtual Machine Console Settings Explained 38
1
Red Hat Enterprise Virtualization 3.4 User Guide
4 .4.4. Virtual Machine Console Settings Explained 38
4 .4.5. Virtual Machine Host Settings Explained 40
4 .4.6. Virtual Machine High Availability Settings Explained 42
4 .4.7. Virtual Machine Resource Allocation Settings Explained 43
4 .4.8. Virtual Machine Boot Options Settings Explained 45
4 .4.9. Virtual Machine Custom Properties Settings Explained 45
4 .5. Configuring Virtual Machines 46
4 .5.1. Completing the Configuration of a Virtual Machine by Defining Network Interfaces and Hard
Disks 46
4 .5.2. Installing Windows on VirtIO-Optimized Hardware 48
4 .5.3. Virtual Machine Run Once Settings Explained 49
4 .5.4. Configuring a Watchdog 52
4 .5.4.1. Adding a Watchdog Card to a Virtual Machine 52
4 .5.4.2. Configuring a Watchdog 53
4 .5.4.3. Confirming Watchdog Functionality 54
4 .5.4.4. Parameters for Watchdogs in watchdog.conf 54
4 .6. Editing Virtual Machines 57
4 .6.1. Editing Virtual Machine Properties 57
4 .6.2. Editing a Network Interface 58
4 .6.3. Extending the Size of an Online Virtual Disk 59
4 .6.4. Floating Disks 59
4 .6.5. Associating a Virtual Disk with a Virtual Machine 59
4 .6.6. Changing the CD for a Virtual Machine 60
4 .6.7. Smart card Authentication 61
4 .6.8. Enabling and Disabling Smart cards 61
4 .7. Removing Virtual Machines 62
4 .7.1. Removing a Virtual Machine 62
4 .8. Snapshots 62
4 .8.1. Managing Snapshots 63
4 .8.2. Creating Snapshots 63
4 .8.3. Cloning Snapshots 63
4 .8.4. Using a Snapshot to Restore a Virtual Machine 64
4 .8.5. Deleting Snapshots 65
4 .9. T emplates 66
4 .9.1. Introduction to T emplates 66
4 .9.2. T emplate T asks 66
4 .9.2.1. Creating a T emplate 66
4 .9.2.2. Explanation of Settings and Controls in the New T emplate Window 68
4 .9.2.3. Editing a T emplate 69
4 .9.2.4. Deleting a T emplate 70
4 .9.3. Sealing T emplates in Preparation for Deployment 70
4 .9.3.1. Sealing a Linux Virtual Machine Manually for Deployment as a T emplate 70
4 .9.3.2. Sealing a Linux Virtual Machine for Deployment as a T emplate using sys-unconfig
4 .9.3.3. Sealing a Windows T emplate 72 71
4 .9.3.3.1. Considerations when Sealing a Windows T emplate with Sysprep 72
4 .9.3.3.2. Sealing a Windows XP T emplate 72
4 .9.3.3.3. Sealing a Windows 7 or Windows 2008 T emplate 73
4 .9.3.4. Using Cloud-Init to Automate the Configuration of Virtual Machines 74
4 .9.3.4.1. Cloud-Init Overview 74
4 .9.3.4.2. Cloud-Init Use Case Scenarios 74
4 .9.3.4.3. Installing Cloud-Init 74
4 .9.3.4.4. Using Cloud-Init to Initialize a Virtual Machine 75
4 .9.3.4.5. Using Cloud-Init to Prepare a T emplate 76
4 .9.4. T emplates and Permissions 77
4 .9.4.1. Managing System Permissions for a T emplate 77
4 .9.4.2. T emplate Administrator Roles Explained 77
4 .9.4.3. T emplate User Roles Explained 78
4 .10. Resources 79
4 .10.1. Monitoring Power User Portal Resources 79
2
Table of Contents
4 .10.1. Monitoring Power User Portal Resources 79
4 .10.2. Quota - A User's Introduction 79
4 .10.3. What to Do When You Exceed Your Quota 80
4 .11. Virtual Machines and Permissions 81
4 .11.1. Managing System Permissions for a Virtual Machine 81
4 .11.2. Virtual Machines Administrator Roles Explained 82
4 .11.3. Virtual Machine User Roles Explained 82
4 .11.4. Assigning Virtual Machines to Users 83
4 .11.5. Removing Access to Virtual Machines from Users 85
P
. .art
. . .III.
. . Advanced
. . . . . . . . . .Usage
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
..........
1. Introduction to Using Virtual Machines - Advanced 86
2. Passing Information to Red Hat Enterprise Virtualization Manager with rhevm-guest-agent 86
C
. .hapter
. . . . . . 5. . . Configuring
. . . . . . . . . . . Console
. . . . . . . . Options
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
..........
5.1. Console Options 88
5.1.1. Introduction to Connection Protocols 88
5.1.2. Configuring Console Options 88
5.1.3. SPICE Console Options 89
5.1.4. VNC Console Options 90
5.1.5. RDP Console Options 91
5.2. Remote Viewer Options 92
5.2.1. Remote Viewer Options 92
5.2.2. Remote Viewer Hotkeys 94
C
. .hapter
. . . . . . 6.
. . Configuring
. . . . . . . . . . . Multiple
. . . . . . . . Monitors
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
..........
6.1. Configuring Multiple Displays for Red Hat Enterprise Linux Virtual Machines 96
6.2. Changing the Resolution of Displays in a Red Hat Enterprise Linux Virtual Machine 96
6.3. Configuring Multiple Displays for Windows Virtual Machines 96
6.4. Changing the Resolution of Displays in a Windows Virtual Machine 97
C
. .hapter . . . . . . 7.
. . Configuring
. . . . . . . . . . . USB
. . . . .Devices
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
..........
7.1. Using USB Devices on Virtual Machines - Introduction 99
7.2. Using USB Devices on Virtual Machines - Native Mode 99
7.3. Using USB Devices on a Windows Client 100
7.4. Using USB Devices on a Red Hat Enterprise Linux Client 100
7.5. Using USB Devices on Virtual Machines - Legacy Mode 101
7.6. Configuring a Linux Client to Use USB Redirection in Legacy Mode 105
7.7. Configuring a Windows Client to Use USB Redirection in Legacy Mode 106
C
. .hapter
. . . . . . 8.
. . Configuring
. . . . . . . . . . . Single
. . . . . . .Sign-On
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109
...........
8.1. Configuring Single Sign-On for Virtual Machines 109
8.2. Configuring Single Sign-On for Red Hat Enterprise Linux Virtual Machines Using IPA (IdM)
8.3. Configuring Single Sign-On for Red Hat Enterprise Linux Virtual Machines Using Active 109
Directory 110
8.4. Configuring Single Sign-On for Windows Virtual Machines 112
. . . . . . . . .History
Revision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .114
...........
3
Red Hat Enterprise Virtualization 3.4 User Guide
Preface
1. Document Conventions
T his 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 Fonts set. T he Liberation
Fonts set is also used in HT ML 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 include the Liberation Fonts
set by default.
1.1. Typographic Conventions
Four typographic conventions are used to call attention to specific words and phrases. T hese
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
keys and key combinations. For example:
T o see the contents of the file m y_next_bestselling_novel in your current working
directory, enter the cat m y_next_bestselling_novel command at the shell prompt and
press Enter to execute the command.
T he above includes a file name, a shell command and a key, all presented in mono-spaced bold and all
distinguishable thanks to context.
Key combinations can be distinguished from an individual key by the plus sign that connects each part of a
key combination. For example:
Press Enter to execute the command.
Press Ctrl+Alt+F2 to switch to a virtual terminal.
T he first example highlights a particular key to press. T he second example highlights a key combination: a
set of three keys 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 m ono-spaced bold. For example:
File-related classes include filesystem for file systems, file for files, and dir for
directories. Each class has its own associated set of permissions.
Proportional Bold
T his 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 submenu titles. For example:
Choose System → Preferences → Mouse from the main menu bar to launch Mouse
Preferences. In the Buttons tab, select the Left-handed m ouse 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).
T o insert a special character into a gedit file, choose Applications → Accessories →
4
Preface
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. T he character you sought will be highlighted in the Character T able. Double-click
this highlighted character to place it in the T ext to copy field and then click the Copy
button. Now switch back to your document and choose Edit → Paste from the gedit menu
bar.
T he 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
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:
T o connect to a remote machine using ssh, type ssh username@ domain.name at a shell
prompt. If the remote machine is exam ple.com and your username on that machine is john,
type ssh john@ exam ple.com .
T he m ount -o rem ount file-system command remounts the named file system. For
example, to remount the /hom e file system, the command is m ount -o rem ount /hom e.
T o see the version of a currently installed package, use the rpm -q package 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 DocBook publishing system.
1.2. Pull-quote Conventions
T erminal output and source code listings are set off visually from the surrounding text.
Output sent to a terminal is set in m ono-spaced rom an 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 m ono-spaced rom an but add syntax highlighting as follows:
static int kvm_vm_ioctl_deassign_device(struct kvm *kvm,
struct kvm_assigned_pci_dev *assigned_dev)
{
int r = 0;
struct kvm_assigned_dev_kernel *match;
mutex_lock(&kvm->lock);
match = kvm_find_assigned_dev(&kvm->arch.assigned_dev_head,
5
Red Hat Enterprise Virtualization 3.4 User Guide
assigned_dev->assigned_dev_id);
if (!match) {
printk(KERN_INFO "%s: device hasn't been assigned before, "
"so cannot be deassigned\n", __func__);
r = -EINVAL;
goto out;
}
kvm_deassign_device(kvm, match);
kvm_free_assigned_device(kvm, match);
out:
mutex_unlock(&kvm->lock);
return r;
}
1.3. Notes and Warnings
Finally, we use three visual styles to draw attention to information that might otherwise be overlooked.
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.
2. Getting Help and Giving Feedback
2.1. Do You Need Help?
If you experience difficulty with a procedure described in this documentation, visit the Red Hat Customer
Portal at http://access.redhat.com. T hrough the customer portal, you can:
search or browse through a knowledgebase of technical support articles about Red Hat products.
submit a support case to Red Hat Global Support Services (GSS).
access other product documentation.
6
Preface
Red Hat also hosts a large number of electronic mailing lists for discussion of Red Hat software and
technology. You can find a list of publicly available mailing lists at https://www.redhat.com/mailman/listinfo.
Click on the name of any mailing list to subscribe to that list or to access the list archives.
2.2. 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 in Bugzilla: http://bugzilla.redhat.com/ against the
product Red Hat Enterprise Virtualization Manager.
When submitting a bug report, be sure to mention the manual's identifier: Guides-User Portal
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, please include the section number and some of the surrounding
text so we can find it easily.
7
Red Hat Enterprise Virtualization 3.4 User Guide
Part I. Getting Started
8
Chapter 1. Accessing the User Portal
Chapter 1. Accessing the User Portal
1.1. Logging in to the User Portal
Log in to the Red Hat Enterprise Virtualization User Portal directly from your web browser.
Procedure 1.1. Logging in to the User Portal
1. Enter the provided User Portal URL in the address bar of your web browser. T he address must be
in the format of https://server.exam ple.com /UserPortal. T he login screen displays.
Alternately, enter the provided server address into the web browser, to access the welcome
screen. Click User Portal to be directed to the User Portal.
9
Red Hat Enterprise Virtualization 3.4 User Guide
Figure 1.1. T he User Portal Login Selection Screen
2. Enter your User Name and Password. Use the Domain drop-down menu to select the correct
domain.
10
Chapter 1. Accessing the User Portal
Figure 1.2. T he User Portal Login Screen
If you have only one running virtual machine in use, select the Connect Autom atically
check box and connect directly to your virtual machine.
If you have more than one running virtual machine or do not wish to automatically connect to a
virtual machine, do not select the Connect Autom atically check box.
Select the language in which the User Portal is presented by using the drop-down menu at the
lower-right of the login window.
3. Click Login. T he list of virtual machines assigned to you displays.
11
Red Hat Enterprise Virtualization 3.4 User Guide
Figure 1.3. User Portal
Report a bug
1.2. Logging out of the User Portal
Logging out of the User Portal:
At the title bar of the User Portal, click Sign out. You are logged out and the User Portal login screen
displays.
Report a bug
1.3. Logging in for the First Time: Installing the Engine Certificate
1.3.1. Installing the Red Hat Enterprise Virtualization Manager Certificate in Firefox
Summary
T he first time you access the User Portal, you must install the certificate used by the Red Hat Enterprise
Virtualization Manager to avoid security warnings.
12
Chapter 1. Accessing the User Portal
Procedure 1.2. Installing the Red Hat Enterprise Virtualization Manager Certificate in Firefox
1. Navigate to the URL for the User Portal in Firefox.
2. Click Add Exception to open the Add Security Exception window.
3. Ensure the Perm anently store this exception check box is selected.
4. Click the Confirm Security Exception button.
Result
You have installed the certificate used by the Red hat Enterprise Virtualization Manager and will not
encounter security warnings when you access the User Portal.
Report a bug
1.3.2. Installing the Red Hat Enterprise Virtualization Manager Certificate in
Internet Explorer
Summary
T he first time you access the User Portal, you must install the certificate used by the Red Hat Enterprise
Virtualization Manager to avoid security warnings.
Procedure 1.3. Installing the Red Hat Enterprise Virtualization Manager Certificate in Internet
Explorer
1. Navigate to the following URL:
https://[your manager's address]/ca.crt
2. Click the Open button in the File Download - Security Warning window to open the
Certificate window.
3. Click the Install Certificate button to open the Certificate Im port Wizard window.
4. Select the Place all certificates in the following store radio button and click
Browse to open the Select Certificate Store window.
5. From the list of certificate stores, select T rusted Root Certification Authorities and
click OK.
6. Click Next to proceed to the Certificate Store screen.
7. Click Next to proceed to the Com pleting the Certificate Im port Wizard screen.
8. Click the Finish button to install the certificate.
Result
You have installed the certificate used by the Red hat Enterprise Virtualization Manager and will not
encounter security warnings when you access the User Portal.
13
Red Hat Enterprise Virtualization 3.4 User Guide
Important
If you are using Internet Explorer to access the User Portal, you must also add the URL for the Red
Hat Enterprise Virtualization welcome page to the list of trusted sites to ensure all security rules for
trusted sites are applied to console resources such as console.vv mime files and Remote
Desktop connection files.
Report a bug
14
Chapter 2. Installing Supporting Components
Chapter 2. Installing Supporting Components
2.1. Installing Console Components
2.1.1. Console Components
A console is a graphical window that allows you to view the start up screen, shut down screen and
desktop of a virtual machine, and to interact with that virtual machine in a similar way to a physical machine.
In Red Hat Enterprise Virtualization, the default application for opening a console to a virtual machine is
Remote Viewer, which must be installed on the client machine prior to use.
Report a bug
2.1.2. Installing Remote Viewer on Linux
Remote Viewer is an application for opening a graphical console to virtual machines. Remote Viewer is a
SPICE client that is included the virt-viewer package provided by the Red Hat Enterprise Linux
Workstation (v. 6 for x86_64 ) channel.
Procedure 2.1. Installing Remote Viewer on Linux
1. Run the following command to install the spice-xpi package and dependencies:
# yum install spice-xpi
2. Run the following command to check whether the virt-viewer package has already been installed
on your system:
# rpm -q virt-viewer
virt-viewer-0.5.2-18.el6_4.2.x86_64
If the virt-viewer package has not been installed, run the following command to install the package
and its dependencies:
# yum install virt-viewer
3. Restart Firefox for your changes to take effect.
4. T he SPICE plug-in is now installed. You can now connect to your virtual machines using the SPICE
protocol.
Report a bug
2.1.3. Installing Remote Viewer for Internet Explorer on Windows
Summary
T he SPICE ActiveX component is required to run Remote Viewer, which opens a graphical console to
virtual machines. Remote Viewer is a SPICE client installed together with the SPICE ActiveX component;
both are provided in the SpiceX.cab file.
15
Red Hat Enterprise Virtualization 3.4 User Guide
Procedure 2.2. Installing Remote Viewer for Internet Explorer on Windows
1. Open Internet Explorer and log in to the User Portal.
2. Start a virtual machine and attempt to connect to the virtual machine using the Browser Client
console option.
3. Click the warning banner and click Install T his Add-on when prompted.
4. Click Install when prompted.
5. Restart Internet Explorer for your changes to take effect.
Result
You have installed the SPICE plug-in and Remote Viewer, and can now connect to virtual machines using
the SPICE protocol from within Internet Explorer.
Report a bug
2.1.4. Installing Remote Viewer on Windows
T he Remote Viewer application provides users with a graphical console for connecting to virtual
machines. Once installed, it is called automatically when attempting to open a SPICE session with a virtual
machine. Alternatively, it can also be used as a standalone application.
Procedure 2.3. Installing Remote Viewer on Windows
1. Open a web browser and download one of the following installers according to the architecture of
your system.
Virt Viewer for 32-bit Windows:
https://[your manager's address]/ovirt-engine/services/files/spice/virt-
viewer-x86.msi
Virt Viewer for 64-bit Windows:
https://[your manager's address]/ovirt-engine/services/files/spice/virt-
viewer-x64.msi
2. Open the folder where the file was saved.
3. Double-click the file.
4. Click Run if prompted by a security warning.
5. Click Yes if prompted by User Account Control.
Result
Remote Viewer is installed and can be accessed via Remote Viewer in the VirtViewer folder of All
Program s in the start menu.
Report a bug
16
Chapter 2. Installing Supporting Components
2.1.5. Manually Associating console.vv Files with Remote Viewer
Summary
If you are prompted to download a console.vv file when attempting to open a console to a virtual
machine using the native client console option and Remote Viewer is already installed, you can manually
associate console.vv files with Remote Viewer so that Remote Viewer will automatically use those files
to open consoles.
Procedure 2.4 . Manually Associating console.vv Files with Remote Viewer
1. A. In the User Portal Basic tab, select the virtual machine and click the Edit button of the
Console section of the display pane to open the Console Options window.
Figure 2.1. Opening the Console Options window in the Basic tab
B. In the User Portal Extended tab, click the Edit Console Options button of a virtual
machine to open the Console Options window.
Figure 2.2. Opening the Console Options window in the Extended tab
2. Change the console invocation method to Native client and click OK.
3. Start the virtual machine.
4. Attempt to open a console to the virtual machine, and click Save when prompted to open or save the
console.vv file.
5. Use Windows Explorer to navigate to the location on your local machine where you saved the file.
6. Double-click the console.vv file and select Select a program from a list of
installed program s when prompted.
7. In the Open with window, select Always use the selected program to open this
17
Red Hat Enterprise Virtualization 3.4 User Guide
kind of file and click the Browse button.
8. Navigate to the C:\Users\[user name]\AppData\Local\virt-viewer\bin directory and
select rem ote-viewer.exe.
9. Click Open and then click OK.
Result
You have manually associated the console.vv file with Remote Viewer. When you use the native client
console invocation option to open a console to a virtual machine, Remote Viewer will automatically use the
console.vv file that the Red Hat Enterprise Virtualization Manager provides to open a console to that
virtual machine without prompting you to select the application to use.
Report a bug
2.2. Installing USB Redirection Components
2.2.1. Installing USB Clerk on Windows
USB Clerk provides a service that is able to install and uninstall Windows USB drivers in guest virtual
machines.
Procedure 2.5. Installing USB Clerk on Windows
1. Open a web browser and download one of the following installers according to the architecture of
your system.
USB Clerk for 32-bit Windows:
https://[your manager's address]/ovirt-
engine/services/files/spice/usbclerk-x86.msi
USB Clerk for 64-bit Windows:
https://[your manager's address]/ovirt-
engine/services/files/spice/usbclerk-x64.msi
2. Open the folder where the file was saved.
3. Double-click the file.
4. Click Run if prompted by a security warning.
5. Click Yes if prompted by User Account Control.
Result
USB Clerk is installed. T he SPICE client sends requests to install or uninstall drivers for USB devices
when users connect or disconnect USB devices to or from a guest, upon request.
Report a bug
18
P art II. Basic Usage
Part II. Basic Usage
19
Red Hat Enterprise Virtualization 3.4 User Guide
Chapter 3. The Basic Tab
3.1. Basic Tab Graphical Interface
T he Basic enables you to view and use all the virtual machines that are available to you. T he screen
consists of three areas: the title bar, a virtual machines area, and a details pane. A number of control
buttons allow you to work with the virtual machines.
Figure 3.1. T he User Portal
T he title bar (1) includes the name of the User logged in to the portal and the Sign out button.
In the virtual machines area, the name of the virtual machines or virtual machine pools assigned to you
display (2). T he logo of the virtual machine's operating system also displays (3). When a virtual machine is
powered up, you can connect to it by double-clicking on the virtual machine's logo.
On each virtual machine's icon, buttons allow you to play, stop or pause a virtual machine. T he buttons
perform the same functions as buttons on a media player (4).
20
Chapter 3. The Basic Tab
T he green play button starts up the virtual machine. It is available when the virtual machine is
paused, stopped or powered off.
T he red stop button stops the virtual machine. It is available when the virtual machine is running.
T he blue pause button temporarily halts the virtual machine. T o restart it, press the green play
button.
T he green reboot button reboots the virtual machine. It is available when the virtual machine is
running.
T he status of the virtual machine is indicated by the text below the virtual machine's icon - Machine is
Ready or Machine is Down.
Clicking on a virtual machine displays the statistics of the selected virtual machine on the details pane to
the right (5), including the operating system, defined memory, number of cores and size of virtual drives.
You can also configure connection protocol options (6) such as enabling the use of USB devices or local
drives.
Report a bug
3.2. Running Virtual Machines
3.2.1. Running Virtual Machines - Overview
In the User Portal, virtual machines are represented by icons that indicate both type and status. T he icons
indicate whether a virtual machine is part of a virtual machine pool or is a standalone Windows or Linux
virtual machine. T he icons also reflect whether the virtual machine is running or stopped.
T he User Portal displays a list of the virtual machines assigned to you. You can turn on one or more virtual
machines, connect, and log in. You can access virtual machines that are running different operating
systems, and you can use multiple virtual machines simultaneously.
In contrast, if you have only one running virtual machine and have enabled automatic connection, you can
bypass the User Portal and log in directly to the virtual machine, similar to how you log in to a physical
machine.
Report a bug
3.2.2. Turning on a Virtual Machine
T o use a virtual machine in the User Portal, you must turn it on and then connect to it. If a virtual machine
is turned off, it is grayed out and displays Machine is Down.
You can be assigned an individual virtual machine or assigned to one or more virtual machines that are
part of a virtual machine pool. Virtual machines in a pool are all clones of a base template, and have the
same operating system and installed applications.
21
Red Hat Enterprise Virtualization 3.4 User Guide
Note
When you take a virtual machine from a virtual machine pool, you are not guaranteed to receive the
same virtual machine each time. However, if you configure console options for a virtual machine
taken from a virtual machine pool, those options are saved as the default for all virtual machines
taken from that virtual machine pool.
Procedure 3.1. T urning on a Virtual Machine
1. T urn on the standalone virtual machine or take a virtual machine from a pool as follows:
T o turn on a standalone virtual machine, select the virtual machine icon and click the button.
Figure 3.2. T urn on virtual machine
T o take a virtual machine from a pool, select the virtual machine pool icon and click the button.
Figure 3.3. T ake virtual machine from a pool
If there is an available virtual machine in the pool, an icon for that virtual machine will appear in
your list. T he rest of this procedure then applies to that virtual machine. If you can take multiple
virtual machines from a pool, the icon for the virtual machine pool will change into an icon for the
last virtual machine you have taken when you take the maximum number of virtual machines
22
Chapter 3. The Basic Tab
possible for that pool.
2. T he virtual machine powers up.
Figure 3.4 . Virtual machine powering up
3. When the virtual machine is powered up, the icon is no longer grayed out. T he text displays as
Machine is Ready. You are now ready to connect.
Figure 3.5. Virtual machine turned on
Note
You can only connect to a virtual machine after it has powered up.
Report a bug
3.2.3. Connecting to a Powered-On Virtual Machine
After a virtual machine has been turned on, you can connect to it, log in, and start work in the same way as
you would with a physical machine. T he text "Machine is Ready" displays on virtual machines that are
powered up.
Procedure 3.2. Connecting to a Powered on Virtual Machine
23
Red Hat Enterprise Virtualization 3.4 User Guide
1. Double-click on the selected virtual machine to connect.
Figure 3.6. Connect to Virtual Machine
2. A console window of the virtual machine displays. You can now use the virtual machine in the same
way that you would use a physical desktop.
Note
If it is the first time you are connecting with SPICE, you will be prompted to install the appropriate
SPICE component or plug-in. If it is the first time you are connecting from a Red Hat Enterprise Linux
computer, install the SPICE plug-in for Mozilla Firefox. If you are connecting from a Windows
computer, install the ActiveX plug-in.
Report a bug
3.2.4. Logging out of a Virtual Machine
It is recommended that you log out from a virtual machine before shutting it down, to minimize the risk of
data loss. If you attempt to forcefully shut down a virtual machine from the User Portal without logging out
of it beforehand, its status will be frozen at "Powering Down". T o gracefully turn off a virtual machine, use
the following steps.
Procedure 3.3. Shutting down a virtual machine
1. Once you have finished using a virtual machine, log out of the guest operating system.
2. If you were using your virtual machine in full screen mode, press Shift+F11 to exit full screen
mode, and close the virtual machine's console window. You are now returned to the User Portal.
T o shut down the virtual machine, click the button. T he virtual machine is grayed out and
displays as "Machine is Down" when it has been turned off.
Report a bug
24
Chapter 4. The Extended Tab
Chapter 4. The Extended Tab
4.1. The Extended Tab Graphical Interface
T he Extended tab graphical interface enables you to access and monitor all the virtual resources that
are available to you. Eight elements of the Extended tab are explained below.
Figure 4 .1. T he Extended T ab
T able 4 .1. T he Extended T ab
Number Element Name Description
1 T itle Bar Includes the name of the User
logged in to the portal and the
Sign Out button.
2 User Portal View Option T abs Power Users have access to the
Extended tab of the User Portal
and the Basic tab of the User
Portal. T he Basic view is the
default view for users with basic
permissions.
25
Red Hat Enterprise Virtualization 3.4 User Guide
Number Element Name Description
3 Navigation Pane T he Navigation Pane allows you
to toggle between the Virtual
Machines, T emplates, and
Resources tabs.
4 Management Bar T he management bar is used to
create and make changes to
virtual machines.
5 Virtual Machine List T he list of virtual machines, with
the operating systems installed
on them and their statuses
(running, paused, or stopped).
6 Virtual Machine Control Buttons Virtual Machine Control Buttons
allow you to play, stop, pause, or
power off virtual machines.
T he green play button
starts the virtual machine. It is
available when the virtual
machine is paused, stopped
or powered off.
T he red stop button stops
the virtual machine. It is
available when the virtual
machine is running.
T he blue pause button
temporarily halts the virtual
machine. T o restart it, press
the green play button.
T he power button turns
off the virtual machine. It is
available when the virtual
machine is running.
T he reboot button
restarts the virtual machine. It
is available when the virtual
machine is running.
7 Console Button T he console button launches a
SPICE window and connects to
machines that have been
powered-up.
8 Details Pane T he Details Pane displays the
statistics of the virtual machine
selected in the Navigation Pane.
Details Pane T ab Functions:
T he General tab displays basic software and hardware information of the virtual machine, including
its name, operating system, display protocol and defined memory.
T he Network Interfaces tab displays the name, type and speed of the network connected to the
virtual machine. You can add, edit and remove network interfaces using this tab.
26
Chapter 4. The Extended Tab
T he Disks tab displays the name, size and format of the disk attached to the virtual machine. You can
add, edit and remove virtual disks using this tab.
T he Snapshots tab displays a view of the virtual machine's operating system and applications. You
can create and use snapshots using this tab.
T he Perm issions tab displays the users and roles assigned to each virtual machine. You can
assign and remove user permissions using this tab.
T he Events tab displays the description and time of events which affect the virtual machine.
T he Applications tab displays the applications which have been installed on the virtual machine.
T he Monitor tab displays the CPU Usage, Memory Usage, and Network Usage statistics for the
machine selected in the Navigation Pane.
T he Sessions tab displays the Logged-In User, Console User, and Console Client IP for the machine
selected in the Navigation Pane.
Report a bug
4.2. Running Virtual machines
4.2.1. Running Virtual Machines Introduction
T his chapter describes how to run, connect to and stop virtual machines on the Power User Portal. You
can use multiple virtual machines simultaneously, or use machines running different operating systems.
Report a bug
4.2.2. Connecting to Virtual Machines
After you have logged into the portal, you can start, stop, or connect to the virtual machines that are
displayed.
Summary
T his procedure describes how to start a stopped virtual machine, and how to connect to the virtual
machine.
Procedure 4 .1. Connecting to Virtual Machines
1.
Figure 4 .2. Virtual machine turned off
Select the virtual machine you wish to connect to and click the Play button. T he virtual machine
powers up. T he Stop symbol next to the virtual machine's name changes to a Powering Up symbol.
When the virtual machine is turned on, the Play symbol displays next to the virtual machine's name.
27
Red Hat Enterprise Virtualization 3.4 User Guide
Figure 4 .3. Virtual machine turned on
2. Click the Console button to connect to the virtual machine.
Figure 4 .4 . Connect to virtual machine
3. If it is the first time connecting with SPICE, you will be prompted to install the appropriate SPICE
component or plug-in. If you are connecting from a Windows computer, install the ActiveX
component. If you are connecting from a Red Hat Enterprise Linux computer, install the Mozilla
Firefox plug-in.
4. A console window of the virtual machine displays. You can now use the virtual machine in the same
way that you would use a physical desktop.
Result
You have started a stopped virtual machine and connected to it.
Warning
By default, a virtual machine running on Windows 7 will be suspended after an hour of inactivity.
T his prevents users from connecting to the virtual machine from the User Portal. T o avoid this,
disable the power-saving feature on the guest's power manager.
Report a bug
4.2.3. Turning Off a Virtual Machine from the User Portal
If you attempt to turn off a virtual machine from the User Portal, its status will freeze at Powering Down,
indicating that it has not completely shut down. Use the following procedure to gracefully turn off a virtual
machine from within the User Portal.
Important
T o minimize the risk of data loss, log off from a virtual machine before turning it off.
Summary
T his procedure explains how to turn off a virtual machine from the User Portal.
Procedure 4 .2. T urning Off a Virtual Machine from the User Portal
1. When you have finished using a virtual machine, log out of the guest operating system.
28
Chapter 4. The Extended Tab
2. If you were using your virtual machine in full screen mode, press Shift+F11 to exit full screen
mode, and close the virtual machine's console window. You are now returned to the User Portal.
T o turn off the virtual machine, click the button. T he Stop symbol appears next to the name of the
virtual machine when it has been turned off.
Result
You have turned off a virtual machine.
Note
You can also turn off virtual machines gracefully using the native method from within the virtual
machine itself. For example, in Windows virtual machines you can click Start → Shut Down, and in
Red Hat Enterprise Linux virtual machines you can click System → Shut Down.
Report a bug
4.2.4. Rebooting a Virtual Machine from the User Portal
Important
T o minimize the risk of data loss, log off from a virtual machine before rebooting.
Summary
T his procedure explains how to reboot a virtual machine from the User Portal.
Procedure 4 .3. Rebooting a Virtual Machine from the User Portal
1. T o reboot a virtual machine, log out of the guest operating system.
2. If you were using your virtual machine in full screen mode, press Shift+F11 to exit full screen
mode, and close the virtual machine's console window. You are now returned to the User Portal.
T o reboot the virtual machine, click the button. T he Reboot symbol appears next to the name of
the virtual machine while it is rebooting, then changes back to a Play symbol when reboot completes.
Result
You have rebooted a virtual machine.
Report a bug
4.3. Creating Virtual Machines
4.3.1. Creating a Virtual Machine
Summary
You can create a virtual machine using a blank template and configure all of its settings.
29
Red Hat Enterprise Virtualization 3.4 User Guide
Procedure 4 .4 . Creating a Virtual Machine
1. Click the Virtual Machines tab.
2. Click the New VM button to open the New Virtual Machine window.
Figure 4 .5. T he New Virtual Machine Window
3. On the General tab, fill in the Nam e and Operating System fields. You can accept the default
settings for other fields, or change them if required.
4. Alternatively, click the Initial Run, Console, Host, Resource Allocation, Boot Options,
and Custom Properties tabs in turn to define options for your virtual machine.
5. Click OK to create the virtual machine and close the window.
6. T he New Virtual Machine - Guide Me window opens. Use the Guide Me buttons to complete
configuration or click Configure Later to close the window.
Result
30
Chapter 4. The Extended Tab
T he new virtual machine is created and displays in the list of virtual machines with a status of Down.
Before you can use this virtual machine, add at least one network interface and one virtual disk, and install
an operating system.
Report a bug
4.3.2. Creating a Virtual Machine Based on a Template
Summary
You can create virtual machines based on templates. T his allows you to create virtual machines that are
pre-configured with an operating system, network interfaces, applications and other resources.
Note
Virtual machines created based on a template depend on that template. T his means that you
cannot remove that template from the Manager if there is a virtual machine that was created based
on that template. However, you can clone a virtual machine from a template to remove the
dependency on that template.
Procedure 4 .5. Creating a Virtual Machine Based on a T emplate
1. Click the Virtual Machines tab.
2. Click the New VM button to open the New Virtual Machine window.
3. Select the Cluster on which the virtual machine will run.
4. Select a template from the Based on T em plate drop-down menu.
5. Select a template sub version from the T em plate Sub Version drop-down menu.
6. Enter a Nam e, Description and any Com m ents, and accept the default values inherited from the
template in the rest of the fields. You can change them if needed.
7. Click the Resource Allocation tab.
31
Red Hat Enterprise Virtualization 3.4 User Guide
Figure 4 .6. Provisioning - T hin
8. Select the T hin radio button in the Storage Allocation area.
9. Select the disk provisioning policy from the Allocation Policy drop-down menu. T his selection
affects the speed of the clone operation and the amount of disk space the new virtual machine will
initially require.
Selecting T hin Provision results in a faster clone operation and provides optimized usage
of storage capacity. Disk space is allocated only as it is required. T his is the default selection.
Selecting Preallocated results in a slower clone operation and provides optimized virtual
machine read and write operations. All disk space requested in the template is allocated at the
time of the clone operation.
10. Select the storage domain on which the virtual disk for the virtual machine will be stored from the
T arget drop-down menu.
11. Click OK.
Result
T he virtual machine is created and displayed in the list in the Virtual Machines tab. You can now log
on to the virtual machine and begin using it, or assign users to it.
32
Chapter 4. The Extended Tab
Report a bug
4.3.3. Creating a Cloned Virtual Machine Based on a Template
Summary
Cloned virtual machines are similar to virtual machines based on templates. However, while a cloned virtual
machine inherits settings in the same way as a virtual machine based on a template, a cloned virtual
machine does not depend on the template on which it was based after it has been created.
Note
If you clone a virtual machine from a template, the name of the template on which that virtual
machine was based is displayed in the General tab of the Edit Virtual Machine window for
that virtual machine. If you change the name of that template, the name of the template in the
General tab will also be updated. However, if you delete the template from the Manager, the
original name of that template will be displayed instead.
Procedure 4 .6. Cloning a Virtual Machine Based on a T emplate
1. Click the Virtual Machines tab.
2. Click the New VM button to open the New Virtual Machine window.
3. Select the Cluster on which the virtual machine will run.
4. Select a template from the Based on T em plate drop-down menu.
5. Select a template sub version from the T em plate Sub Version drop-down menu.
6. Enter a Nam e, Description and any Com m ents, and accept the default values inherited from the
template in the rest of the fields. You can change them if needed.
7. Click the Resource Allocation tab.
33
Red Hat Enterprise Virtualization 3.4 User Guide
Figure 4 .7. Provisioning - Clone
8. Select the Clone radio button in the Storage Allocation area.
9. Select the disk provisioning policy from the Allocation Policy drop-down menu. T his selection
affects the speed of the clone operation and the amount of disk space the new virtual machine will
initially require.
Selecting T hin Provision results in a faster clone operation and provides optimized usage
of storage capacity. Disk space is allocated only as it is required. T his is the default selection.
Selecting Preallocated results in a slower clone operation and provides optimized virtual
machine read and write operations. All disk space requested in the template is allocated at the
time of the clone operation.
10. Select the storage domain on which the virtual disk for the virtual machine will be stored from the
T arget drop-down menu.
11. Click OK.
34
Chapter 4. The Extended Tab
Note
Cloning a virtual machine may take some time. A new copy of the template's disk must be created.
During this time, the virtual machine's status is first Im age Locked, then Down.
Result
T he virtual machine is created and displayed in the list in the Virtual Machines tab. You can now
assign users to it, and can begin using it when the clone operation is complete.
Report a bug
4.4. Explanation of Settings and Controls in the New Virtual
Machine and Edit Virtual Machine Windows
4.4.1. Virtual Machine General Settings Explained
T he following table details the options available on the General tab of the New Virtual Machine and
Edit Virtual Machine windows.
T able 4 .2. Virtual Machine: General Settings
Field Name Description
Cluster T he name of the host cluster to which the virtual
machine is attached. Virtual machines are hosted
on any physical machine in that cluster in
accordance with policy rules.
Based on T em plate T he template on which the virtual machine will be
based. T his field is set to Blank by default, which
allows you to create a virtual machine on which an
operating system has not yet been installed.
T em plate Sub Version T he version of the template on which the virtual
machine will be based. T his field is set to the most
recent version for the given template by default. If
no versions other than the base template are
available, this field is set to base tem plate by
default. Each version is marked by a number in
brackets that indicates the relative order of the
versions, with higher numbers indicating more
recent versions.
Operating System T he operating system. Valid values include a
range of Red Hat Enterprise Linux and Windows
variants.
35
Red Hat Enterprise Virtualization 3.4 User Guide
Field Name Description
Optim ized for T he type of system for which the virtual machine is
to be optimized. T here are two options: Server,
and Desktop, and the field is set to Server by
default. Virtual machines optimized to act as
servers have no sound card, use a cloned disk
image and are not stateless. In contrast, virtual
machines optimized to act as desktop machines
do have a sound card, use an image (thin
allocation) and are stateless.
Nam e T he name of virtual machine. Names must not
contain any spaces, and must contain at least one
character from A-Z or 0-9. T he maximum length of
a virtual machine name is 64 characters.
Description A meaningful description of the new virtual
machine.
Com m ent A field for adding plain text, human-readable
comments regarding the virtual machine.
Stateless Select this check box if the virtual machine is to run
in stateless mode. T he stateless mode is used
primarily for desktop virtual machines. Running a
stateless desktop or server creates a new COW
layer on the virtual machine hard disk image where
new and changed data is stored. Shutting down
the stateless virtual machine deletes the new
COW layer, returning the virtual machine to its
original state. T his type of virtual machine is useful
when creating virtual machines that need to be
used for a short time, or by temporary staff.
Start in Pause Mode Select this check box to always start the VM in
pause mode. T his option is suitable for virtual
machines which require a long time to establish a
SPICE connection, for example virtual machines in
remote locations.
Delete Protection Select this check box to make deletion of the virtual
machine impossible. It is possible to delete the
virtual machine only when this check box is not
selected.
At the bottom of the General tab is a drop-down box that allows you to assign network interfaces to the
new virtual machine. Use the plus and minus buttons to add or remove additional network interfaces.
Report a bug
4.4.2. Virtual Machine System Settings Explained
T he following table details the options available on the System tab of the New Virtual Machine and
Edit Virtual Machine windows.
T able 4 .3. Virtual Machine: System Settings
36
Chapter 4. The Extended Tab
Field Name Description
Mem ory Size T he amount of memory assigned to the virtual
machine. When allocating memory, consider the
processing and storage needs of the applications
that are intended to run on the virtual machine.
Maximum guest memory is constrained by the
selected guest architecture and the cluster
compatibility level.
T otal Virtual CPUs T he processing power allocated to the virtual
machine as CPU Cores. Do not assign more cores
to a virtual machine than are present on the
physical host.
Cores per Virtual Socket T he number of cores assigned to each virtual
socket.
Virtual Sockets T he number of CPU sockets for the virtual
machine. Do not assign more sockets to a virtual
machine than are present on the physical host.
Report a bug
4.4.3. Virtual Machine Initial Run Settings Explained
T he following table details the options available on the Initial Run tab of the New Virtual Machine
and Edit Virtual Machine windows. T he settings in this table are only visible if the Use Cloud-
Init/Sysprep check box is selected.
T able 4 .4 . Virtual Machine: Initial Run Settings
Field Name Description
Use Cloud-Init/Sysprep T his check box toggles whether Cloud-Init or
Sysprep will be used to initialize the virtual
machine.
VM Hostnam e Allows you to specify a host name for the virtual
machine.
Configure T im e Zone Allows you to apply a specific time zone for the
virtual machine. Select this check box and select a
time zone from the T im e Zone drop-down menu
to specify the time zone.
37
Red Hat Enterprise Virtualization 3.4 User Guide
Field Name Description
Authentication Allows you to configure authentication details for
the virtual machine. Click the disclosure arrow to
display the settings for this option.
Use already configured password:
Allows you to specify that any passwords that
have been configured for the virtual machine
will be used.
Root Password: Allows you to specify a root
password for the virtual machine. Enter the
password in this text field and the Verify
Root Password text field to verify the
password.
SSH Authorized Keys: Allows you to specify
SSH keys to be added to the authorized keys
file of the virtual machine.
Regenerate SSH Keys: Allows you to
regenerate SSH keys for the virtual machine.
Networks Allows you to specify network-related settings for
the virtual machine. Click the disclosure arrow to
display the settings for this option.
DNS Servers: Allows you to specify the DNS
servers to be used by the virtual machine.
DNS Search Dom ains: Allows you to specify
the DNS search domains to be used by the
virtual machine.
Network: Allows you to configure network
interfaces for the virtual machine. Select this
check box and use the + and - buttons to add
or remove network interfaces to or from the
virtual machine. When you click the + button, a
set of fields becomes visible that allow you to
specify whether to use DHCP, and configure an
IP address, netmask, and gateway, and specify
whether the network interface will start on boot.
Custom Script Allows you to enter custom scripts that will be run
on the virtual machine when it starts. T he scripts
entered in this field are custom YAML sections that
are added to those produced by the Manager, and
allow you to automate tasks such as creating
users and files, configuring yum repositories and
running commands. For more information on the
format of scripts that can be entered in this field,
see the Custom Script documentation.
Report a bug
4.4.4. Virtual Machine Console Settings Explained
38
Chapter 4. The Extended Tab
T he following table details the options available on the Console tab of the New Virtual Machine and
Edit Virtual Machine windows.
T able 4 .5. Virtual Machine: Console Settings
Field Name Description
Protocol Defines the display protocol to be used. SPICE is
the recommended protocol for Linux and Windows
virtual machines, excepting Windows 8 and
Windows Server 2012. Optionally, select VNC for
Linux virtual machines. A VNC client is required to
connect to a virtual machine using the VNC
protocol.
VNC Keyboard Layout Defines the keyboard layout for the virtual
machine. T his option is only available when using
the VNC protocol.
USB Support Defines whether USB devices can be used on the
virtual machine. T his option is only available for
virtual machines using the SPICE protocol. Select
either:
Disabled - Does not allow USB redirection
from the client machine to the virtual machine.
Legacy - Enables the SPICE USB redirection
policy used in Red Hat Enterprise Virtualization
3.0. T his option can only be used on Windows
virtual machines, and will not be supported in
future versions of Red Hat Enterprise
Virtualization.
Native - Enables native KVM/ SPICE USB
redirection for Linux and Windows virtual
machines. Virtual machines do not require any
in-guest agents or drivers for native USB. T his
option can only be used if the virtual machine's
cluster compatibility version is set to 3.1 or
higher.
Monitors T he number of monitors for the virtual machine.
T his option is only available for virtual desktops
using the SPICE display protocol. You can choose
1, 2 or 4 . Since Windows 8 and Windows Server
2012 virtual machines do not support the SPICE
protocol, they do not support multiple monitors.
Sm artcard Enabled Smart cards are an external hardware security
feature, most commonly seen in credit cards, but
also used by many businesses as authentication
tokens. Smart cards can be used to protect Red
Hat Enterprise Virtualization virtual machines. T ick
or untick the check box to activate and deactivate
Smart card authentication for individual virtual
machines.
39
Red Hat Enterprise Virtualization 3.4 User Guide
Field Name Description
Disable strict user checking Click the Advanced Param eters arrow and
select the check box to use this option. With this
option selected, the virtual machine does not need
to be rebooted when a different user connects to it.
By default, strict checking is enabled so that only
one user can connect to the console of a virtual
machine. No other user is able to open a console
to the same virtual machine until it has been
rebooted. T he exception is that a SuperUser can
connect at any time and replace a existing
connection. When a SuperUser has connected,
no normal user can connect again until the virtual
machine is rebooted.
Disable strict checking with caution, because you
can expose the previous user's session to the
new user.
Soundcard Enabled A sound card device is not necessary for all virtual
machine use cases. If it is for yours, enable a
sound card here.
VirtIO Console Device Enabled T he VirtIO console device is a console over VirtIO
transport for communication between the host user
space and guest user space. It has two parts:
device emulation in QEMU that presents a virtio-pci
device to the guest, and a guest driver that
presents a character device interface to user
space applications. T ick the check box to attach a
VirtIO console device to your virtual machine.
Report a bug
4.4.5. Virtual Machine Host Settings Explained
T he following table details the options available on the Host tab of the New Virtual Machine and
Edit Virtual Machine windows.
T able 4 .6. Virtual Machine: Host Settings
Field Name Description
40
Chapter 4. The Extended Tab
Field Name Description
Start Running On Defines the preferred host on which the virtual
machine is to run. Select either:
Any Host in Cluster - T he virtual machine
can start and run on any available host in the
cluster.
Specific - T he virtual machine will start
running on a particular host in the cluster.
However, the Manager or an administrator can
migrate the virtual machine to a different host in
the cluster depending on the migration and
high-availability settings of the virtual machine.
Select the specific host from the drop-down list
of available hosts.
Migration Options Defines options to run and migrate the virtual
machine. If the options here are not used, the
virtual machine will run or migrate according to its
cluster's policy.
Allow m anual and autom atic
m igration - T he virtual machine can be
automatically migrated from one host to another
in accordance with the status of the
environment, or manually by an administrator.
Allow m anual m igration only - T he
virtual machine can only be migrated from one
host to another manually by an administrator.
Do not allow m igration - T he virtual
machine cannot be migrated, either
automatically or manually.
T he Use Host CPU check box allows virtual
machines to take advantage of the features of the
physical CPU of the host on which they are
situated. T his option can only be enabled when
Allow m anual m igration only or Do not
allow m igration are selected.
T he Use custom m igration downtim e
check box allows you to specify the maximum
number of milliseconds the virtual machine can be
down during live migration. Configure different
maximum downtimes for each virtual machine
according to its workload and SLA requirements.
T he VDSM default value is 0.
Report a bug
41
Red Hat Enterprise Virtualization 3.4 User Guide
4.4.6. Virtual Machine High Availability Settings Explained
T he following table details the options available on the High Availability tab of the New Virtual
Machine and Edit Virtual Machine windows.
T able 4 .7. Virtual Machine: High Availability Settings
Field Name Description
Highly Available Select this check box if the virtual machine is to be
highly available. For example, in cases of host
maintenance or failure, the virtual machine will be
automatically moved to or re-launched on another
host. If the host is manually shut down by the
system administrator, the virtual machine is not
automatically moved to another host.
Note that this option is unavailable if the
Migration Options setting in the Hosts tab is
set to either Allow m anual m igration only
or No m igration. For a virtual machine to be
highly available, it must be possible for the
Manager to migrate the virtual machine to other
available hosts as necessary.
Priority for Run/Migration queue Sets the priority level for the virtual machine to be
migrated or restarted on another host.
42
Chapter 4. The Extended Tab
Field Name Description
Watchdog Allows users to attach a watchdog card to a virtual
machine. A watchdog is a timer that is used to
automatically detect and recover from failures.
Once set, a watchdog timer continually counts
down to zero while the system is in operation, and
is periodically restarted by the system to prevent it
from reaching zero. If the timer reaches zero, it
signifies that the system has been unable to reset
the timer and is therefore experiencing a failure.
Corrective actions are then taken to address the
failure. T his functionality is especially useful for
servers that demand high availability.
Watchdog Model: T he model of watchdog card
to assign to the virtual machine. At current, the only
supported model is i6300esb.
Watchdog Action: T he action to take if the
watchdog timer reaches zero. T he following
actions are available:
none - No action is taken. However, the
watchdog event is recorded in the audit log.
reset - T he virtual machine is reset and the
Manager is notified of the reset action.
poweroff - T he virtual machine is immediately
shut down.
dum p - A dump is performed and the virtual
machine is paused.
pause - T he virtual machine is paused, and
can be resumed by users.
Report a bug
4.4.7. Virtual Machine Resource Allocation Settings Explained
T he following table details the options available on the Resource Allocation tab of the New Virtual
Machine and Edit Virtual Machine windows.
T able 4 .8. Virtual Machine: Resource Allocation Settings
Field Name Sub-element Description
43
Red Hat Enterprise Virtualization 3.4 User Guide
Field Name Sub-element Description
CPU Allocation CPU Shares Allows users the set the level of
CPU resources a virtual machine
can demand relative to other
virtual machines.
Low - 512
Medium - 1024
High - 2048
Custom - A custom level of
CPU shares defined by the
user.
CPU Pinning topology Enables the virtual machine's
virtual CPU (vCPU) to run on a
specific physical CPU (pCPU) in
a specific host. T his option is not
supported if the virtual machine's
cluster compatibility version is
set to 3.0. T he syntax of CPU
pinning is v#p[_v#p], for
example:
0#0 - Pins vCPU 0 to pCPU
0.
0#0_1#3 - Pins vCPU 0 to
pCPU 0, and pins vCPU 1 to
pCPU 3.
1#1-4 ,^2 - Pins vCPU 1 to
one of the pCPUs in the
range of 1 to 4, excluding
pCPU 2.
In order to pin a virtual machine
to a host, you must select Do
not allow m igration under
Migration Options, and
select the Use Host CPU check
box.
Mem ory Allocation T he amount of physical memory
guaranteed for this virtual
machine.
Storage Allocation T he T em plate
Provisioning option is only
available when the virtual
machine is created from a
template.
T hin Provides optimized usage of
storage capacity. Disk space is
allocated only as it is required.
44
Chapter 4. The Extended Tab
Field Name Sub-element Description
Clone Optimized for the speed of guest
read and write operations. All
disk space requested in the
template is allocated at the time
of the clone operation.
VirtIO-SCSI Enabled Allows users to enable or
disable the use of VirtIO-SCSI on
the virtual machines.
Report a bug
4.4.8. Virtual Machine Boot Options Settings Explained
T he following table details the options available on the Boot Options tab of the New Virtual
Machine and Edit Virtual Machine windows
T able 4 .9. Virtual Machine: Boot Options Settings
Field Name Description
First Device After installing a new virtual machine, the new
virtual machine must go into Boot mode before
powering up. Select the first device that the virtual
machine must try to boot:
Hard Disk
CD-ROM
Network (PXE)
Second Device Select the second device for the virtual machine to
use to boot if the first device is not available. T he
first device selected in the previous option does
not appear in the options.
Attach CD If you have selected CD-ROM as a boot device, tick
this check box and select a CD-ROM image from
the drop-down menu. T he images must be
available in the ISO domain.
Report a bug
4.4.9. Virtual Machine Custom Properties Settings Explained
T he following table details the options available on the Custom Properties tab of the New Virtual
Machine and Edit Virtual Machine windows.
T able 4 .10. Virtual Machine: Custom Properties Settings
Field Name Description Recommendations and
Limitations
sap_agent Enables SAP monitoring on the -
virtual machine. Set to true or
false.
45
Red Hat Enterprise Virtualization 3.4 User Guide
Field Name Description Recommendations and
Limitations
sndbuf Enter the size of the buffer for -
sending the virtual machine's
outgoing data over the socket.
Default value is 0.
vhost Disables vhost-net, which is the vhost-net provides better
kernel-based virtio network performance than virtio-net, and
driver on virtual network interface if it is present, it is enabled on all
cards attached to the virtual virtual machine NICs by default.
machine. T o disable vhost, the Disabling this property makes it
format for this property is: easier to isolate and diagnose
performance issues, or to debug
LogicalNetworkName: vhost-net errors, for example if
false migration fails for virtual
machines on which vhost does
T his will explicitly start the virtual not exist.
machine without the vhost-net
setting on the virtual NIC
attached to
LogicalNetworkName.
viodiskcache Caching mode for the virtio disk. For Red Hat Enterprise
writethrough writes data to Virtualization 3.1, if viodiskcache
the cache and the disk in is enabled, the virtual machine
parallel, writeback does not cannot be live migrated.
copy modifications from the
cache to the disk, and none
disables caching.
Warning
Increasing the value of the sndbuf custom property results in increased occurrences of
communication failure between hosts and unresponsive virtual machines.
Report a bug
4.5. Configuring Virtual Machines
4.5.1. Completing the Configuration of a Virtual Machine by Defining Network
Interfaces and Hard Disks
Summary
Before you can use your newly created virtual machine, the Guide Me window prompts you to configure at
least one network interface and one virtual disk for the virtual machine.
Procedure 4 .7. Completing the Configuration of a Virtual Machine by Defining Network
Interfaces and Hard Disks
46
Chapter 4. The Extended Tab
1. On the New Virtual Machine - Guide Me window, click the Configure Network
Interfaces button to open the New Network Interface window. You can accept the default
values or change them as necessary.
Figure 4 .8. New Network Interface window
Enter the Nam e of the network interface.
2. Use the drop-down menus to select the Network and the T ype of network interface for the new
virtual machine. T he Link State is set to Up by default when the NIC is defined on the virtual
machine and connected to the network.
Note
T he options on the Network and T ype fields are populated by the networks available to the
cluster, and the NICs available to the virtual machine.
3. If applicable, select the Specify custom MAC address check box and enter the network
interface's MAC address.
4. Click the arrow next to Advanced Param eters to configure the Port Mirroring and Card
Status fields, if necessary.
5. Click OK to close the New Network Interface window and open the New Virtual Machine
- Guide Me window.
6. Click the Configure Virtual Disk button to open the New Virtual Disk window.
7. Add either an Internal virtual disk or an External LUN to the virtual machine.
47
Red Hat Enterprise Virtualization 3.4 User Guide
Figure 4 .9. New Virtual Disk Window
8. Click OK to close the New Virtual Disk window. T he New Virtual Machine - Guide Me
window opens with changed context. T here is no further mandatory configuration.
9. Click Configure Later to close the window.
Result
You have added a network interface and a virtual disk to your virtual machine.
Report a bug
4.5.2. Installing Windows on VirtIO-Optimized Hardware
Summary
T he virtio-win.vfd diskette image contains Windows drivers for VirtIO-optimized disk and network
devices. T hese drivers provide a performance improvement over emulated device drivers.
T he virtio-win.vfd is placed automatically on ISO storage domains that are hosted on the Manager
server. It must be manually uploaded using the engine-iso-uploader tool to other ISO storage domains.
You can install the VirtIO-optimized device drivers during your Windows installation by attaching a diskette
to your virtual machine.
48
Chapter 4. The Extended Tab
T his procedure presumes that you added a Red Hat VirtIO network interface and a disk that uses the
VirtIO interface to your virtual machine.
Procedure 4 .8. Installing VirtIO Drivers during Windows Installation
1. Click the Virtual Machines tab and select a virtual machine.
2. Click the Run Once button, and the Run Once window displays.
3. Click Boot Options to expand the Boot Options configuration options.
4. Click the Attach Floppy check box, and select virtio-win.vfd from the drop down selection
box.
5. Click the Attach CD check box, and select from the drop down selection box the ISO containing the
version of Windows you want to install.
6. Move CD-ROM UP in the Boot Sequence field.
7. Configure the rest of your Run Once options as required, and click OK to start your virtual machine,
and then click the Console button to open a graphical console to your virtual machine.
Result
Windows installations include an option to load additional drivers early in the installation process. Use this
option to load drivers from the virtio-win.vfd diskette that was attached to your virtual machine as A:.
For each supported virtual machine architecture and Windows version, there is a folder on the disk
containing optimized hardware device drivers.
Report a bug
4.5.3. Virtual Machine Run Once Settings Explained
T he Run Once window defines one-off boot options for a virtual machine. For persistent boot options, use
the Boot Options tab in the New Virtual Machine window. T he following table details the
information required for the Run Once window.
T able 4 .11. Virtual Machine: Run Once Settings
Field Name Description
49
Red Hat Enterprise Virtualization 3.4 User Guide
Field Name Description
Boot Options Defines the virtual machine's boot sequence,
running options, and source images for installing
the operating system and required drivers.
Attach Floppy - Attaches a diskette image
to the virtual machine. Use this option to install
Windows drivers. T he diskette image must
reside in the ISO domain.
Attach CD - Attaches an ISO image to the
virtual machine. Use this option to install the
virtual machine's operating system and
applications. T he CD image must reside in the
ISO domain.
Boot Sequence - Determines the order in
which the boot devices are used to boot the
virtual machine. Select either Hard Disk, CD-
ROM or Network, and use the arrow keys to
move the option up or down.
Run Stateless - Deletes all changes to the
virtual machine upon shutdown. T his option is
only available when you have attached a virtual
disk to the virtual machine.
Start in Pause Mode - Starts then pauses
the virtual machine to enable connection to the
console, suitable for virtual machines in remote
locations.
Linux Boot Options T he following options boot a Linux kernel directly
instead of through the BIOS bootloader.
kernel path - A fully qualified path to a
kernel image to boot the virtual machine. T he
kernel image must be stored on either the ISO
domain (path name in the format of
iso://path-to-im age) or on the host's
local storage domain (path name in the format
of /data/im ages).
initrd path - A fully qualified path to a
ramdisk image to be used with the previously
specified kernel. T he ramdisk image must be
stored on the ISO domain (path name in the
format of iso://path-to-im age) or on the
host's local storage domain (path name in the
format of /data/im ages).
kernel param s - Kernel command line
parameter strings to be used with the defined
kernel on boot.
Initial Run Allows you to specify whether Cloud-Init or
50
Chapter 4. The Extended Tab
Field Name Sysprep will be used to initialize the virtual
Description
machine. T he Use Cloud-Init check box is the
only main option in the Initial Run section; the
following rows outline the settings for configuring
this feature.
VM Hostnam e - Allows you to specify a host
name for the virtual machine.
Configure T im e Zone - Allows you to
apply a specific time zone for the virtual
machine. Select this check box and select a
time zone from the T im e Zone drop-down
menu to specify the time zone.
Authentication
Use already configured password -
Allows you to specify that any passwords that
have been configured for the virtual machine
will be used.
Root Password - Allows you to specify a root
password for the virtual machine. Enter the
password in this text field and the Verify
Root Password text field to verify the
password.
SSH Authorized Keys - Allows you to
specify SSH keys to be added to the
authorized keys file of the virtual machine.
Regenerate SSH Keys - Allows you to
regenerate SSH keys for the virtual machine.
Networks
DNS Servers: Allows you to specify the DNS
servers to be used by the virtual machine.
DNS Search Dom ains: Allows you to specify
the DNS search domains to be used by the
virtual machine.
Network: Allows you to configure network
interfaces for the virtual machine. Select this
check box and use the + and - buttons to add
or remove network interfaces to or from the
virtual machine. When you click the + button, a
set of fields becomes visible that allow you to
specify whether to use DHCP, and configure an
IP address, netmask, and gateway, and specify
whether the network interface will start on boot.
Custom Script
Allows you to enter custom scripts that will be
run on the virtual machine when it starts. T he
scripts entered in this field are custom YAML
sections that are added to those produced by
the Manager, and allow you to automate tasks
51
Red Hat Enterprise Virtualization 3.4 User Guide
Field Name such as creating users and files, configuring
Description
yum repositories and running commands. For
more information on the format of scripts that
can be entered in this field, see the Custom
Script documentation.
Host Defines the virtual machine's host.
Any host in cluster: - Allocates the
virtual machine to any available host.
Specific - Allows the user to define a
specific host for the virtual machine.
Display Protocol Defines the protocol to connect to virtual machines.
VNC - Can be used for Linux virtual machines.
Requires a VNC client to connect to a virtual
machine using VNC. Here you can also specify
VNC Keyboard Layout from the drop-down
menu.
SPICE - Recommended protocol for Linux and
Windows virtual machines, excepting Windows
8 and Server 2012 virtual machines.
Custom Properties Additional VDSM options for running virtual
machines.
sap_agent - Enables SAP monitoring on the
virtual machine. Set to true or false.
sndbuf - Enter the size of the buffer for
sending the virtual machine's outgoing data
over the socket.
vhost - Enter the name of the virtual host on
which this virtual machine should run. T he
name can contain any combination of letters
and numbers.
viodiskcache - Caching mode for the virtio
disk. writethrough writes data to the cache
and the disk in parallel, writeback does not
copy modifications from the cache to the disk,
and none disables caching.
Report a bug
4.5.4. Configuring a Watchdog
4 .5.4 .1. Adding a Watchdog Card to a Virtual Machine
Summary
52
Chapter 4. The Extended Tab
Add a watchdog card to a virtual machine.
Procedure 4 .9. Adding a Watchdog Card to a Virtual Machine
1. Click the Virtual Machines tab and select a virtual machine.
2. Click Edit to open the Edit Virtual Machine window.
3. Click Show Advanced Options to display all tabs and click the High Availability tab.
4. From the Watchdog Model drop-down menu, select the watchdog model to use.
5. From the Watchdog Action drop-down menu, select the action that the virtual machine will take
when the watchdog is triggered.
6. Click OK.
Result
You have added a watchdog card to the virtual machine.
Report a bug
4 .5.4 .2. Configuring a Watchdog
Summary
T o activate a watchdog card attached to a virtual machine, you must install the watchdog package on that
virtual machine and start the watchdog service.
Procedure 4 .10. Configuring a Watchdog
1. Log on to the virtual machine on which the watchdog card is attached.
2. Run the following command to install the watchdog package and dependencies:
# yum install watchdog
3. Edit the /etc/watchdog.conf file and uncomment the following line:
watchdog-device = /dev/watchdog
4. Save the changes.
5. Run the following commands to start the watchdog service and ensure this service starts on boot:
# service watchdog start
# chkconfig watchdog on
Result
You have configured the watchdog service on a virtual machine.
Report a bug
53
Red Hat Enterprise Virtualization 3.4 User Guide
4 .5.4 .3. Confirming Watchdog Functionality
Summary
Confirm that a watchdog card has been attached to a virtual machine and that the watchdog service is
active.
Warning
T his procedure is provided for testing the functionality of watchdogs only and must not be run on
production machines.
Procedure 4 .11. Confirming Watchdog Functionality
1. Log on to the virtual machine on which the watchdog card is attached.
2. Run the following command to confirm that the watchdog card has been identified by the virtual
machine:
# lspci | grep watchdog -i
3. Run one of the following commands to confirm that the watchdog is active:
Run the following command to trigger a kernel panic:
# echo c > /proc/sysrq-trigger
Run the following command to terminate the watchdog service:
# kill -9 `pgrep watchdog`
Result
T he watchdog timer can no longer be reset, so the watchdog counter reaches zero after a short period of
time. When the watchdog counter reaches zero, the action specified in the Watchdog Action drop-down
menu for that virtual machine is performed.
Report a bug
4 .5.4 .4 . Parameters for Watchdogs in watchdog.conf
T he following is a list of options for configuring the watchdog service available in the
/etc/watchdog.conf file. T o configure an option, you must ensure that option is uncommented and
restart the watchdog service after saving the changes.
Note
For a more detailed explanation of options for configuring the watchdog service and using the
watchdog command, see the watchdog man page.
54
Chapter 4. The Extended Tab
T able 4 .12. watchdog.conf variables
Variable name Default Value Remarks
ping N/A An IP address that the watchdog will
attempt to ping to verify whether that
address is reachable. You can specify
multiple IP addresses by adding
additional ping lines.
interface N/A A network interface that the watchdog
will monitor to verify the presence of
network traffic. You can specify multiple
network interfaces by adding additional
interface lines.
file /var/log/m essa A file on the local system that the
ges watchdog will monitor for changes. You
can specify multiple files by adding
additional file lines.
change 14 07 T he number of watchdog intervals after
which the watchdog checks for changes
to files. A change line must be
specified on the line directly after each
file line, and applies to the file line
directly above that change line.
m ax-load-1 24 T he maximum average load that the
virtual machine can sustain over a one-
minute period. If this average is
exceeded, the watchdog will be
triggered. A value of 0 disables this
feature.
m ax-load-5 18 T he maximum average load that the
virtual machine can sustain over a five-
minute period. If this average is
exceeded, the watchdog will be
triggered. A value of 0 disables this
feature. By default, the value of this
variable is set to a value approximately
three quarters that of m ax-load-1.
m ax-load-15 12 T he maximum average load that the
virtual machine can sustain over a
fifteen-minute period. If this average is
exceeded, the watchdog will be
triggered. A value of 0 disables this
feature. By default, the value of this
variable is set to a value approximately
one half that of m ax-load-1.
m in-m em ory 1 T he minimum amount of virtual memory
that must remain free on the virtual
machine. T his value is measured in
pages. A value of 0 disables this
feature.
55
Red Hat Enterprise Virtualization 3.4 User Guide
Variable name Default Value Remarks
repair-binary /usr/sbin/repa T he path and file name of a binary file
ir on the local system that will be run
when the watchdog is triggered. If the
specified file resolves the issues
preventing the watchdog from resetting
the watchdog counter, the watchdog
action will not be triggered.
test-binary N/A T he path and file name of a binary file
on the local system that the watchdog
will attempt to run during each interval. A
test binary allows you to specify a file
for running user-defined tests.
test-tim eout N/A T he time limit, in seconds, for which
user-defined tests can run. A value of 0
allows user-defined tests to continue for
an unlimited duration.
tem perature-device N/A T he path to and name of a device for
checking the temperature of the
machine on which the watchdog
service is running.
m ax-tem perature 120 T he maximum allowed temperature for
the machine on which the watchdog
service is running. T he machine will be
halted if this temperature is reached.
Unit conversion is not taken into
account, so you must specify a value
that matches the watchdog card being
used.
adm in root T he email address to which email
notifications will be sent.
interval 10 T he interval, in seconds, between
updates to the watchdog device. T he
watchdog device expects an update at
least once every minute, and if there are
no updates over a one-minute period,
the watchdog will be triggered. T his
one-minute period is hard-coded into
the drivers for the watchdog device, and
cannot be configured.
logtick 1 When verbose logging is enabled for
the watchdog service, the watchdog
service periodically writes log
messages to the local system. T he
logtick value represents the number
of watchdog intervals after which a
message is written.
56
Chapter 4. The Extended Tab
Variable name Default Value Remarks
realtim e yes Specifies whether the watchdog is
locked in memory. A value of yes locks
the watchdog in memory so that it is not
swapped out of memory, while a value
of no allows the watchdog to be
swapped out of memory. If the watchdog
is swapped out of memory and is not
swapped back in before the watchdog
counter reaches zero, the watchdog will
be triggered.
priority 1 T he schedule priority when the value of
realtim e is set to yes.
pidfile /var/run/syslo T he path and file name of a PID file that
gd.pid the watchdog will monitor to see if the
corresponding process is still active. If
the corresponding process is not active,
the watchdog will be triggered.
Report a bug
4.6. Editing Virtual Machines
4.6.1. Editing Virtual Machine Properties
Summary
Changes to storage, operating system or networking parameters can adversely affect the virtual machine.
Ensure that you have the correct details before attempting to make any changes. Virtual machines must be
powered off before some changes can be made to them. T his procedure explains how to edit a virtual
machine. It is necessary to edit virtual machines when you want to change the settings of the virtual
machine.
T he following fields can be edited while a virtual machine is running:
Nam e
Description
Com m ent
Delete Protection
Network Interfaces
Use Cloud-Init/Sysprep (and its properties)
Use custom m igration downtim e
Highly Available
Priority for Run/Migration queue
Watchdog Model
57
Red Hat Enterprise Virtualization 3.4 User Guide
Watchdog Action
Physical Mem ory Guaranteed
Mem ory Balloon Device Enabled
VirtIO-SCSI Enabled
First Device
Second Device
Attach CD
kernel path
initrd path
kernel param eters
T o change all other settings, the virtual machine must be powered off.
Procedure 4 .12. Editing a virtual machine:
1. Select the virtual machine to be edited. Click the Edit button to open the Edit Virtual
Machine window.
2. Change the General, System , Initial Run, Console, Host, High Availability,
Resource Allocation, Boot Options, and Custom Options fields as required.
3. Click OK to save your changes. Your changes will be applied once you restart your virtual machine.
Result
You have changed the settings of a virtual machine by editing it.
Report a bug
4.6.2. Editing a Network Interface
Summary
T his procedure describes editing a network interface. In order to change any network settings, you must
edit the network interface.
Procedure 4 .13. Editing a Network Interface
1. Click the Virtual Machines tab and select a virtual machine.
2. Click the Network Interfaces tab of the details pane and select the network interface to edit.
3. Click Edit to open the Edit Network Interface window. T his dialog contains the same fields
as the New Network Interface dialog.
58
Chapter 4. The Extended Tab
4. After you have made the required changes, click OK to save your changes.
Result
You have now changed the network interface by editing it.
Report a bug
4.6.3. Extending the Size of an Online Virtual Disk
Summary
T his procedure explains how to extend the size of a virtual drive while the virtual drive is attached to a
virtual machine.
Procedure 4 .14 . Extending the Size of an Online Virtual Disk
1. Click the Virtual Machines tab and select a virtual machine.
2. Select the Disks tab in the details pane.
3. Select a target disk from the list in the details pane.
4. Click the Edit button in the details pane.
5. Enter a value in the Extend size by(GB) field.
6. Click OK button.
Result
T he target disk's status becomes locked for a short time, during which the drive is resized. When the
resizing of the drive is complete, the status of the drive becomes OK.
Report a bug
4.6.4. Floating Disks
Floating disks are disks that are not associated with any virtual machine.
Floating disks can minimize the amount of time required to set up virtual machines. Designating a floating
disk as storage for a virtual machine makes it unnecessary to wait for disk preallocation at the time of a
virtual machine's creation.
Floating disks can be attached to virtual machines or designated as shareable disks, which can be used
with one or more virtual machines.
Report a bug
4.6.5. Associating a Virtual Disk with a Virtual Machine
Summary
T his procedure explains how to associate a virtual disk with a virtual machine. Once the virtual disk is
associated with the virtual machine, the virtual machine is able to access it.
59
Red Hat Enterprise Virtualization 3.4 User Guide
Procedure 4 .15. Associating a Virtual Disk with a Virtual Machine
1. Click the Virtual Machines tab and select a virtual machine.
2. In the details pane, select the Disks tab.
3. Click Add in the menu at the top of the Details Pane.
4. T ype the size in GB of the disk into the Size(GB) field.
5. T ype the disk alias into the Alias field.
6. Click OK in the bottom right corner of the Add Virtual Disk window.
7. T he disk you have associated with the virtual machine appears in the details pane after a short time.
Result
T he virtual disk is associated with the virtual machine.
Note
No Quota resources are consumed by attaching virtual disks to, or detaching virtual disks from,
virtual machines.
Note
Using the above procedure, it is now possible to attach a virtual disk to more than one virtual
machine.
Report a bug
4.6.6. Changing the CD for a Virtual Machine
Summary
You can change the CD accessible to a virtual machine while that virtual machine is running.
Note
You can only use ISO files that have been added to the ISO domain of the cluster in which the
virtual machine is a member. T herefore, you must upload ISO files to that domain before you can
make those ISO files accessible to virtual machines.
Procedure 4 .16. Changing the CD for a Virtual Machine
1. From the Virtual Machines tab, select a virtual machine that is currently running.
60
Chapter 4. The Extended Tab
2. Click the Change CD button to open the Change CD window.
Figure 4 .10. T he Change CD Window
3. From the drop-down menu, select [Eject] to eject the CD currently accessible to the virtual
machine, or select an ISO file from the list to eject the CD currently accessible to the virtual machine
and mount that ISO file as a CD.
4. Click OK.
Result
You have ejected the CD previously accessible to the virtual machine, or ejected the CD previously
accessible to the virtual machine and made a new CD accessible to that virtual machine
Report a bug
4.6.7. Smart card Authentication
Smart cards are an external hardware security feature, most commonly seen in credit cards, but also used
by many businesses as authentication tokens. Smart cards can be used to protect Red Hat Enterprise
Virtualization virtual machines.
Report a bug
4.6.8. Enabling and Disabling Smart cards
Summary
T he following procedure explains how to enable and disable the Smart card feature for virtual machines.
Procedure 4 .17. Enabling and Disabling Smart cards
1. Ensure that the Smart card hardware is plugged into the client machine and is installed according to
manufacturer's directions.
2. Select the desired virtual machine, and click the Edit button. T he Edit Virtual Machine
window will appear.
3. Select the Console tab, and tick the check box labeled Sm artcard enabled, then click Ok.
4. Run the virtual machine by clicking the Console icon or through the User Portal; Smart card
authentication is now passed from the client hardware to the virtual machine.
61
Red Hat Enterprise Virtualization 3.4 User Guide
5. T o disable Smart card authentication, return to the Edit Virtual Machine window and untick
the Sm artcard enabled check box.
Result
You can now enable and disable Smart card authentication on virtual machines.
Important
If the Smart card hardware is not correctly installed, enabling the Smart card feature will result in the
virtual machine failing to load properly.
Report a bug
4.7. Removing Virtual Machines
4.7.1. Removing a Virtual Machine
Summary
Remove a virtual machine from the Red Hat Enterprise Virtualization environment.
Important
T he Rem ove button is disabled while virtual machines are running; you must shut down a virtual
machine before you can remove it.
Procedure 4 .18. Removing a Virtual Machine
1. Click the Virtual Machines tab and select the virtual machine to remove.
2. Click the Rem ove button to open the Rem ove Virtual Machine(s) window.
3. Optionally, select the Rem ove Disk(s) check box to remove the virtual disks attached to the virtual
machine together with the virtual machine. If the Rem ove Disk(s) check box is cleared, the virtual
disks will remain in the environment as floating disks.
4. Click OK.
Result
T he virtual machine is removed from the environment and is no longer listed in the Virtual Machines
resource tab. If you selected the Rem ove Disk(s) check box, the virtual disks attached to the virtual
machine are also removed.
Report a bug
4.8. Snapshots
62
Chapter 4. The Extended Tab
4.8.1. Managing Snapshots
Before you make changes to your virtual machine, it is good practice to back up all the virtual machine's
existing data using snapshots. A snapshot displays a view of the virtual machine's operating system and
all its applications at a given point in time, and can be used to restore a virtual machine to a previous state.
Important
Live snapshots can only be taken on Data Centers running Red Hat Enterprise Virtualization 3.1 or
higher. Otherwise, the virtual machine must first be powered down.
Report a bug
4.8.2. Creating Snapshots
Summary
T his procedure explains how to create a snapshot of a virtual machine.
Procedure 4 .19. Creating a snapshot of a virtual machine
1. Click the Virtual Machines tab and select a virtual machine.
2. Select the Snapshots tab in the details pane. Click Create.
3. T he Create Snapshot dialog displays. Enter a description for the snapshot, select Disks to
include using the check boxes. and click OK.
4. A new snapshot of the virtual machine's operating system and applications is created. It displays in
a list on the left side of the Snapshots tab.
Result
You have taken a snapshot of a virtual machine.
Report a bug
4.8.3. Cloning Snapshots
Summary
T his procedure explains how to clone a virtual machine from a snapshot.
Procedure 4 .20. Cloning Snapshots
1. Click the Virtual Machines tab and select a virtual machine.
2. Select the Snapshots tab in the details pane.
3. Select the snapshot from which to create a clone in the list in the details pane.
4. Click Clone at the top of the details pane.
63
Red Hat Enterprise Virtualization 3.4 User Guide
5. T he Clone VM from Snapshot window opens. T his window is similar to the New VM window. Fill
in the parameters and click OK in the lower-right corner of the Clone VM from Snapshot
window.
Result
You have cloned a virtual machine from a snapshot.
Report a bug
4.8.4. Using a Snapshot to Restore a Virtual Machine
Summary
A snapshot can be used to restore a virtual machine to its previous state.
Procedure 4 .21. Using a snapshot to restore a virtual machine
1. Click the Virtual Machines tab and select a virtual machine.
2. Click the Snapshots tab in the details pane to list the available snapshots.
3. Select a snapshot to restore in the left side-pane. T he snapshot details display in the right side-
pane.
4. Click the drop down beside Preview to open the Custom Preview Snapshot window.
Figure 4 .11. Custom preview snapshot
5. Use the check boxes to select the VM Configuration, Mem ory, and Disk/s you wish to restore,
then click OK. T his allows you to create and restore from a customized snapshot using the
configuration and disk/s from multiple snapshots.
64
Chapter 4. The Extended Tab
Figure 4 .12. Custom preview snapshot
T he status of the snapshot will change to Preview Mode. T he status of the virtual machine briefly
changes to Im age Locked before returning to Down.
6. Start the virtual machine and it will run with the disk image of the snapshot.
7. Click Com m it to permanently restore the virtual machine to the condition of the snapshot. Any
subsequent snapshots are erased.
Alternatively, click the Undo button to deactivate the snapshot and return the virtual machine to its
previous state.
Result
T he virtual machine is restored to its state at the time of the snapshot, or returned to its state before the
preview of the snapshot.
Report a bug
4.8.5. Deleting Snapshots
Summary
T his procedure describes how to delete a snapshot.
Procedure 4 .22. Deleting a Snapshot
1. Click the Virtual Machines tab and select a virtual machine.
65
Red Hat Enterprise Virtualization 3.4 User Guide
2. Select the Snapshots tab. A list of snapshots displays.
3. Select the snapshot to delete and click the Delete button. A dialog prompts you to confirm the
deletion. Click OK to continue.
Result
You have deleted a snapshot.
Important
Deleting a snapshot does not remove any information from the virtual machine - it simply removes a
return-point. However, restoring a virtual machine from a snapshot deletes any content that was
written to the virtual machine after the time the snapshot was taken.
Report a bug
4.9. Templates
4.9.1. Introduction to Templates
A template is a copy of a preconfigured virtual machine, used to simplify the subsequent, repeated creation
of similar virtual machines. T emplates capture installed software and software configurations, as well as
the hardware configuration, of the original virtual machine.
When you create a template from a virtual machine, a read-only copy of the virtual machine's disk is taken.
T he read-only disk becomes the base disk image of the new template, and of any virtual machines created
from the template. As such, the template cannot be deleted whilst virtual machines created from the
template exist in the environment.
Virtual machines created from a template use the same NIC type and driver as the original virtual machine,
but utilize separate and unique MAC addresses.
Note
A virtual machine may require to be sealed before being used to create a template.
Report a bug
4.9.2. Template Tasks
4 .9.2.1. Creating a T emplate
Summary
Create a template from an existing virtual machine to use as a blueprint for creating additional virtual
machines.
Procedure 4 .23. Creating a T emplate from an Existing Virtual Machine
66
Chapter 4. The Extended Tab
1. Click the Virtual Machines tab and select a virtual machine.
2. Ensure the virtual machine is powered down and has a status of Down.
3. Click Make T em plate to open the New T em plate window.
Figure 4 .13. T he New T emplate window
4. Enter a Nam e, Description and Com m ent for the template.
5. From the Cluster drop-down menu, select the cluster with which the template will be associated.
By default, this will be the same as that of the source virtual machine.
6. Optionally, select the Create as a Sub T em plate version check box, select a Root
T em plate and enter a Sub Version Nam e to create the new template as a sub template of an
existing template.
7. In the Disks Allocation section, enter an alias for the disk in the Alias text field and select the
storage domain on which the disk will be stored from the T arget drop-down list. By default, these
will be the same as those of the source virtual machine.
67
Red Hat Enterprise Virtualization 3.4 User Guide
8. T he Allow all users to access this T em plate check box is selected by default. T his
makes the template public.
9. T he Copy VM perm issions check box is not selected by default. Select this check box to copy
the permissions of the source virtual machine to the template.
10. Click OK.
Result
T he virtual machine displays a status of Im age Locked while the template is being created. T he process
of creating a template may take up to an hour depending on the size of the virtual machine disk and your
storage hardware. When complete, the template is added to the T em plates tab. You can now create new
virtual machines based on the template.
Note
When a template is made, the virtual machine is copied so that both the existing virtual machine and
its template are usable after template creation.
Report a bug
4 .9.2.2. Explanation of Settings and Controls in the New T emplate Window
T he following table details the settings for the New T em plate window.
T able 4 .13. New T emplate and Edit T emplate Settings
Field Description/Action
Nam e T he name of the template. T his is the name by
which the template is listed in the T em plates tab
in the Administration Portal and is accessed via
the REST API. T his text field has a 40-character
limit and must be a unique name with any
combination of uppercase and lowercase letters,
numbers, hyphens, and underscores.
Description A description of the template. T his field is
recommended but not mandatory.
Com m ent A field for adding plain text, human-readable
comments regarding the template.
Cluster T he cluster with which the template will be
associated. T his is the same as the original virtual
machines by default. You can select any cluster in
the data center.
68
Chapter 4. The Extended Tab
Field Description/Action
Create as a Sub T em plate version Allows you to specify whether the template will be
created as a new version of an existing template.
Select this check box to access the settings for
configuring this option.
Root T em plate: T he template under which
the sub template will be added.
Sub Version Nam e: T he name of the
template. T his is the name by which the
template is accessed when creating a new
virtual machine based on the template.
Disks Allocation Alias - An alias for the virtual machine disk used
by the template. By default, the alias is set to the
same value as that of the source virtual machine.
Virtual Size - T he current actual size of the
virtual disk used by the template. T his value
cannot be edited, and is provided for reference
only.
T arget - T he storage domain on which the virtual
disk used by the template will be stored. By default,
the storage domain is set to the same value as
that of the source virtual machine. You can select
any storage domain in the cluster.
Allow all users to access this Allows you to specify whether a template is public
T em plate or private. A public template can be accessed by
all users, whereas a private template can only be
accessed by users with the T em plateAdm in or
SuperUser roles.
Copy VM perm issions Allows you to copy explicit permissions that have
been set on the source virtual machine to the
template.
Report a bug
4 .9.2.3. Editing a T emplate
Summary
Once a template has been created, its properties can be edited. Because a template is a copy of a virtual
machine, the options available when editing a template are identical to those in the Edit Virtual
Machine window.
Procedure 4 .24 . Editing a T emplate
1. Use the T em plates resource tab, tree mode, or the search function to find and select the template
in the results list.
2. Click Edit to open the Edit T em plate window.
69
Red Hat Enterprise Virtualization 3.4 User Guide
3. Change the necessary properties and click OK.
Result
T he properties of the template are updated. T he Edit T em plate window will not close if a property field
is invalid.
Report a bug
4 .9.2.4 . Deleting a T emplate
Summary
Delete a template from your Red Hat Enterprise Virtualization environment.
Warning
If you have used a template to create a virtual machine, make sure that you do not delete the
template as the virtual machine needs it to continue running.
Procedure 4 .25. Deleting a T emplate
1. Use the resource tabs, tree mode, or the search function to find and select the template in the
results list.
2. Click Rem ove to open the Rem ove T em plate(s) window.
3. Click OK to remove the template.
Result
You have removed the template.
Report a bug
4.9.3. Sealing Templates in Preparation for Deployment
4 .9.3.1. Sealing a Linux Virtual Machine Manually for Deployment as a T emplate
Summary
Generalize (seal) a Linux virtual machine before making it into a template. T his prevents conflicts between
virtual machines deployed from the template.
Procedure 4 .26. Sealing a Linux Virtual Machine
1. Log in to the virtual machine. Flag the system for re-configuration by running the following command
as root:
# touch /.unconfigured
2. Remove ssh host keys. Run:
70
Chapter 4. The Extended Tab
# rm -rf /etc/ssh/ssh_host_*
3. Set HOST NAME=localhost.localdom ain in /etc/sysconfig/network
4. Remove /etc/udev/rules.d/70-*. Run:
# rm -rf /etc/udev/rules.d/70-*
5. Remove the HWADDR= line from /etc/sysconfig/network-scripts/ifcfg-eth* .
6. Optionally delete all the logs from /var/log and build logs from /root.
7. Shut down the virtual machine. Run:
# poweroff
Result
T he virtual machine is sealed and can be made into a template. You can deploy Linux virtual machines
from this template without experiencing configuration file conflicts.
Report a bug
4 .9.3.2. Sealing a Linux Virtual Machine for Deployment as a T emplate using sys-unconfig
Summary
Generalize (seal) a Linux virtual machine using the sys-unconfig command before making it into a
template. T his prevents conflicts between virtual machines deployed from the template.
Procedure 4 .27. Sealing a Linux Virtual Machine using sys-unconfig
1. Log in to the virtual machine.
2. Remove ssh host keys. Run:
# rm -rf /etc/ssh/ssh_host_*
3. Set HOST NAME=localhost.localdom ain in /etc/sysconfig/network
4. Remove the HWADDR= line from /etc/sysconfig/network-scripts/ifcfg-eth* .
5. Optionally delete all the logs from /var/log and build logs from /root.
6. Run the following command:
# sys-unconfig
Result
T he virtual machine shuts down; it is now sealed and can be made into a template. You can deploy Linux
virtual machines from this template without experiencing configuration file conflicts.
Report a bug
71
Red Hat Enterprise Virtualization 3.4 User Guide
4 .9.3.3. Sealing a Windows T emplate
4 .9.3.3.1. Considerations when Sealing a Windows T emplate with Sysprep
A template created for Windows virtual machines must be generalized (sealed) before being used to
deploy virtual machines. T his ensures that machine-specific settings are not reproduced in the template.
T he Sysprep tool is used to seal Windows templates before use.
Important
Do not reboot the virtual machine during this process.
Before starting the Sysprep process, verify the following settings are configured:
T he Windows Sysprep parameters have been correctly defined.
If not, click Edit and enter the required information in the Operating System and Dom ain fields.
T he correct product key has been entered in the engine-config configuration tool.
If not, run the configuration tool on the Manager as the root user, and enter the required information.
T he configuration keys that you need to set are ProductKey and SysPrepPath. For example, the
Windows 7 configuration value is ProductKeyWindow7 and SysPrepWindows7Path. Set these
values with this command:
# engine-config --set ProductKeyWindow7=<validproductkey> --cver=general
Report a bug
4 .9.3.3.2. Sealing a Windows XP T emplate
Summary
Seal a Windows XP template using the Sysprep tool before using the template to deploy virtual machines.
Note
You can also use the procedure above to seal a Windows 2003 template. T he Windows 2003
Sysprep tool is available at http://www.microsoft.com/download/en/details.aspx?id=14830.
Procedure 4 .28. Sealing a Windows XP T emplate
1. Download sysprep to the virtual machine to be used as a template.
T he Windows XP Sysprep tool is available at http://www.microsoft.com/download/en/details.aspx?
id=11282
2. Create a new directory: c:\sysprep.
3. Open the deploy.cab file and add its contents to c:\sysprep.
72
Chapter 4. The Extended Tab
4. Execute sysprep.exe from within the folder and click OK on the welcome message to display the
Sysprep tool.
5. Select the following check boxes:
Don't reset grace period for activation
Use Mini-Setup
6. Ensure that the shutdown mode is set to Shut down and click Reseal.
7. Acknowledge the pop-up window to complete the sealing process; the virtual machine shuts down
automatically upon completion.
Result
T he Windows XP template is sealed and ready for deploying virtual machines.
Report a bug
4 .9.3.3.3. Sealing a Windows 7 or Windows 2008 T emplate
Summary
Seal a Windows 7 or Windows 2008 template before using the template to deploy virtual machines.
Procedure 4 .29. Sealing a Windows 7 or Windows 2008 T emplate
1. In the virtual machine to be used as a template, open a command line terminal and type regedit.
2. T he Registry Editor window opens. On the left pane, expand HKEY_LOCAL_MACHINE →
SYST EM → SET UP.
3. On the main window, right-click to add a new string value using New → String Value.
4. Right-click on the file and select Modify to open the Edit String window.
5. Enter the following information in the provided fields:
Value name: UnattendFile
Value data: a:\sysprep.inf
6. Launch Sysprep from C:\Windows\System 32\sysprep\sysprep.exe.
7. Enter the following information into the Sysprep tool:
Under System Cleanup Action, select Enter System Out-of-Box-Experience
(OOBE).
Select the Generalize check box if you need to change the computer's system identification
number (SID).
Under Shutdown Options, select Shutdown.
Click OK to complete the sealing process; the virtual machine shuts down automatically upon
completion.
73
Red Hat Enterprise Virtualization 3.4 User Guide
Result
T he Windows 7 or Windows 2008 template is sealed and ready for deploying virtual machines.
Report a bug
4 .9.3.4 . Using Cloud-Init to Automate the Configuration of Virtual Machines
4 .9.3.4 .1. Cloud-Init Overview
Cloud-Init is a tool for automating the initial setup of virtual machines such as configuring the host name,
network interfaces, and authorized keys. It can be used when provisioning virtual machines that have been
deployed based on a template to avoid conflicts on the network.
T o use this tool, the cloud-init package must first be installed on the virtual machine. Once installed, the
Cloud-Init service starts during the boot process to search for instructions on what to configure. You can
then use options in the Run Once window to provide these instructions one time only, or options in the
New Virtual Machine, Edit Virtual Machine and Edit T em plate windows to provide these
instructions every time the virtual machine starts.
Report a bug
4 .9.3.4 .2. Cloud-Init Use Case Scenarios
Cloud-Init can be used to automate the configuration of virtual machines in a variety of scenarios. Several
common scenarios are as follows:
Virtual Machines Created Based on T emplates
You can use the Cloud-Init options in the Initial Run section of the Run Once window to
initialize a virtual machine that was created based on a template. T his allows you to customize
the virtual machine the first time that virtual machine is started.
Virtual Machine T emplates
You can use the Use Cloud-Init/Sysprep options in the Initial Run tab of the New
T em plate and Edit T em plate windows to specify options for customizing virtual machines
created based on that template.
Virtual Machine Pools
You can use the Use Cloud-Init/Sysprep options in the Initial Run tab of the New
Pool window to specify options for customizing virtual machines taken from that virtual machine
pool. T his allows you to specify a set of standard settings that will be applied every time a virtual
machine is taken from that virtual machine pool. You can inherit or override the options specified
for the template on which the virtual machine is based, or specify options for the virtual machine
pool itself.
Report a bug
4 .9.3.4 .3. Installing Cloud-Init
Summary
Install Cloud-Init on a virtual machine.
74
Chapter 4. The Extended Tab
Procedure 4 .30. Installing Cloud-Init
1. Log on to the virtual machine.
2. Enable the Red Hat Common channel.
With RHN Classic:
# rhn-channel --add --channel=rhel-x86_64-server-rh-common-6
With Subscription Manager:
# subscription-manager repos --enable=rhel-6-server-rh-common-rpms
3. Install the cloud-init package and dependencies:
# yum install cloud-init
Result
You have installed the cloud-init package and dependencies.
Report a bug
4 .9.3.4 .4 . Using Cloud-Init to Initialize a Virtual Machine
Summary
Use Cloud-Init to automate the initial configuration of a Linux virtual machine that has been provisioned
based on a template.
Procedure 4 .31. Using Cloud-Init to Initialize a Virtual Machine
1. Click the Virtual Machines tab and select a virtual machine.
2. Click Run Once to open the Run Virtual Machine(s) window.
3. Expand the Initial Run section and select the Cloud-Init check box.
4. Enter a host name in the VM Hostnam e text field.
5. Select the Configure T im e Zone check box and select a time zone from the T im e Zone drop-
down menu.
6. Select the Use already configured password check box to user the existing credentials, or
clear that check box and enter a root password in the Root Password and Verify Root
Password text fields to specify a new root password.
7. Enter any SSH keys to be added to the authorized hosts file on the virtual machine in the SSH
Authorized Keys text area.
8. Select the Regenerate SSH Keys check box to regenerate SSH keys for the virtual machine.
9. Enter any DNS servers in the DNS Servers text field.
75
Red Hat Enterprise Virtualization 3.4 User Guide
10. Enter any DNS search domains in the DNS Search Dom ains text field.
11. Select the Network check box and use the + and - buttons to add or remove network interfaces to
or from the virtual machine.
12. Enter any custom scripts in the Custom Script text area.
13. Click OK.
Important
Cloud-Init is only supported on cluster compatibility version 3.3 and higher.
Result
T he virtual machine boots and the specified settings are applied.
Report a bug
4 .9.3.4 .5. Using Cloud-Init to Prepare a T emplate
Summary
Use Cloud-Init to specify a set of standard settings to be included in a template.
Note
While the following procedure outlines how to use Cloud-Init when preparing a template, the same
settings are also available in the New Virtual Machine and Edit T em plate windows.
Procedure 4 .32. Using Cloud-Init to Prepare a T emplate
1. Click the Virtual Machines tab and select a virtual machine.
2. Click Edit to open the Edit Virtual Machine window.
3. Click the Initial Run tab and select the Use Cloud-Init/Sysprep check box.
4. Enter a host name in the VM Hostnam e text field.
5. Select the Configure T im e Zone check box and select a time zone from the T im e Zone drop-
down menu.
6. Expand the Authentication section and select the Use already configured password
check box to user the existing credentials, or clear that check box and enter a root password in the
Root Password and Verify Root Password text fields to specify a new root password.
7. Enter any SSH keys to be added to the authorized hosts file on the virtual machine in the SSH
Authorized Keys text area.
8. Select the Regenerate SSH Keys check box to regenerate SSH keys for the virtual machine.
76
Chapter 4. The Extended Tab
9. Expand the Networks section and enter any DNS servers in the DNS Servers text field.
10. Enter any DNS search domains in the DNS Search Dom ains text field.
11. Select the Network check box and use the + and - buttons to add or remove network interfaces to
or from the virtual machine.
12. Expand the Custom Script section and enter any custom scripts in the Custom Script text
area.
13. Click Ok.
Important
Cloud-Init is only supported on cluster compatibility version 3.3 and higher.
Result
T he virtual machine boots and the specified settings are applied.
Report a bug
4.9.4. Templates and Permissions
4 .9.4 .1. Managing System Permissions for a T emplate
As the SuperUser, the system administrator manages all aspects of the Administration Portal. More
specific administrative roles can be assigned to other users. T hese restricted administrator roles are
useful for granting a user administrative privileges that limit them to a specific resource. For example, a
DataCenterAdm in role has administrator privileges only for the assigned data center with the exception
of the storage for that data center, and a ClusterAdm in has administrator privileges only for the
assigned cluster.
A template administrator is a system administration role for templates in a data center. T his role can be
applied to specific virtual machines, to a data center, or to the whole virtualized environment; this is useful
to allow different users to manage certain virtual resources.
T he template administrator role permits the following actions:
Create, edit, export, and remove associated templates.
Import and export templates.
Note
You can only assign roles and permissions to existing users.
Report a bug
4 .9.4 .2. T emplate Administrator Roles Explained
T emplate Administrator Permission Roles
77
Red Hat Enterprise Virtualization 3.4 User Guide
T he table below describes the administrator roles and privileges applicable to template administration.
T able 4 .14 . Red Hat Enterprise Virtualization System Administrator Roles
Role Privileges Notes
T emplateAdmin Can perform all operations on Has privileges to create, delete
templates. and configure a template's
storage domain and network
details, and to move templates
between domains.
NetworkAdmin Network Administrator Can configure and manage
networks attached to templates.
Report a bug
4 .9.4 .3. T emplate User Roles Explained
T emplate User Permission Roles
T he table below describes the user roles and privileges applicable to using and administrating templates
in the User Portal.
T able 4 .15. Red Hat Enterprise Virtualization T emplate User Roles
Role Privileges Notes
T emplateCreator Can create, edit, manage and T he T em plateCreator role is
remove virtual machine not applied to a specific template;
templates within assigned apply this role to a user for the
resources. whole environment with the
Configure window.
Alternatively apply this role for
specific data centers, clusters, or
storage domains.
T emplateOwner Can edit and delete the template, T he T em plateOwner role is
assign and manage user automatically assigned to the
permissions for the template. user who creates a template.
Other users who do not have
T em plateOwner permissions
on a template cannot view or use
the template.
UserT emplateBasedVm Can use the template to create Cannot edit template properties.
virtual machines.
NetworkUser Logical network and network If the Allow all users to
interface user for templates. use this Network option was
selected when a logical network
is created, NetworkUser
permissions are assigned to all
users for the logical network.
Users can then attach or detach
template network interfaces to or
from the logical network.
Report a bug
78
Chapter 4. The Extended Tab
4.10. Resources
4.10.1. Monitoring Power User Portal Resources
Before making configuration changes to virtual machines in the User Portal, it is recommended that you
take an inventory of the resources available. T his is to ensure the resources are sufficient for peak
performance and to avoid overloading the hosts running the virtual machines.
T he Resources tab in the navigation pane shows a cumulative view of all the resources available in the
User Portal, and the performance and statistics of each virtual machine.
Figure 4 .14 . Resources tab
Virtual CPUs: T his box displays the number of your machines' virtual CPUs in use, and the
consumption of CPU quota used by you and others.
Mem ory: T his box displays the consumption of memory quota used by you and others, and available
memory as defined by the quota.
Storage: T his box displays the consumption of storage quota by you and others, the total size of all
your virtual disks, and the number and total size of your virtual machines' snapshots. It also displays a
breakdown of storage details for each virtual machine. Click the + button next to the virtual machine
name to display all the virtual disks attached to the virtual machine.
Report a bug
4.10.2. Quota - A User's Introduction
79
Red Hat Enterprise Virtualization 3.4 User Guide
When you create a virtual machine, the virtual machine consumes CPU and storage resources from its
data center. Quota compares the amount of virtual resources consumed by the creation of the virtual
machine to the storage allowance and the run-time allowance set by the system administrator.
If you do not have enough of either kind of allowance, you are not allowed to create the virtual machine.
Avoid exceeding your quota limit by using the Resources tab to monitor your CPU and storage
consumption.
Figure 4 .15. Resources tab
Report a bug
4.10.3. What to Do When You Exceed Your Quota
Red Hat Enterprise Virtualization provides a resource-limitation tool called quota, which allows system
administrators to limit the amount of CPU and storage each user can consume. Quota compares the
amount of virtual resources consumed when you use the virtual machine to the storage allowance and the
run-time allowance set by the system administrator.
When you exceed your quota, a pop-up window informs you that you have exceeded your quota, and you
will no longer have access to virtual resources. For example, this can happen if you have too many
concurrently running virtual machines in your environment.
80
Chapter 4. The Extended Tab
Figure 4 .16. Quota exceeded error message
T o regain access to your virtual machines, do one of the following:
Shut down the virtual machines that you do not need. T his will bring your resource consumption down
to a level at which it is not in excess of the quota, and you will be able to run virtual machines again.
If you cannot shut down any existing virtual machines, contact your system administrator to extend your
quota allowance or remove any unused virtual machines.
Report a bug
4.11. Virtual Machines and Permissions
4.11.1. Managing System Permissions for a Virtual Machine
As the SuperUser, the system administrator manages all aspects of the Administration Portal. More
specific administrative roles can be assigned to other users. T hese restricted administrator roles are
useful for granting a user administrative privileges that limit them to a specific resource. For example, a
DataCenterAdm in role has administrator privileges only for the assigned data center with the exception
of the storage for that data center, and a ClusterAdm in has administrator privileges only for the
assigned cluster.
A UserVm Manager is a system administration role for virtual machines in a data center. T his role can be
applied to specific virtual machines, to a data center, or to the whole virtualized environment; this is useful
to allow different users to manage certain virtual resources.
T he user virtual machine administrator role permits the following actions:
Create, edit, and remove virtual machines.
81
Red Hat Enterprise Virtualization 3.4 User Guide
Run, suspend, shutdown, and stop virtual machines.
Note
You can only assign roles and permissions to existing users.
Many end users are concerned solely with the virtual machine resources of the virtualized environment. As
a result, Red Hat Enterprise Virtualization provides several user roles which enable the user to manage
virtual machines specifically, but not other resources in the data center.
Report a bug
4.11.2. Virtual Machines Administrator Roles Explained
Virtual Machine Administrator Permission Roles
T he table below describes the administrator roles and privileges applicable to virtual machine
administration.
T able 4 .16. Red Hat Enterprise Virtualization System Administrator Roles
Role Privileges Notes
DataCenterAdmin Data Center Administrator Possesses administrative
permissions for all objects
underneath a specific data
center except for storage.
ClusterAdmin Cluster Administrator Possesses administrative
permissions for all objects
underneath a specific cluster.
NetworkAdmin Network Administrator Possesses administrative
permissions for all operations on
a specific logical network. Can
configure and manage networks
attached to virtual machines. T o
configure port mirroring on a
virtual machine network, apply
the NetworkAdm in role on the
network and the
UserVm Manager role on the
virtual machine.
Report a bug
4.11.3. Virtual Machine User Roles Explained
Virtual Machine User Permission Roles
T he table below describes the user roles and privileges applicable to virtual machine users. T hese roles
allow access to the User Portal for managing and accessing virtual machines, but they do not confer any
permissions for the Administration Portal.
T able 4 .17. Red Hat Enterprise Virtualization System User Roles
82
Chapter 4. The Extended Tab
Role Privileges Notes
UserRole Can access and use virtual Can log in to the User Portal and
machines and pools. use virtual machines and pools.
PowerUserRole Can create and manage virtual Apply this role to a user for the
machines and templates. whole environment with the
Configure window, or for
specific data centers or clusters.
For example, if a PowerUserRole
is applied on a data center level,
the PowerUser can create virtual
machines and templates in the
data center. Having a
PowerUserRole is equivalent
to having the Vm Creator,
DiskCreator, and
T em plateCreator roles.
UserVmManager System administrator of a virtual Can manage virtual machines,
machine. create and use snapshots, and
migrate virtual machines. A user
who creates a virtual machine in
the User Portal is automatically
assigned the UserVmManager
role on the machine.
UserT emplateBasedVm Limited privileges to only use Level of privilege to create a
T emplates. virtual machine by means of a
template.
VmCreator Can create virtual machines in T his role is not applied to a
the User Portal. specific virtual machine; apply
this role to a user for the whole
environment with the
Configure window. When
applying this role to a cluster,
you must also apply the
DiskCreator role on an entire
data center, or on specific
storage domains.
NetworkUser Logical network and network If the Allow all users to
interface user for virtual use this Network option was
machines. selected when a logical network
is created, NetworkUser
permissions are assigned to all
users for the logical network.
Users can then attach or detach
virtual machine network
interfaces to or from the logical
network.
Report a bug
4.11.4. Assigning Virtual Machines to Users
83
Red Hat Enterprise Virtualization 3.4 User Guide
If you are creating virtual machines for users other than yourself, you have to assign roles to the users
before they can use the virtual machines. Note that permissions can only be assigned to existing users.
See the Red Hat Enterprise Virtualization Installation Guide for details on creating user accounts.
T he Red Hat Enterprise Virtualization User Portal supports three default roles: User, PowerUser and
UserVmManager. However, customized roles can be configured via the Red Hat Enterprise Virtualization
Manager Administration Portal. T he default roles are described below.
A User can connect to and use virtual machines. T his role is suitable for desktop end users
performing day-to-day tasks.
A PowerUser can create virtual machines and view virtual resources. T his role is suitable if you are
an administrator or manager who needs to provide virtual resources for your employees.
A UserVmManager can edit and remove virtual machines, assign user permissions, use snapshots
and use templates. It is suitable if you need to make configuration changes to your virtual environment.
When you create a virtual machine, you automatically inherit UserVm Manager privileges. T his enables
you to make changes to the virtual machine and assign permissions to the users you manage, or users
who are in your Identity Management (IdM) or RHDS group.
See Red Hat Enterprise Virtualization Installation Guide for more information on directory services support
in Red Hat Enterprise Virtualization.
Summary
T his procedure explains how to add permissions to users.
Procedure 4 .33. Assigning Permissions to Users
1. Click the Virtual Machines tab and select a virtual machine.
2. On the details pane, select the Perm issions tab.
3. Click New. T he Add Perm ission to User dialog displays. Enter a Name, or User Name, or part
thereof in the Search text box, and click Go. A list of possible matches display in the results list.
4. Select the check box of the user to be assigned the permissions. Scroll through the Role to
Assign list and select UserRole. Click OK.
5. T he user's name and role display in the list of users permitted to access this virtual machine.
Result
You have added permissions to a user.
Note
If a user is assigned permissions to only one virtual machine, Single Sign On (SSO) can be
configured for the virtual machine. SSO enables the user to bypass the User Portal and log in
directly to the virtual machine. SSO can be enabled or disabled via the User Portal on a per virtual
machine basis.
Report a bug
84
Chapter 4. The Extended Tab
4.11.5. Removing Access to Virtual Machines from Users
Summary
T his procedure explains how to remove user permissions.
Procedure 4 .34 . Removing Access to Virtual Machines from Users
1. Click the Virtual Machines tab and select a virtual machine.
2. On the details pane, select the Perm issions tab.
3. Click Rem ove. A warning message displays, asking you to confirm removal of the selected
permissions.
4. T o proceed, click OK. T o abort, click Cancel.
Result
You have now removed permissions from a user.
Report a bug
85
Red Hat Enterprise Virtualization 3.4 User Guide
Part III. Advanced Usage
1. Introduction to Using Virtual Machines - Advanced
T his chapter describes how to configure advanced operations on virtual machines. It includes:
Configuration of protocol options
Use of USB devices with virtual machines
Support for multiple monitors
Report a bug
2. Passing Information to Red Hat Enterprise Virtualization Manager
with rhevm-guest-agent
In order to monitor the virtual resources of your guest machines in the Power User Portal, you need to
install the rhevm-guest-agent package on each guest machine you plan to monitor. T his is done one
way for Red Hat Enterprise Linux guests and another way for Windows guests. After rhevm-guest-
agent has been installed on your guest, resource usage information about that guest is visible in the
Power User Portal.
Summary
Follow the instructions below to install the rhevm-guest-agent on your virtual machines. T he rhevm-
guest-agent passes information about the guest's resource usage to the monitoring tools available in
the Power User Portal. After you have performed this procedure, you are able to see the resource
consumption of your guest machines.
T he rhevm-guest-agent passes information about your virtual machines to the Red Hat Enterprise
Virtualization Manager, making it possible for you to monitor your virtual machines and your resource
consumption in the Power User Portal. Install the rhevm-guest-agent on your guest machine by
doing one of the following:
A. For Red Hat Enterprise Linux Guests
T o install the rhevm-guest-agent using the yum command on Red Hat Enterprise Linux virtual
guests that have been registered on the Red Hat Enterprise Virt Agent channel in RHN,
run the following:
# yum install rhevm-guest-agent -y
B. For Windows Guests
T o install the rhevm-guest-agent on windows guests, attach the rhev-guest-tools ISO to the
guest machine, launch the RHEV-tools InstallShield Wizard, and install the set of Windows guest
tools. T he guest agent is among the tools that the Wizard installs.
a. On the User Portal, select the virtual machine. Click the Change CD button and select the
RHEV-toolsSetup iso from the drop down list.
b. Select the CD Drive containing the RHEV-tools CD that you attached earlier.
86
P art III. Advanced Usage
c. Select RHEV-toolsSetup.
d. Select Yes in the User Account Control window.
e. Follow the prompts on the RHEV-T ools InstallShield Wizard window. Ensure that all
check boxes in the list of RHEV T ools components are selected to be installed.
Figure 28. Selecting All Components of Red Hat Enterprise Virtualization T ools for
Installation
f. After the installation, restart your computer by selecting the Yes, I want to restart m y
com puter now radio button and clicking Finish.
Result
rhevm-guest-agent now passes usage information to the Red Hat Enterprise Virtualization Manager,
and you can monitor your virtual guests' resource usage in the Power User Portal.
Report a bug
87
Red Hat Enterprise Virtualization 3.4 User Guide
Chapter 5. Configuring Console Options
5.1. Console Options
5.1.1. Introduction to Connection Protocols
Connection protocols are the underlying technology used to provide graphical consoles for virtual
machines and allow users to work with virtual machines in a similar way as they would with physical
machines. Red Hat Enterprise Virtualization currently supports the following connection protocols:
SPICE
Simple Protocol for Independent Computing Environments (SPICE) is the recommended connection
protocol for Red Hat Enterprise Virtualization. SPICE is installed and executed on the client that connects
to the virtual machine. It provides features including USB redirection and multiple monitor support.
VNC
Virtual Network Computing (VNC) can be used for Red Hat Enterprise Linux virtual machines. If a virtual
machine is configured to use VNC as its default protocol, you must use a VNC client to connect to that
virtual machine. Connecting to a virtual machine using VNC is not possible from the User Portal.
RDP
Remote Desktop Protocol (RDP) can be used for Windows virtual machines. However, this protocol is only
available when users access the User Portal from a Windows machine with Remote Desktop. Moreover,
before users can connect to a Windows virtual machine using RDP, remote sharing must be set up on the
virtual machine and the firewall on the virtual machine must be configured to allow remote desktop
connections.
Note
SPICE is not currently supported on virtual machines running Windows 8. If a Windows 8 virtual
machine is configured to use the SPICE protocol, it will detect the absence of the required SPICE
drivers and automatically fall back to using RDP.
Report a bug
5.1.2. Configuring Console Options
Connection protocols enable you to see and interact with virtual machines. In Red Hat Enterprise
Virtualization Manager, each connection protocol provides several options for configuring how you connect
to graphical console, such as the method of invocation and whether to enable or disable USB redirection.
Procedure 5.1. T o configure SPICE console options
1. Select a running virtual machine. Click the Edit Console Options button.
2. Click the Edit Console Options button to open the Console Options window.
88
Chapter 5. Configuring Console Options
Figure 5.1. T he Edit Console Options button
Note
Further options specific to the SPICE and VNC connection protocols, such as the keyboard layout
when using the VNC connection protocol, can be configured in the Console tab of the Edit
Virtual Machine window.
Report a bug
5.1.3. SPICE Console Options
When the SPICE connection protocol is selected, the following options are available in the Console
Options window.
Figure 5.2. T he Console Options window
89
Red Hat Enterprise Virtualization 3.4 User Guide
Console Invocation
Auto: T he Manager automatically selects the method for invoking the console.
Native client: When you connect to the console of the virtual machine, a file download dialog
provides you with a file that opens a console to the virtual machine via Remote Viewer.
Browser plugin: When you connect to the console of the virtual machine, you are connected directly
via Remote Viewer.
SPICE HT ML5 browser client (T ech preview): When you connect to the console of the
virtual machine, a browser tab is opened that acts as the console.
SPICE Options
Pass Ctrl-Alt-Del to virtual m achine: Select this check box for this key combination to be
intercepted in the virtual machine.
Enable USB Auto-Share: Select this check box to automatically redirect USB devices to the virtual
machine. If this option is not selected, USB devices will connect to the client machine instead of the
guest virtual machine. T o use the USB device on the guest machine, manually enable it in the SPICE
client menu.
Open in Full Screen: Select this check box for the virtual machine console to automatically open
in full screen when you connect to the virtual machine. Press SHIFT +F11 to toggle full screen mode
on or off.
Enable WAN options: Select this check box to enable WAN color depth and effects for the virtual
machine console. Select this check box for only Windows virtual machines. Selecting this check box
sets the parameters WAN-DisableEffects and WAN-ColorDepth. Selecting Enable WAN options
sets Wan-DisableEffects to animation and sets the color depth to 16 bits.
Enable SPICE Proxy: Select this check box to enable the SPICE proxy.
Important
T he Browser plugin console option is only available when accessing the Administration Portal
through Internet Explorer. T his console options uses the version of Remote Viewer provided by the
SpiceX.cab installation program. For all other browsers, the Native client console option is
the default. T his console option uses the version of Remote Viewer provided by the virt-
viewer-x86.m si and virt-viewer-x64 .m si installation files.
Report a bug
5.1.4. VNC Console Options
When the VNC connection protocol is selected, the following options are available in the Console
Options window.
90
Chapter 5. Configuring Console Options
Figure 5.3. T he Console Options window
Console Invocation
Native Client: When you connect to the console of the virtual machine, a file download dialog
provides you with a file that opens a console to the virtual machine via Remote Viewer.
NoVNC: When you connect to the console of the virtual machine, a browser tab is opened that acts as
the console.
Report a bug
5.1.5. RDP Console Options
When the RDP connection protocol is selected, the following options are available in the Console
Options window.
91
Red Hat Enterprise Virtualization 3.4 User Guide
Figure 5.4 . T he Console Options window
Console Invocation
Auto: T he Manager automatically selects the method for invoking the console.
Native client: When you connect to the console of the virtual machine, a file download dialog
provides you with a file that opens a console to the virtual machine via Remote Desktop.
RDP Options
Use Local Drives: Select this check box to make the drives on the client machine to be accessible
on the guest virtual machine.
Report a bug
5.2. Remote Viewer Options
5.2.1. Remote Viewer Options
When you specify the Native client or Browser plugin console invocation options, you will connect
to virtual machines using Remote Viewer. T he Remote Viewer window provides a number of options for
interacting with the virtual machine to which it is connected.
92
Chapter 5. Configuring Console Options
Figure 5.5. T he Remote Viewer connection menu
T able 5.1. Remote Viewer Options
Option Hotkey
File
Screenshot: T akes a screen capture of the
active window and saves it in a location of your
specification.
USB device selection: If USB redirection
has been enabled on your virtual machine, the
USB device plugged into your client machine
can be accessed from this menu.
Quit: Closes the console. T he hot key for this
option is Shift+Ctrl+Q.
93
Red Hat Enterprise Virtualization 3.4 User Guide
Option Hotkey
View
Full screen: T oggles full screen mode on or
off. When enabled, full screen mode expands
the virtual machine to fill the entire screen.
When disabled, the virtual machine is displayed
as a window. T he hot key for enabling or
disabling full screen is SHIFT +F11.
Zoom : Z ooms in and out of the console
window. Ctrl++ zooms in, Ctrl+- zooms out,
and Ctrl+0 returns the screen to its original
size.
Autom atically resize: T ick to enable the
guest resolution to automatically scale
according to the size of the console window.
Displays: Allows users to enable and disable
displays for the guest virtual machine.
Send key
Ctrl+Alt+Del: On a Red Hat Enterprise
Linux virtual machine, it displays a dialog with
options to suspend, shut down or restart the
virtual machine. On a Windows virtual machine,
it displays the task manager or Windows
Security dialog.
Ctrl+Alt+Backspace: On a Red Hat
Enterprise Linux virtual machine, it restarts the
X sever. On a Windows virtual machine, it does
nothing.
Ctrl+Alt+F1
Ctrl+Alt+F2
Ctrl+Alt+F3
Ctrl+Alt+F4
Ctrl+Alt+F5
Ctrl+Alt+F6
Ctrl+Alt+F7
Ctrl+Alt+F8
Ctrl+Alt+F9
Ctrl+Alt+F10
Ctrl+Alt+F11
Ctrl+Alt+F12
Printscreen: Passes the Printscreen
keyboard option to the virtual machine.
Help T he About entry displays the version details of
Virtual Machine Viewer that you are using.
Release Cursor from Virtual Machine SHIFT +F12
Report a bug
5.2.2. Remote Viewer Hotkeys
94
Chapter 5. Configuring Console Options
You can access the hotkeys for a virtual machine in both full screen mode and windowed mode. If you are
using full screen mode, you can display the menu containing the button for hotkeys by moving the mouse
pointer to the middle of the top of the screen. If you are using windowed mode, you can access the hotkeys
via the Send key menu on the virtual machine window title bar.
Note
If vdagent is not running on the client machine, the mouse can become captured in a virtual
machine window if it is used inside a virtual machine and the virtual machine is not in full screen. T o
unlock the mouse, press Shift+F12.
Report a bug
95
Red Hat Enterprise Virtualization 3.4 User Guide
Chapter 6. Configuring Multiple Monitors
6.1. Configuring Multiple Displays for Red Hat Enterprise Linux
Virtual Machines
A maximum of four displays can be configured for a single Red Hat Enterprise Linux virtual machine when
connecting to the virtual machine using the SPICE protocol.
1. Start a SPICE session with the virtual machine.
2. Open the View drop-down menu at the top of the SPICE client window.
3. Open the Display menu.
4. Click the name of a display to enable or disable that display.
Note
By default, Display 1 is the only display that is enabled on starting a SPICE session with a
virtual machine. If no other displays are enabled, disabling this display will close the session.
Report a bug
6.2. Changing the Resolution of Displays in a Red Hat Enterprise
Linux Virtual Machine
1. Open the System menu from the GNOME panel.
2. Open the Preferences section.
3. Click Display to open the Display Preferences window.
4. Select the display whose resolution is to be changed.
5. Select the resolution from the Resolution drop-down list.
Note
T he maximum resolution that can be set for any display is 2560 x 1600. T he minimum
resolution that can be set for the primary display is 640 x 480; all other displays can be set
to a minimum of 400 x 375.
Report a bug
6.3. Configuring Multiple Displays for Windows Virtual Machines
A maximum of four displays can be configured for a single Windows virtual machine when connecting to
the virtual machine using the SPICE protocol.
96
Chapter 6. Configuring Multiple Monitors
1. Click the Virtual Machines tab and select a virtual machine.
2. With the virtual machine in a powered-down state, right-click the virtual machine and click Edit to
open the Edit Virtual Machine window.
3. Click the Console tab.
4. Select the number of displays from the Monitors drop-down list.
Note
T his setting controls the maximum number of displays that can be enabled for the virtual
machine. While the virtual machine is running, additional displays can be enabled up to this
number.
5. Click Ok.
6. Start a SPICE session with the virtual machine.
7. Open the View drop-down menu at the top of the SPICE client window.
8. Open the Display menu.
9. Click the name of a display to enable or disable that display.
Note
By default, Display 1 is the only display that is enabled on starting a SPICE session with a
virtual machine. If no other displays are enabled, disabling this display will close the session.
Report a bug
6.4. Changing the Resolution of Displays in a Windows Virtual
Machine
T he method for changing the resolution of a Windows virtual machine varies slightly in accordance with the
version of Windows installed on the virtual machine. T he following procedures outline how to change the
resolution of virtual machines running Windows 7, Windows Vista or Windows XP.
Procedure 6.1. Windows 7
1. Right-click the desktop and click Screen resolution to open the Screen Resolution
window.
2. Select the display whose resolution is to be changed.
3. Select the resolution from the Resolution drop-down list.
97
Red Hat Enterprise Virtualization 3.4 User Guide
Procedure 6.2. Windows Vista
1. Right-click the desktop and click Personalize to open the Personalization section of the
Control Panel.
2. Click Display Settings to open the Display Settings window.
3. Select the display whose resolution is to be changed.
4. Use the Resolution slider to change the resolution of the screen.
5. Click Apply to apply the new resolution.
Procedure 6.3. Windows XP
1. Right-click the desktop and click Properties to open the Display Settings window.
2. Select the display whose resolution is to be changed.
3. Use the Resolution slider to change the resolution of the screen.
4. Click Apply to apply the new resolution.
Note
T he maximum resolution that can be set for any display is 2560 x 1600. T he minimum resolution
that can be set for the primary display is 800 x 600; all other displays can be set to a minimum of
640 x 480.
Report a bug
98
Chapter 7. Configuring USB D evices
Chapter 7. Configuring USB Devices
7.1. Using USB Devices on Virtual Machines - Introduction
A virtual machine connected with the SPICE protocol can be configured to connect directly to USB devices.
T he USB device will only be redirected if the virtual machine is active and in focus. USB redirection can be
manually enabled each time a device is plugged in or set to automatically redirect to active virtual machines
in the SPICE client menu.
Important
Note the distinction between the client machine and guest machine. T he client is the hardware from
which you access a guest. T he guest is the virtual desktop or virtual server which is accessed
through the User Portal.
Report a bug
7.2. Using USB Devices on Virtual Machines - Native Mode
USB redirection Native mode allows KVM/SPICE USB redirection for Linux and Windows virtual machines.
Virtual (guest) machines require no guest-installed agents or drivers for native USB. All packages required
by the client are brought forward by the SPICE xpi Firefox plugin. T he USBClerk package must be installed
on the Windows client. Native USB mode is supported on the following clients and guests:
Client
Red Hat Enterprise Linux 6.0 and higher
Red Hat Enterprise Linux 5.5 and higher
Windows XP
Windows 7
Windows 2008
Windows 2008 Server R2
Guest
Red Hat Enterprise Linux 6.0 and higher
Red Hat Enterprise Linux 5.5 and higher
Windows XP
Windows 7
Windows 2008
99
Red Hat Enterprise Virtualization 3.4 User Guide
Note
If you have a 64-bit architecture PC, you must use the 64-bit version of Internet Explorer to install
the 64-bit version of the USB driver. T he USB redirection will not work if you install the 32-bit
version on a 64-bit architecture. As long as you initially install the correct USB type, you then can
access USB redirection from both 32 and 64-bit browsers.
Report a bug
7.3. Using USB Devices on a Windows Client
T he usbclerk service must be running on the Windows client for the USB device to be redirected to the
guest. Ensure the version of usbclerk matches the architecture of the client machine. For example, the
64-bit version of usbclerk must be installed on 64-bit Windows machines.
Procedure 7.1. Using USB Devices on a Windows Client
1. When the usbclerk service is installed and running, select a virtual machine that has been
configured to use the SPICE protocol.
2. Ensure USB support is set to Native:
a. Click the Edit button to open the Edit Virtual Machine window.
b. Click the Console tab.
c. From the USB Support drop-down menu, select Native.
d. Click OK.
3. Right-click the virtual machine and click Edit Console Options to open the Console Options
window, and select the Enable USB Auto-Share check box.
4. Start the virtual machine and click the Console button to connect to that virtual machine. When you
plug your USB device into the client machine, it will automatically be redirected to appear on your
guest machine.
Report a bug
7.4. Using USB Devices on a Red Hat Enterprise Linux Client
T he usbredir package enables USB redirection from Red Hat Enterprise Linux clients to virtual machines.
usbredir is a dependency of the spice-xpi package, and is automatically installed together with that
package.
Procedure 7.2. Using USB devices on a Red Hat Enterprise Linux client
1. Click the Virtual Machines tab and select a virtual machine that has been configured to use the
SPICE protocol.
100
Chapter 7. Configuring USB D evices
2. Ensure USB support is set to Native:
a. Click the Edit button to open the Edit Virtual Machine window.
b. Click the Console tab.
c. From the USB Support drop-down menu, select Native.
d. Click OK.
3. Right-click the virtual machine and click Edit Console Options to open the Console Options
window, and select the Enable USB Auto-Share check box.
4. Start the virtual machine and click the Console button to connect to that virtual machine. When you
plug your USB device into the client machine, it will automatically be redirected to appear on your
guest machine.
Report a bug
7.5. Using USB Devices on Virtual Machines - Legacy Mode
Legacy mode for USB redirection enables the SPICE USB redirection policy used in Red Hat Enterprise
Virtualization 3.0. Legacy mode must be manually configured.
Legacy USB mode is supported on the following clients and guests:
Client
Red Hat Enterprise Linux 6.0 and higher
Red Hat Enterprise Linux 5.5 and higher
Windows XP
Windows 7
Windows 2008
Guest
Windows XP
Windows 7
Configuring a Linux Client to Use USB Redirection in Legacy Mode
If you connect to a virtual guest from a Red Hat Enterprise Linux client machine, you have to install several
SPICE packages before you can share USB devices between the client and the guest.
Procedure 7.3. Using USB devices on Red Hat Enterprise Linux clients:
1. Install SPICE packages on client
On your Linux client machine, install the following packages:
spice-usb-share
101
Red Hat Enterprise Virtualization 3.4 User Guide
kmod-kspiceusb-rhel60 for Red Hat Enterprise Linux 6 or
kmod-kspiceusb-rhel5u6 for Red Hat Enterprise Linux 5
T hese packages are available on the Red Hat Network, from the Red Hat Enterprise Linux
Supplementary Software channel for your version of Red Hat Enterprise Linux. T o install the
packages, run:
# yum install spice-usb-share kmod-kspiceusb
2. Run SPICE USB services
Start the spiceusbsrvd service and load the kspiceusb module. Run:
# service spiceusbsrvd start
# modprobe kspiceusb
3. Install RHEV-T ools on guest
Locate the CD drive to access the contents of the Guest T ools ISO, and launch RHEV-
T oolsSetup.exe. If the Guest T ools ISO is not available in your CD drive, contact your system
administrator. After the tools have been installed, you will be prompted to restart the machine for
changes to be applied.
4. Open firewall ports
Allow connections on T CP port 32023 on any firewalls between the guest machine and the client
machine.
5. Enable USB Auto-Share
On the User Portal, select your guest machine. Ensure that you have enabled SPICE USB Auto-
Share on the guest machine.
6. Attach USB device
Connect to your guest machine. Place the SPICE console window of your guest desktop in focus,
then attach a USB device to the client. T he USB device displays in your guest desktop.
102
Chapter 7. Configuring USB D evices
Figure 7.1. List of Connected USB devices - Linux Client
When you close the SPICE session the USB device will no longer be shared with the guest.
Configuring a Windows Client to Use USB Redirection in Legacy Mode
If you are connecting from a Windows client machine, and wish to use USB devices on your guest, you
have to enable SPICE USB redirection.
Note
Refer to the Red Hat Enterprise Virtualization Manager Release Notes for specific channel names
current to your system.
Procedure 7.4 . Enabling USB redirection on Windows:
1. Install USB redirector package on client
On a Windows client machine, install RHEV-USB-Client.exe. T his package can be obtained from
the Red Hat Enterprise Virtualization Manager (v.3.4 x86_64 ) channel on the Red
Hat Network, under the Downloads list.
2. Install RHEV-T ools on guest
103
Red Hat Enterprise Virtualization 3.4 User Guide
Locate the CD drive to access the contents of the Guest T ools ISO, and launch RHEV-
T oolsSetup.exe. If the Guest T ools ISO is not available in your CD drive, contact your system
administrator. After the tools have been installed, you will be prompted to restart the machine for
changes to be applied.
3. Open firewall ports
Allow connections on T CP port 32023 on any firewalls between the guest machine and the client
machine.
4. Enable USB sharing
On the User Portal, select your guest machine. Ensure that you have enabled SPICE USB sharing
on the guest machine.
5. Attach USB device
Connect to your guest machine and attach a USB device to the client. If the required USB device
does not appear directly on the guest desktop, right-click on the SPICE frame and select USB
Devices. Choose your device from the list displayed.
Figure 7.2. List of connected USB devices
104
Chapter 7. Configuring USB D evices
Important
When some USB devices are connected on Windows clients, the autoplay window will appear and
the client will take control of the device, making it unavailable to the guest. T o avoid this issue,
disable USB autoplay on your Windows clients.
Note
You can also define additional USB policies for Windows clients, to allow or block access to certain
USB devices. For details, see the sections on USB Filter Editor in the Red Hat Enterprise
Virtualization Administration Guide.
Report a bug
7.6. Configuring a Linux Client to Use USB Redirection in Legacy
Mode
If you connect to a virtual guest from a Red Hat Enterprise Linux client machine, you have to install several
SPICE packages before you can share USB devices between the client and the guest.
Procedure 7.5. Using USB devices on Red Hat Enterprise Linux clients:
1. Install SPICE packages on client
On your Linux client machine, install the following packages:
spice-usb-share
kmod-kspiceusb-rhel60 for Red Hat Enterprise Linux 6 or
kmod-kspiceusb-rhel5u6 for Red Hat Enterprise Linux 5
T hese packages are available on the Red Hat Network, from the Red Hat Enterprise Linux
Supplementary Software channel for your version of Red Hat Enterprise Linux. T o install the
packages, run:
# yum install spice-usb-share kmod-kspiceusb
2. Run SPICE USB services
Start the spiceusbsrvd service and load the kspiceusb module. Run:
# service spiceusbsrvd start
# modprobe kspiceusb
3. Install RHEV-T ools on guest
105
Red Hat Enterprise Virtualization 3.4 User Guide
Locate the CD drive to access the contents of the Guest T ools ISO, and launch RHEV-
T oolsSetup.exe. If the Guest T ools ISO is not available in your CD drive, contact your system
administrator. After the tools have been installed, you will be prompted to restart the machine for
changes to be applied.
4. Open firewall ports
Allow connections on T CP port 32023 on any firewalls between the guest machine and the client
machine.
5. Enable USB Auto-Share
On the User Portal, select your guest machine. Ensure that you have enabled SPICE USB Auto-
Share on the guest machine.
6. Attach USB device
Connect to your guest machine. Place the SPICE console window of your guest desktop in focus,
then attach a USB device to the client. T he USB device displays in your guest desktop.
When you close the SPICE session the USB device will no longer be shared with the guest.
Report a bug
7.7. Configuring a Windows Client to Use USB Redirection in
Legacy Mode
If you are connecting from a Windows client machine, and wish to use USB devices on your guest, you
have to enable SPICE USB redirection.
Note
See the Red Hat Enterprise Virtualization Manager Release Notes for specific channel names
current to your system.
Procedure 7.6. T o enable USB redirection on Windows:
1. Install USB redirector package on client
On a Windows client machine, install the RHEV-USB-Client.exe. T his package can be obtained
from the Red Hat Enterprise Virtualization Manager (v.3.4 x86_64 ) channel on
the Red Hat Network, under the Downloads list.
2. Install RHEV-T ools on guest
Locate the CD drive to access the contents of the Guest T ools ISO, and launch RHEV-
T oolsSetup.exe. If the Guest T ools ISO is not available in your CD drive, contact your system
administrator. After the tools have been installed, you will be prompted to restart the machine for
changes to be applied.
3. Open firewall ports
Allow connections on T CP port 32023 on any firewalls between the guest machine and the client
106
Chapter 7. Configuring USB D evices
machine.
4. Enable USB sharing
On the User Portal, select your guest machine. Ensure that you have enabled SPICE USB sharing
on the guest machine.
5. Attach USB device
Connect to your guest machine and attach a USB device to the client. If the required USB device
does not appear directly on the guest desktop, right-click on the SPICE frame and select USB
Devices. Choose your device from the list displayed.
Figure 7.3. List of connected USB devices
Important
When some USB devices are connected on Windows clients, the autoplay window will appear and
the client will take control of the device, making it unavailable to the guest. T o avoid this issue,
disable USB autoplay on your Windows clients.
107
Red Hat Enterprise Virtualization 3.4 User Guide
Note
You can also define additional USB policies for Windows clients, to allow or block access to certain
USB devices. For details, see the sections on USB Filter Editor in the Red Hat Enterprise
Virtualization Administration Guide.
Report a bug
108
Chapter 8. Configuring Single Sign-On
Chapter 8. Configuring Single Sign-On
8.1. Configuring Single Sign-On for Virtual Machines
Configuring single sign-on allows you to automatically log in to a virtual machine using the credentials you
use to log in to the User Portal. Single sign-on can be used on both Red Hat Enterprise Linux and
Windows virtual machines.
Report a bug
8.2. Configuring Single Sign-On for Red Hat Enterprise Linux Virtual
Machines Using IPA (IdM)
T o configure single sign-on for Red Hat Enterprise Linux virtual machines using GNOME and KDE
graphical desktop environments and IPA (IdM) servers, you must install the rhevm-guest-agent package
on the virtual machine and install the packages associated with your window manager.
Important
T he following procedure assumes that you have a working IPA configuration and that the IPA
domain is already joined to the Manager. You must also ensure that the clocks on the Manager, the
virtual machine and the system on which IPA (IdM) is hosted are synchronized using NT P.
Procedure 8.1. Configuring Single Sign-On for Red Hat Enterprise Linux Virtual Machines
1. Log in to the Red Hat Enterprise Linux virtual machine.
2. Run the following command to enable the required channel:
# rhn-channel --add --channel=rhel-x86_64-rhev-agent-6-server
3. Run the following command to download and install the guest agent packages:
# yum install rhevm-guest-agent
4. Run the following commands to install the single sign-on packages:
# yum install rhev-agent-pam-rhev-cred
# yum install rhev-agent-gdm-plugin-rhevcred
5. Run the following command to install the IPA packages:
# yum install ipa-client
6. Run the following command and follow the prompts to configure ipa-client and join the virtual
machine to the domain:
# ipa-client-install --permit --mkhomedir
109
Red Hat Enterprise Virtualization 3.4 User Guide
Note
In environments that use DNS obfuscation, this command should be:
# ipa-client-install --domain=[FQDN] --server==[FQDN]
7. Fetch the details of an IPA user:
# getent passwd [IPA user name]
T his will return something like this:
[some-ipa-user]:*:936600010:936600001::/home/[some-ipa-user]:/bin/sh
You will need this information in the next step to create a home directory for [some-ipa-user].
8. Set up a home directory for the IPA user:
a. Create the new user's home directory:
# mkdir /home/[some-ipa-user]
b. Give the new user ownership of the new user's home directory:
# chown 935500010:936600001 /home/[some-ipa-user]
Result
You have enabled single sign-on for your Red Hat Enterprise Linux virtual machine. Log in to the User
Portal using the user name and password of a user configured to use single sign-on and connect to the
console of the virtual machine. You will be logged in automatically.
Report a bug
8.3. Configuring Single Sign-On for Red Hat Enterprise Linux Virtual
Machines Using Active Directory
T o configure single sign-on for Red Hat Enterprise Linux virtual machines using GNOME and KDE
graphical desktop environments and Active Directory, you must install the rhevm-guest-agent package on
the virtual machine, install the packages associated with your window manager and join the virtual machine
to the domain.
Important
T he following procedure assumes that you have a working Active Directory configuration and that
the Active Directory domain is already joined to the Manager. You must also ensure that the clocks
on the Manager, the virtual machine and the system on which Active Directory is hosted are
synchronized using NT P.
110
Chapter 8. Configuring Single Sign-On
Procedure 8.2. Configuring Single Sign-On for Red Hat Enterprise Linux Virtual Machines
1. Log in to the Red Hat Enterprise Linux virtual machine.
2. Run the following command to enable the required channel:
# rhn-channel --add --channel=rhel-x86_64-rhev-agent-6-server
3. Run the following command to download and install the guest agent packages:
# yum install rhevm-guest-agent
4. Run the following command to install the single sign-on packages:
# yum install rhev-agent-gdm-plugin-rhevcred
5. Run the following command to install the Samba client packages:
# yum install samba-client samba-winbind samba-winbind-clients
6. On the virtual machine, modify the /etc/sam ba/sm b.conf file to contain the following, replacing
DOMAIN with the short domain name and REALM.LOCAL with the Active Directory realm:
[global]
workgroup = DOMAIN
realm = REALM.LOCAL
log level = 2
syslog = 0
server string = Linux File Server
security = ads
log file = /var/log/samba/%m
max log size = 50
printcap name = cups
printing = cups
winbind enum users = Yes
winbind enum groups = Yes
winbind use default domain = true
winbind separator = +
idmap uid = 1000000-2000000
idmap gid = 1000000-2000000
template shell = /bin/bash
7. Run the following command to join the virtual machine to the domain:
net ads join -U [user name]
8. Run the following command to start the winbind service and ensure it starts on boot:
# service winbind start
# chkconfig winbind on
9. Run the following commands to verify that the system can communicate with Active Directory:
Verify that a trust relationship has been created:
111
Red Hat Enterprise Virtualization 3.4 User Guide
# wbinfo -t
Verify that you can list users:
# wbinfo -u
Verify that you can list groups:
# wbinfo -g
10. Run the following command to configure the NSS and PAM stack:
a. Run the following command to open the Authentication Configuration window:
# authconfig-tui
b. Select the Use Winbind check box, select Next and press Enter.
c. Select the OK button and press Enter.
Result
You have enabled single sign-on for your Red Hat Enterprise Linux virtual machine. Log in to the User
Portal using the user name and password of a user configured to use single sign-on and connect to the
console of the virtual machine. You will be logged in automatically.
Report a bug
8.4. Configuring Single Sign-On for Windows Virtual Machines
T o configure single sign-on for Windows virtual machines, the Windows guest agent must be installed on
the guest virtual machine. T he RHEV Guest T ools ISO file provides this agent. If the RHEV-
toolsSetup.iso image is not available in your ISO domain, contact your system administrator.
Procedure 8.3. Configuring Single Sign-On for Windows Virtual Machines
1. From the Extended tab of the User Portal, select the Windows virtual machine. Ensure the machine
is powered up, then click the Change CD button.
2. From the list of images, select RHEV-toolsSetup.iso. Click OK.
3. Once you have attached the guest tools, click the Console icon and log in to the virtual machine.
4. On the virtual machine, locate the CD drive to access the contents of the guest tools ISO file and
launch RHEV-T oolsSetup.exe. After the tools have been installed, you will be prompted to restart
the machine to apply the changes.
Result
You have enabled single sign-on for your Windows virtual machine. Log in to the User Portal using the
user name and password of a user configured to use single sign-on and connect to the console of the
virtual machine. You will be logged in automatically.
112
Chapter 8. Configuring Single Sign-On
Report a bug
113
Red Hat Enterprise Virtualization 3.4 User Guide
Revision History
Revision 3.4 -17 Wed 11 Jun 2014 Andrew Burden
Brewing for 3.4 GA.
Revision 3.4 -15 Wed 30 Apr 2014 Z ac Dover
Final build.
Revision 3.4 -14 T hurs 24 Apr 2014 T imothy Poitras
BZ #1075477 - Updated note re: enabling/disabling SSO on VMs.
Revision 3.4 -13 T ue 22 Apr 2014 Lucy Bopf
BZ #1088716 - Updated screen shots for User Portal (Basic and Extended) to include new reboot button.
Revision 3.4 -11 Wed 16 Apr 2014 Z ac Dover
T est build with updated brand
Revision 3.4 -10 Wed 16 Apr 2014 T imothy Poitras
BZ #1085670 - T idied tagging and syntax in multiple topics.
Revision 3.4 -9 T ue 15 Apr 2014 Lucy Bopf
BZ #1075919 - Added a list of parameters that can be changed while a Virtual Machine is running.
Revision 3.4 -8 T hu 03 Apr 2014 Andrew Dahms
BZ #1091596 - Added a note that console settings for virtual machines taken from virtual machine pools
are persistent.
BZ #1088648 - Updated the description of selecting virtual machines in procedures involving virtual
machine properties.
BZ #1085786 - Clarified that the Run Stateless option is only enabled on virtual machines with virtual disks.
BZ #1081744 - Updated the description of the DataCenterAdmin role.
BZ #1076282 - Added a note outlining that the name of the base template is retained for cloned virtual
machines.
BZ #1074421 - Added an explanation of how to add and configure watchdogs.
BZ #1071044 - Added a description of how to manually associate console.vv files with Remote Viewer.
BZ #1039217 - Updated the description of how to install and access console components.
Revision 3.4 -7 Wed 02 Apr 2014 Lucy Bopf
BZ #1076892 - Added the VNC Keyboard Layout option in the Run Once window.
BZ #1076318 - Updated and added procedures and screen shots to include new Reboot button.
BZ #1075526 - Updated and added procedures and screen shots for creating and previewing snapshots.
Revision 3.4 -6 T ue 01 Apr 2014 Z ac Dover
Beta build with Publican 3.99 for rhevm-doc - altered spec.tmpl
Revision 3.4 -3 T hu 27 Mar 2014 Andrew Dahms
114
Revision History
BZ #1081268 - Updated the procedure for changing the CD accessible to a virtual machine.
BZ #1076283 - Added an explanation of how to configure Cloud-Init settings for virtual machines and
templates.
BZ #1075492 - Updated sections on creating and using templates to outline the new template sub version
feature.
BZ #1075487 - Added an explanation of how to configure persistent Cloud-Init settings.
Revision 3.4 -2 T hu 20 Mar 2014 Andrew Dahms
BZ #1078606 - Updated the location of the USB Clerk and Virt Viewer .msi files.
BZ #1075878 - Updated the procedure for removing virtual disks from virtual machines.
BZ #1043433 - Added a description of how to ensure USB support is set to native for USB redirection.
Revision 3.4 -1 Mon 17 Mar 2014 Andrew Dahms
Initial creation for the Red Hat Enterprise Virtualization 3.4 release.
115
You might also like
- Red Hat Enterprise Linux-8-Configuring and Managing Virtualization-En-usNo ratings yetRed Hat Enterprise Linux-8-Configuring and Managing Virtualization-En-us303 pages
- Red Hat Enterprise Linux-9-Security hardening-en-USNo ratings yetRed Hat Enterprise Linux-9-Security hardening-en-US224 pages
- (Ebook PDF) Hands On Virtual Computing 2nd Edition Instant Download100% (1)(Ebook PDF) Hands On Virtual Computing 2nd Edition Instant Download53 pages
- Red Hat Enterprise Linux-8-Deploying Red Hat Enterprise Linux 8 On Public Cloud platforms-en-USNo ratings yetRed Hat Enterprise Linux-8-Deploying Red Hat Enterprise Linux 8 On Public Cloud platforms-en-US102 pages
- Red Hat Enterprise Linux 7 System AdminiNo ratings yetRed Hat Enterprise Linux 7 System Admini129 pages
- Red Hat Virtualization 4.3 Technical Reference en US100% (1)Red Hat Virtualization 4.3 Technical Reference en US234 pages
- Red Hat Enterprise Linux-6-Virtualization Administration Guide-En-USNo ratings yetRed Hat Enterprise Linux-6-Virtualization Administration Guide-En-US440 pages
- Red Hat Enterprise Linux-6-Virtualization Administration Guide-en-USNo ratings yetRed Hat Enterprise Linux-6-Virtualization Administration Guide-en-US430 pages
- Red Hat Enterprise Linux-6-Virtualization Administration Guide-en-US PDFNo ratings yetRed Hat Enterprise Linux-6-Virtualization Administration Guide-en-US PDF432 pages
- Red Hat Enterprise Linux 6 Deployment Guide en USNo ratings yetRed Hat Enterprise Linux 6 Deployment Guide en US780 pages
- Red Hat Virtualization-4.4-Installing Red Hat Virtualization As A Standalone Manager With Local Databases-En-UsNo ratings yetRed Hat Virtualization-4.4-Installing Red Hat Virtualization As A Standalone Manager With Local Databases-En-Us89 pages
- Red Hat Virtualization-4.0-REST API Guide-en-USNo ratings yetRed Hat Virtualization-4.0-REST API Guide-en-US688 pages
- Virtuozzo Hybrid Cloud Self Service GuideNo ratings yetVirtuozzo Hybrid Cloud Self Service Guide143 pages
- Red Hat Enterprise Linux 7 Networking Guide en USNo ratings yetRed Hat Enterprise Linux 7 Networking Guide en US183 pages
- Documentation of Life Experience: Als RPL Form 188% (8)Documentation of Life Experience: Als RPL Form 15 pages
- Red Hat Enterprise Linux-8-Configuring and Managing Virtualization-En-UsNo ratings yetRed Hat Enterprise Linux-8-Configuring and Managing Virtualization-En-Us284 pages
- Red Hat Enterprise Linux 7 Kernel Crash Dump GuideNo ratings yetRed Hat Enterprise Linux 7 Kernel Crash Dump Guide27 pages
- Red Hat Virtualization 4.4 Release Notes en USNo ratings yetRed Hat Virtualization 4.4 Release Notes en US64 pages
- Theft Detection and Disconnection in Electricity Energy Meter Using IoTNo ratings yetTheft Detection and Disconnection in Electricity Energy Meter Using IoT3 pages
- Red Hat Enterprise Linux-6-Virtualization Administration Guide-en-US PDFNo ratings yetRed Hat Enterprise Linux-6-Virtualization Administration Guide-en-US PDF247 pages
- Red Hat Virtualization-4.1-Virtual Machine Management Guide-en-US PDFNo ratings yetRed Hat Virtualization-4.1-Virtual Machine Management Guide-en-US PDF182 pages
- Red Hat Enterprise Linux-8-Configuring and Managing virtualization-en-US PDFNo ratings yetRed Hat Enterprise Linux-8-Configuring and Managing virtualization-en-US PDF220 pages
- JBoss Enterprise Application Platform 6.3 Development Guide en USNo ratings yetJBoss Enterprise Application Platform 6.3 Development Guide en US468 pages
- Red - Hat - Virtualization 4.4 Release - Notes en UsNo ratings yetRed - Hat - Virtualization 4.4 Release - Notes en Us97 pages
- Red Hat Enterprise Virtualization 3.3 Technical Reference GuideNo ratings yetRed Hat Enterprise Virtualization 3.3 Technical Reference Guide76 pages
- Red Hat Enterprise Linux-8-Configuring and Managing virtualization-en-USNo ratings yetRed Hat Enterprise Linux-8-Configuring and Managing virtualization-en-US232 pages
- Guidelines For Technical Writing in BiomedicalNo ratings yetGuidelines For Technical Writing in Biomedical34 pages
- Red Hat Enterprise Linux-8-Deploying Red Hat Enterprise Linux 8 On Public Cloud Platforms-En-USNo ratings yetRed Hat Enterprise Linux-8-Deploying Red Hat Enterprise Linux 8 On Public Cloud Platforms-En-US101 pages
- Red Hat Enterprise Linux-6-Virtualization Tuning and Optimization GuideNo ratings yetRed Hat Enterprise Linux-6-Virtualization Tuning and Optimization Guide37 pages
- Red Hat Virtualization 4.3: Virtual Machine Management GuideNo ratings yetRed Hat Virtualization 4.3: Virtual Machine Management Guide173 pages
- Red Hat Enterprise Linux-7-Migration Planning Guide-en-US PDFNo ratings yetRed Hat Enterprise Linux-7-Migration Planning Guide-en-US PDF67 pages
- Red Hat Enterprise Linux-7-Migration Planning Guide-en-US PDFNo ratings yetRed Hat Enterprise Linux-7-Migration Planning Guide-en-US PDF67 pages
- Red Hat Enterprise Linux-7-Virtualization Getting Started Guide-en-USNo ratings yetRed Hat Enterprise Linux-7-Virtualization Getting Started Guide-en-US49 pages
- Redmine Plugin Extension and Development Sample ChapterNo ratings yetRedmine Plugin Extension and Development Sample Chapter12 pages
- Red Hat Enterprise Linux-7-Performance Tuning Guide-En-USNo ratings yetRed Hat Enterprise Linux-7-Performance Tuning Guide-En-US78 pages
- Red Hat Enterprise Linux-7-Virtualization Getting Started Guide-En-USNo ratings yetRed Hat Enterprise Linux-7-Virtualization Getting Started Guide-En-US48 pages
- Red Hat Virtualization 4.1 RHEVM Shell GuideNo ratings yetRed Hat Virtualization 4.1 RHEVM Shell Guide67 pages
- Red Hat Enterprise Linux 7 Networking Guide en USNo ratings yetRed Hat Enterprise Linux 7 Networking Guide en US198 pages
- Red Hat Enterprise Virtualization For Servers-2.1-Installation Guide-En-USNo ratings yetRed Hat Enterprise Virtualization For Servers-2.1-Installation Guide-En-US70 pages
- Red Hat Enterprise Virtualization 3.4 Beta Installation Guide en USNo ratings yetRed Hat Enterprise Virtualization 3.4 Beta Installation Guide en US190 pages
- Red Hat Virtualization 4.4 Python SDK Guide en USNo ratings yetRed Hat Virtualization 4.4 Python SDK Guide en US43 pages
- Red Hat Enterprise Virtualization 3.5 Technical NotesNo ratings yetRed Hat Enterprise Virtualization 3.5 Technical Notes37 pages
- Red Hat Enterprise Linux-7-High Availability Add-On Reference-En-USNo ratings yetRed Hat Enterprise Linux-7-High Availability Add-On Reference-En-US81 pages
- Agilent Eesof Eda: Overview On Designing A Low-Noise Vco On Fr4No ratings yetAgilent Eesof Eda: Overview On Designing A Low-Noise Vco On Fr46 pages
- JBoss Enterprise Application Platform 6.3 Installation Guide en USNo ratings yetJBoss Enterprise Application Platform 6.3 Installation Guide en US91 pages
- Red Hat Certified Specialist in Virtualization: Study GuideNo ratings yetRed Hat Certified Specialist in Virtualization: Study Guide37 pages
- Red Hat Enterprise Linux-5-Virtual Server Administration-en-USNo ratings yetRed Hat Enterprise Linux-5-Virtual Server Administration-en-US58 pages
- Red Hat Enterprise Linux 6 V2V Guide en USNo ratings yetRed Hat Enterprise Linux 6 V2V Guide en US62 pages
- Red Hat Satellite 6.4: Virtual Instances GuideNo ratings yetRed Hat Satellite 6.4: Virtual Instances Guide32 pages
- Red Hat Enterprise Linux-7-Virtualization Getting Started Guide-En-USNo ratings yetRed Hat Enterprise Linux-7-Virtualization Getting Started Guide-En-US42 pages
- Red Hat Enterprise Linux 7: Virtualization Getting Started GuideNo ratings yetRed Hat Enterprise Linux 7: Virtualization Getting Started Guide49 pages
- Chapter 6 Foundations of Business IntelligenceNo ratings yetChapter 6 Foundations of Business Intelligence17 pages
- Red Hat Virtualization 4.1: Introduction To The User PortalNo ratings yetRed Hat Virtualization 4.1: Introduction To The User Portal23 pages
- Jedec Standard: DELPHI Compact Thermal Model GuidelineNo ratings yetJedec Standard: DELPHI Compact Thermal Model Guideline24 pages
- Red Hat Enterprise Linux-7-High Availability Add-On Overview-En-USNo ratings yetRed Hat Enterprise Linux-7-High Availability Add-On Overview-En-US22 pages
- A Reinforcement Learning Approach To Job-Shop Scheduling: Wei Zhang Thomas G. DietterichNo ratings yetA Reinforcement Learning Approach To Job-Shop Scheduling: Wei Zhang Thomas G. Dietterich7 pages
- PassLeader JN0-102 Exam Dumps (201-250)No ratings yetPassLeader JN0-102 Exam Dumps (201-250)11 pages
- Data Compression UNIT-5 MCQ Questions With Solutions AKTU - GOEL DIGITAL SOLUTIONNo ratings yetData Compression UNIT-5 MCQ Questions With Solutions AKTU - GOEL DIGITAL SOLUTION8 pages
- Trabajo de Ingles - Carlos Romaina FloresNo ratings yetTrabajo de Ingles - Carlos Romaina Flores2 pages
- Advanced Multiplayer Game Development with Ureal Engine 5: A Comprehensive Guide to C++ ScriptingFrom EverandAdvanced Multiplayer Game Development with Ureal Engine 5: A Comprehensive Guide to C++ ScriptingNo ratings yet
- Ubuntu 20.04 Essentials: A Guide to Ubuntu 20.04 Desktop and Server EditionsFrom EverandUbuntu 20.04 Essentials: A Guide to Ubuntu 20.04 Desktop and Server EditionsNo ratings yet
- Ubuntu 18.04 Essentials: Learn to Install, Administer and Use Ubuntu 18.04 SystemsFrom EverandUbuntu 18.04 Essentials: Learn to Install, Administer and Use Ubuntu 18.04 SystemsNo ratings yet
