Sleep and wake a computer

Sleep pauses a computer in memory. The workload stops executing, and the computer keeps its RAM so that wake can resume it quickly.

Before you start

You need the CLI installed and signed in, a selected workspace where you have the admin or editor role, and a computer named demo. Create one if you don't have it.

Sleep needs no data disk or snapshot support, and it is not a durable backup. Persistent storage depends on the deployment's storage pool. See Computer lifecycle states for the constraints and persistence details.

Sleep

Check the computer first:

nevia status demo

The state must be ready, with no transition pending. An arrow such as ready (→ sleeping) means a transition is still running. Wait for it to finish.

Sleep ends any command running through exec, so let commands finish first if you need their results.

nevia suspend demo --wait
nevia status demo

The state is now sleeping, with no arrow. The CLI command is still called nevia suspend. It calls the API sleep route, which pauses the machine in memory. Reading status does not wake the computer.

--wait follows an operation when the API needs more time. If the wait times out, the operation keeps running. Check status before you send another lifecycle command. See the suspend command reference for wait options.

Wake

Start with demo in sleeping, with no transition pending:

nevia status demo
nevia awake demo --wait
nevia status demo

The state is now ready, with no arrow. The workload resumes from its retained memory and disk state, and you can run a new command. An exec session that ended during sleep does not reconnect.

In the console, open Computers, select demo, and choose Sleep or Wake. Wait for the state badge to show sleeping or ready.

Restart

The current build has no restart and the CLI has no restart command. Sleep and wake resume retained state without rerunning the image's startup command.