Search This Blog

Friday, May 30, 2014

HP-UX 11i - Instant Capacity: icapmodify Fails to Add Cores to a vPar on a GiCap


Issue
A GiCap group is present with all the required sharing rights and members already configured and have previously been able to activate and deactivate cores from any member of the group; however, now trying to add two additional cores to one of the virtual partitions (vPar) and getting the following error:

# icapmodify -a 2

ERROR: 2 cores are required to fulfill this request.
Only 0 cores are available.

ERROR: Unable to satisfy the request. 3 cores are still active in
this virtual partition.

Solution
According to the vparstatus output below, the maximum and minimum number of cores that can be assigned to the vpar in question named vpar1 are 1 and 3 respectively. In addition, the number of cores currently assigned to the same vpar is 3; therefore, it has reached its maximum number of cores.

# vparstatus
[Virtual Partition]
Boot
Virtual Partition Name State Attributes Kernel Path Opts
====================== ===== ========== ======================= =====
vpar1                   Down Dyn,Manl,Nsr /stand/vmunix
vpar2                   Down Dyn,Manl,Nsr /stand/vmunix
[Virtual Partition Resource Summary]

CPU Num Num Memory Granularity
Virtual Partition Name Min/Max CPUs IO ILM CLM
============================== ======= ==== ==== ==========
vpar1                   1/ 3    3    3 1024 1024
vpar2                   1/ 4    1    3 1024 1024
...

If additional cores need to be assigned to a vpar that has already reached it maximum number of cores, this limit needs to be increased at least by the number of cores we need to add. For example, if two additional cores are going to be assigned to vpar1 above, the max number of cores needs to be set to 5. This can be acomplished by running:

# vparmodify -p vpar1 -m cpu:::1:5

After this change was applied to the target vpar, the icapmodify command succeeded in assigning the two additional cores.

No comments:

Post a Comment