HP Integrity Essentials Global Workload Manager: Workload Management for HP Integrity Virtual Machines

15
as needed, too. Figure 4C shows the net result when gWLM activates TiCAP resources for the virtual
machines in Partition 1. In this case, the result for the virtual machines is similar to that of iCAP
activation in the previous scenario; however, the three cores in each vPar in nPartition2 remain active.
As a result, during the allotted time, more resources are active in the complex. At the same time, the
virtual machines that originally had to share CPU resources (VM1 and VM2, VM5 and VM6) now
have a whole core each.
Figure 4C - Same Complex with Redistribution of TiCAP Resources to Meet Demands
How You Enable gWLM to Use Temporary Instant Capacity: For information on how to
configure and use TiCAP, see the gWLM documentation, available from:
http://docs.hp.com/en/vse.html
For more information on configuring Temporary Instant Capacity, see the latest HP Instant Capacity
User’s Guide available at the following location (select “Network and Systems Management” and
then “Utility Pricing Solutions”):
http://docs.hp.com
Scenario 4: gWLM Maintains Virtual Machine Minimum vCPU When
Resources Are Needed Elsewhere
This scenario demonstrates how gWLM responds when managing SMP (multiprocessor) virtual
machines whose cores are needed elsewhere. Given virtual machines VM2 and VM3 of nPartition1 in
Figure 5, suppose the applications running in the virtual partitions in nPartition2 are higher priority
than those running on the virtual machines in nPartition1. If vPartition2 in nPartition2 requires another
core to meet a spike in demand, gWLM will borrow an active core from the VM Host if it can
continue to maintain the minimum configuration of vCPUs required by each of the virtual machines.