HP Integrity Virtual Machines Version 4.2 Release Notes

10 Error Logging
This chapter contains information about the way Integrity VM logs messages.
10.1 Changes and Issues in This Release
There are no new error logging issues in the V4.2 release.
10.2 Known Issues and Information
The following sections describe known issues and information from previous releases that still
apply to V4.2.
10.2.1 Old Version of /etc/rc.config.d/hpvmconf Not Overwritten
When you install the new version of Integrity VM, a new version of the /etc/rc.config.d/
hpvmconf file is placed on the system. You receive the following messages:
A new version of /etc/rc.config.d/hpvmconf has been placed on the system. The new version is located at /opt/
hpvm/newconfig/etc/rc.config.d/hpvmconf. The existing version of /etc/rc.config.d/hpvmconf is not being
overwritten, since it appears that it has been modified by the administrator since it was delivered.
You might receive the following message:
The postinstall script for HPVM.HPVM-CORE had a warning (exit code 103). The script location was /var/tmp/
BAA008384/catalog/HPVM.1/HPVM-CORE/postinstall. This script has warnings, but the execution of this fileset
will still proceed. Check the above output from the script for
further details.
10.2.2 Guest Log Can Grow Unbounded
The guest monitor log file (/var/opt/hpvm/guests/vm_name/log) records guest start and
stop information. These log files can grow very large. Use the hpvmconsole command
rec -rotate to close the current log file, rename it, and open a new one.
10.2.3 Log Messages Written to Old Log File
Log messages might be written to the command.log.old file instead of the command.log file.
If this is a problem, reboot the VM Host system. This reinitializes the log file for applications that
generate Integrity VM log messages to write to the current command.log file.
10.2.4 Saved MCA or INIT Register State Can Be Inaccurate
Virtual machines do not support standard management processor console errdump commands.
The virtual console's Virtual Machine menu provides the ed command for this purpose. The
options for a virtual machine are -mca and -init. When you examine the saved guest state
using the ed -mca or ed -init command, the preserved branch registers (B1-B5) do not always
contain accurate data.
10.2.5 Modifying the Size of the Monitor Log File
Integrity VM includes a monitor log (/var/opt/hpvm/common/hpvm_mon_log), which
captures the state of the VM Host. The size of the log file is determined by the VMMLOGSIZE
tunable, stored in the /etc/rc.config.d/hpvmconf file.
When the log file reaches VMMLOGSIZE, the current timestamp is appended to the name of the
log file and a new log file is opened. If you see many such files, increase the value of the
VMMLOGSIZE tunable. Do not set the value of the VMMLOGSIZE tunable below its 1024 KB
default.
10.1 Changes and Issues in This Release 87