Overview
After creating a VM, you can control its lifecycle with start, stop, and reboot operations. These actions are performed via the API using POST requests to the VM’s action endpoint.Prerequisites
Stop a VM
Stop a running VM to pause its execution while retaining all resources:Stopped VMs retain their resources (CPU, RAM, storage) and IP address. You are still billed for reserved resources while the VM is stopped.
passive when stopped.
Start a VM
Start a stopped VM to resume its execution:active once fully booted.
Reboot a VM
Reboot a running VM to restart the operating system:Reboot performs a graceful restart. The VM briefly transitions through boot states before returning to
active.VM Status Reference
| Status | Description | Billable |
|---|---|---|
active | Running and accessible | Yes |
passive | Stopped, resources reserved | Yes |
provisioning | Being created | Yes |
booting | Starting up | Yes |
initiating | Initial setup | Yes |
finalizing | Shutting down | Yes |
failure | Failed operation | No |
unknown | Unhandled state | No |
Check VM Status
Retrieve the current status of a VM:List All VMs
View all VMs in your account:Next Steps
- Resize VMs — Scale CPU and RAM
- Delete VMs — Remove VMs permanently
- API Reference: VM Actions — Full API specification