Table of Contents
Advertisement
Where there is unused processor capacity in underutilized Shared-Processor Pools, the
micro-partitions within the Shared-Processor Pools cede the capacity to the POWER
Hypervisor.
In busy Shared-Processor Pools where the micro-partitions have used all of the Entitled Pool
Capacity, the POWER Hypervisor will allocate additional cycles to micro-partitions if all of the
following conditions are met:
The Maximum Pool Capacity of the Shared-Processor Pool hosting the micro-partition has
not been met.
The micro-partition is uncapped.
The micro-partition has enough virtual-processors to take advantage of the additional
capacity.
Under such circumstances, the POWER Hypervisor allocates additional processor capacity to
micro-partitions on the basis of their uncapped weights, independent of the Shared-Processor
Pool hosting the micro-partitions.
Dynamic adjustment of Maximum Pool Capacity
The Maximum Pool Capacity of a Shared-Processor Pool, other than the default
Shared-Processor Pool
0
or CLI.
Dynamic adjustment of Reserve Pool Capacity
The Reserved Pool Capacity of a Shared-Processor Pool, other than the default
Shared-Processor Pool
0
CLI.
Dynamic movement between Shared-Processor Pools
A micro-partition can be moved dynamically from one Shared-Processor Pool to another
using the HMC and either the GUI or CLI. Because the Entitled Pool Capacity is partly made
up of the sum of the entitled capacities of the micro-partitions, removing a micro-partition from
a Shared-Processor Pool will reduce the Entitled Pool Capacity for that Shared-Processor
Pool. Similarly, the Entitled Pool Capacity of the Shared-Processor Pool that the
micro-partition joins will increase.
Deleting a Shared-Processor Pool
Shared-Processor Pools cannot be deleted from the system, but they can be deactivated by
setting the Maximum Pool Capacity and the Reserved Pool Capacity to zero. By doing so, the
Shared-Processor Pool will still exist but will not be active. You can use the HMC interface to
deactivate a Shared-Processor Pool. Be aware that a Shared-Processor Pool cannot be
deactivated unless all micro-partitions hosted by the Shared-Processor Pool have been
removed.
Live Partition Mobility and Multiple Shared-Processor Pools
A micro-partition can leave a Shared-Processor Pool due to PowerVM Live Partition Mobility.
Similarly, a micro-partition can join a Shared-Processor Pool in the same way. When
performing PowerVM Live Partition Mobility, you are given the opportunity to designate a
destination Shared-Processor Pool on the target server to receive and host the migrating
micro-partition.
, can be adjusted dynamically from the HMC using either the GUI
, can be adjusted dynamically from the HMC using either the GUI or
Chapter 3. Virtualization
107
Advertisement
Table of Contents
