HP Integrity Virtual Machines 4.2.5: Release Notes

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 Appendix A (page 105).
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 Integrity VM section of the HP Integrity Virtual Machines 4.2: Installation,
Configuration, and Administration manual.
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
6.1.2 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 6.1.1 (page 61).
6.1.3 Managing Existing Integrity VM Guests With LSM
You can import existing Integrity VM guests that are configured with whole LUNs, and perform the
following LSM operations on these VMs: Online Move, Power On, Power Off, and Unmanage.
All other operations are not supported with these imported guests.
Integrity VM Hosts that are managing only VMs with whole LUNs do not need to be configured
with Serviceguard and SLVM. If you plan to create new guests on that VM Host, follow the steps
in Section 6.1.1 (page 61).
6.2 Known Issues and Information
The following sections describe known issues and information from previous releases that still apply
to V4.2.5.
62 Guest Administration