HP Integrity Virtual Machines 4.3: Release Notes (5900-2265, May 2012)

8 Storage Information
This chapter contains information about storage devices used as backing stores for guest virtual
devices.
8.1 Changes included in V4.3 January 2012 Patch Release
The following section provides information about V4.3 January 2012 patch release.
8.1.1 NPIV Support
January 2012 Patch Release
NPIV allows the creation of multiple virtual Fibre Channel ports (VFCs) over one physical port (PFC)
on a VM Host. Each of these virtual ports should be created with a unique World Wide Name
(virtual WWN) by which to identify it, just like the unique embedded WWN by which a physical
port is identified. You can use the HP-UX GUID Manager to allocate and manage WWNs for use
with NPIV. For information about the GUID Manager, see HP-UX GUID Manager Administrator
Guide at the following website: http://www.hp.com/go/hpux-vpars-docs
The NPIV feature creates such virtual ports over a physical port on the Integrity VM Host and then
allocates them as resources to guests created on the Integrity VM Host. The resource that is added
to the virtual machines is not a disk, tape, DVD, changer or a burner, but a virtual Host Bus Adapter
(vHBA). The guest then discovers targets and devices behind the vHBA using the same mechanism
that is used on the native host to discover devices behind a physical HBA. Just like the case of a
native host, an NPIV guest will automatically discover new targets and devices behind the vHBA.
8.1.1.1 Adding an NPIV Resource
You can specify an NPIV resource using the hpvmcreate when the guest is being created or the
hpvmmodify command after guest creation. Before creating a vHBA, use the fcmsutil command
to check if the physical HBA on the system supports NPIV.
The hpvmstatus command output now includes the vHBA for guests that have it configured. For
example:
# hpvmstatus -P guest1 -d
[Virtual Machine Devices]
[Storage Interface Details]
disk:avio_stor:0,0,0:avio_stor:/dev/rdisk/disk31
disk:avio_stor:0,0,1:lv:/dev/vg_on_host/rlvol3
hba:avio_stor:0,4,0x50060b00006499b9,0x50060b00006499ba:npiv:/dev/fcd1
hba:avio_stor:1,3,0x50060b00006499a8,0x50060b00006499a9:npiv:/dev/fcd0
[Network Interface Details]
network:avio_lan:0,1,0xF2AF8F8647BF:vswitch:vswitch1:portid:1
network:avio_lan:0,5,0x569FC1F96205:vswitch:vswitch1:portid:3
[Misc Interface Details]
serial:com1::tty:console
NOTE: NPIV devices will remain in the database even if the Integrity VM v4.3 January 2012
patch release is removed.
For information about migrating VMs with NPIV devices, see “Migrating VMs with NPIV
Devices” (page 41)
8.1.1.2 Configuration Limits
A guest can have up to 286 LUN — 256 AVIO and 30 VIO. A guest can have a maximum of 30
file backing stores, including both AVIO and VIO.
NOTE: VIO is deprecated in V4.3, and not supported in the next release.
8.1 Changes included in V4.3 January 2012 Patch Release 33