Top Ten Tips for Using Integrity Virtual Machines

7
#9 –Set Entitlements Conservatively
Symptoms: Functionality, Performance
Virtual machines may not start, displaying the message:
Warning 1: Insufficient cpu resource for guest.
These problems may prevent HPVM guest vm-name from booting.
hpvmstart: Unable to continue.
Otherwise, virtual machines may not perform as well as expected due to inadequate resource
allocation.
Prevention and Treatment
Such problems often result when using multi-CPU virtual machines (virtual SMPs). The virtual CPUs of
a virtual SMP must run on separate physical CPUs. As a result, the entitlement for the virtual SMP with
N virtual CPUs must be available on N different physical CPUs. For example, consider a single-CPU
VM with entitlement of 70% running on an Integrity server with 2 physical CPUs. A second VM with
2 virtual CPUs is defined with entitlement of 50%. This second VM will not start, even though the
aggregate available CPU entitlement is 130% (100% of one physical CPU and 30% of the other).
This is because only 30% entitlement is available on one of the physical CPUs and the virtual SMP
needs 50% on both physical CPUs.
In general, you should use the minimum or default entitlements until one or more of the VMs are not
receiving adequate CPU resources for their workloads.
Note that the default entitlement settings for a VM are different depending on whether it was created
by the CLI (hpvmcreate) or the GUI (VM Manager).
#10 – Install Versions of VMProvider and gWLM
Appropriate for Your Version of Integrity VM
Symptoms: Functionality
On the VM Host system, Integrity VM 2.0 is not compatible with older versions of HP’s Global
Workload Manager (gWLM) and Virtual Machine WBEM Provider (VMProvider). You will need
version 2.5 or later of gWLM and version 2.0 or later of VMProvider.
Prevention and Treatment
Replace older versions of gWLM with version 2.5. When installing Integrity VM (bundle T2767AC),
simultaneously install the VMProvider bundle from the Integrity VM media.