Manualshelf

HP-UX Virtual Partitions Release Notes (A.05.09)

ManualsBrandsHP ManualsSoftwareHP Integrity Virtual Machines Manager (vmmgr) Software
11121314151617181920
Workaround
Note that in a vPars environment, when system events are reported via EMS either from system
firmware or an OS instance, the system events are decoded and reported on all virtual
partitions. The OS instance that is shown as sending the event is not necessarily indicative of
the actual virtual partition that encountered the problem. The Reporting Entity ID is the only
clue to which virtual partition reported the problem. The output will be similar to the following:
Reporting entity ID: 6 ( Cab 0 Cell 0 CPU 6 ) (possibly from one vPar)
• Virtual Partition Does Not Boot After Root Mirror is Created
Related Defect ID and Patch Number
JAGaf54464
Applicable On
◦ vPars A.05.xx on Integrity
◦ vPars A.04.xx on Integrity
Description
A virtual partition does not boot from its mirror root disk because there is no longer a valid
EFI to hardware path mapping in the vPars database.
Symptoms
After creating a mirror root disk, the virtual partition fails to boot from this disk. You may see
messages similar to the following:
Load of 1/0/8/1/0.22.31.0.0.0.1 failed: Not Found
Workaround
After the mirror is created, use the vparefiutil -u command to add the new hardware
path to EFI path mapping to the vPars database. Note that on Integrity systems running vPars,
whenever the EFI path of a boot disk changes (for example, if an OS is re-installed on the
disk), the new hardware to EFI path mapping has to be updated in the vPars database. This
can be done by running the vparefiutil -u command. For more information on EFI and
vPars, see the “EFI and Integrity Notes” section in the HP-UX Virtual Partitions Administrator’s
Guide.
• Virtual Partition Appears to Hang After Typing Control-s
Related Defect ID and Patch Number
JAGae98555
Applicable On
◦ vPars A.05.xx on PA-RISC
◦ vPars A.04.xx on PA-RISC
◦ vPars A.03.xx on PA-RISC
Description
While a virtual partition is shutting down, panicking, or booting, typing Control-s to suspend
its console output may cause the virtual partition to stop making forward progress. The virtual
partition may appear to hang.
Symptoms
If a Control-s is typed at the system keyboard while the virtual partition currently writing to the
console is shutting down, panicking, or booting, that virtual partition may appear to hang.
12 vPars A.05.09 Release Notes