​

vers pause

​

Synopsis

vers pause                           # Pause current HEAD VM
vers pause <vm-id>                   # Pause specific VM

​

Description

​

Basic Usage

​

Pause Current VM

vers pause

​

Pause Specific VM

vers pause vm-abc123

​

What Happens When You Pause

• State Preserved: All memory, running processes, and open files are saved
• Resources Released: CPU and active memory are freed up
• Quick Resume: VM can be quickly resumed exactly where it left off
• Network Disconnected: SSH connections are terminated but can be re-established after resume

​

Understanding Output

vers pause vm-abc123
Pausing VM 'vm-abc123'...
✓ VM 'vm-abc123' paused successfully
VM state: Paused

• Which VM was paused
• The operation completed successfully
• The current state of the VM

​

VM State Requirements

​

Can Pause

• Running VMs can be paused
• VMs with active SSH connections (connections will be terminated)
• VMs with running processes (processes are suspended)

​

Cannot Pause

• Already Paused VMs (no effect, but not an error)
• Stopped VMs (different state, use resume for paused VMs)

​

Error Handling

​

VM Not Found

vers pause vm-nonexistent
# Error: failed to pause VM 'vm-nonexistent': not found

​

No Current VM

vers pause
# Error: no VM ID provided and HEAD not found

​

Already Paused

vers pause vm-already-paused
# May show success but VM remains in paused state

​

Tips

• Use vers status to see which VMs are paused
• Pausing frees resources for other VMs to run
• Long-running scripts will pause mid-execution and resume when VM resumes

​

Common Patterns

​

Pause all running VMs to save cost

for vm in $(vers status --format json | jq -r '.[] | select(.state == "Running") | .vm_id'); do
  vers pause "$vm"
done

​

Pause HEAD before stepping away

vers pause              # pauses HEAD
# ...come back later...
vers resume             # resumes HEAD

​

See Also

• vers resume - Resume paused VMs
• vers status - Check VM states
• vers connect - Connect to running VMs