HP Integrity Virtual Machines 4.2.5: Release Notes

2.3.1 After Installation, Integrity VM Might Hang Upon Reboot
Due to a timing issue, Integrity VM V4.2.5 might hang upon reboot after it is installed. This is an
intermittent issue. To fix the problem, install patch PHKL_41227, which will be available from the
HP IT Resource Center website: http://itrc.hp.com by the middle of August 2010.
2.3.2 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:
# /sbin/init.d/pctl stop
# /sbin/init.d/pctl start
To stop and restart the scopeux process, use the following commands:
# /sbin/init.d/ovpa stop
# /sbin/init.d/ovpa start
2.3.3 Compatibility of Insight Dynamics - VSE V6.0 with Integrity VM V4.2.5
You can use Version 6.0 of the Insight Dynamics — VSE with Integrity VM Version 4.2.5, but this
version of Insight Dynamics - VSE does not support the new features in Integrity VM Version 4.2.5.
2.3.4 Warning Messages That Can be Ignored
During the installation or update of Integrity VM along with the HostAvioLan and/or the
HostAVIOStor products, you might see the following warning messages in the /var/adm/syslog/
syslog.log file:
WARNING: mod_uninstall: Attempt to uninstall hvsd module: Module is not installed
WARNING: mod_uninstall: Attempt to uninstall hssn module: Module is not installed
These warning messages can be safely ignored.
2.3.5 Software Failures on VM Host Due to Use of Large base_pagesize Tunable
Integrity VM Version 4.2 and later support both 4KB (default) and 64KB settings for the
base_pagesize tunable. In previous versions, installation of Integrity VM set the base_pagesize
tunable to 64KB, because of the significant improvements in memory efficiency that resulted. HP
still recommends setting the base_pagesize tunable to 64K for this reason. However, there are
several defects that can significantly hamper software installation and operation when HP-UX is
configured with 64K base_pagesize. For more details, see the white paper on this topic, Tunable
Base Page Size available from http://www.hp.com/go/hpux-core-docs/.
2.3.6 HP-UX Installation and Update Failures When Using Physical Installation Media
The update from 0903 OE media might fail on VM Host (physical) systems, leaving the operating
system in an unusable state. This is caused by a defect in HP-UX when running with a base_pagesize
of 64K. Installation of Integrity VM sets the base_pagesize (BPS) to 64K, and Integrity VM Version
4.1 requires HP-UX 0903 on the VM Host system. The failure manifests in at least two ways:
20 Installation Notes