HP vPars and Integrity Virtual Machines V6.1 Release Notes

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.
3.1.12 SMH is unresponsive when running stress tests on a VSP
Applications like SMH (which needs significant CPU bandwidth) are not likely to be very responsive
when the VSP cores are already under heavy load servicing vPar/VM I/O requests. HP recommends
that you increase the number of VSP CPU-cores under such circumstances.
3.1.13 WARNING: VCPU0 not scheduled message can be ignored
In vPars V6.1, messages similar to the following are occasionally seen during the initial boot of a
vPar:
WARNING: VCPU0 not scheduled for NNNNN ms" messages in hpvm_mon_log
They can occur during the early portion of booting the vPar before HP-UX is launched into the vPar,
when either the EFI layer or the boot loader is running.
You can safely ignore these messages.
3.1.14 VSP requires dedicated CPU to support a vPars
If you plan to use vPars, you need to setup the VSP with a dedicated CPU to support them. Virtual
machines do not require a dedicated CPU.
3.1.15 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 will fail, even with the -F option.
This will cause 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
3.1.16 Integrity VM and vPar CLI commands experience poor performance when
there are numerous devices on the VSP
Commands like vparmodify, hpvmmodify, hpvmcreate and hpvmclone, (commands used
to modify the vPar or VM configuration), experience slow performance when there are numerous
devices available on the VSP, or configured in the vPar and/or VM configurations. When you
have a large number of devices, it is more than likely that the majority of those devices are storage
devices. If storage devices are being exposed to the VSP from a SAN and then individually mapped
to vPar/VM configurations, alternatively, you can map SAN-based LUNs directly to the VMs or
vPars using NPIV. Replacing individually mapped SAN-based LUNs with one or more virtual HBAs
using NPIV ports, reduces the number of devices that need to be managed, and thus improves the
CLI performance. For information about using NPIV with vPars and Integrity VM, see the HP-UX
vPars and Integrity VM V6.1 Administrator Guide on the BSC website: http://www.hp.com/go/
virtualization-manuals.
16 Issues in this release