Power actions
Power actions live behind the Actions menu on the VM detail page, and as inline icons on the Cloud Virtual Machines list. Each action creates an entry in the Activity feed.
Where to find them
Actions that don’t apply to the VM’s current state are disabled — for example, Start on a running VM. Members with read-only access don’t see the write actions.
Actions
Start
Powers on a stopped VM. Boot completes when the VM appears as Running in the list and the IP responds to traffic.
Stop
Gracefully shuts down a running VM by signalling ACPI poweroff to the guest. The VM transitions through Stopping to Stopped. Stopped VMs retain their disks, IP, and configuration. On Hourly billing, stopped VMs stop incurring compute charges (storage continues to be billed); Monthly and Yearly commitments are fixed for the commitment term.
If the guest does not honor the ACPI signal, the platform will force power-off after a timeout. Long-running workloads should drain or quiesce before you stop the VM.
Reboot
Restarts the VM in place. This is equivalent to a reboot issued inside the guest — the kernel boots fresh, but disks, IP, and plan stay the same. Use Reboot after kernel upgrades or to clear a stuck process when SSH is unresponsive but the host is healthy. The list’s Restart icon does the same.
Console
Browser console access isn’t available in the portal yet — the Console control is shown as Coming soon. Until it ships, use these instead:
- Sign-in details — Overview → Connection Details shows the SSH command, or the username and password for password-based Linux VMs and Windows (RDP).
- Lost SSH access (Linux) — on Settings → Access, add another saved SSH key, or reset the OS password and turn on password login. The VM must be running.
- Locked out by a firewall — fix the firewall group’s rules on the Firewalls page.
- Guest won’t boot — reboot the VM, or create a new VM from a snapshot or backup.
Delete
Permanently removes the VM and its root disk. Open Delete from the Actions menu or the list’s row icon. In the Delete Virtual Machine dialog:
-
Type the VM name exactly to confirm (use the copy button next to the name).
-
Attached data volumes — if any are attached, the dialog warns that they will be detached automatically. The volumes and their data are kept in Block Storage. Unmount them inside the VM first to avoid filesystem corruption.
-
Public IP — if the VM has a public IP that isn’t already a Reserved IP, choose whether to keep it:
- Check Reserve public IP <address> to keep the address as a Reserved IP named after the VM. Reserved IP billing continues.
- Leave it unchecked to release the address.
If the address is already a Reserved IP, the dialog confirms it will be kept — it’s detached from the VM and stays in Reserved IPs.
Delete is irreversible. Snapshots and backups taken before deletion are retained according to their own retention policy and can be used to recover into a new VM, but the original VM cannot be restored in place once deleted.
Before deleting, consider:
- Take a final snapshot if you might need the data.
- Unmount attached block storage volumes inside the guest.
- Note the IP if a third-party DNS provider points to it, or reserve it in the delete dialog.
Status reference
CLI and API
Start, stop, reboot, and delete are exposed through the public API and the
ibee CLI. Replace VM_ID with the ID from ibee vms list:
Browser console access isn’t available in the portal, the CLI, or the public API yet.
Troubleshooting
VM stuck in Stopping
The guest may be ignoring the shutdown request. Wait a few minutes, then check the Activity feed. If it doesn’t recover, contact IBEE support.
Delete or Reboot is disabled Another operation (for example a backup, snapshot, or resize) is in progress — the row icons show Operation in progress…. Wait for it to finish, then try again.
Can’t connect after a change Browser console access isn’t available yet. Check Overview → Connection Details, the VM’s firewall group, and Settings → Access, as described under Console.
