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

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.05.xx on PA-RISC
• 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.
• panic: RAM FS space exceeds available memory
Related Defect ID and Patch Number QXCR1000765131
Applicable On vPar A.05.02 and A.05.03 vPar releases on PA-RISC
Description With latest 11.31 WINSTALL, partition requires more than 64MB of contiguous
memory to run. If 64MB granule is configured, monitor assigns 64MB of memory to load
kernel text/data below 2GB which is not sufficient and will result in vPar panic with the
panic string “panic: RAM FS space exceeds available memory” while loading
WINSTALL kernel.
Symptoms The virtual partition panics with the following message when the user tries
to boot the 11.31 WINSTALL kernel.
panic: RAM FS space exceeds available memory
Workaround If 64MB granularity is configured, do the following.
— Assign an additional 64 MB memory by range within the 2 GB to 4 GB range.
— Assign 128 MB memory by range below the 2 GB range.
• Virtual partition does not boot when boot disk has been added to vpdb
using extended hardware path (agile hardware path)
Related Defect ID and Patch Number QXCR1000764504
Applicable On vPars A.05.03 on PA-RISC
Description Virtual partition will not boot when an agile hardware path is specified as
the boot disk for a bridged device.
Symptoms Virtual partition cannot be booted in vPars mode. The monitor log will contain
error logs similar to the following example.
ERROR:CPU1:MON:Could not read IODC firmware for HPA 0x0000000000300800
ERROR:CPU1:MON:iodc_perror: dev_open/Boot device init (0x42)
ERROR:CPU1:MON: iodc_errno=0xfffffffe
INFO:CPU1:MON:Disk Error: disk_errno=3
WARNING:CPU1:MON:lvm error: lvm_errno=1
WARNING:CPU1:MON:Unknown filesystem for path (0/0/6/1/0.4.0.12.0;)/stand/vmunix
ERROR:CPU1:MON:Failed to open (0/0/6/1/0.4.0.12.0;)/stand/vmunix
ERROR:CPU1:MON:Failed to load (0/0/6/1/0.4.0.12.0;)/stand/vmunix
ERROR:CPU1:MON:[23:37:40 1/14/2008 GMT] vpar1 load failed
12