HP-UX Virtual Partitions Administrator Guide (includes A.05.09) (5900-2188, March 2012)

x06x06x06Unbound CPU Kernel Entries
x07x07x07
x08x08x08
x06, x07, x08Paths 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 vPars Monitor will assign the remaining three CPUs at hardware paths x06, x07, and x08:
vpar4Virtual Partition
x06Paths of Bound CPU(s)
x07
x08
(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:
vpar4vpar3vpar1Virtual Partition
x06x05x01Paths of Bound CPU(s)
x07x02
x08
(none)x06x06Unbound CPU Kernel Entries
x07x07
x08x08
unbound CPUs are now at x03 and x04Paths 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:
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.
Cause 277