 |
» |
|
|
 |
To create
a virtual machine, VM Manager uses the Create Virtual Machine wizard to guide you through the process.
Each step presents a dialog that allows you to specify the required
information. At any time you can get help, return to previous steps,
or exit the wizard. By creating a new virtual machine, you assign
attributes and resources to it. This creates an association among
the virtual devices known to the virtual machine and the physical
devices managed by the VM Host. Where possible, reasonable default values are
provided for each dialog. However, the default values are not necessarily
optimal. You must determine what values are optimal based on the unique
requirements of your machine (such as the applications you plan to
run and the performance you expect). To access the Create Virtual Machine wizard, select Create Virtual Machine... from the VM Manager menu bar. The Create Virtual Machine
wizard leads you through the following steps. For more information
about any step, see the corresponding VM Manager help topic. Specify VM Identity Specify the virtual
machine name, an optional description, the intended guest operating
system, and the virtual machine hardware startup value (autoboot). Specify Processor Entitlements The processor
entitlement sets the guaranteed amount of processing power for each
virtual CPU in a virtual machine. The processor entitlement is the
default entitlement (10%), a percentage of physical processor power,
or a specific, fixed processor speed. If supported by the
version of Integrity VM running on the VM Host, you can specify an
entitlement cap and the minimum and maximum number of vCPUs to be
allotted to the virtual machine. An entitlement cap is the maximum
amount of computing power allotted to a virtual machine for each vCPU. Specify Memory Specify
the amount of memory for the virtual machine. If the VM Host has Integrity
VM 3.0 or later installed and the OS type you chose in step 1 supports
dynamic memory (for example, specifying HP-UX as the intended guest
OS, with Integrity VM 3.0 or later installed on the VM Host), the
memory screen allows you to set dynamic memory parameters. Specify Network Devices To add a virtual network device, click Add Network Device... on the first network device screen.
This brings up the Add Network Device screen. First, select the type of virtual network interface card. The default
is an emulated LAN device. You can select Accelerated Virtual Input/Output
(AVIO) device type if AVIO is supported by the version of Integrity
VM (version 3.5 or later) on the VM Host and by the intended guest
OS. For more information, see the HP Integrity Virtual Machines Installation, Configuration,
and Administration manual. After you select
the virtual network interface type, select the virtual switch from
the list provided or create a virtual switch. To provide network access
for the virtual machine, a virtual switch is necessary. To add a virtual storage device, click Add Storage Device... on the first storage device screen.
This brings up the Add Storage Device screen. First, select the type of virtual storage adapter. The default is
an emulated SCSI adapter. You can select Accelerated Virtual Input/Output
(AVIO) adapter type if AVIO is supported by the version of Integrity
VM (version 3.5 or later) on the VM Host and by the intended guest
OS. If the VM Host
is running HP-UX 11i v3, the Add Storage Device screen gives you the choice of listing storage devices by their
agile address (the default) or by their legacy address. HP recommends
using agile device addressing when configuring storage devices. This
provides benefits especially for multipath devices. With legacy addressing,
the screen lists one entry for each path to a storage device that
has multiple paths. With agile addressing, the screen lists only one
entry for each multipath storage device. To change the addressing
scheme for viewing, select the appropriate addressing scheme. If the
VM Host runs an earlier version of HP-UX, you are not given a choice:
the table lists devices by the legacy addressing scheme only. For
more information about agile addressing, see the VM Host
Storage tab help topic. For more information on AVIO devices and on agile addressing,
see the HP Integrity Virtual Machines Installation, Configuration,
and Administration manual. After you select the
virtual storage adapter type, select the physical backing device from
the list provided (such as disk, DVD, tape, LVM volume, files).
Summary Review the identity and resources
specified for the new virtual machine and preview the command that
will be used to create it. This summary step allows you to review
all information before the new virtual machine is created. At this step, you can still cancel (exit the Create Virtual
Machine wizard) or return to modify previous steps in the wizard. When you click Finish, the wizard executes
the hpvmcreate commands displayed in the Command Preview area: If the Create
VM even if resources are insufficient, missing or unavailable check box is not selected, the wizard executes the first of two
commands (hpvmcreate -s) to check for resource
availability and other issues without actually creating the virtual
machine. This command reports any errors or warnings at the top of
the page. If warnings or errors are detected, the virtual machine
will not be created. Upon analyzing any reported warnings, you can
choose to create the virtual machine anyway by selecting the check
box and clicking Finish again. If no serious problems are detected by the first command,
the wizard then executes the second command (hpvmcreate -F), which creates the virtual machine. If the Create
VM even if resources are insufficient, missing or unavailable check box is selected, the wizard does not check for resource warnings.
It simply runs the hpvmcreate -F to create the
virtual machine even if potential resource issues exist (but not if
a fatal error is detected). For example, if this check box is selected,
you can create a virtual machine that uses a physical disk that some
other running virtual machine is already using. As another example,
you can create a virtual machine for which you incorrectly specified
a storage device file. You can correct these kinds of problems after
the virtual machine is created and before it is started. For information
about problem solving, see “Troubleshooting Virtual Machine Problems”.
Specify VLAN IDs If the
VM Host supports vswitch VLANs (virtual LANs), and virtual NICs (vNICs)
are specified for the new virtual machine, then you can assign VLAN
IDs to the newly created virtual machine. You can assign a VLAN ID
to the vswitch port connected to each virtual NIC in the virtual machine.
By default, VLANs are not specified (VLAN ID is “none”). When you click OK on this page, any modifications
to the VLAN IDs are updated, after which the Create Virtual Machine
wizard Next Steps page is displayed. Next Steps After creating the new virtual
machine, VM Manager presents you with the next steps you can take
to manage and use the new virtual machine. The steps presented depend
on the environment in which you created the virtual machine. For example,
when virtual machine scheduling on a VM Host is managed by HP Global
Workload Manager (gWLM), the Next Steps page
advises you to associate the virtual machine with a gWLM policy and
add the virtual machine to a Shared Resource Domain (SRD). You cannot
start the virtual machine until you complete that action. If the new virtual machine includes AVIO devices (AVIO
support is provided on HP Integrity VM version 3.5 or later), you
are advised to make sure the appropriate OS that supports AVIO is
installed on the VM Host and the virtual machine. If the intended
OS on the virtual machine does not support AVIO, you are warned of
this. For each virtual machine containing an AVIO device, the VM Host
OS and the guest OS must support AVIO. In addition, HP strongly
recommends that AVIO components (such as drivers and libraries) on
the virtual machine be updated to the latest release of the OS. If
the virtual machine OS is Windows or Linux, install additional AVIO-compatible
drivers on the VM Host and virtual machine; the Windows and Linux
AVIO drivers include instructions for installing the drivers on virtual
machines. If the virtual machine OS is HP-UX, the AVIO components
on the VM Host and virtual machine should be from the same release
of the OS; for example, both VM Host and virtual machine should use
the components from the same OE or from the same Web Release (for
example, WEB0803). For more information about AVIO requirements,
see the HP Integrity Virtual Machines Installation, Configuration,
and Administration manual. Other steps you can take include starting the virtual
hardware for the virtual machine, accessing the virtual machine console,
getting information about the virtual machine, and tuning the performance
of the virtual machine. You can configure the virtual machine's Extensible Firmware
Interface (EFI) to boot the guest OS automatically when the virtual
machine is started (powered on). Configure EFI when the virtual machine
has been started and before booting the OS. You can interact with
EFI through the virtual Management Processor (vMP) for the virtual
machine. The vMP provides access to the console for the virtual machine.
To interact with vMP, use the hpvmconsole command.
For more information, see the HP Integrity Virtual Machines Installation, Configuration,
and Administration manual. If you are using VM Manager from HP SMH, click OK to finish. VM Manager displays the page from which you initiated
the Create Virtual Machine wizard. If you are using VM Manager from HP SIM, click Apply gWLM Policy. To skip this step and add the new
virtual machine to the SRD later, click Apply Later (you must click either button). When you click Apply Later, VM Manager displays the page from which you initiated the Create
Virtual Machine wizard. When you are ready to add the virtual machine
to the SRD, select the virtual machine from the appropriate screen
(for example, from the VM Host Virtual Machines tab) and then select Policy Apply gWLM Policy ... from
the VM Manager menu bar. For more information, see the VM Manager Policy Menu help topic.  |  |  |  |  | NOTE: After creating a virtual machine using VM Manager, if you return
immediately to Virtualization Manager, the machine might not yet appear
in Virtualization Manager. This means HP SIM has not yet completed
identifying the new virtual machine. However, it appears when the
identification process completes (usually within a minute or two). |  |  |  |  |
|