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

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.
• Intermittent system hangs when displaying large output on console
Related Defect ID and Patch Number QXCR1000812861
Applicable On vPars A.05.01 and later versions on HP Integrity systems
Description While displaying large output on the console of a single processor partition
causes momentary hangs - sometimes long enough for some time critical applications like
service guard to bring the system down.
Symptoms Sometimes vPars crashes when a cat or a tail command with a big file is
run from the console.
Workaround Do not display or print large files on the console. Use more command to
view large files or connect to vPar via telnet and display.
• Unable to ignite vPar on A9891A Smart Array card boot path
Related Defect ID and Patch Number QXCR1000821825
Applicable On vPars A.05.01 and later versions on PA-RISC systems
Description Unable to do a vPar ignite of HP-UX onto an A9891A Smart Array logical
drive. This happens on HP 9000 rp8440 and HP 9000 rp7440 systems.
Symptoms The vPar monitor fails to boot the vPar after igniting the first required reboot.
Workaround None
• Update of efipath/hpux hwpath mapping fails when a path from deneb
hardware is given
Related Defect ID and Patch Number QXCR1000824412
Applicable On vPars A.05.03 and later versions
Description The update disk path operation when connected to a deneb card (AD221,
AD222, AD393) using vparefiutil -u -H command fails.
Symptoms The vparefiutil -u -H < hardwarepath > command fails with the
error message: A bootable disk cannot be found at or below < hardwarepath >
Workaround Use vparefiutil -u command to update mappings of the disks connected
through deneb card. For example: Instead of using the vparefiutil -u -H
0/0/12/0/0/0/0/4/0/0/0.1.14.0.0.0.1, use vparefiutil –u command.
• ALTBOOT automatically set when booted in vPars mode
Related Defect ID and Patch Number JAGag43601
Applicable On vPars A.05.xx on PA-RISC systems
Description After creating a new vPars database (vpdb) the ALTBOOT variable for a virtual
partition may be automatically set when booting in vPars mode. Explicitly set alternate boot
path settings are unaffected by this issue.
Symptoms ALTBOOT variable for a virtual partition is automatically set.
Workaround To avoid this issue, you can either:
Known Problems and Workarounds 9