HP-UX Virtual Partitions Administrator's Guide (includes A.05.02)

How vPars and its Components Work

Boot Sequence

Chapter 2

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):

The Monitor loads the partition database (the default is /stand/vpdb) from the same disk that

/stand/vpmon was booted. The Monitor internally creates (but does not boot) each virtual partition according

to the resource assignments in the partition database.

Next, the vPars Monitor runs in interactive mode (when no options to /stand/vpmon are given) with a

command line interface.

MON>

To boot a kernel in a virtual partition (that is, to launch a virtual partition), use the Monitor command

vparload. For example, to launch the virtual partition named uma1:

MON> vparload -p uma1

In this example, the vPars Monitor would load the virtual partition uma1 and launch the kernel from the boot

device speciﬁed for uma1. (The boot device is assigned when the virtual partition is created and is recorded in

the Monitor database.)

HP-UX is now booted on the virtual partition uma1.

Once a virtual partition is running, you will be at the virtual console of a virtual partition. Subsequent virtual

partitions can be booted using the vPars command vparboot at the HP-UX shell prompt of uma1. For

information on how to boot a virtual partition, see “Booting a Virtual Partition” on page 159.

PA-RISC Integrity

ISL> hpux /stand/vmunix HPUX> boot vmunix

PA-RISC Integrity

ISL> hpux /stand/vpmon HPUX> boot vpmon