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

How vPars and its Components Work

Boot Sequence

Chapter 2

Boot Sequence

NOTE This section describes a manual boot sequence to help explain how vPars impacts the boot

process, but you can continue to use an autoboot sequence to boot all partitions. See

“Boot||Shut: Autoboot” on page 140.

Boot Sequence: Quick Reference

On a server without vPars, a simplified boot sequence is:

Adding vPars adds the Monitor layer, so now hpux (for Integrity, hpux.efi) loads the Monitor. Then the

Monitor boots the kernels of the virtual partitions. The boot sequence becomes

Boot Sequence: The Details

With or without vPars, the firmware loads and launches ISL or EFI.

In a server without vPars, from ISL or EFI, the loader hpux or hpux.efi loads the kernel /stand/vmunix:

However, in a server with vPars, from the loader (hpux or hpux.efi) loads the vPars Monitor

(/stand/vpmon):

PA-RISC Integrity

1. ISL (Initial System Loader) 1. EFI (Extensible Firmware Interface)

2. hpux (secondary system loader) 2. hpux.efi

3. /stand/vmunix (kernel) 3. /stand/vmunix

1. ISL or EFI

(firmware)

2. hpux or hpux.efi

3. /stand/vpmon (vPars Monitor and partition database)

4. /stand/vmunix (kernels of the virtual partitions)

PA-RISC Integrity

ISL> Shell> fs0:

fs0:\> \efi\hpux\hpux.efi

PA-RISC Integrity

ISL> hpux /stand/vmunix HPUX> boot vmunix

PA-RISC Integrity

ISL> hpux /stand/vpmon HPUX> boot vpmon