Operating Environment Software Manual

PHSS_41416 1.0 HPVM A.04.20.05 vmTools (Patch for A.04.20.05 HPVM-Guest)
◦ Logical Volume Manager (LVM) software
Install LVM B.11.31.1010 on the VM Host. To locate LVM on the software depot
website, go to http:// software.hp.com and search for the keyword LVM
• Execute the Integrity VM hpvmhostgdev —a command to ensure that all devices are
populated in the gdev database. The hpvmhostgdev command can analyze disklist and
lvlist output and add unused gdevs to the Integrity VM database.
For information about the hpvmhostgdev script, see Appendix A in the HP Integrity Virtual
Machines 4.2.5: Release Notes.
• Configure the Integrity VM Host with Serviceguard (11.19 or 11.20) and Shared Logical
Volume Manager (SLVM). (An imported VM with a whole LUN is not required to be in a
Serviceguard Package.)
See HP Integrity Virtual Machines 4.2: Installation, Configuration, and Administration at
www.hp.com/go/hpux-hpvm-docs for more information.
• Create the appropriate size SLVM volume group (VG) for the device management database
using LVM Version 2.1 or higher. For example:
# vgcreate -V 2.1 -s 4m -S 100g /dev/slvm_v21 /dev/disk/disk61
For information about creating SLVM groups, see HP Integrity Virtual Machines 4.2: Installation,
Configuration, Administration at www.hp.com/go/hpux-hpvm-docs and the SLVM Online
Volume Reconfiguration whitepaper at http://docs.hp.com/en/16178/
reconfig-wp.pdf?jumpid=reg_R1002_USEN.
• Add the SLVM volume group into the device database using the hpvmdevmgmt command.
Set the new attribute to the hpvmdevmgmt command, VIRTPTYPE, with the PRESERVE=YES
attribute setting, to container_volume_SLVM for each of the SLVM groups added to the
device management database. For example:
# hpvmdevmgmt -a gdev:/dev/slvm_v22:attr:VIRTPTYPE=container_volume_SLVM,PRESERVE=YES
NOTE: For a virtual machine created with SLVM Logical Volume, the SLVM volume group
must be part of container_volume_SLVM in order for the virtual machine to be imported
as a logical server.
• Import operations are supported for Integrity VMs that contain:
— Physical (whole) disks on a SAN
— Virtual disks in a Shared Logical Volume Manager (SLVM) volume group
• Storage:
— Online move operations are supported for virtual machines that are configured with
virtual disks backed by whole LUNs (from a previous import operation) or by SLVM
logical volumes.
— To create an Integrity VM virtual machine logical server, specify Accelerated Virtual
I/O (AVIO) Storage with virtual disk-backed storage only.
— Create and add SLVM Volume Groups to the storage pool on the VM Host for the
CreateVirtual Disk operation to run successfully.
All virtual disks will be a logical volume created in a Shared Logical Volume (SLVM)
Volume Group.
— Local storage is not supported for Integrity VM virtual machines.
— Suspend/Resume of Integrity VMs is not supported.
— Logical servers upgraded from Insight Dynamics 6.0 and 6.1 are supported with a
physical FC SAN volume using persistent DSF for the following operations:
Authorizations, requirements, and configuration 57