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
4.3.5 DIO-capable functions might become inconsistent with information in vPar or
VM device database
Under certain conditions, the ownership of DIO-capable functions might become inconsistent with
the information in the vPar or VM device database such that hpvmhwmgmt -p dio -l indicates
that a DIO-capable function is owned by host. However, the hpvmdevmgmt -l gdev command
indicates that it is assigned to the vPar or VM resource pool as a gdev.
In such a case, if you want to use the DIO-capable function again as an Integrity VM resource,
use the following command to resynchronize the krs(5) and ioconfig(4) databases with the
Integrity VM device database:
# hpvmdiorecover -r
For more information, see the hpvmdiorecover(1) manpage.
4.3.6 When DIO device is assigned or removed from the DIO pool, error messages
appear multiple times
On systems with large number of I/O slots, when a DIO device is assigned or removed from the
DIO pool using the hpvmhwmgmt(1M) command, following messages may appear multiple times
on the command output even though the operation is successful. These messages can be ignored
and you can continue with the usage of the DIO devices.
hpvmhwmgmt -p dio -a 41/0/1/0/0/0/0
Error : Driver already attached
Target slot : 9-0-2-1-0-5
Error : On line ADD failed !! Attention LED may be left in blinking state
Target slot : 9-0-2-1-0-5
4.4 Storage
4.4.1 Presenting a Logical Volume created on iSCSI devices as AVIO backing store
to a guest not supported
Presenting a Logical Volume that is created on an iSCSI device as an AVIO backing store to a
guest is not supported.
4.4.2 Size change operations on a SLVM volume based backing store do not get
reflected in the vPar or VM
When a SLVM LV is configured as a backing store for a vPar or VM guest, any changes made to
the LV size will be automatically propagated to the vPar or VM guest only if it is running on the
cluster node configured as the “server” for the volume group to which the LV belongs. If, at the
time of the size change operation, the vPar or VM guest is running on the cluster node configured
as the “client”, then, the vPar or VM must be restarted before the new size gets reflected.
4.4.3 The hpvmdevinfo command may not list the correct host to guest device
mapping for legacy AVIO backing stores
After a legacy AVIO backing store (that is, a non NPIV device) is added online to an existing
virtual HBA, the hpvmdevinfo command, when executed on the VSP, may fail to report the vPar
or VM guest device that corresponds to the newly added backing store.
In such cases, the hpvmdevinfo command must be explicitly executed on the vPar or VM guest
in question for the right device mapping information to be available on the VSP.
4.4.4 Probe of NPIV HBAs for Fibre Channel targets may timeout
During online migration, the target VM Host probes any NPIV HBAs for FC (Fibre Channel) targets.
If this probe takes close to 30 seconds (or longer), online migration times out and aborts. The
hpvmmigrate command prints an error:
22 Known problems, limitations, and workarounds