HP Integrity Virtual Server Manager 6.3 User Guide

8. Next Steps for vPars
After creating the new vPar, Integrity Virtual Server Manager presents you with the next steps
you can take to manage and use the new vPar. The steps presented depend on the environment
in which you created the vPar. For example, when vPar scheduling on a VSP is managed by
Global Workload Manager (gWLM), the Next Steps page advises you to associate the vPar
with a gWLM policy and add the vPar to a Shared Resource Domain (SRD). You cannot start
the vPar until you complete that action.
If the new vPar includes AVIO devices (AVIO support is provided on HP Integrity vPar Version
3.5 or later), you are advised to make sure the appropriate OS that supports AVIO is installed
on the VSP and the vPar. If the intended OS on the vPar does not support AVIO, you are
warned of this. In addition, HP strongly recommends that AVIO components (such as drivers
and libraries) on the vPar and VSP be updated to the latest release of the OS. If the vPar OS
is Windows or Linux, install additional AVIO-compatible drivers on the vPar; the Windows
and Linux AVIO drivers include instructions for installing the drivers on vPars. 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 vPar, accessing the vPar
console, adding additional software (provider components) needed to support management
of the vPar, getting information about the vPar, and tuning the performance of the vPar.
NOTE: Any devices added using the Create Virtual Partition wizard are not functional on
the vPar until the new vPar is started. Certain devices are not seen in a Integrity Virtual Server
Manager Storage tab until the vPar is started.
You can configure the vPar's Extensible Firmware Interface (EFI) to boot the guest OS
automatically when the vPar is started (powered on). Configure EFI when the vPar has been
started and before booting the OS. You can interact with EFI through the virtual Management
Processor (vMP) for the vPar. The vMP provides access to the console for the vPar. 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 Partition
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 vPar 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 Partition wizard. When you are
ready to add the vPar to the SRD, select the vPar 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 vPar 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 vPar. However, it appears when the identification process completes
(usually within a minute or two).
Modifying vPars
To modify a vPar, select one of the following items from the Virtual Server Manager Modify menu.
For more information about any item, see the corresponding Virtual Server Manager help topic.
NOTE: You can modify only one vPar at a time.
116 Working with VMs or vPars