Note: Automatic startup is not supported when the virtual machine is vSphere HA enabled.
This issue occurs if the global host setting for AutoStart is disabled on the ESXi host.
In VMware vSphere, the AutoStart feature follows a hierarchy:
Global Host Setting: Acts as a master switch (SystemDefaults).
Individual VM Setting: Defines the specific behavior for that VM.
If the Global Host Setting is set to "Disabled," the host will ignore all individual VM startup configurations. This can be counterintuitive as the UI may still allow the configuration of individual VMs even when the global feature is toggled off.
To resolve this issue, AutoStart must be enabled at the host level.
Option 1: Using the vSphere Client (Recommended)
"Automatically start and stop the virtual machines with the system" is selected."Automatic ordered" or "Automatic" Startup group. (If VMs are not seen in the list, follow the below steps)"Move to" option to move the VMs to the desired group Option 2: Using the ESXi Command Line (CLI)
Verify if the configuration is active without rebooting the host by running the following command: vim-cmd hostsvc/autostartmanager/autostart
If configured correctly, the host will attempt to trigger the startup flow.
If global settings are enabled, the "Recent Tasks" pane will show a failure message that the VM is already in the requested state.
If global settings are disabled, no tasks will be created, and no errors will be generated.