HP Matrix Operating Environment Software - Manual (Page 24)

◦ Suspend/Resume of Integrity VMs is not supported.
◦ For information on VM guest storage options, see “VM guest storage options ” (page 24) .
•
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.)
VM guest storage options
Table 4 VM guest storage options
Integrity VM
1
Microsoft
Hyper-V VM VMware VM
NPIV
SLVM with
Serviceguard NT file system
(NTFS) Network file
system (NFS)
Raw disk
mapping
(RDM) VM file
system
(VMFS)
Storage type
✓ ✓ ✓ ✓ ✓ Fibre channel
✓ 4 ✓ 5 ✓ 3, 4
iSCSI
2
✓ 4 ✓ 4
DAS
✓ 4 ✓ 4
SAS
✓ 4 Network attached
storage (NAS)
1
Integrity VM virtual machine guests must have an HP-UX operating system type. Windows and Linux guests are not
supported.
2 To use iSCSI, you must provide connectivity to a compatible iSCSI SAN. As with Fibre Channel storage, end-to-end
support for an iSCSI storage device is generally certified by the storage vendor.
3
Supported by VMware ESX 4.0 and later.
4
Not supported by Matrix recovery management.
5
Not supported by Matrix OE, including Matrix infrastructure orchestration.
Requirements for Virtual Connect logical servers
Firmware for ProLiant blades only in a Virtual Connect Domain Group
•
Virtual Connect Manager 3.15 or higher
•
HP BladeSystem Onboard Administrator 3.10 or higher. See “Configuring Systems Insight
Manager with Onboard Administrator credentials” (page 25) for important information.
HP BladeSystem Onboard Administrator 3.15 or higher is required for FCoE (Fibre Channel
over Ethernet) and BL680 G7 blade support.
24 Managing logical servers