Tutorials

Cold-mode recovery

Pause, save, restore, and wake sandboxes from backend-specific snapshot state.

Cold mode lets a sandbox stop consuming a running VM while keeping recoverable state.

Firecracker sealed pause/resume

cargo run -- pause agent-sandbox
cargo run -- snapshot ls
cargo run -- resume agent-sandbox

Firecracker pause/resume writes sealed instance state and verifies it before resume. This is the local mvm primitive.

Full-VM memory checkpoints

cargo run -- checkpoint create agent-sandbox --class vm-full
cargo run -- checkpoint restore agent-sandbox --name <checkpoint-name>

Full-VM checkpoints capture full machine state. They are currently unavailable through the selectable workload runners; request them only when mvmctl doctor reports a compatible backend and capability. mvm records the checkpoint content hash in the audit chain when the launch plan and host signer are available, and restore records whether the content matched the prior chain entry.

Security checklist

Snapshot artifacts may contain guest memory, files, credentials, tokens, and browser/session state.
Restore support is backend-specific.
A restore is not a security boundary; it is a lifecycle transition.
Deleting a snapshot is not the same as proving physical erasure.
Published latency numbers must state backend, artifact, and readiness boundary.