For the complete documentation index, see llms.txt. This page is also available as Markdown.

VM Lifecycle and States

A VM moves through a series of states from creation to deletion. The current state is reported in the status field of the VM object, which you can retrieve with GET /v3/flexVM/clouds/{cloudUuid}/vms/{vmUuid}.

VM states

Status
Description

provisioning

The VM is being created and resources are being allocated on a Node.

created

The VM has been created but has not yet started.

starting

The VM is booting.

running

The VM is powered on and operational.

stopping

The VM is shutting down.

stopped

The VM is powered off. Its disks are retained.

paused

The VM is suspended, with its state held in memory.

failed

The VM entered an error state during provisioning or operation.

deleting

The VM is being removed and its disks are being wiped.

deleted

The VM has been removed.

Typical lifecycle

A newly created VM transitions through provisioningcreatedstartingrunning.

From running, you change a VM's state by issuing commands (stop, reboot, and so on) — see Managing VMs. Stopping a VM moves it through stoppingstopped; starting it again returns it through startingrunning.

Deleting a VM moves it through deletingdeleted and immediately wipes its local LVM disk and any NVMe passthrough disk. See Creating and Deleting a VM.

A VM in the failed state cannot be recovered. Delete it and create a new one. If failures persist, contact i3D.net support.

Last updated

Was this helpful?