HP Integrity Virtual Machines 4.2.5: Release Notes

Virtual Software Environment software versions earlier than V4.0 must upgrade to HP Insight
Dynamics — VSE V4.1 (which contains VMMgr V4.0).
VMMgr V4.0 is designed to run on HP-UX 11i v3 with Integrity VM V4.2.5 or earlier. It cannot
use or display any new features in Integrity VM V4.2,5, but does support new features in HP-UX
11i v3, including the new agile addressing hardware paths and device files for storage devices.
This means the following:
• The VMMgr product V4.0 allows the display and setting of the maximum and minimum setting
of vCPUS and entitlement caps and the display of the graceful stop timeout. VMMgr V4.0
also uses the currently set entitlement caps to validate input on the Modify > Virtual Machine
Entitlement dialog.
• V4.0 does not display any information about MSE group membership for the VM Host, nor
support the initiation of either an offline or online guest migration from one VM host to another.
If a virtual machine is running on one member of an MSE group, it will be displayed as stopped
on a different member of the MSE group without indicating that the virtual machine is not
currently runnable on that host. It would permit a user to attempt to start the virtual machine.
However, in this case, the underlying Integrity VM V4.2.5 hpvmstart command that VMMgr
executes would issue an error message indicating that the virtual machine is not runnable on
the current VM Host.
Also, if a virtual machine that is defined on 2 different VM Hosts in an MSE group has the
same Integrity VM UUID on both hosts, HP Insight Dynamics — VSE V4.1 and V6.0 might not
display the virtual machine as contained in the VM Host where it is currently running in the
Visualization Manager component. It might appear in Visualization Manager as if the virtual
machine is running on one of the other VM Hosts where it is defined.
• Beginning with VMMgr V4.0, you can display persistent device files (and their associated
LUN hardware paths) as backing device choices when adding a storage device.
The VMMgr product V4.0 correctly displays devices by either legacy and agile specifications
on the storage tab, depending on which was used when the virtual storage device was added
to the virtual machine, and will correctly map those virtual devices to their respective physical
backing devices. In addition, VMMgr V4.0 adds a new simplified display on the storage tab
that eases tracing the connections from the virtual machine's virtual device to the physical
backing device. The original, more complex, display is also available by selecting the "Show
host bus adapter" checkbox on the storage tab. Persistent device files and LUN hardware
paths are displayed in the physical storage device representations (boxes).
These limitations will be addressed in a future release of VMMgr.
2.3.13 Installing the HP Integrity Virtual Machines Product Over the Evaluation
Software
If you installed the evaluation version of Integrity VM, you must remove the evaluation software
before you install the current version of the product. For example, to remove the evaluation version
of Integrity VM, enter the following commands:
# swremove -x autoreboot=true T2801AA vmProvider
# rm -rf /opt/hpvm
# rm -rf /opt/hpvmprovider
Do not remove the directory /var/opt/hpvm. This directory contains all the virtual machine
configurations that were created with the evaluation software.
2.3.14 Do Not Install Applications on the VM Host System
When you install Integrity VM, HP-UX kernel parameters are changed to accommodate the virtual
machine environment. This makes the system unsuitable for running any other applications.
Regardless of whether guests are configured and running, the VM Host system is not configured
to allow applications to share system resources. You can run system management utilities and
24 Installation Notes