Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
HP-UX Virtual Partitions Administrator’s Guide > Chapter 2 How vPars and Its Components Work

Boot Sequence

» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Glossary

 » Index

This section describes the boot differences in a vPars system relative to a non-vPars system.

For information on the HP-UX boot process, ISL, SSL, EFI, and vmunix, see the HP-UX System Administrator's Guide: Routine Management Tasks available at http://docs.hp.com and see also the following manpages:

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 “Autoboot”.

Boot Sequence: Quick Reference

On a server without vPars, a simplified boot sequence is as follows.

PA-RISC

Integrity

1. ISL

(Initial System Loader)

1. EFI

(Extensible Firmware Interface)

2. hpux

(secondary system loader)

2. hpux.efi

(HP-UX boot loader)

3. /stand/vmunix

(kernel)

3. /stand/vmunix

 

Adding vPars adds the vPars Monitor layer, so now hpux(for Integrity, hpux.efi) loads the vPars Monitor. Then the vPars Monitor boots the kernels of the virtual partitions. The boot sequence becomes the following.

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)

Boot Sequence: The Details

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

PA-RISC

Integrity

ISL>
Shell> fs0: fs0:\> \efi\hpux\hpux.efi

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

PA-RISC

Integrity

ISL> hpux /stand/vmunix

HPUX> boot vmunix

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

PA-RISC

Integrity

ISL> hpux /stand/vpmon

HPUX> boot vpmon

The vPars Monitor loads the partition database (the default is /stand/vpdb) from the same disk that /stand/vpmon was booted. The vPars 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 vPars 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 specified for uma1. (The boot device is assigned when the virtual partition is created and is recorded in the vPars 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”.

Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© 2008 Hewlett-Packard Development Company, L.P.