HP Integrity Virtual Machines 4.3: Installation, Configuration, Administration

NOTE: The SLVM volume groups must be in the activated mode before running the
hpvmhostrdev script. For information about deactivated volume groups, see Section 8.1.2
(page 144).
4. Execute the Integrity VM 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 Integrity VM 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 Integrity VM Host 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 HP
Serviceguard with Integrity VM section.
If you already have your VMs clustered in a VM as a Serviceguard Package, but prefer not
to manage them this way, run the following Serviceguard command to properly deconfigure
(delete) the package:
# hpvmsg_package -U -P package_guest_name
8.1.1 Storage Requirements for Managing Existing Integrity VM Guests with Logical
Server Management
To use Logical Server Management (LSM) to manage virtual machines created outside of LSM,
the guest 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 Integrity VM device management database.
The supported operations are: Import, Online Move, Power On, Power Off, Activate, and
Deactivate, and Unmanage.
NOTE: For information about virtual machines created with LSM or HP Insight Orchestration
using SLVM-based LVs, see Section 8.1 (page 143).
8.1.2 Storage for Deactivated Volume Groups not Protected by Integrity 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:
144 Managing Guests