VirtualDomain resource will not start in cluster

This document (7022121) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Linux Enterprise Server 11 Service Pack 4 (SLES 11 SP4)
SUSE Linux Enterprise Server 12 Service Pack 2 (SLES 12 SP2)
SUSE Linux Enterprise High Availability Extension 11 Service Pack 4
SUSE Linux Enterprise High Availability Extension 12

Situation

VirtualDomain resource immediately stops when starting in the cluster.
The VM can be brought up manually outside of the cluster.

Resolution

The cluster placement-strategy needs to be changed to "default" which ignores utilization values. By default the placement-strategy is set to "balanced".
Cluster configuration change can be done via HAWK or from command line "crm configure edit" or other preferred methods.
Change:
placement-strategy=default

Cause

When you setup a VirtualDomain resource by default it will populate the utilization parameters (cpu and hv_memory) and with the default "placement strategy = balanced", the resource will not start.
You either need to change the placement-strategy of the cluster or populate the utilization node attributes in the cluster.
This can be done using the "NodeUtilization" resource agent or manually modifying the values on each node. Documentation references below.

Additional Information

Documentation references
Section 6.4.6 Placing Resources Based on their load

Section 7.3.7 - Configuring Placement of Resources Based on Load Impact

Disclaimer

This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.