HP-UX vPars and Integrity VM V6.1.5 Administrator Guide (5900-2295, April 2013)

11 Managing vPars/VMs
To manage a vPar/VM, connect to the vPar/VM using a remote connection and use the operating
system administration procedures appropriate to the guest OS. vPars and Integrity VM provides
utilities for managing vPars and virtual machines from the VSP and from inside the vPar/VM. This
chapter describes how to manage vPars/VMs using Integrity VM commands and utilities, including
the use of Logical Server Management (LSM) to manage VMs. The following topics are included
in this chapter:
• Managing VMs with LSM
• Integrity VM Virtualization Provider
• Monitoring vPars/VMs
• Creating vPar/VM administrators and operators
• Installing VirtualBase
• Using the virtual console
• Using the virtual iLO Remote Console
• vPar/VM configuration files
• Dynamic memory for VMs
• Log files
• Managing the device database
11.1 Managing VMs with LSM
Integrity VM V6.1.5 fully supports HP Matrix OE Logical Server Management (LSM) Version 7.0.
With this version, administrators can manage the full life-cycle of VMs with the following LSM
operations: create, modify, delete, activate, deactivate, power on/off, import, move, and unmanage.
NOTE: The following steps must be run on the VSP before you can use LSM to create virtual
machines and before you can use HP Insight Orchestration to provision VMs.
To create a VM using LSM, you must adhere to the following:
1. Create the appropriate size shared LVM (SLVM) volume group (VG) for the device management
database using LVM Version 2.2. For example:
• Create the volume group using LVM Version 2.2:
# vgcreate -V 2.2 -s 4m -S 100g /dev/slvm_v21 /dev/disk/disk61
NOTE: When using SLVM, Serviceguard should be installed, but a Serviceguard cluster
does not need to be configured.
For information about creating SLVM volume groups, see the SLVM Online Volume
Reconfiguration whitepaper at SLVM Online Volume Reconfiguration.
2. Add SLVM volume groups into the device database using the hpvmdevmgmt command. For
each SLVM volume group you add to the device management database, set the device attribute
VIRTPTYPE to container_volume_SLVM, with the PRESERVE=YES attribute setting. For
example:
# hpvmdevmgmt -a gdev:/dev/slvm_v22:attr:VIRTPTYPE=container_volume_SLVM,PRESERVE=YES
For information about storage requirements for importing logical servers with backing storage
from SLVM volume groups, see Section 11.1.1 (page 170)
11.1 Managing VMs with LSM 169