HP Integrity Virtual Machines 4.2.5: Release Notes

4.3.2.16 Occasional Floating-Point Assist Fault Messages.
Occasional floating-point assist fault messages appear when running Mozilla. This problem also
occurs on native Integrity servers running Linux. For more information, see the “Developer & Solution
Partner Program (DSPP)” webpage on http://www.hp.com, and search for “floating-point assist
fault”.
4.3.2.17 Serviceguard in VM Host Configuration
The default KILLTIME of 10 seconds (in hpvmsg_stop for a legacy package) and a wait of 10
seconds (in hpvmsg_ext for a modular package) might be too aggressive in some environments
and can result in a file system corruption on Linux guests. HP recommends that you tune this value,
so that the file systems on the guests are successfully unmounted before the guest is powered off.
4.4 OpenVMS Guests
The following sections contain the release notes specific to OpenVMS guests.
4.4.1 Creating OpenVMS Guests
To create an OpenVMS guest (virtual machine) on the VM Host, use the following command, where
vmsg1 is the name of the guest:
# hpvmcreate -P vmsg1 -O OpenVMS -c 2 -r 2g
For information about installing OpenVMS guests, see the HP OpenVMS V8.4 for Integrity Servers
Upgrade and Installation Guide at the following website: OpenVMS Documentation.
4.4.2 Minimum Processor Requirement for OpenVMS Guests
OpenVMS guests are supported on Integrity VM Host systems with Intel® Itanium® 2 9000/9100
Series processors or later processors that OpenVMS supports natively.
4.4.3 Minimum VM Host Page Size
The OpenVMS guest might have problems booting if one or more of the following occurs:
The VM Host is under memory pressure due to frequent allocations and freeing large amounts
of memory.
The VM Host has just enough physical memory to support the guest's requirements and the
VM Host's base_pagesize is set to 4K.
OpenVMS expects a guest pagesize of 8K, and the boot processing can have issues loading an
in-memory disk used during the boot process. If either of the following situations occur, setting the
VM Host's base_pagesize to 64K or setting the guest's preferred pagesize to 8K should resolve
the problem:
The following message is written to the VM Host's /var/opt/hpvm/common/hpvm_mon_log
file:
# WARNING: Host memory is fragmented.
# Reducing VHPT preferred page size from 64K to 16K.
# This may result in degraded performance for this virtual machine.
Where # is a guest vm number assigned by hpvmdvr.
Depending on how fragmented and how small the VM Host pagesizes are, the following
OpenVMS error message and text appear on the guest’s console:
%SYSBOOT-F-LDFAIL, unable to load SYS$PUBLIC_VECTORS.EXE, status = 00000044
**************************************************************
* Exception taken before exception handler has been loaded! *
* Unable to take crashdump. *
52 Installing Guests