HP vPars and Integrity Virtual Machines V6.1 Release Notes

disk [2,0,18] /dev/rdisk/disk6201 /dev/rdisk/disk326
disk [2,0,19] /dev/rdisk/disk6413 /dev/rdisk/disk333
# ioscan –kfNd gvsd
Class I H/W Path Driver S/W State H/W Type Description
=================================================================
ext_bus 12 0/2/0/0 gvsd CLAIMED INTERFACE HPVM AVIO Stor Adapter
3.1.18 Simultaneous interrupt migration operations in both VSP and VM might cause
VSP system crash
In some scenarios, performing simultaneous interrupt migration operations in both the VSP and the
VM might result in a VSP system crash.
To work around this, HP recommends that you do not perform interrupt migration operations
simultaneously on both the VSP and the VM. There is no harm in performing interrupt migration
operations individually on the VSP and the VM.
3.1.19 Copy of a vPar/VM might be left in runnable state if migration fails
If a migration fails, a vPar/VM might be left in a runnable state (but not running) on the target VSP.
If this happens, further attempts at migration will fail with a message that the vPar/VM exists and
is runnable on the target VSP.
To work around this, either remove the vPar/VM with the hpvmremove command, or set the
vPar/VM not runnable using the hpvmmodify -x runnable_status=disabled command.
3.1.20 Changes to the Default EFI AVIO Storage Driver Enumeration Policy
Prior to HP Integrity Virtual Machines V4.3, the default policy of the EFI AVIO storage driver was
to enumerate and configure all AVIO storage devices defined in a guest's configuration. This would
make all AVIO storage devices visible to EFI. With V4.3 (and later), the default enumeration policy
is to enumerate and configure only those AVIO storage devices that are present as EFI boot options.
The enumeration policy is also differentiated by storage type: SCSI (non-NPIV) LUNs, and FC (NPIV)
LUNs.
The change to the enumeration policy has been made to reduce the time to boot to EFI in the cases
of guest configurations with large amounts of AVIO storage devices configured. This policy change
affects only the devices enumerated or configured at the EFI level, not at the guest operating system
level.
As a result of the default enumeration policy change, some attempted operations within EFI (such
as boot management, or new guest installations) may fail because of non-present AVIO storage
devices. To make the AVIO storage devices visible to EFI, the enumeration policy can be changed
to enumerate or configure all AVIO storage devices.
Use the drvcfg EFI utility to change the enumeration policy to do the following:
• Enumerate boot LUNs only. (Default policy)
• Enumerate all LUNs.
You can set the enumeration policy separately for SCSI (non-NPIV) LUNs and FC (NPIV) LUNs;
however, setting the policy to enumerate all LUNs (especially FC LUNs) might result in long guest
boot times in configurations with a large number of LUNs. You might notice a long delay before
the EFI Boot Manager menu screen is presented and when entering the EFI Shell, or before the
device mappings are displayed and the EFI shell prompt is presented.
The following example shows the policy configuration dialog. In this example, the policy is being
unchanged from the default policy.
# drvcfg -s
HP AVIO Stor Driver Configuration
==================================
Warning: enumerating all SCSI or FC LUNs increases initialization times.
18 Issues in this release