HP vPars and Integrity Virtual Machines V6.1 Administrator Guide

NOTE: The SLVM volume groups must be in the activated mode before running the
hpvmhostrdev script. For information about deactivated volume groups, see Section 11.1.2
(page 166).
4. Execute the hpvmhostgdev -a command to ensure that all devices are populated in the
gdev database. The hpvmhostgdev command analyzes disklist and lvlist output and
adds unused gdevs to the device database.
NOTE: If you add new devices in the future, run the hpvmhostgdev -a script again. If
you want to select the guest devices instead of adding all of them to the gdev database, create
a list of unused disks and logical volumes with the -l option and pipe them to a file. Use the
specified device-list file to add devices for guest use with the -f option.
# hpvmhostgdev -l > devicelist
# hpvmhostgdev -f devicelist
For information about the hpvmhostgdev script, see the hpvmhostgdev (1M) manpage.
5. Managing VMs does not require them to be in a VM as a Serviceguard Package. However,
if you plan to use clustered VMs, ensure that the VSP is properly configured with Serviceguard
(11.19 or 11.20) and Shared Logical Volume Manager (SLVM).
NOTE: For information about configuring Serviceguard and SLVM, see the Using Serviceguard
manual on the BSC website.
If you already have your VMs clustered in a VM as a Serviceguard Package, but prefer not
to manage them this way, you can use the cmdeployvpkg Serviceguard command to properly
deconfigure (delete) the package. For information about the cmdeployvpkg command, see
the HP Serviceguard Toolkit for Integrity Virtual Servers User Guide at HP Serviceguard Toolkit
for Integrity Virtual Servers.
11.1.1 Storage requirements for managing existing VMs with Logical Server
Management
To use Logical Server Management (LSM) to manage vPars or virtual machines created outside of
LSM, the VM backing storage needs to be the following:
• Whole LUNs — The supported LSM operations are: Import, Online Move, Power On, Power
Off, and Unmanage.
• SLVM-based logical volumes (LVs) — The volume group (VG) type must be
container_volume_SLVM in the vPar/VM device management database.
The supported operations are: Import, Online Move, Power On, Power Off, Activate, and
Deactivate, and Unmanage.
NOTE: For information about vpars and virtual machines created with LSM or HP Insight
Orchestration using SLVM-based LVs, see Section 11.1 (page 165).
11.1.2 Storage for deactivated volume groups not protected by VM storage
management
When an LVM volume group is deactivated, the storage (physical volumes) used by that storage
is designated as unused by HP-UX system administration tools such as System Management
Homepage (SMH). This is also true for Integrity VM storage management. As a result, these physical
volumes are not automatically protected from use by virtual machines as virtual disks.
You can resolve this problem in one of two ways:
166 Managing vPars/VMs