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 the original vPars on 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 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 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”.
See “vPars Monitor: Booting the vPars Monitor”.
See “Autoboot”.
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

Integrity Differences Relative to PA-RISC

Technical documentation

» Table of Contents

» Glossary

» Index

Booting

Commands

For Further Information