HP Integrity Virtual Machines 4.2.5: Release Notes

**************************************************************
* Exception Frame Display: *
…
Crash dump information follows this output.
Use one of the following solutions to fix either of these issues:
• Set the VM Host base_pagesize = 64K (See the base_pagesize(5) manpage for details of
determining and setting the VM Host’s base_pagesize.)
• Set the guest preferred pagesize to 8K:
# hpvmmodify -P vm-name -x tunables=ptsz=13
4.4.4 Guest Device Placement and Adapter Limitation
The OpenVMS guest utilizes the PKDRIVER SCSI port driver and the DKDRIVER SCSI class driver.
A guest configuration uses a UNIX-like algorithm to place storage devices on an AVIO storage
adapter starting with entry “0,0” and continuing through “7,7”, where each AVIO storage adapter
can have up to 128 targets. The default device placement algorithm places 14 devices on each
adapter, in order. Thus, when the guest creation (hpvmcreate) or modification (hpvmmodify)
utility attempts to add a device (using the –a option), it adds, in order, from “0,0,0” through
“0,0,14” before creating a new adapter and starting over again with “0,1,0” through “0,1,14”.
You can specify usage of any target value from 0 through 127.
Each Integrity VM adapter corresponds to the OpenVMS controller letters A through Z. The exact
mapping depends on the order of devices found in the guest configuration file. Typically, “0,0”
maps to PKA/DKA, while “0,1” maps to PKB/DKB, and so on. The following are known restrictions:
• The guest target value is a pure number assigned as the unit number of the device. The guest
target value is not the same as a hardware SCSI target, where the disk in the 0th slot would
be DKA0, the disk in the 1st slot would be DKA100, the disk in the 2nd slot would be DKA200,
and so forth. Furthermore, it is not possible to assign the ‘lun’ number for the storage devices,
such as DKA101. Placing a device at “0,0,1” results in the guest device “DKA1:”.
• 16 unique DKDRIVER SCSI class adapters can be created. OpenVMS identifys them as DKAn:
through DKPn:, where ‘n’ is the target value. Attempts to use a 17th adapter results in a port
class PKQ0: being created with no corresponding DKQn: devices. The Integrity VM guest
creation (hpvmcreate) and modification (hpvmmodify) utilities are not aware of this
restriction.
You can add devices dynamically by using the hpvmmodify command on the VM Host to add
the storage in conjunction with the OpenVMS command sysman io autoconfigure all on
the guest to find the storage.
4.4.5 OpenVMS System Dump Analyzer (SDA)
Using the OpenVMS SDA command CLUE CONFIG the first time results in a CLUE-W-NOSYMBIOS,
cannot access SYMBIOS table warning. Subsequent CLUE CONFIG commands display
incorrect data. Additionally, using EXAM/PHYS FE000 to view the guests SMBIOS data results
in the message %SDA-E-NOREAD, unable to access location 00000000.000FE000.
This issue seems to affect the SDA utility.
4.4.6 Formatting SYSTEM UUID
The sys$getsyi() or f$getsyi lexical for SYSTEM_UUID appear to return a UUID that is incorrectly
formatted as compared to the value seen in the VM Host's guest configuration output (hpvmstatus
–V –P vm-name). However, the returned value is normal and expected. The returned string needs
to be properly formatted to be viewed as a “normal” UUID. Use the following DCL code to format
and print the UUID value:
4.4 OpenVMS Guests 53