HP-UX Virtual Partitions Release Notes A.04.07 (HP-UX 11i v2) (T1335-91000, March 2010)

• 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 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.
Workaround Type Control-q to resume console output.
• Configuring an Ultra2 or Ultra160 Card with vparutil
Related Defect ID and Patch Number JAGaf00411
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 the nPartitionable servers, using the vparutil command to configure an
Ultra2 or Ultra160 SCSI card can cause the virtual partition that owns the SCSI card to fail
to boot.
Symptoms On the nPartitionable servers, the virtual partition connected to an Ultra2 or
Ultra160 SCSI boot device fails to boot after the SCSI card was configured using the vparutil
command.
Workaround
Known Problems and Workarounds 9