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
# hpvmdevinfo -P guest1
Virtual Machine Device Bus,Device, Backing Store Host Device Virtual Machine
Name Type Target Type Name Device Name
===================== ====== =================== ============= ============= ==============
guest1 lan [0,0,0xA61236178451] hwpath 7/0/0/0/0/0/0 Not available
guest1 lan [0,1,0x2605EDC34156] hwpath 7/0/0/2/0/0/1 Not available
guest1 lan [0,2,0x464A7005B7AC] hwpath Not available
Workaround
Before migration, configure the vPar or VM to have unique labels for each DIO device.
For example,
# hpvmhwmgmt -p dio -l
H/W Path Class Owner Assignment Level Label
Description
============= ====== ====== =================== =========== =============
6/0/0/2/0/0/0 lan hpvm HP PCIe 2-p 10GbE Built-device
6/0/0/2/0/0/1 lan hpvm HP PCIe 2-p 10GbE Built-device TEST_045_048B
7/0/0/0/0/0/0 lan hpvm HP PCIe 2-p 10GbE Built-device TEST_045_048C
7/0/0/0/0/0/1 lan hpvm HP PCIe 2-p 10GbeE Built-device
7/0/0/2/0/0/0 lan hpvm HP PCIe 2-p 10GbeE Built-device
7/0/0/2/0/0/1 lan hpvm HP PCIe 2-p 10GbeE Built-device TEST_045_048A
4.7 User interface—CLI
4.7.1 VSPs with 128 or more CPUs must set the tunable msgtql to at least 4906
When this tunable is at default value of 1024, some HP-UX vPars and Integrity VM commands
may exhibit abnormally long delays.
4.7.2 Stopping an NPIV guest with the hpvmstop command may fail
Stopping a vPar or a VM guest configured with NPIV vHBAs created on an Emulex FC port or
FCoC port may fail with the following error:
hpvmstop: WARNING (guest1): Polite stop didn't work - trying harder: guest1
hpvmstop: WARNING (guest1): Impolite stop didn't work - trying SIGKILL: guest1
hpvmstop: ERROR (guest1): Unable to stop vPar or VM 'guest1', even with SIGKILL
hpvmstop: Unable to continue.
This is due to the time taken to delete the NPIV instances associated with the vPar or VM being
shutdown, which in turn is a factor of the number of targets that are mapped to it. Each target
takes approximately two seconds during the NPIV instance deletion. The greater the number of
targets associated with the NPIV vHBAs, the higher the overall time taken to shutdown the vPar or
VM guest.
Workaround
HP recommends that the time allocated for a graceful guest shutdown (graceful_stop_timeout) be
increased suitably using the hpvmmodify command, and then the hpvmstop command be used
with the -g option to allow for a graceful guest shutdown.
NOTE: vPars and Integrity VM recommends that a vPar or VM guest always be shutdown using
the normal graceful shutdown options from within the guest OS.
4.8 Known system crashes, panics, hangs and MCAs
4.8.1 vPar or VM guest may panic in SCSI services during installation of HP-UX
11.31.1203
The vPar or VM guest may panic in SCSI services during installation of HP-UX 11.31.1203 with
the stack trace like the following:
kmem_arena_varalloc + 0x190
escsi_kr_open + 0x7b0
escsi_reg_lun + 0x1230
26 Known problems, limitations, and workarounds