HP-UX Virtual Partitions Administrator's Guide (includes A.03.05 and A.04.05)

I/O Hardware Paths
For non-nPartitionable systems, the beginning portions of the I/O hardware paths are in the
format:
• sba/lba
But for nPartitionable systems, the beginning portions of the I/O hardware paths include the cell
and are in the format:
• cell/sba/lba
Impact on vPars Commands: Specifying I/O
On a non-nPartitionable system, a vparcreate command might look like:
# vparcreate -p winona1 -a cpu::2 -a cpu:::2 -a mem::1024 -a io:0.0 -a
io:0.4 -a io:0.0.2.0.6.0:BOOT
• where -a io:0.0 represents the sba/lba format.
But on an nPartitionable system, the equivalent vparcreate command would look like:
# vparcreate -p vpar1 -a cpu::2 -a cpu:::2 -a mem::1024 -a io:0.0.0 -a
io:0.0.4 -a io:0.0.0.2.0.6.0:BOOT
• where the -a io:0.0.0 represents the cell/sba/lba format. If only -a io:0.0 were
used on an nPartitionable system, this would be specifying only the cell/sba.
CAUTION: When using vPars A.03.01 or earlier, I/O is assigned only at or below the LBA level.
For correct I/O allocation, you must include the LBA. Specifying only the SBA is not supported. On
nPartitionable systems, if you specify only the cell/sba format for I/O allocation, the vPars
commands will not assume that all LBAs under the SBA are to be included in the allocation; the
system may panic.
NOTE: When specifying the boot disk or alternate boot disk hardware paths, the full hardware
path must always be specified. It must be in legacy hardware path format, as virtual partitions
does not support lun or lunpath hardware path formats.
CPU Hardware Paths
The same is true for CPU hardware paths. In the non-nPartitionable systems, the CPU path is
• cpu
But for nPartitionable systems, the CPU path includes the cell, so the CPU path is
• cell/cpu
Impact on vPars Commands: Specifying CPU
Since the nPartitionable systems include the cell in the hardware path, when specifying a CPU
hardware path, you must include the cell number to specify the entire CPU hardware path.
On a non-nPartitionable system, if the ioscan output shows
41 processor Processor
45 processor Processor
where 41 and 45 are the hardware paths of two CPUs, then the vparcreate command might
look like:
# vparcreate -p winona2 -a cpu::2 -a cpu:::2 -a cpu:41 -a cpu:45 ...
But for an nPartitionable system, if the ioscan output shows
0/12 processor Processor
0/13 processor Processor
52 Planning Your System for Virtual Partitions