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

Known Problems and Workarounds
This section provides a list of problems and limitations known to HP at the time of publication.
If workarounds are available, they are included. For information on specific defects, see the HP
ITRC at http://itrc.hp.com.
• No support of agile addressing (extended hardware paths) for non-11.31
virtual partitions in mixed HP-UX 11i v1/v2/v3 vPars environments
Related Defect ID and Patch Number QXCR1000764993
Applicable On vPars A.04.xx on HP-UX 11i v2 (B.11.23), vPars A.03.xx on HP-UX 11i v1
(B.11.11)
Description Any agile hardware path placed into the vPars database (/stand/vpdb)
cannot be used to boot HP-UX 11.11 or HP-UX 11.23 virtual partitions.
Symptoms Virtual partition OS panic, of the following type:
panic: all VFS_MOUNTROOTs failed: NEED DRIVERS ?????
Workaround Use legacy hardware paths when assigning boot paths to virtual partitions
running HP-UX v2 (B.11.23) or HP-UX v1 (B.11.11).
• Configuring a virtual partition with a low amount of base memory can
result in a system hang or lead to slow system performance
Symptoms System hang or slow system performance
Workaround Configure the virtual partition with enough base memory using the guidelines
in the following table.
Minimum Base MemoryTotal Memory Assigned to the Virtual Partition
1/2 of total memory1 GB to 8 GB
4 GB8 GB to 16 GB
1/4 of total memoryOver 16 GB
• Dynamically adding RAM on PA-RISC servers with older PDC firmware
causes a panic in mixed HP-UX 11i v1/v2/v3 vPars environment
Applicable On vPars A.05.xx on PA-RISC
Description If PDC firmware is not updated, side effect can be a panic during dynamic
memory migration.
Symptoms Panic during dynamic memory migration.
Workaround Update PDC firmware to the supported revision as specified in the HP-UX
Virtual Partitions Ordering and Configuration Guide.
• vparreset: Error: Cannot access PIM data for virtual partition
Applicable On
• vPars A.04.xx on PA-RISC
• vPars A.03.xx on PA-RISC
Description On PA-RISC systems configured with virtual partitions, the vparreset
command sometimes reports an error message, however the reset succeeds.
Symptoms The vparreset command throws the following error message, but a crash
dump is taken successfully.
vparreset: Error: Cannot access PIM data for virtual partition vparname
Workaround None. Ignore the message if the reset is successful.
8