HP Integrity Virtual Machines 4.2.5: Release Notes

6 Guest Administration
This chapter contains information about managing Integrity VM guests.
6.1 Changes and Issues in this Release
The following sections discuss new guest administration information in the V4.2.5 release.
6.1.1 Integrity VM Fully Supported with ID-VSE Logical Server Management 6.2
Integrity VM now fully supports ID-VSE Logical Server Management (LSM). With this version of
Integrity VM, administrators can now 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 Integrity VM Host before you can use LSM to create
Integrity VM guests and before you can use HP Insight Orchestration to provision VMs.
To create Integrity VM guests using ID-VSE LSM 6.2, you must adhere to the following:
1. Create the appropriate size SLVM volume group (VG) for the device management database
using LVM Version 2.1 or later. For example:
• Create the volume group using LVM Version 2.1:
# vgcreate -V 2.1 -s 4m -S 100g /dev/slvm_v21 /dev/disk/disk61
• Create the volume group using LVM Version 2.2:
# vgcreate -V 2.2 -s 4m -S 70g /dev/slvm_v22 /dev/disk/disk70
For information about creating SLVM volume groups, see the HP Integrity Virtual Machines
4.2: Installation, Configuration, Administration manual at HP Integrity Virtual Machines and
Online VM Migration and 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 6.1.2 (page 62)
3. Run hpvmhostrdev —u to add the underlying disks of the created SLVM volume groups into
the device database as restricted devices.
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.2.22
(page 87).
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.
6.1 Changes and Issues in this Release 61