HP vPars and Integrity Virtual Machines V6.1 Administrator Guide
• If the volume group is to remain deactivated, the VSP administrator can manually add the
physical volume as a restricted device with the hpvmdevmgmt command.
• Or, after activating the volume group, execute the hpvmhostrdev command, so that the VSP
storage management database is updated accordingly.
An HP-UX system administrator can deactivate a volume group using the vgchange command. It
can also be deactivated, if it is a shared LVM (SLVM) volume group, whenever the associated
Serviceguard cluster is reconfigured, or the VSP system is rebooted. Take care to check that all
SLVM volume groups are activated after a VSP reboot or Serviceguard cluster reconfiguration.
11.1.3 Managing existing VM with LSM
You can import existing VMs 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 VMs.
Integrity VSPs that are managing only VMs with whole LUNs do not need to be configured with
Serviceguard and SLVM. If you plan to create new VMs on that VSP, follow the steps in Section 11.1
(page 165).
11.1.4 Managing VMs using gWLM
VMs configured with processing power specified in cycles instead of percentage are incompatible
with gWLM A.02.50 and earlier versions.
If gWLM/Matrix OE produces an error message similar to the following, a VM is configured with
the processing power specified in cycles:
A VM encountered with no size
This is apparent when using gWLM A.02.50 with Integrity VM A.03.00. You can correct the
problem by modifying the guest and specifying processing power in percentage rather than CPU
cycles. For example, to modify the guest named compass1 to use 10% of the CPU processing
power, enter the following command
# hpvmmodify -P compass1 -e 10
You must boot the guest to initiate this setting for gWLM.
Alternatively, upgrade gWLM to A.03.00 for use with Integrity VM A.03.00.
11.2 VM Virtualization Provider
The Integrity VM Virtualization Provider, used with the logical server feature in the Matrix OE,
enables virtual to virtual migration with logical server management (LSM). A logical server is a set
of configuration information that you create, activate, and move across physical and virtual
machines. It contains the logical server definition and description, including the server computer
resources (for example, the number of CPU cores and amount of memory), and the server
connections to storage fabric and networks.
For information about LSM and VMM, see documentation on the Business Support Center website.
11.2.1 Adding and removing devices
vPars and Integrity VM adds devices not in use by the VSP automatically. You can add devices
that are not automatically added by using the hpvmdevmgmt gdev PRESERVE attribute. The
following device types require manual addition:
• File backed disks
• File backed DVDs
• VxVM volumes
The following examples show how to add various device types to the storage pool:
11.2 VM Virtualization Provider 167