HP-UX Workload Manager User's Guide

Integration with other products

Integrating with HP Integrity Virtual Machines (Integrity VM)

Appendix D 409

Running WLM on an Integrity VM Host

To run WLM on the Integrity VM Host, you must use a strictly

host-based configuration—a WLM configuration designed exclusively for

moving cores across HP-UX Virtual Partitions or nPartitions, or for

activating Temporary Instant Capacity (TiCAP) or Pay per use (PPU)

cores. (WLM will not run with FSS groups or PSETs on Integrity VM

Hosts where guests are running.) In addition, ensure that the minimum

number of cores allocated to a WLM host is greater than or equal to the

maximum number of virtual CPUs (vCPU count) assigned to each VM

guest. Otherwise, VM guests with a vCPU count greater or equal to

WLM’s minimum allocation could receive insufficient resources and

eventually crash. For example, if an Integrity VM host has 8 cores and

three guests with 1, 2, and 4 virtual CPUs, respectively, your WLM host

should maintain an allocation of at least 4 cores at all times. You can

achieve this by using the WLM hmincpu keyword.

Running WLM within an Integrity VM (guest)

To run WLM within an Integrity VM, you cannot use Instant Capacity,

Pay per use, and vPar integration. However, guests will take advantage

of cores added to the Integrity VM Host by Instant Capacity, Temporary

Instant Capacity, and Pay per use.

As noted previously, WLM must continue allocating at least as many

cores as the maximum number of virtual CPUs in any VM guest on the

system. In addition, specify a WLM interval greater than 60 seconds.

This helps ensure a fair allocation of CPU resources for FSS groups.

For more HP Integrity VM information

For more information on HP Integrity VM, see the following Web site and

navigate to the "Solution components" page: