1.1 About HP Integrity Virtual Machines...................................................................................................15
1.2 Running Applications in the Integrity VM Environment........................................................................16
1.3 Related Products.................................................................................................................................17
1.4 Using This Manual..............................................................................................................................18
1.5 Using the Integrity VM Documentation................................................................................................18
1.5.1 Integrity VM Manpages...............................................................................................................18
1.5.2 Help Files...................................................................................................................................19
11-1Options to the hpvmcollect Command.............................................................................................129
9
10
About This Document
This document describes how to install and configure the Integrity Virtual Machines product, and how
to create and install virtual machines and guest operating systems.
Refer to the Release Notes accompanying this documentation for recent updates, known issues, and other
information.
NOTE:The terms Integrity Virtual Machines and Integrity VM are used interchangeably throughout this
guide.
1 Intended Audience
This document is intended for system and network administrators responsible for installing, configuring,
and managing Integrity VM and virtual machines. Administrators are expected to have an in-depth
knowledge ofHP-UX operating system concepts, commands, and configuration.In addition, administrators
must be familiar with the Integrity machine console and how to install the operating systems running on
their virtual machines.
2 New and Changed Information in This Edition
This manual supersedes the manual of the same title for HP Integrity Virtual Machines Version A.01.00
(T2767-90004). For more information about the new version of the product, see “Upgrading from Earlier
Versions of Integrity VM” (page 23). For information about the features and changes in this version of
Integrity VM, see the HP Integrity Virtual Machines Release Notes.
3 Typographic Conventions
This document uses the following typographic conventions.
Book TitleTitle of a book or other document.
Linked TitleTitle that is a hyperlink to a book or other document.
http://www.hp.comA Web site address that is a hyperlink to the site.
Command
user input
computer output
EnterThe name of a keyboard key. Note that Return and Enter both refer to the same
termDefined use of an important word or phrase.
variableThe name of an environment variable, for example PATH or errno.
value
find(1)HP-UX manpage. In this example, “find” is the manpage name and “1” is the
NOTE:Examples captured from software can display software versions that differ from the actual
released product.
Command name or qualified command phrase.
Commands and other text that you type.
Text displayed by the computer.
key. A sequence such as Ctrl+A indicates that you must hold down the key labeled
Ctrl while pressing the A key.
A value that you may replace in a command or function, or information in a display
that represents several possible values.
manpage section.
4 Product Naming Conventions
Table 1 defines the naming conventions for the versions of the HP-UX operating system.
1 Intended Audience11
Table 1 HP-UX Versions
Table 2 defines the naming conventions for the versions of the Integrity VM product.
Table 2 Integrity VM Versions
5 Document Organization
This manual consists of the following chapters:
•“Introduction” (page 15) describes the concept of the virtual machine as it applies to Integrity VM.
•“Installing Integrity VM” (page 21) describes how to install the Integrity VM product.
•“Creating Virtual Machines” (page 27) describes how to create virtual machines.
•“Creating HP-UX Guests” (page 41) describes how to create HP-UX guests
•“Creating Windows Guests” (page 47) describes how to create Windows® guests.
•“Creating Virtual Storage Devices” (page 61) describes how to create virtual storage devices.
•“Creating Virtual Networks” (page 89) describes how to create virtual networks.
•“Managing Guests” (page 101) describes how to start, stop, and manage virtual machines.
•“Migrating Virtual Machines” (page 111) describes how to migrate guests to other VM Host systems.
•“Using HP Serviceguard with Integrity VM” (page 115) describes how to set up Serviceguard to
manage your guests.
•“Reporting Problems with Integrity VM” (page 129) describes how to solve virtual machine problems.
•“Integrity VM Manpages” (page 133) lists the HP-UX manpages provided with the HP Integrity VM
software.
•The “Glossary” (page 181) defines many of the terms used in the Integrity VM documentation.
Version NameVersion Number
HP-UX 11.23HP-UX 11i V2
HP-UX 11i V2 May 2005 releaseHP-UX 11i V2 (0505)
HP-UX 11i V2 September 2006 releaseHP-UX 11i V2 (0609)
HP-UX 11.31HP-UX 11i V3
Version NameVersion Number
HP Integrity Virtual Machines version 1.2Integrity VM A.01.20
HP Integrity Virtual Machines version 2.0Integrity VM A.02.00
6 Related Information
You candownload thelatest version ofthis documentfrom docs.hp.com.The followingrelated documents
can also be downloaded from the same site:
•HP Integrity Virtual Machines Release Notes
•Ignite-UX Reference
•Troubleshooting Ignite-UX Installation Booting White Paper
•HP-UX Installation and Update Guide
•HP-UX Reference
•Managing Serviceguard
•Windows on Integrity: Smart Setup Guide
•HP Auto Port Aggregation (APA) Support Guide
•Using HP-UX VLANS
The web site docs.hp.com also includes technical papers about using virtual machines.
For a time-limited evaluation version of Integrity VM, search software.hp.com.
12About This Document
7 Publishing History
Manufacturing Part
Number
Systems
8 HP Encourages Your Comments
HP encourages your comments concerning this document. We are truly committed to providing
documentation that meets your needs.
Your comments and suggestions regarding product features will help us develop future versions of the
Virtual Server Environment Management Software. Use the following e-mail address to send feedback
directly to the VSE Management Software development team: vse@hpuxweb.fc.hp.com.
NOTE:HP cannot provide product support through this e-mail address. To obtain product support,
contact your HP Support representative, your HP Services representative, or your authorized HP reseller.
For more information about support services, see the support web site at http://www.hp.com/go/support.
For other ways to contact HP, see the Contact HP web site at http://welcome.hp.com/country/us/en/
This chapter describes the Integrity Virtual Machines product, including:
•“About HP Integrity Virtual Machines” (page 15)
•“Running Applications in the Integrity VM Environment” (page 16)
•“Related Products” (page 17)
•“Using This Manual” (page 18)
•“Using the Integrity VM Documentation” (page 18)
•“Help Files” (page 19)
1.1 About HP Integrity Virtual Machines
Integrity Virtual Machines is a soft partitioning and virtualization technology that provides operating
system isolation, with sub-CPU allocation granularity and shared I/O. Integrity VM can be installed on
an Integrity server or hardware partition (nPartition) running HP-UX. The Integrity VM environment
consists of two types of components:
•VM Host
•Virtual machines (also called guests)
The VM Host virtualizes physical processors, memory, and I/O devices, allowing you to allocate them as
virtual resources to each virtual machine.
Virtual machines are abstractions of real, physical machines. The guest operating system runs on the
virtual machine just as it would run on a physical Integrity server, with no special modification. Integrity
VM provides a small guest software package that aids in local management of the guest's virtual machine.
Figure 1-1 Hardware Consolidation using Integrity VM
Guests are fully loaded, operational systems, completewith operating system, system managementutilities,
applications, and networks, all running in the virtual machine environment that you set up for them. You
boot and manage guests using the samestorage media and procedures that you would if the guest operating
system were running on its own dedicated physical hardware platform. Even the system administration
privileges can be allocated to specific virtual machine administrators.
1.1 About HP Integrity Virtual Machines15
One way to benefit from Integrity VM is to run multiple virtual machines on the same physical machine.
There is no set limit to the number of virtual machines that can be configured, but no more than 256 virtual
machines can be booted simultaneously on a single VM Host. Each virtual machine is isolated from the
others. The VM Host administrator allocates virtual resources to the guest. The guest accesses the number
of CPUs that the VM Host administrator allocates to it. CPU use is governed by an entitlement system
that you can adjust to maximize CPU use and improve performance. A symmetric multiprocessing system
can run on the virtual machine if the VM Host system has sufficient physical CPUs for it. Figure 1-1
illustrates how an HP-UX system and a Windows system can be consolidated on a single Integrity server.
The HP-UX boot disk is consolidated onto the same storage device as the VM Host boot disk and the
Windows guest storage. The Windows guest also has access to removable media (CD/DVD) that can be
redefined as necessary.
Because multiple virtual machines share the same physical resources, I/O devices can be allocated to
multiple guests, maximizing use of the I/O devices and reducing the maintenance costs of the data center.
By consolidating systems onto one platform, your data center requires less hardware and management
resources.
Another use for virtual machines is to duplicate operating environments easily, maintaining isolation on
each virtual machine while managing them from a single, central console. Integrity VM allows you to
create and clone virtual machines with a simple command interface. You can modify existing guests and
arrange networks that provide communication through the VM Host's network interface or the guest local
network (localnet). Because all the guests share the same physical resources, you can be assured of identical
configurations, including the hardware devices backing each guest's virtual devices. Testing upgraded
software and system modifications is a simple matter of entering a few commands to create, monitor, and
remove virtual machines.
Integrity VM can improve the availability and capacity of your data center. Virtual machines can be used
to run isolated environments that support differentapplications on the same physicalhardware. Application
failures and system events on one virtual machine do not affect the other virtual machines. I/O devices
allocated to multiple virtual machines allow more users per device, enabling the data center to support
more users and applications on fewer expensive hardware platforms and devices.
1.2 Running Applications in the Integrity VM Environment
The VM Host system runs the Integrity VM software, which is responsible for allocating processor and
memory resources to the running guests. The VM Host system can run physical resource, performance,
and software management and monitoring tools. To allow the VM Host to allocate resources to the virtual
machines, do not run end-user applications, such as database software, on the VM Host system. Instead,
run them on virtual machines.
Typical software you can run on the VM Host includes the following:
•HP-UX Foundation Operating Environment (FOE)
NOTE:The HP-UX FOE and license is included with the Integrity VM media so that you can install
and run Integrity VM on the VM Host system. For HP-UX guests, you must purchase FOE licenses.
•Software installation tools (Ignite-UX and Software Distributor-UX)
•Hardware diagnostic and support toolsto monitor guests (WBEM, online diagnostics, Instant Support
Enterprise Edition [ISEE])
•Utility pricing tools (Instant Capacity, Pay per use)
•Hardware management tools (nPartition Manager, storage and network management tools)
•Multipath storage solutions
Do not run the following types of software on the VM Host system:
•vPars (Virtual Partitions and virtual machines are mutually exclusive.)
•Workload Manager (WLM)
A guest running on a virtual machine runs the way it does on a physical system. By allocating virtual
resources, you provide the guest operating system and applications with access to memory, CPUs, network
devices, and storage devices as if they were part of a dedicated system.
16Introduction
Typical software you can run on a guest includes the following:
•HP-UX Foundation Operating Environment (FOE)
•Windows 2003 for Integrity Servers (Enterprise edition)
•Software installation tools (Ignite-UX and Software Distributor-UX)
•System performance monitoring tools (GlancePlus, Measureware, OpenView Operations Agent)
Applications do not have to be changed to run on a guest OS. Operating system patches and hardware
restrictions apply to guests.
Do not run the following types of applications on a guest:
•Integrity VM software
•Hardware diagnostic tools and support tools (should be run on the VM Host)
•Utility pricing tools (run on the VM Host)
•Capacity planning tools (run on the VM Host)
•Applicationsthat require direct access to physical hardware (for example, disaster-tolerant solutions)
•Multipath storage solutions
•SAN Management tools and applications that require access to serial interfaces (Integrity VM
virtualizes SCSI and Ethernet devices only)
•Auto port aggregation (APA)
You must purchase licenses for any software you run on a virtual machine, including the HP-UX operating
system and any HP or third-party layered software. You can purchase the licenses for HP software under
the HP Virtualization Licensing program. For more information, contact your HP Support representative.
You can install the VM Host on a system that is running HP-UX 11i v2 May 2005 or later. Guests must
also be running HP-UX 11i v2 May 2005 or later. Always read the product release notes before installing
any software product so that you have the latest information about changes and additions to the
documentation. The following chapters describe how to install the Integrity VM software and how to
create guests to run on the VM Host system.
1.3 Related Products
Some of the HP products that you can use with Integrity VM include:
•HP Integrity VM Manager — A graphical user interface for creating and managing HP Integrity
virtual machines. Runs under either HP System Management Homepage (SMH) or HP Systems
Insight Manager as part of the HP Integrity VSE. For more information, see the Getting Started withIntegrity Virtual Machine Manager guide.
•HP Integrity Virtual Server Environment (VSE) — A graphical user interface for managing HP Integrity
central managed systems (CMS). Runs under HP Systems Insight Manager. For more information,
see the HP VSE Management Software Quick Start Guide.
•HP-UX operating system — Integrity VM runs on HP-UX 11i v2 Integrity systems. For more
information, see the HP-UX 11i v2 Installation and Update Guide.
•HPIntegrity Support Pack and Microsoft® Windows®Server 2003 Service Pack 1 — HP recommends
that you install the Support Pack and SP1 on all HP Integrity servers running Windows Server 2003,
64-bit.. For more information, see the HP Integrity Support Pack and Microsoft Windows Server 2003Service Pack 1 Release Notes.
•VERITAS Volume Manager— A data storage solution product that can be used to manage the physical
disks on the VM Host. For more information, see the VERITAS Volume Manager Administrator's Guide.
•HP Auto Port Aggregation (APA) — A network switch that allows you to manage multiple network
interfaces, which can be allocated to guests. For more information, see the HP Auto Port Aggregation
(APA) Support Guide
•HP Integrity Virtual Machines VMMigrate utility — Anoptional, separately-installed software package
that allows you to move virtual machines from one VM Host to another. For more information, see
“Migrating Virtual Machines” (page 111) in this manual.
1.3 Related Products17
•HP Serviceguard — A software product that allows you to create clusters of HP-UX systems for high
availability. For moreinformation, see the Managing Serviceguard manual, and “UsingHP Serviceguard
with Integrity VM” (page 115), in this manual.
•HP Integrity Essentials Global Workload Manager (gWLM) — A software product that allows you
to centrally define resource-sharing policies that you can use across multiple Integrity servers. These
policies increase system utilization and facilitate controlled sharing of system resources.
1.4 Using This Manual
This manual provides all the information you need to install Integrity VM, create virtual machines, install
and manage guests, and use all the features of Integrity VM. Table 1-1 describes each chapter in this
manual.
Table 1-1 Chapters of this Manual
Read if...Chapter
You are new to HP Integrity Virtual Machines.“Introduction” (page 15)
You are installing the HP Integrity Virtual Machines product.“Installing Integrity VM” (page 21)
“Creating Virtual Machines” (page 27)
“Creating HP-UX Guests” (page 41)
“Creating Windows Guests” (page 47)
“Creating Virtual Storage Devices” (page 61)
“Creating Virtual Networks” (page 89)
“Migrating Virtual Machines” (page 111)
“Using HP Serviceguard with Integrity VM” (page 115)
“Glossary” (page 181)
You are setting up new virtual machines on your VM Host
system.
You are creating virtual machines that will run the HP-UX
operating system.
You are creating virtual machines that will run the HP Integrity
Windows 2003 Enterprise operating system.
You need to make changes to the storage devices used by the
VM Host or virtual machines.
You need to make changes to the network devices on the VM
Host systemor to the virtual networkdevices used by the virtual
machines.
You need to manage existing virtual machines.“Managing Guests” (page 101)
You need to move virtual machines from one VM Host system
to another.
Youneed to set up Serviceguard to manage your VMHost system
or your virtual machines.
Youencounter problems while creating or using virtual machines.“Reporting Problems with Integrity VM” (page 129)
You need to understand how to use an Integrity VM command.“Integrity VM Manpages” (page 133)
You do not understand the definition of a term used in the
Integrity VM product documentation.
1.5 Using the Integrity VM Documentation
The Integrity VM product includes several useful sources of information, whether you are considering
how to set up your virtual machines or determining how to upgrade your installation.
1.5.1 Integrity VM Manpages
For online information about using Integrity VM, refer to the following manpages:
•hpvm(5) - describes the Integrity VM environment.
•hpvmclone(1M) - describes how to create virtual machines based on existing virtual machines.
•hpvmcollect(1M) - describes how to collect virtual machine statistics.
•hpvmconsole(1M) - describes how to use the virtual machine console.
•hpvmcreate(1M) - describes how to create virtual machines.
•hpvmdevmgmt(1M) - describes how to modify the way virtual devices are handled.
•hpvminfo(1M) - describes how to get information about the VM Host.
•hpvmmigrate(1M) - describes how to migrate virtual machines from one VM Host to another.
18Introduction
•hpvmmodify(1M) - describes how to modify virtual machines.
•hpvmnet(1M) - describes how to create and modify virtual networks.
•hpvmstart(1M) - describes how to start virtual machines.
•hpvmstatus(1M), - describes how to get statistics about the guests.
•hpvmstop(1M) - describes how to stop a virtual machine.
•hpvmremove(1M) - describes how to remove a virtual machine.
•hpvmresources(1M) - describes how to specify the storage and network devices used by virtual machines.
1.5.2 Help Files
The virtual machine console is a special interface for managing guests. To start the virtual console after
you create a guest, enter the hpvmconsole command and specify the guest name. For help using the
virtual console, enter the HE command. For more information about the virtual console, see “Using the
Virtual Console” (page 105).
1.5 Using the Integrity VM Documentation19
20
2 Installing Integrity VM
This chapter describes how to install the Integrity VM software and how to prepare the VM Host
environment for guests. It includes the following sections:
•“Installation Requirements” (page 21)
•“Installation Procedure” (page 22)
•“Upgrading from Earlier Versions of Integrity VM” (page 23)
•“Verifying the Installation of Integrity VM” (page 24)
To prepare your VM Host system for Integrity VM installation, your configuration must satisfy the
hardware, software, and network requirements described in this section. To install Integrity VM, you need
a computer that fits the specifications listed in “VM Host System Requirements” (page 21).
NOTE:Before installing this product, read the HP Integrity Virtual Machine Release Notes. The most
up-to-date release notes are available on http://docs.hp.com.
2.1.1 VM Host System Requirements
The resourceson the VM Host system (such as disks, network bandwidth, memory, and processing power,
are shared by the VM Host and all the running guests. Guests running simultaneously share the remaining
memory and processing power. By default, network and storage devices are also sharable among guests.
Some resources must be made exclusive to the VM Host, such as the VM Host operating system boot disk.
Table 2-1 describes the minimum configuration requirements for installing Integrity VM on the VM Host
system.
Table 2-1 Requirements for Installing Integrity VM
DescriptionResource
An Integrity serverComputer
Operating system
Disk storage
HP-UX 11i v2 May 2005 or later, running on an Integrity server, as well as any
appropriate software patches (see the HP Integrity Virtual Machines Release Notes). The
license for Integrity VM includes the license for running the HP-UX Foundation
Operating Environment on the VM Host system.
Required for network connection and configuration.Local area network (LAN) card
An appropriate source for installing software (DVD or network connection).Source installation media
Sufficient disk space for the following:
• The VM Host operating system (refer to the HP-UX 11i v2 Installation and UpgradeGuide)
• The VM Host software (50 MB)
• Swap space size should be at least as large as physical memory plus 4GB (for
example, for 16 GB of RAM, swap space should be 20 GB)
NOTE: HP-UX uses this space to start up guests, but guests are never swapped
out.
• Disk space for each guest operating system, including swap space
• Disk space for the applications running on each guest
• 4.7 MB for each running guest as the allowance for backing up configuration files
2.1 Installation Requirements21
Memory
Table 2-1 Requirements for Installing Integrity VM (continued)
DescriptionResource
Sufficient physical memory (RAM), including the following:
• 750 MB + 7.5% of memory beyond the first GB (that is, 7.5% of (total physical
memory - 1 GB))
• Total aggregate memoryrequired foreach guest(operating systemand application
requirements)
HP-UX 11i v2 May 2005 requires a minimum of 1 GB of memory, so a guest running
HP-UX must be configured with at least that much memory.
• Additional 7% of aggregate guest memory for overhead
For example, for a VM Host with 16 GB of memory and two VMs configured with
3GB of memory each, the memory requirements would be calculated as follows:
• 1.86 GB for the VM Host (750 MB plus 7.5% of 15 GB)
• 6.42 GB total guest requirement (107% of 6 GB)
• Total requirements = 8.28 GB of memory
This leaves 7.72 GB of memory for additional guests.
Integrity VM software
Network configuration
The software bundle T2767AC. Refer to “Bundle Names” (page 22) for information
about the required software for installing Integrity VM.
A configured and operational network, with at least one LAN card if you plan to allow
remote access to guest virtual consoles. To allow guests network access, the VM Host
must haveat leastone functioning network interfacecard (NIC).For more information
about configuring network devices for virtual machines, see “Creating Virtual
Networks” (page 89).
2.1.2 Bundle Names
Integrity VM software is bundled as T2767AC, which includes VMAGENT, the Integrity VM fair-share
scheduler. When you install Integrity VM, the following software bundles are installed:
•T2767AC
•PRM-Sw-Krn (included with T2767AC)
•VMGuestLib
In addition to the T2767AC bundle, you can install the following optional software bundles:
•VMProvider (to use the HP Integrity VM Manager to manage the VM Host)
•VMMigrate (to be able to migrate virtual machines from one VM Host to another). For information
about using the hpvmmigrate command, see “Migrating Virtual Machines” (page 111).
2.1.3 Using VM Manager Requires the Latest WBEM Services on the VM Host
The version of HP WBEM Services for HP-UX must be A.02.00.10 or later. Integrity VM fails to install if
the version of WBEM Services on your VM Host is older than A.02.00.10. The HP WBEM Services for
HP-UX software bundle (B8465BA) is available as part of the HP-UX 11i V2 0606 (June 2006) operating
system and later. For VM Hosts running earlier versions of HP-UX, download the latest version of WBEM
Services from www.hp.com.
2.2 Installation Procedure
Once you have read the product release notes and verified that you have met the proper system
requirements as described in “VM Host System Requirements” (page 21), install the Integrity VM software
as described in this section.
NOTE:Installing the Integrity VM software mayrequire the system to reboot. Therefore, the swinstall
command line installation includes the autoreboot=true parameter.
To install the HP Integrity VM software, follow these steps:
22Installing Integrity VM
1.If you have the installation media, mount it.
If you are installing from the network, identify the VM Host and pathname that correspond to the
software distribution depot that contains the T2767AC bundle (for example,
my.server.foo.com:/depot/path).
2.Use the swinstall command to install Integrity VM and specify the path to the depot. For example:
b.Select the Integrity VM bundle (T2767AC) from the list presented by the GUI.
The VM Host and guest configuration files are stored at /var/opt/hpvm. The new configuration
files are not compatible with those of previous versions of Integrity VM.Therefore, if you are upgrading
to the current version, the guest configuration files (except the /ISO-Images/ directory) are saved
to the /var/opt/hpvm_backup directory. If you revert to the older version of Integrity VM, you
can use the backup configuration files to restore your VM Host and guest configurations.
3.Unmount and remove any installation media. The VM Host system automatically reboots, if necessary.
4.Once the Integrity VMsoftware is installed and running, the VM Host is available. Enter the following
command to get information about the status of the guests:
# hpvmstatus
hpvmstatus: No guest information is available.
hpvmstatus: Unable to continue.
The installation is now complete, with the following results:
•Integrity VM is installed in the /var/opt/hpvm directory.
•Integrity VM data files are installed under the /var/opt/hpvm directory.
•Integrity VM commands are installed in the /opt/hpvm/bin directory.
•Integrity VM installation modifies certain kernel parameters. If you use multiple shells to manage
Integrity VM, change the kernel parameters on all your shells. Table 7-1 lists the kernel parameters
that are modified when you install Integrity VM.
Table 2-2 Kernel Parameters
dbc_max_pct
dbc_min_pct
maxdsiz_64bit
swapmem_on
You can now create guests using the hpvmcreate command, as described in Chapter 3 (page 27).
2.3 Upgrading from Earlier Versions of Integrity VM
When you upgrade Integrity VM from an earlier version, you should:
1.Shut down all running guests (using the hpvmstop command).
2.Locate and install the new version of Integrity VM.
3.Install new versions of the vmmigrate utility and the VMProvider, if they were previously installed.
4.Reboot the VM Host system.
Modified ValueDefault ValueParameter
150
15
343597383684294967296
01
2.3 Upgrading from Earlier Versions of Integrity VM23
Existing guest configuration information, operating system software,and application data are not affected
when you upgrade Integrity VM.
If you have installed an evaluation version of Integrity VM, you should remove the evaluation software
before installing the Integrity VM product. For more information, refer to the Integrity VM Release Notes.
2.4 Verifying the Installation of Integrity VM
To verify that Integrity VM installed successfully, enter the following hpvminfo command:
# hpvminfo
hpvminfo: Running on an HPVM host.
To see exactly what versions of specific bundles are installed, enter the swlist command:
Guests are not affected by this procedure. To remove guests, see the procedures in “Removing Virtual
Machines” (page 38).
2.6 Reserving VM Host Devices
You can protect the storage and network resources used by the VM Host against usage and corruption by
virtual machines by marking the VM Host devices as restricted devices. For example, you can reserve the
disk storage on which the VM Host operating system and swap space reside, which prevents guests from
24Installing Integrity VM
being able to access the same disk storage devices. The hpvmdevmgmt command allows you to establish
restricted devices.
For example, to restrict the /dev/rscsi/c2t0d0 device, enter the following command:
# hpvmdevmgmt –a rdev:/dev/rscsi/c2t0d0
To complete the restriction of volumes, each device included in the volume must also be restricted. For
more informationabout using the hpvmdevmgmt command, see “Managing the DeviceDatabase” (page 107).
2.7 Troubleshooting Installation Problems
If the installation verification fails, report the problem using the procedures described in “Reporting
Problems with Integrity VM” (page 129). Some problems encountered in the process of installing Integrity
VM are described in the following sections.
2.7.1 Error messages during installation
One or more of the following messages might be displayed during Integrity VM installation:
could not write monParams: Device is busy
hpvmnet * already exists
/sbin/init.d/hpvm start ran without running /sbin/init.d/hpvm stop
You can ignore these messages.
2.7 Troubleshooting Installation Problems25
26
3 Creating Virtual Machines
After you install Integrity VM, you can begin to create guests. This chapter includes the following sections:
When you create a new virtual machine, you specify its characteristics. Later, you can change the virtual
machine characteristics. The characteristics of a virtual machine are listed in Table 3–1.
You can create a virtual machine using the following commands:
•hpvmcreate
•hpvmclone
After you create a virtual machine, you can modify it using the the hpvmmodify command. All of these
commands accept the same options for specifying virtual machine characteristics. Each option and
characteristic is described in more detail later in this chapter.
Table 3-1 Characteristics of an Integrity Virtual Machine
-P vm-name
-O os_type
-c number_vcpus
-e percent
-E cycles
-r amount
-a rsrc
3.1.1 Virtual Machine Name
Use the-p vm-name option tothe hpvmcreate command to specify the name of the new virtual machine.
This option is required. In the following example, the new virtual machine is named compass1:
# hpvmcreate -P compass1
Where DescribedVirtual Machine CharacteristicCommand Option
“Virtual Machine Name” (page 27)Virtual machine name. You must specify a
name when you create or modify the virtual
machine. You cannot modify this
characteristic.
“Guest Operating System” (page 28)Operating system. If you do not specify the
operating system type, it is set to
UNKNOWN.
“Virtual CPUs” (page 28)Virtual CPUs (vCPUs). If you omit this
option when you create the virtual machine,
the default is one vCPU.
“Entitlement” (page 28)CPU entitlement. If you omit this option
when you create the virtual machine, the
default is 10%.
“Guest Memory Allocation” (page 29)Memory. If you omit this option when you
create the virtual machine, the default is 2
GB.
“Virtual Devices” (page 29)Virtual devices.If you omit thisoption when
you create the virtual machine, it has access
to no network and storage devices.
The virtual machine name can be up to 256 alphanumeric characters. To provide remote console access to
the guest, its name must be a legal UNIX account name (no more than eight characters, where the colon
(:) and newline (\) characters are not valid). See password(1M) for more information about HP-UX account
3.1 Specifying Virtual Machine Characteristics27
names. For more information about setting up remote console access to the guest, see “Using the Virtual
Console” (page 105).
3.1.2 Guest Operating System
Use the -o os_type option to the hpvmcreate command to specify the type of operating system that
will run on the virtual machine. This option is not required.
For os_type, specify one of the following:
•hpux
•windows
If you do not supply the operating system type, it defaults to UNKNOWN. When you install the operating
system, this value in the guest configuration file is automatically set to the appropriate operating system
type.
In the following example, the virtual machine compass1 is specified as an HP-UX guest:
# hpvmcreate -P compass1 -o hpux
For more information about creating HP-UX guests, refer to Chapter 4 (page 41).
For more information about creating Windows guests, refer to Chapter 5 (page 47).
When a running guest transitions from running in the machine console to running in the operating system,
the operating system type is detected. If the operating system type is different from the information in the
guest's configuration file, it is automatically updated to reflect the current operating system.
3.1.3 Virtual CPUs
Use the -c number_vcpus option to the hpvmcreate command to specify the number of virtual CPUs
(vCPUs) that the virtual machine can use. If you do not specify the number of vCPUs, the default is 1. For
example, to set the new virtual machine compass1 to have two vCPUs, enter the following command:
# hpvmcreate -P compass1 -c 2
Every virtual machine has at least one vCPU. A virtual machine cannot use more than vCPUs than the
number of physical CPUs on the VM Host system. (For the purpose of this discussion, the term “physical
CPU” refers to a processing entity on which a software thread can be scheduled.)
Integrity VM allows you to create a virtual machine with more vCPUs than the number of physical CPUs
on the VM Host system. Warning messages are dislayed if there are not enough physical CPUs to run the
virtual machine. This feature allows you to create virtual machines for future configurations. However,
the virtual machine is not allowed to start on a VM Host system that does not have enough physical CPUs.
3.1.4 Entitlement
Use the -e or -E option to specify the virtual machine's entitlement.
Virtual machine entitlement is the minimum amount of processingpower guaranteedto the virtual machine
from each virtual CPU. When you create a virtual machine, you can use the -e option to specify the
entitlement as a percentage, from 5% to 100%. If you do not specify the entitlement, the virtual machine
receives 10% entitlement by default.
Alternatively, you can use the -E option to specify the entitlement as the number of CPU clock cycles per
second to be guaranteed to each vCPU on the virtual machine.
For example, to specify an entitlement of 20% for the new virtual machine compass1, enter the following
command:
# hpvmcreate -P compass1 -e 20
When the virtual machine is booted, the VM Host ensures that sufficient processing power is available
for each running virtual machine to receive its entitlement. For virtual machines with multiple virtual
CPUs, the entitlement is guaranteed on all the vCPUs in the virtual machine's configuration. For example,
if a virtual machine has four vCPUs, and the entitlement is set at 12%, the VM Host ensures that the
equivalent of at least 48% of a physical CPU's processing power is available to that virtual machine. As
28Creating Virtual Machines
many physical processors as the virtual machine has vCPUs can contribute to the total processing power
of the virtual machine.
To allow multiple virtual machines to run at the same time, make sure that the entitlement of each virtual
machine does not prevent the others from obtaining sufficient processor resources. The sum of all
entitlements across all active virtual machines cannot total more than 100% for any physical processor. If
available processor resources are insufficient, the virtual machine is not allowed to boot; error messages
are displayed to indicate the specific problem.
If a virtual machine is busy and sufficient processing power is available on thehost system, the virtual
machine can receive more than its entitlement. When there is contention for processing power (on a VM
Host system with busy virtual machines), each virtual machine is limited to its entitlement.
3.1.5 Guest Memory Allocation
Use the -r amount option to the hpvmcreate command to specify the amount of virtual memory (in
either gigabytes or megabytes) to be allocated to the guest. If you do not specify the memory allocation,
the default is 2 GB. For example, to allocate three gigabytes to the virtual machine compass1, enter the
following command:
# hpvmcreate -P compass1 -r 3G
The amount of memory to allocate is the total of the following:
•The amount of memory required by the guest operating system. For example, the HP-UX 11i v2
operating system requires 1 GB of memory.
•The amount of memory required by the applications running on the guest.
The amount of memory should be at least the total of these two amounts. If there is not enough memory
in the current configuration, Integrity VM issues a warning but allows you to create the virtual machine.
This allows you to create virtual machines for future configurations. When the virtual machine is started,
the VM Host makes sure that there is sufficient memory to run the virtual machine. In addition to the
amount of memory you specify for the virtual machine, the VM Host requires a certain amount overhead
for booting the guest operating system. The amount of memory allocated to all the running guests cannot
exceed the amount of physical memory minus the amount used by the VM Host for its operating system
and its administrative functions. For more information about the memory requirements of the VM Host,
see “Installation Requirements” (page 21).
3.1.6 Virtual Devices
Use the -a option to the hpvmcreate command to allocate network and storage devices to the virtual
machine. The VM Host presents the devices to the virtual machine as “virtual devices.” You specify both
the physical device to allocate to the virtual machine and the virtual device name that the virtual machine
will use to access the device. The following sections provide brief instructions for creating virtual network
devices and virtual storage devices.
3.1.7 Creating Virtual Network Devices
The guest virtual network consists of:
•Virtual network interface cards (vNICs)
•Virtual switches (vswitches)
For virtual machines to communicate either with other virtual machines or outside the VM Host system,
each virtual machine's virtual network must be associated with a virtual switch (vswitch). If you start a
virtual machine without a vswitch, the virtual machine has no network communication channel. A vswitch
functions like a physical network interface card (pNIC), accepting network traffic from one or more virtual
machines and directing network traffic to an associated port. A vswitch can be associated with a VM Host
pNIC, or it can be local to the virtual machines on the VM Host and provide a dedicated network among
guests.
Integrity VM always creates a vswitch named localnet. This network is not associated with a pNIC. It
is used only for communication between the guests running on the same VM Host. The localnet vswitch
does not use a name server or router, and the VM host does not access the localnet vswitch. For more
information, see “Local Networks” (page 91).
3.1 Specifying Virtual Machine Characteristics29
You can create vswitches any time, before or after creating guests that access the vswitches. If you create
the virtual machine before creating the vswitch, the virtual machine is created and warning messages
display the specific problem. This allows you to create virtual machines for future configurations.
To create a vswitch, enter the hpvmnet -c command. For example:
# hpvmnet -c -S vswitch-name -n nic-id
where:
•vswitch-name is the name you assign to the vswitch.
•nic-id is the pNIC ID on the VM Host. If you omit the nic-id, the vswitch is created for the
localnet.
To start the vswitch, enter the hpvmnet -b command. For example:
# hpvmnet -b -S vswitch-name
To allocate the vswitch to the virtual machine named compass2, use the —a option to the hpvmcreate
command. For example:
# hpvmcreate -P vm-name -a network:lan:[hardware-address]:vswitch:vswitch-name
where hardware-address (optional) the vNIC PCI busnumber, device, and MAC address. This portion
of the command is optional. If you omit the specific bus, device, and MAC address information, it is
generated for you. HP recommends that you allow this information to be automatically generated. In this
case, simply omit the hardware-address value from the command line. For example:
# hpvmcreate -P -a network:lan::vswitch:vswitch-name
For more information about using the hpvmnet command, see “Creating Vswitches” (page 90).
On the guest, use standard operating commands and utilities to associate the vNIC with an IP address,
or use DHCP just as you would for a physically independent machine.
By default, vswitches are sharable; you can allocate the same vswitch to multiple virtual machines.
With Integrity VM A.02.00 and later, you can create virtual LANs (VLANs), which allow virtual machines
to communicate with other virtual machines using the same VLAN, either on the same VM Host or on
different VM Host systems. You associate the VLAN port number with a vswitch, then allocate that vswitch
to virtual machines that communicate on that VLAN. For more information about VLANs, see the manual
Using HP-UX VLANs.
For more information about creating and managing vswitches, see Chapter 7 (page 89).
3.1.8 Creating Virtual Storage Devices
When you create a virtual machine, you specify the virtual storage devices that the virtual machine uses.
Virtual storage devices are backed by physical devices on the VM Host system. The VM Host system must
have sufficient physical storage for the VM Host and for all of the virtual machines.
When you create a virtual machine with the hpvmcreate command, you can specify both the virtual
devices that the virtual machine recognizes and the physical backing stores on the VM Host system. Use
the -a option to create and allocate the virtual device to the virtual machine. For example:
# hpvmcreate -a device-type:adapter-type:[hardware-address]:storage-type:device
where:
•device-type is the type of virtual device that the virtual machine will use. This can be one of the
following:
—disk
—dvd
—tape
30Creating Virtual Machines
Loading...
+ 158 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.