HP-UX vPars and Integrity VM V6.3 Release Notes (762790-001, July 2014) (Edition: 1.6)
Table Of Contents
- HP-UX vPars and Integrity VM V6.3 Release Notes
- Contents
- HP secure development lifecycle
- 1 Introduction
- 2 Installing or upgrading to HP-UX vPars and Integrity VM V6.3
- 3 New functionality and changes from earlier versions
- 3.1 New features and enhancements
- 3.1.1 Enhanced capability for emulated platform NVRAM (Non Volatile RAM)
- 3.1.2 Increased resources for Integrity VM guests
- 3.1.3 Dynamic addition of I/O devices
- 3.1.4 PCI OLR support on Superdome 2 VSPs
- 3.1.5 AVIO Networking improvements
- 3.1.6 AVIO Storage improvements
- 3.1.7 Greater flexibility for online VM migration
- 3.1.8 Improvements to Virtual Server Management
- 3.1.9 Improvements to VSP resource management
- 3.2 Changes from previous versions
- 3.1 New features and enhancements
- 4 Known problems, limitations, and workarounds
- 4.1 CPU/vCPU
- 4.2 Memory
- 4.3 Networking
- 4.3.1 Cannot remove a VLAN-based vNIC if the VLAN has been removed
- 4.3.2 hpvmhwmgmt might add ports in link aggregates into the DIO pool
- 4.3.3 DIO limitations
- 4.3.4 Known issues or limitations with DIO support for 10GigEthr-02 (iexgbe)
- 4.3.5 DIO-capable functions might become inconsistent with information in vPar or VM device database
- 4.3.6 When DIO device is assigned or removed from the DIO pool, error messages appear multiple times
- 4.4 Storage
- 4.4.1 Presenting a Logical Volume created on iSCSI devices as AVIO backing store to a guest not supported
- 4.4.2 Size change operations on a SLVM volume based backing store do not get reflected in the vPar or VM
- 4.4.3 The hpvmdevinfo command may not list the correct host to guest device mapping for legacy AVIO backing stores
- 4.4.4 Probe of NPIV HBAs for Fibre Channel targets may timeout
- 4.4.5 NPIV LUNs not shown by default invocation of ioscan
- 4.4.6 The interrupt balancing daemon must not be enabled in vPars and Integrity VM guests
- 4.4.7 Online addition of DMP device as backing store is not supported
- 4.5 VM <—> vPar conversion
- 4.6 Migration, Suspend, and Resume operations on Integrity VM guests
- 4.6.1 Use of -F with hpvmmigrate on a suspended VM can cause VM to be not runnable on both source and target
- 4.6.2 Copy of a vPar or VM might be left in runnable state if migration fails
- 4.6.3 Interrupt migration of vNICs during Online guest migration can result in network disconnectivity
- 4.6.4 Physical NIC link state change during hpvmsuspend to hpvmresume may result vNIC in down state
- 4.6.5 Offline migration of a guest- with multiple DIO resources might succeed with errors if the DIO devices are added under the same label
- 4.7 User interface—CLI
- 4.8 Known system crashes, panics, hangs and MCAs
- 5 HP-UX vPars and Integrity VM support policy
- 5.1 Support duration
- 5.2 VSP firmware requirements
- 5.3 VSP server and OS support
- 5.4 HP-UX version support for vPar and Integrity VM guests
- 5.5 Storage device support for vPar and Integrity VM guests
- 5.6 Network device support for vPar and Integrity VM guests
- 5.7 Support for migration of vPars and Integrity VMs
- 6 Support and other resources
- 7 Documentation feedback
5.5.2.2 Supported NPIV configurations
Supported LimitLimit Description
16NPIV HBAs per vPar or VM
32 (Qlogic HBAs) and 8 (Emulex HBAs)Number of NPIV HBAs per physical HBA
16Number of paths supported per NPIV device
2048Number of LUNs per HBA
2048Number of NPIV devices per vPar or VM
NOTE: In configurations where multiple NPIV HBAs created from a single physical HBA are used
by different vPars or VMs, all I/O from these vPars or VMs share a single physical HBA, which
could lead to performance bottlenecks in high I/O scenarios.
For balanced performance, HP recommends that you spread NPIV HBAs for vPars or VMs across
multiple physical adapters.
nl
nl
5.5.3 Multipathing software support
Multipathing software is supported on the VSP. Unless specified otherwise, multipathing is supported
for use with AVIO (virtual adapter type specified as avio_stor). The required version for these
products is determined by the combination of software vendor and release of HP-UX installed on
the VSP.
vPars and Integrity VM Version 6.3Backing Store
• HP-UX 11i v3 built-in multipathing
• Symantec Dynamic multipathing (DMP)
Whole Disk (or LUN)
1
• HP-UX 11i v3 built-in multipathing
• PVLinks
• EMC PowerPath
1
with legacy whole disk DSF in a Volume Group
LVM Logical Volumes
• HP-UX 11i v3 built-in multipathing
• EMC PowerPath
1
with legacy whole disk DSF in a Disk Group
• Symantec DMP
VxVM Logical Volumes
• HP-UX 11i v3 built-in multipathing
• PVLinks
• EMC PowerPath
1
with legacy disk DSF in a Volume Group
• Symantec DMP
VxFS Files
1
EMC PowerPath cannot be used for multipathing with whole disk backing stores configured using Agile DSFs.
For NPIV devices, multipathing is supported in the guest, and not on the VSP. All aspects of
multipathing that apply to FC devices are also applicable to NPIV devices.
5.5.4 Firmware requirements for EVA series storage arrays
The AVIO Storage Driver supports Active-Active firmware types on EVA series (3000/5000 and
4000/6000/8000). Ensure that the following firmware revision levels are met before configuring
AVIO backing stores on these arrays:
5.5 Storage device support for vPar and Integrity VM guests 35