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

Problem with Adding Unbound CPUs to a Virtual Partition

Cause

Appendix B 163

Cause

When a virtual partition boots, the HP-UX kernel creates a table of the

existing unbound CPUs available at the time the virtual partition is

booted. If there is not an existing entry in the table for a speciﬁc CPU,

that CPU cannot be added to the partition.

Example

To simplify the example, this appendix uses a generic eight-way

(8-processor) server whose processors are at the hypothetical hardware

paths of x01, x02, x03, x04, x05, x06, x07, and x08.

Create the Virtual Partitions

Suppose we create three partitions using the following commands.

# vparcreate -p vpar1 -a cpu::2 -a cpu:::2

# vparcreate -p vpar2 -a cpu::2 -a cpu:::2

# vparcreate -p vpar3 -a cpu::1

And suppose that the monitor chooses the following hardware paths for

the bound CPUs:

This conﬁguration leaves the following three CPUs as unbound CPUs:

Boot the Virtual Partitions

When we boot the partitions, they will boot with the following bound

CPUs; their respective kernels will have the following unbound CPU

entries.

Virtual Partition vpar1 vpar2 vpar3

Paths of Bound

CPU(s)

x01

x02

x03

x04

x05

Paths of

Unbound CPUs

x06, x07, x08