HP-UX Virtual Partitions Release Notes (A.05.03)
NOTE: After using vparenv to change the boot mode from vPars mode to nPars mode,
further booting and loading of virtual partitions will fail although the vPars monitor has not
been rebooted. To boot or load virtual partitions, use vparenv to change the boot mode back to
vPars mode.
Usage Scenarios
• If you are running HP-UX in nPars mode (standalone), use the following vPars command
to switch to vPars mode:
OS-Prompt> vparenv -m vPars /* sets the mode for the next nPartition reboot*/
OS-Prompt> reboot /* to reboot the system into vPars mode */
• If you are at the Monitor prompt, use the following Monitor command to switch to nPars
mode:
MON> reboot nPars /* sets the mode and reboots the system */
• If you are at the EFI shell prompt, use the following EFI utility to switch to either nPars or
vPars mode:
Shell:> fsN:
fsN:> vparconfig reboot nPars|vPars
Since vparconfig is not a built-in EFI shell command, you must go to the disk to execute
vparconfig. For example, to switch to vPars mode:
Shell:> fs0: /* go to the EFI partition of the disk */
fs0:> vparconfig reboot vPars /* sets the mode and reboots the system */
Note: vparconfig is an EFI utility which gets installed in the EFI partition during the
installation of the vPars product.
• If you are at the EFI shell prompt in vPars mode and you do not have vPars installed on
any of your disks, you can use the built-in EFI command parconfig to switch to nPars
mode:
Shell:> parconfig nPars
Shell:> parconfig reset
NOTE: Remember to issue a parconfig reset after setting the mode. parconfig
nPars only sets the mode to nPars. You must issue the parconfig reset command to
reset the system so it boots into nPars mode.
NOTE: parconfig does not support switching to vPars mode. In other words, you can
use parconfig to set the mode to nPars, but you cannot use parconfig to set the mode
to vPars.
Known Problems Fixed in This Version
This section lists the known problems fixed in vPars A.05.03.
For information on specific defects, see the HP ITRC at http://itrc.hp.com.
• QXCR1000760681 vparstatus shows -ve CPUs after vparboot -I on vpar with
floater CPUs
• QXCR1000760757 0612.1111 iCAP startup failure: “No core found matching
hardware path <>”
10