| United States-English |
|
|
|
![]() |
Installing and Managing HP-UX Virtual Partitions (vPars) > Chapter 2 How
vPars WorksBoot Sequence |
|
On a server without vPars, a simplified boot sequence is:
Adding vPars adds the monitor layer, so now hpux loads the monitor and then the monitor boots the kernels of the virtual partitions. The boot sequence becomes With or without vPars, the firmware loads and launches ISL. ISL> In a server without vPars, at the ISL prompt, the secondary system loader hpux loads the kernel /stand/vmunix: However, in a server with vPars, at the ISL prompt, the secondary system loader hpux loads the vPars monitor /stand/vpmon: ISL> hpux /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 szilva1: MON> vparload -p szilva1 In this example, the vPars monitor would load the virtual partition szilva1 and launch the kernel from the boot device specified for szilva1. (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 szilva1. 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 UNIX shell prompt of szilva1. For more information on the HP-UX boot process, see the following manpages: For more information on how to boot a virtual partition, see “Booting a Virtual Partition”. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||