Hubfly spaceDocs
Console

Box · Guide

Power, resize and operations

Understand power controls, capacity changes, and the operation states that make Box actions reliable.

Power controls

Start powers on a stopped Box. Shutdown and reboot request graceful guest actions. Force stop cuts power when the guest will not respond.

  • Graceful shutdown and reboot do not silently escalate to force stop. If the guest hangs, inspect the operation and deliberately choose force stop if needed.
  • Save application data and use an orderly shutdown before planned maintenance. A force stop can interrupt filesystem writes.

Resize CPU, memory and root disk

A resize can request vCPUs, memory in MiB, and rootDiskGib. Choose try_live_then_restart, restart_now, or next_boot when calling the API.

  • Live CPU and memory growth is limited by the maximum topology reserved when the Box was created. Reducing CPU or memory requires a restart.
  • Current, desired, and next-boot values can differ while an operation is in progress. Read runtime configuration and operation status before reporting a change as applied.
  • Root disks grow only. Automatic filesystem growth is limited to supported managed Linux root layouts; verify the guest filesystem capacity after resizing.

Follow asynchronous work

Mutations return an operation ID. Use the project operations list to see phase, progress, and the terminal result.

  • Succeeded means host work completed and Dashboard reconciled the observed resource. Failed means inspect the operation error and resource state before retrying.
  • Partial means some cleanup or change happened. A partial delete needs finish-cleanup on that operation; do not create a replacement resource based on a guess.
  • Cancellation is supported for certain pending operations. It is not a rollback guarantee for work already applied.

Delete safely

Deleting a Box starts checkpointed cleanup of its VM and related host state. It can take time and may require recovery if any step fails.

  • Back up data first and detach or account for volumes you need to keep. Deleting a Box is not a backup strategy.
  • Wait for the delete operation to finish. If it ends partial, call finish-cleanup on the operation rather than repeatedly issuing delete.

Automating this workflow

See the matching Box API endpoints for exact request fields and response schemas. Host operations can continue after an API request returns.

Back to the Box guide · All Box API groups

Something unclear or out of date? Emailsupport@hubfly.spaceBack to top