System Management Release Notes
4.2 Issues with Time Zone Configuration
Workaround
Deassign the
SYS$DST_DELTA_TIME
logical, when the error message appears on
the system.
$ DEASSIGN/EXECUTIVE_MODE/SYSTEM SYS$DST_DELTA_TIME
4.3 OpenVMS as a Guest Operating System on Integrity VM
OpenVMS Version 8.4 now supports HP Virtualization and can be installed as
a guest operating system on HP Integrity Virtual Machines (Integrity VM). For
more information about product specific limitations, see the respective product
documentation.
This section describes known problems and restrictions in OpenVMS guest on
Integrity VM.
4.3.1 "Guest Punishment" Scenarios
V8.4
Scenario 1
A problem in Integrity VM Version 4.1 Field Test Evaluation Kit for OpenVMS
Version 8.4 causes OpenVMS guests to fail with the following message displayed
on the guest’s MP console:
*** A fatal error has occurred -- VM terminated ***
**** Dumping Guest Image ****
**** Done with dump (nnnnnKbytes) ****
At the same time, the Integrity VM monitor log (found on the VM Host
in /var/opt/hpvm/common/hpvm_mon_log) must include guest punishment
information as follows:
Assertion failed mmxlate.c:nnn: PTE_TYPE(pte) == PTE_TYPE_TRPT || PTE_TYPE(pte) == PTE_TYPE_SPPT
scopeDeact EA0C000000000000
===============================================================================
Guest punishment: Virtual Machine Monitor Assertion Failed (CPUnnnnnnn)
===============================================================================
This problem occurs when a privileged hardware instruction (for example, mov r1
= psr) is executed in process space, rather than in system space (that is, in the
VMS executive).
When an application uses the $CMKRNL system service to enter kernel mode, it
can execute privileged hardware instructions in process space. The kernel mode
routines may be within the main image of the application, or within a shareable
image. To run such an application, the user must have CMKRNL privilege, or the
image must be installed: a main image with privileges, and a shareable image as
a protected shareable image.
The application may be part of OpenVMS, a local customer application, or may be
from a third-party.
If the problem occurs, a possible workaround is to install the image that performs
the privileged hardware instructions using /RESIDENT. This ensures that the
code of the image is in the system space.
4–2 System Management Release Notes
