HP-UX Virtual Partitions Administrator Guide (includes A.05.07) (5900-1229, September 2010)

On PA-RISC, you do not need to set modes.
• vparboot -I and the LAN Card On Integrity platforms, performing a vparboot -I
uses the LAN card of the target partition to obtain the bootable kernel.
See “Ignite-UX, the LAN, the LAN card, and vparboot -I” (page 78).
On PA-RISC, the lan card of the source partition is used.
• Boot String On Integrity platforms, the boot string used at the hpux.efi prompt (hpux>) is
“boot vpmon”.
See “Boot Sequence” (page 30).
See “vPars Monitor: Booting the vPars Monitor” (page 134).
See “Autoboot” (page 167).
On PA-RISC, the boot string at the hpux prompt (HPUX>) is “hpux /stand/vpmon”.
Commands
• vPars Commands These commands are effective only on Integrity:
— vparefiutil
— vparenv
— vparconfig
These commands are effective only on PA-RISC:
— vparreloc
— vparutil
• nPar Commands On PA-RISC systems, when you run the parstatus -p <partition
number> -V command, the command displays the same primary boot path on all the vPars
belonging to an nPar. However, on Integrity systems, for each vPar, the command displays
the primary boot path corresponding to that vPar (the primary boot path is stored as the
private EFI variable corresponding to that vPar).
For Further Information
• “EFI and Integrity Notes” (page 37)
• “Comparing vPars on PA-RISC and Integrity” (page 39)
Comparing vPars on PA-RISC and Integrity
This table shows the differences in features between vPars on PA-RISC and Integrity platforms.
Table 2-1 PA-RISC and Integrity Differences
IntegrityPA-RISCvPars Functionality
HP-UX 11i v2 (B.11.23) with vPars
A.04.xx
HP-UX 11i v3 (B.11.31) with vPars
A.05.xx
HP-UX 11i v1 (B.11.11) with vPars
A.03.xx
HP-UX 11i v2 (B.11.23) with vPars
A.04.xx
HP-UX 11i v3 (B.11.31) with vPars
A.05.xx
Supported OS
HP-UX 11i v2 to 11i v3HP-UX 11i v1 to 11i v2
HP-UX 11i v2 to 11i v3
Updates Allowed
EFIISLServer Boot Firmware
Comparing vPars on PA-RISC and Integrity 39