Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
HP Integrity Virtual Machines: Release Notes > Chapter 3 Restrictions

Error Logging

» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Index

This section lists release notes associated with Integrity VM error logging

Guest error messages for the null storage type

If your guest configuration uses the null physical store type for a backing store, the following error messages are displayed on the guest console and log file when the guest is started:

ERROR: Cannot determine device capacity
ERROR: Cannot initialize SCSI Device

These error messages are displayed by Integrity VM when it encounters a zero-capacity device (such as a null physical storage device type). You can ignore these error message; alone, they do not indicate a problem with the guest configuration. Guest operation is not impacted by this error message.

Log messages logged 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 lof file for applications that generate Integrity VM log messages to write to the current command.log file.

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 instead. The only supported options for a virtual machine are the ed -mca and -init options. 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.

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.

Guest log can grow unbounded

The per-guest monitor log file (/var/opt/hpvm/guests/vm_name/log) records guest start and stop information. These log files can grow very large. For guests that restart frequently, HP recommends periodically renaming or deleting the log file while the guest is off.

Virtual console logs different from physical machine logs

The virtual console allows you to use the sl to list the System Event log and the Forward Progress log. The displays from the virtual console differ from those generated on a physical machine in the following ways:

  • Event numbering is inconsistent for different lines.

  • Although the command menu allows you to specify a cell number, virtual machines are not cellular. Therefore, this option is not functional.

Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© 2006 Hewlett-Packard Development Company, L.P.