Power actions
Power actions are the on/off switches for a VM: Start turns it on, Stop shuts it down, Reboot restarts it, and Delete removes it for good. They work the same way for Cloud VMs and GPU VMs. Each action runs in the background; the VM’s status shows what is happening, and every action is recorded in Activity logs.
Which action to use
A stopped VM is billed. Billing runs from the moment a VM is created until it is deleted, whether it is running or stopped. Stopping a VM is not a way to save money.
How it works
- You choose an action. IBEE accepts it and starts an operation in the background.
- The VM shows a temporary status: Starting, Stopping, Rebooting or Deleting.
- When the operation finishes, the status becomes Running or Stopped, or the VM disappears from the list after a delete. If it fails, the status shows Error and Activity logs give the reason.
Before you begin
- You need write access to the workspace. Read-only members don’t see the Actions menu or the row icons.
- Only one operation can run on a VM at a time. Wait for a backup, snapshot, restore or resize to finish first.
- Before you stop or delete, save your work and stop applications cleanly (for example
sudo systemctl stop postgresql). - Before you delete, unmount attached volumes inside the VM (
sudo umount /mnt/volume_name) so their filesystems stay clean.
Run an action in the portal
Choose the action
Click Actions in the top right, then Start, Stop, Reboot or Delete. Actions that don’t fit the VM’s current status are greyed out: for example, Start on a running VM, or Reboot on a stopped one. Start, Stop and Reboot run straight away, without a confirmation.
You can also use the icons at the end of each row in the Cloud Virtual Machines list: Restart (the same as Reboot) and Delete.
What each action does
Start
Powers on a Stopped VM. Disks, IP addresses and settings are as you left them.
Stop
Asks the operating system to shut down cleanly, as if you pressed the power button once. If the VM is still on after 30 seconds, IBEE switches it off forcibly, which is like pulling the plug: unsaved data can be lost. Shut down long-running work yourself first if it needs more time.
A stopped VM keeps its disks, IP addresses, firewall group and settings, and is still billed.
Reboot
Restarts a Running VM. The operating system restarts fresh; disks, IP address and plan stay the same. Use it after kernel updates, or when the server stops responding but is still on.
Console
Browser console access isn’t available yet; the control shows Coming soon. Until it ships:
- Sign-in details are under Overview → Connection Details.
- Lost SSH access (Linux): on Settings → Access, add another saved SSH key, or reset the password and turn on password login. The VM must be running.
- Locked out by a firewall: fix the rules of the VM’s group on the Firewalls page.
- The VM won’t boot: create a new VM from a snapshot or backup.
Delete
Permanently removes the VM and its root disk. In the Delete Virtual Machine dialog:
-
Type the VM name exactly to confirm. The dialog says: “This action cannot be undone.”
-
If volumes are attached, the dialog warns that they “will be detached automatically”. The volumes and their data are kept in Block Storage, and stay billed until you delete them.
-
If the VM has an automatically assigned public IP, choose what happens to it:
- Tick Reserve public IP <address> to keep the address as a Reserved IP. “Reserved IP billing continues.”
- Leave it unticked to release the address. You may not get it back.
If the address is already a Reserved IP, it is detached and stays in Reserved IPs.
-
Click Delete VM.
Deleting a VM also stops its backup schedule. Existing backups and snapshots are kept, and billed, until you delete them under Tools → Backups and Tools → Snapshots. You can use them to create a new VM.
Delete can’t be undone. The VM and its root disk are gone. Take a snapshot first if you might need anything on it, and note the IP address if DNS records point to it.
A VM on a Monthly commitment can’t be deleted until the commitment ends: the Delete button shows “Committed until <date>. Contact support to delete it.”
CLI and API
Use the VM ID from ibee vms list. GPU VMs use ibee gpus instead of ibee vms.
To keep the address instead, tick Reserve public IP in the portal, or pass --public-ip-action reserve with the Reserved IP’s billing entry in --reserved-ip-billing-catalog.
With the API, every power action is a POST with an X-Idempotency-Key header (a unique value you make up, so a retried request isn’t run twice):
The answer is 202 Accepted with an operation_id. Poll GET /compute/operations/{operation_id}?workspace_id=... until status is succeeded, failed, cancelled or timed_out. If your request times out, read the operation; don’t send the action again.
GPU VMs use the same paths under /compute/gpu-vms. A delete of a VM with an automatically assigned public IP needs a JSON body with public_ip_action: release, or reserve together with reserved_ip_billing_catalog (the Reserved IP’s billing entry, with its sku_id) and an optional reserved_ip_label of up to 120 characters. Without it, the API answers 400.
That field applies only to an automatically assigned IP. If the VM’s IP is already a Reserved IP, send no body: release and reserve are both refused with 400. The IP stays in your workspace and keeps billing until you release it.
Status reference
Limits and timing
Troubleshooting
Related pages
- Resize a VM
- Create a snapshot: before you delete
- Reserved IPs: keep an address after delete
- Monitoring
