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

Note that the entries for the unbound CPUs are only entries for unbound CPUs that can potentially
be added to the partition. At this point, we have not assigned any unbound CPUs to any of the
partitions:
vpar3vpar2vpar1
Virtual Partition
x05x03
x04
x01
x02
Paths of Bound CPU(s)
x06
x07
x08
x06
x07
x08
x06
x07
x08
Unbound CPU Kernel Entries
x06, x07, x08
Paths of Unbound CPUs
Looking at vpar3, because kernel entries for CPUs at x06, x07, and x08 exist, any of the unbound
CPUs (x06, x07, or x08) can be added to vpar3. They could also be added to vpar1 or vpar2.
Create A Fourth Virtual Partition
Supposed we create and boot a fourth partition using the following command:
# vparcreate -p vpar4 -a cpu::3 -a cpu:::3
The Monitor will assign the remaining three CPUs at hardware paths x06, x07, and x08:
vpar4
Virtual Partition
x06
x07
x08
Paths of Bound CPU(s)
(none)Unbound CPU Kernel Entries
Remove a Virtual Partition
If we shutdown and remove vpar2 (using vparremove), its bound CPUs will become unbound,
and the current configuration will be the following:
vpar4vpar3vpar1
Virtual Partition
x06
x07
x08
x05x01
x02
Paths of Bound CPU(s)
(none)
x06
x07
x08
x06
x07
x08
Unbound CPU Kernel Entries
unbound CPUs are now at x03 and x04
Paths of Unbound CPUs
There are now two unbound CPUs, but these CPUs are not the same ones that were available at the
time the partitions vpar1 or vpar3 were booted.
Problem is Encountered
At this point, if we attempt to add an unbound CPU to vpar3 using the following command:
# vparmodify -p vpar3 -a cpu::1
the command will fail and return the error message:
304 Problem with Adding Unbound CPUs to a Virtual Partition (A.03.xx)