The HA dev team would like to better understand why customers are using VM restart priority of "disabled".
Some specific questions:
- In what scenarios are you/customers setting the VM restart priority to "Disabled"?
- In these scenario(s), is VM/App monitoring ever enabled? Note, VM/App monitoring is turned off by default
- If you/customers are setting restart-priority=disabled to keep a VM on a specific host, could a required VM-to-host rule be used instead? This would allow HA to restart the VM when the host comes back up after a failure.
BACKGROUND:
What is "Vm Restart Priority" setting? In a vsphere HA cluster, if a host fails and its VMs need to be restarted, the restart order can be controlled using "Vm Restart Priority"Setting. The values for this setting are: Disabled, Low, Medium (the default), and High. If you select "Disabled", vSphere HA is disabled for the virtual machine, which means that it is not restarted on other ESXi hosts if its host fails. The Disabled setting is ignored by the vSphere HA VM/Application monitoring feature since this feature protects virtual machines against operating system-level failures and not virtual machine failures.
Reference: