Operating Environment Software User Manual

◦ 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 24).
• Network:
Create an Integrity VM virtual machine logical server using 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.
◦
◦ 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 Virtual Connect 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 VMVMware VM
SLVM with
ServiceGuard
2
NT file system
(NTFS)
Network file
system (NFS)
Raw disk
mapping (RDM)
VM file system
(VMFS)Storage type
✓✓✓
3
✓Fibre channel
✓
6
✓
7
✓
5, 6
iSCSI
4
✓
6
✓
6
DAS
✓
6
✓
6
SAS
✓
6
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
SLVM with Serviceguard is currently the only storage solution supported by Matrix infrastructure orchestration for Integrity
VM.
3
Not supported by Matrix infrastructure orchestration.
4
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.
5
Supported by VMware ESX 4.0 and later.
6
Not supported by Matrix recovery management.
7
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.
• HP Integrated Lights-Out (iLO2) for ProLiant 2.00 or higher
• Latest available firmware update for your server blade BIOS
24 Managing logical servers