Skip to main content

​
vers resume

Resume a paused Vers VM.

​
Usage

vers resume                    # Resume current HEAD VM
vers resume [vm-id|alias]      # Resume specific VM

​
How it works

The resume command:
  1. VM resolution: Uses HEAD VM if no identifier provided, otherwise resolves the specified VM/alias
  2. State update: Makes an API call to set the VM state to “Running”
  3. Progress display: Shows progress during the resume operation
  4. Confirmation: Displays success message and current VM state

​
What happens when you resume

  • VM state changes to “Running”
  • Suspended processes can continue execution
  • Network connections become available for SSH access
  • Resources are allocated back to the VM

​
Error handling

​
VM not found

vers resume nonexistent-vm
Error: failed to find VM: not found

​
No HEAD VM

vers resume
Error: no VM ID provided and HEAD not found
Solution: Run vers run to create a VM or specify a VM ID directly.

​
API failures

vers resume vm-abc123
Error: failed to resume VM 'vm-abc123': connection timeout

​
Prerequisites

  • VM must exist and be accessible
  • VM should typically be in “Paused” state for resume to be meaningful
  • Network connectivity to perform the state update

​
Common Patterns

​
Resume a specific paused VM

vers resume my-dev-vm

​
Resume every paused VM

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

​
Resume and connect in one flow

vers resume my-dev-vm && vers connect my-dev-vm

​
See Also