Installing and Managing HP-UX Virtual Partitions (includes A.03.03)

How vPars and its Components Work
Integrity Differences Relative to PA-RISC
Chapter 2
37
Integrity Differences Relative to PA-RISC
Beginning with vPars A.04.01, vPars is supported on both Integrity and PA-RISC platforms. This section
describes the major conceptual differences for booting and running vPars on Integrity relative to PA-RISC.
Booting
• Modes
On Integrity platforms, you have to set the mode (vPars or nPars) to be able to boot the nPartition into
standalone (nPars) or the vPars environment (vPars).
See “Modes: Switching between nPars and vPars Modes (Integrity only)” on page 93.
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” on page 67.
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” on page 33.
See “Monitor: Booting the vPars Monitor” on page 101.
See “Boot||Shut: Autoboot” on page 141.
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
See “EFI and Integrity Notes” on page 35.
These commands are effective only on PA-RISC:
— vparreloc
— vparutil
See also:
• “EFI and Integrity Notes” on page 35
• “Differences in Different Versions of vPars” on page 42