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

CPU, Memory, and IO Resources
IO: Allocation Notes (vPars A.04, A.03 and earlier)
Chapter 6
161
For an nPartitionable system, the vparcreate command would look like:
#vparcreate -p vpar1 -a cpu::1 -a cpu:::1 -a mem::1024 -a io:0.0.0 \
-a io:0.0.0.2.0.6.0:BOOT
where the IO assignment is specified using the LBA level (-a io:0.0.0.) and the boot disk is specified
using the full hardware path (-a io:0.0.0.2.0.6.0).
For information on using the LBA level on nPartitionable systems, also see “Planning, Installing, and
Using vPars with an nPartitionable Server” on page 50.
• SBA/LBA versus cell/SBA/LBA
When viewing hardware paths, note the following:
1. The explicit specification of an LBA on a non-nPartitionable system consists of two fields: sba/lba
2. The explicit specification of an LBA on an nPartitionable system consists of three fields:
cell/sba/lba
3. With A.03.02 and later and A.04.xx, all LBAs under a SBA are implied when explicitly specifying a
SBA without specifying any LBA. Therefore, the path specified on a command line can have different
meanings depending upon the vPars version, the type of server, and the user intent. For example, the
path of x/y can mean any of the following:
— sba=x, lba=y on a non-nPartitionable server running vPars A.03.01 or earlier
— sba=x, lba=y on a non-nPartitionable server running vPars A.03.02 or later or A.04.xx
— cell=x, sba=y on an nPartitionable server running vPars A.03.02 or later or A.04.xx
• Supported IO
Check your hardware manual to verify that your mass storage unit can be used as a bootable device. If a
mass storage unit cannot be used as a boot disk on a non-vPars server, it cannot be used as a boot disk on
a vPars server. vPars does not add any additional capability to the hardware.
For information on supported IO interface cards and configurations, see the document HP-UX Virtual
Partitions Ordering and Configuration Guide.