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
2 Installing or upgrading to HP-UX vPars and Integrity VM
V6.3
2.1 Virtualization Services Platform
The physical server on which HP-UX vPars and Integrity VM is installed is referred to as a VSP
(Virtualization Services Platform). vPars and Integrity VMs are subsequently created on these
installations. The VSP is an HP-UX based system intended to provide virtualization services for vPars
and Integrity VM guest instances that are hosted on it. Consequently, the VSP must not be used as
a general purpose HP-UX server; you must ensure that application workloads are not run on a VSP.
2.2 Hardware requirements for the VSP
The following HP Integrity servers may be used as VSPs for HP-UX vPars and Integrity VM V6.3.
• HP Integrity servers
• HP Integrity i2 servers
rx2800◦
◦ Bladesystem
◦ Superdome 2
• HP Integrity i4 servers
rx2800◦
◦ Bladesystem
◦ Superdome 2
VSPs require the following physical resources:
• Processors
Adequate number of processors must be available on the VSP for all vPars and Integrity VMs
that are hosted on it.
In addition to providing computing resources for vPars and Integrity VMs, the VSP requires
some processor resources for system operations and processing shared I/O loads from the
guests.
When vPars are used, at least one processor must be dedicated to the VSP; primarily for
interrupt processing of shared I/O resources. Additional processors may have to be dedicated
to the VSP if the shared I/O interrupt load is sufficiently high.
• Memory
The host HP-UX operating system installed on a VSP, consumes some system memory when
the VSP is booted with it. The amount of memory that is used is dependent on VSP system
configuration and activated device drivers.
HP-UX vPars and Integrity VM V6.3 reserves additional memory for system virtualization
operations. This is set to a default value of 8% of available system memory at the time HP-UX
vPars and Integrity VM V6.3 is started.
Memory for all vPars and Integrity VMs on that VSP is allocated from the remaining VSP system
memory.
2.1 Virtualization Services Platform 11