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
Workaround
The interrupt balancing daemon is disabled by default. Do not enable the interrupt balancing
daemon.
4.4.7 Online addition of DMP device as backing store is not supported
Addition of DMP device on running guest fails with the following error:
# hpvmmodify -p1 -a disk:avio_stor::disk:/dev/vx/rdmp/c513t16d5
Error: Online Addition of DMP device /dev/vx/rdmp/c513t16d5 is not supported.
hpvmmodify: Unable to modify the vPar or VM.
When you attempt a DMP device addition online, the new device addition does not get saved to
the guest configuration to be applied when the guest is next restarted. You have to repeat the
device addition after the vPar or VM guest is shut down.
4.5 VM <—> vPar conversion
4.5.1 Converting VMs to vPars causes LAN IDs to shift
The I/O hardware paths on VMs do not have a cell number in the path. For vPars, I/O resources
are shown under a cell, and because of that, I/O hardware paths have an additional "0/" prefix.
When a VM is converted to a vPar, the vNIC hardware path will be different, so ioscan enumerates
it with a different PPA (lan index).
Workaround
Boot the vPar to single user mode, fix the /etc/rc.config.d/netconf file with the new PPA
number, and then switch to run level 3.
To preserve the LAN instance number, Matrix OE Portable Image product must be installed and
enabled on the guest OS before making the transformation.
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
You can use the -F to override resource checking during a VM migrate operation. However, if
you use this option on a suspended VM, and you have also used NPIV on the VM and a target
VSP that cannot support that NPIV port, the VM migrate operation fails, even with the -F option.
This causes the VM to be nonrunnable on both the source VSP and target VSP.
To re-enable the VM on the source VSP, remove the suspend state of the VM on the source VSP
with the following commands:
hpvmmodify -P vmname -x suspend_file=delete –F
hpvmmodify -P vmname -x register_status=enabled
4.6.2 Copy of a vPar or VM might be left in runnable state if migration fails
If a migration fails, a vPar or VM might be left in a runnable state (but not running) on the target
VSP. If this happens, further attempts at migration fails with a message that the vPar or VM exists
and is runnable on the target VSP.
Workaround
Either remove the vPar or VM with the hpvmremove command, or set the vPar or VM not runnable
using the hpvmmodify -x runnable_status=disabled command.
24 Known problems, limitations, and workarounds