Is it true that you must create cyclical dependencies for vSphere HA Orchestrated Restart to succeed?

In vSphere High Availability (HA) orchestrated restarts, cyclical dependencies are not required for the successful functioning of the feature. Instead, vSphere HA orchestrated restart relies on the configuration of priorities and restart orders for virtual machines (VMs). This allows for a precise control over which VMs should be restarted first based on their dependency on each other.

Creating cyclical dependencies could complicate the restart process, as it introduces a loop that may prevent VMs from knowing their correct order for startup. Hence, the correct configuration approach should avoid dependencies that loop back to prior VMs in the sequence. This ensures a smooth and efficient restart process under HA conditions without the need for intricately woven cyclical dependencies.

Understanding the architecture and mechanics of HA orchestrated restarts is crucial for effective VM management and fault tolerance within a vSphere environment.