Fault - RuleViolation

Extends: VmConfigFault
See also: ClusterRuleInfo, HostSystem

Fault Description

The virtual machine if powered on, would violate an affinity/anti-affinity rule. In this case, the VM can still be powered on manually by a user who knows what they are doing, but VirtualCenter will never automatically move or power on a VM such that it triggers the violation.

Properties

Name	Type	Description
host*	ManagedObjectReference to a HostSystem	The host that the virtual machine can not be powered on without violate a rule. *Since* VI API 2.5
rule	ClusterRuleInfo	The rule that is violated. It can be an affinity or anti-affinity rule. *Since* vSphere API 4.0
Properties inherited from VmConfigFault
None
Properties inherited from VimFault
None
Properties inherited from MethodFault
dynamicProperty, dynamicType, faultCause, faultMessage

*May not be present
Show WSDL type definition

         <complexType xmlns="http://www.w3.org/2001/XMLSchema" xmlns:vim25="urn:vim25" name="RuleViolation">
            <complexContent>
               <extension base="vim25:VmConfigFault">
                  <sequence>
                     <element name="host" type="vim25:ManagedObjectReference" minOccurs="0"/>
                     <element name="rule" type="vim25:ClusterRuleInfo" minOccurs="0"/>
                  </sequence>
               </extension>
            </complexContent>
         </complexType>