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

Introduction
Supported Environments
Chapter 1 23
http://docs.hp.com/hpux/11i/index.html#Virtual%20Partitions
Operating Systems
• All virtual partitions must run HP-UX 11i (December 2000 Release
or later) in 64-bit mode on PA-RISC platforms.
HP Product Interaction
• nPartitions
To use parmgr, you need to have Partition Manager version
B.11.11.01.05 or later. For more information, see “Installing and
Removing vPars-related Bundles” on page 81.
Only one vPars monitor is booted per nPartition.
Virtual partitions exist within an nPartition, but they cannot span
across nPartitions.
All cells of the nPartition must reside in the same cabinet.
For a given nPartition, the Virtual Front Panel (VFP) displays an OS
heartbeat whenever at least one virtual partition within the
nPartition is up.
Each virtual partition within a given nPartition can be assigned a
subset of only the hardware assigned to the nPartition. Furthermore,
only the active hardware assigned to the nPartition can be used by
the virtual partitions within the nPartition.
All vPars within a nPartition share the same console device. For a
given nPartition, this is the nPartition’s console. For more
information on the console and console logs, see “Virtual Consoles”
on page 41 and “Logs on a nPartition Server” on page 43.
nPartitions remain isolated from other nPartitions, regardless of
whether vPars is installed. You can have virtual partitions installed
within a nPartition without affecting the other nPartitions.
The vPars database is entirely separate from the nPartition complex
profile data. Therefore,a change in the vPars partition database does
not change any complex profile data. For an example on changing