The Boot Settings page allows you to configure the VM State and Boot Order at the environment level. 

In the Environment Details page, under the Edit Environment section on the right, click Boot Settings (previously Boot Order) to view a page detailing the VMs, Boot Orders, and their current VM States. 

Update the Boot Order

In the Boot Order field, select the order you want the VMs to boot.

You can boot all of the virtual machines together or organize them into booting groups.

VMs can be grouped into a maximum of three groups, and each booting group can have 1-25 VMs. By default, all VMs will be in Group 1.

- You can set up to three booting groups, which will boot consecutively.

- When customizing the VMs’ boot order, the environment's spin-up time may increase, as VM booting groups will spin up consecutively.

Booting order example: Let’s say you utilize three booting groups. The first group contains one virtual machine, the second group contains two virtual machines, and the third group contains three virtual machines. In this case, the virtual machines in Groups 2 and 3 will not begin booting until the first group has completed. The two virtual machines in the second group will boot simultaneously.

Update the VM State

In case the memory restoration of a VM is not required, 'Power Off' as a VM state is recommended to optimize the VMs resume time.

In the VM State field, you can set the ‘VM State’ per each VM in a Blueprint by selecting one of the following options:

• Power Off - VMs will be powered off, and when resumed, will power back on without RAM state.
• Suspend - VMs will suspend and resume with RAM state.

The default setting will be Suspend. The default value per Blueprint can be configured at a project level. See Configuring the Default VM State for more information.

SaaS template states cannot be edited and must remain in a Suspend state.

Click Save to save your changes. 

Once saved, a notification will appear, and the state of the machine will change to the selected status. This status can be seen in the Environment Settings and Viewer.

The VM state will still be enforced even if the end user chooses to suspend their environments or if an automatic suspension policy is in effect.

Saving your changes will only impact the current environment instance. In order to commit the changes to future environments, you will need to take a snapshot through the Environment Details page. 

The VMs List will display the current state of VMs, reflecting whether they are powered off or suspended. Taking a snapshot will save the current boot settings.

Viewing the VM State in the Snapshot

Snapshots will display the VM State at the time the snapshot was created on the Snapshot Details page under the VM List.