HP Integrity Virtual Machines Version 4.2 Release Notes

2 Installation Notes
This chapter contains notes about installing and upgrading Integrity VM and associated software
on the VM Host system.
2.1 Installing Integrity VM
This section describes information about installing the HP Integrity Virtual Machines product
and associated software on the VM Host system.
HP Integrity Virtual Machines B.04.20 is supported on HP Integrity servers or nPartitions running
HP-UX 11i v3 March 2010 1003). When you upgrade or reinstall Integrity VM, guests are stopped,
but they are not removed. When the new version of Integrity VM starts, the virtual machines
might also start, depending on the setting of the guest boot attribute.
NOTE: Version 4.2 of Integrity Virtual Machines requires the installation of both the
HostAVIOStor and HostAvioLan bundles. Other Integrity Virtual Machines documentation may
state this requirement is optional, but it is not. In addition, to use the AVIO network driver on
a Windows guest, you must install the VMGuestSW bundle.
The VM Host system is not a general-purpose system; it is dedicated to the hosting of virtual
machines. After you install Integrity VM, no operating system or process management
reconfiguration should be performed outside those provided by the Integrity VM interfaces.
Specific examples of actions that are not supported on the VM Host system include:
Changing priorities or scheduling attributes of processes on the VM Host system.
Modifying kernel tunables in any way.
Do not install the VM Host software on a VM guest, and do not install the HPVM-Guest software
on the VM Host. Neither configuration is supported.
If the current version of your VM Host AVIO (HostAVIOStor) storage driver is B.11.31.0903 or
later, then before you install this Integrity VM V.4.2 patch kit, upgrade the guest AVIO storage
driver (GuestAVIOStor) to B.11.31.0903/B.11.23.0903 or later on both HP-UX 11i v2 and HP-UX
11i v3 guests.
If you do not upgrade your AVIO guest storage drivers, you might see occasional open failures
of AVIO storage devices.
For complete information about the requirements for installing Integrity VM, see the HP Integrity
Virtual Machines 4.2: Installation, Configuration, and Administration manual.
2.2 Changes and Issues in This Release
The following sections describe changes, issues, and new information pertaining to this release.
2.2.1 Unable to Communicate with the FSS Agents Messages in /var/opt/hpvm/
common/command.log
When Integrity VM is stopped either with the /sbin/init.d/hpvm stop command or as a
result of removing or updating the version of Integrity VM on the VM Host, messages of the
following form might be logged in the /var/opt/hpvm/common/command.log file:
ERROR|host|root|Unable to communicate with the FSS agent
The messages, which are a result of interactions with the performance metrics processes scopeux
and perfd, are normally transient and stop after about a minute. Approximately 60-70 messages
might be generated in that time. You can clear this condition by either rebooting the VM Host
or by stopping and restarting the metrics collection processes.
To stop and restart the perfd process, use the following commands:
2.1 Installing Integrity VM 19