For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
LoginGet Started
DocsAPI ReferenceChangelog
DocsAPI ReferenceChangelog
    • Home
  • Getting Started
  • Infrastructure
    • GPU VMs
    • Cloud VMs
      • Create a VM
      • Instance types
      • OS images
      • Custom images
      • Resize a VM
      • Power actions
      • Networking for VMs
      • Attach volumes
      • Monitoring
    • Object Storage
    • Block Storage
  • Network & Security
    • Load Balancer
    • DNS
    • CDN
    • Firewalls
    • SSL Certificates
  • Tools
    • Backups
    • Snapshots
    • ISOs
    • SSH Keys
    • API Tokens
    • Secret Manager
    • Container Registry
  • Platform Fundamentals
    • Projects and tenancy model
    • IAM
    • Networking overview
    • Billing and usage
    • Limits and quotas
    • SLA and reliability
  • Tutorials
    • Deploy a web app
    • Host a static website with object storage
    • Run an AI model on a GPU VM
    • Set up a load-balanced architecture
    • Backup and disaster recovery
    • Multi-region deployment
  • Migration Guides
    • Migrate from AWS
    • Migrate from GCP
    • Migrate from Vultr and Linode
    • Move S3 workloads to IBEE Object Storage
    • VM image migration
  • Reference
    • Pricing
    • Regions
    • Limits
    • Error codes
    • Service level agreement
  • Support
    • Contact Support
    • Create a request
    • Troubleshooting guides
    • Visit ibee.ai
LogoLogo
LoginGet Started
On this page
  • Where to find them
  • Actions
  • Start
  • Stop
  • Reboot
  • Console
  • Delete
  • Status reference
  • CLI and API
  • Troubleshooting
  • Related pages
InfrastructureCloud VMs

Power actions

Was this page helpful?
Edit this page
Previous

Networking for VMs

Next
Built with

Power actions live behind the Actions menu on the server detail page, and as inline icons on the Cloud VMs list. Each action creates an entry in the Activity feed.

Where to find them

SurfaceAvailable actions
Server detail page → Actions menuStart · Stop · Reboot · Console · Delete
Cloud VMs list → row iconsConsole · Restart · Delete

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 but stop incurring compute charges (storage continues to be billed).

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.

Console

Opens a browser-based serial/VNC console for out-of-band access. Use it when:

  • SSH or RDP is misconfigured or blocked.
  • A firewall change locked you out.
  • The VM is booting and you want to see early-boot output.
  • You need to log in as root after losing the SSH key.

The console session is tied to your IBEE Cloud login — no separate credentials are required at the console layer, but you still need OS-level credentials to log in.

Delete

Permanently removes the VM, its root disk, and any attached ephemeral resources. The public IP is released back to the pool.

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.
  • Detach any block storage volumes you want to keep — attached volumes survive VM deletion only if explicitly detached first.
  • Note the IP if a third-party DNS provider points to it.

Status reference

StatusMeaning
ProvisioningInitial deployment in progress.
RunningVM is booted and reachable.
Stopping / StartingTransient state during a power action.
StoppedPowered off; disks retained.
RebootingRestart in progress.
ErrorThe last operation failed. Open the activity feed for details.

CLI and API

Power actions are exposed via the API. Replace <vm-id> with your server ID (visible on the detail page header):

$# Start
$ibeectl vm start <vm-id>
$
$# Stop
$ibeectl vm stop <vm-id>
$
$# Reboot
$ibeectl vm reboot <vm-id>
$
$# Delete (requires --confirm)
$ibeectl vm delete <vm-id> --confirm

Troubleshooting

VM stuck in Stopping The guest is ignoring ACPI shutdown. Wait for the force-stop timeout, or reboot to recover and stop again after the workload drains.

Console shows a blank screen Press Enter to refresh the TTY. If the screen stays blank during boot, the kernel may be hung — reboot the VM and watch from the console for early-boot errors.

Can’t delete a VM Detach any block storage volumes first, and cancel in-flight operations (a backup or snapshot in progress will block deletion).

Related pages

  • Create a VM
  • Monitoring
  • Snapshots
  • Backups