Skip to content
[bhatti]

bhatti start

Resume a stopped sandbox from its on-disk snapshot. The VM continues exactly where it left off — same processes, same memory, same network connections.

Synopsis

bhatti start <sandbox> [--force]

Description

Restores the VM from its on-disk snapshot bundle (memory.img + checkpoint.bin + manifest.json). Typical cold restore is sub-second (~380ms measured on Apple Silicon); a warm sandbox — one whose memory is still resident — resumes in ~4ms.

If a previous restore failed (for example because the underlying rootfs file was corrupt or the VMM helper couldn't be launched), the sandbox enters the unknown state and bhatti start refuses to retry by default. Pass --force to retry — useful after fixing the underlying issue.

You normally don't need to call start explicitly. Any API request — exec, file read, an HTTP request to a published URL — wakes a cold sandbox transparently before executing.

Examples

bhatti start dev

sandbox/dev started

# Retry after a previously failed restore
bhatti start dev --force

Options

| Flag | Default | Description | | ---- | ------- | ----------- | | --force | false | Retry start even if the sandbox is in an unknown state from a previously failed restore. |

See Global flags for --url, --token, --json, --timing, --data-dir.

See also