HP Matrix Operating Environment 7.3 and 7.3 Update 1 Logical Server Management User Guide

# 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 or NPIV storage.
Create and add SLVM Volume Groups to the storage pool on the VM Host for the Create
Virtual 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.
For information on VM guest storage options, see “VM guest storage options (page 26).
Network:
Create an Integrity VM virtual machine logical server using the following:
Accelerated Virtual I/O (AVIO) network devices. The Integrity VM Host administrator
must create all required virtual switches that will be used by Integrity VM guests
before managing the Integrity VM Host.
Direct I/O network devices (DIO). The Integrity VM Host administrator must ensure
that the required Direct I/O network devices are added to the Direct I/O network
pool for guests, and labelled with a network name. For example:
# hpvmhwmgmt -p dio -a 0/0/0/5/0/0/1
# hpvmhwmgmt -p dio -m 0/0/0/5/0/0/1 -L public_network
The vSwitch name can be a maximum of 8 characters. (This restriction is important if you
intend to manage Integrity VM logical servers and cross-technology logical servers [ESX
virtual machine and Virtual Connect logical servers], because, for cross-technology logical
servers, at least one network in the VC Domain Group must be named identically to a
vSwitch on the ESX Host.)
Authorizations, requirements, and configuration 25