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
3 New functionality and changes from earlier versions
HP-UX vPars and Integrity VM V6.3 introduces several new features and enhancements. Some
changes have been made to operational details from earlier versions. This chapter gives an overview
of these.
3.1 New features and enhancements
3.1.1 Enhanced capability for emulated platform NVRAM (Non Volatile RAM)
The hpvmnvram(1M) command has been enhanced to add network boot path to EFI boot menu
of vPar and Integrity VM guests.
3.1.2 Increased resources for Integrity VM guests
You can create Integrity VM guests with as many as 32 virtual processors (vCPUs) and up to 256
GB RAM.
3.1.3 Dynamic addition of I/O devices
All I/O adapter types supported by HP-UX vPars and Integrity VMs can be added to running
instances of both vPar and Integrity VMs, within the limits of available physical resources and I/O
slots on the vPars or Integrity VMs. This feature is available on all platforms supported by HP-UX
vPars and Integrity VM V6.3.
Dependencies
The guest kit for vPars and Integrity VM guests must be upgraded to HP-UX vPars and Integrity VM
V6.3.
3.1.4 PCI OLR support on Superdome 2 VSPs
Until now, PCI OLR operations on Superdome 2 systems have had several limitations if HP-UX vPars
and Integrity VM was active. This release adds full support for PCI OLR operations on Superdome
2 systems. HP-UX vPars and Integrity VM product seamlessly works with olrad(1M) functionality
on the VSP to enable suspend and replace operations when active guests are using IO devices
backed by the VSP device being replaced.
Dependencies
The guest kit for all vPar and Integrity VM guests on Superdome 2 VSPs must be upgraded to HP-UX
vPars and Integrity VM V6.3.
3.1.5 AVIO Networking improvements
AVIO LAN interfaces in Integrity VM guests have been enhanced to use multiple queues for incoming
(receive side) network traffic. This is expected to improve network throughput for incoming traffic.
AVIO LAN drivers have been updated to support TCP Timestamp option during LRO.
Nettl tracing has been enhanced to capture network traffic between guests.
3.1.6 AVIO Storage improvements
• NPIV support has been added for Emulex CNA cards.
3.1 New features and enhancements 15