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

Problem with Adding Unbound CPUs to a Virtual Partition (A.03.xx and earlier)
Cause
Appendix B
239
There are now two unbound CPUs, but these CPUs are not the same processors 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:
vparmodify Error: “-a cpu::1”: One or more unbound CPUs were not available when virtual
partition vpar3 was booted. You must shutdown the partition to add them.
Although two unbound CPUs are available, their hardware paths are x03 and x04. But the kernel entries for
vpar3 are x06, x07, and x08. Therefore, the command will fail.
The Workaround: Reboot the Target Virtual Partition
Because unbound CPU kernel entries are created when the target partition is booted, you can reboot the
target partition so that kernel entries created correctly reflect the available unbound CPUs.
In our example, if we want to add an unbound CPU to vpar3, we can reboot vpar3:
vpar3# vparstatus
vpar3# shutdown -r
When vpar3 boots again, its kernel will create the correct entries for the unbound CPUs, which are now at
x03 and x04. The configuration becomes:
Because the unbound CPUs are at x03 and x04 and the kernel entries for vpar3 are x03 and x04, the
command to add an unbound CPU to vpar3
# vparmodify -a vpar3 -a cpu::1
now will be successful.
Virtual Partition vpar1 vpar3 vpar4
Paths of Bound
CPU(s)
x01
x02
x05 x06
x07
x08
Unbound CPU
Kernel Entries
x06
x07
x08
x03
x04
(none)
Paths of
Unbound CPUs
unbound CPUs are now at x03 and x04