HP Integrity Virtual Server Manager 6.3 User Guide

on the VSP and the VM. If the intended OS on the VM does not support AVIO, you are warned
of this. In addition, HP strongly recommends that AVIO components (such as drivers and
libraries) on the VM and VSP be updated to the latest release of the OS. If the VM OS is
Windows or Linux, install additional AVIO-compatible drivers on the VM; the Windows and
Linux AVIO drivers include instructions for installing the drivers on VMs. For more information
about AVIO requirements, see the HP-UX vPars and Integrity VM Administrator Guide manual.
Other steps you can take include starting the virtual hardware for the VM, accessing the VM
console, adding additional software (provider components) needed to support management
of the VM, getting information about the VM, and tuning the performance of the VM.
NOTE: Any devices added using the Create Virtual Machine wizard are not functional on
the VM until the new VM is started. Certain devices are not seen in a Integrity Virtual Server
Manager Storage tab until the VM is started.
You can configure the VM's Extensible Firmware Interface (EFI) to boot the guest OS
automatically when the VM is started (powered on). Configure EFI when the VM has been
started and before booting the OS. You can interact with EFI through the virtual Management
Processor (vMP) for the VM. The vMP provides access to the console for the VM. To interact
with vMP, use the hpvmconsole command. For more information, see the HP-UX vPars and
Integrity VM Administrator Guide manual.
If you are using Integrity Virtual Server Manager from HP SMH, click OK to finish. Integrity
Virtual Server Manager displays the page from which you initiated the Create Virtual Machine
wizard.
If you are using Integrity Virtual Server Manager from HP Matrix Operating Environment, click
Apply gWLM Policy. To skip this step and add the new VM to the SRD later, click Apply Later
(you must click either button). When you click Apply Later, Integrity Virtual Server Manager
displays the page from which you initiated the Create Virtual Machine wizard. When you
are ready to add the VM to the SRD, select the VM from the appropriate screen (for example,
from the VSP Virtual Servers tab) and then select Policy →Apply gWLM Policy ... from the
Integrity Virtual Server Manager menu bar. For more information, see the Integrity Virtual
Server Manager Policy Menu help topic.
NOTE: After creating a VM using Integrity Virtual Server Manager, if you return immediately
to HP Matrix OE visualization, the machine might not yet appear in HP Matrix OE visualization.
This means Systems Insight Manager/HP Matrix Operating Environment has not yet completed
identifying the new VM. However, it appears when the identification process completes (usually
within a minute or two).
Modifying VMs
To modify a VM, select one of the following items from the Integrity Virtual Server Manager Modify
menu. For more information about any item, see the corresponding Integrity Virtual Server Manager
help topic.
NOTE: You cannot modify a VM that is currently migrating online. You must wait until migration
completes. You cannot modify a VM that has migrated to another VSP (the target): the VM (on the
source VSP) is in the Not Runnable state.
• Virtual Machine vCPU Entitlement to modify the processor entitlement of a selected VM. If
supported by the version of Integrity VM running on the VSP, you can modify the entitlement
cap. An entitlement cap is the maximum amount of computing power allotted to a VM for
each vCPU.
88 Working with VMs or vPars