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 Known problems, limitations, and workarounds
This chapter provides information about problems, limitations, and workarounds known at the time
HP-UX vPars and Integrity VM V6.3 was released.
4.1 CPU/vCPU
4.1.1 Increasing CPU entitlement on running Integrity VM guests may cause problems
When the hpvmmodify(1M) is invoked on a running VM to increase its minimum entitlement (-e
option), it may display a warning.
# hpvmmodify -P vm_name -e minimum entitlement
vPar/VM vm_name configuration problems: Warning 1: vPar/VM CPUs (n) greater than available limit (0). These
problems
may prevent the vPar or VM vm_name from
starting. hpvmmodify: The modification process is continuing. hpvmmodify:
The modification process is continuing.
As a consequence, a reserved VM might not be able to start, because not enough CPU is available.
Another consequence is that the VSP resources might become overcommitted:
# hpvmstatus -s
[HPVM Server System Resources]
*** VSP resources are over-committed ***
vPar/VM types supported by this VSP = vPar, Shared
Processor speed = 1330 Mhz
Total physical memory = 32659 Mbytes
.......
......
Workaround
Reduce the minimum entitlement of the VM whose entitlement increase created the condition.
4.1.2 CPU deconfigured by firmware can be assigned to vPar or VM
If a CPU experiences local MCAs many times, the system firmware de-configures the CPU without
HP-UX knowledge. This might cause the VSP to give the CPU to one of the vPars or VMs (which
originally owned the CPU). The result of this is a vPar or VM hang in the bootloader.
The likelihood of this situation occurring is low, but if it does, stop and restart the vPar or VM to
cause different CPUs to be assigned to the vPar or VM.
4.1.3 On VM guests running HP-UX, compressed system dump takes a long time
HP-UX provides a tunable to enable compressed system dumps; this feature is intended to reduce
dump time.
Data compression is a processor intensive operation.
With VM guests, it has been observed that scheduling delays of the virtual CPUs may contribute
to excessive time consumption for compressing dump data; leading to increased system dump
time. HP recommends that system dump compression be turned off for VM guests running HP-UX.
This is achieved by setting the tunable “dump_compress_on” to zero using kctune(1M).
4.2 Memory
4.2.1 loratune(1M) must not be used on VSPs when HP-UX vPars and Integrity VM
is active
Running loratune(1M) on VSPs where HP-UX vPars and Integrity VM is active may result in
undesirable behaviour; including failure to start vPars or VMs.
4.1 CPU/vCPU 19