qm-resume

Resume a specific virtual machine

$ qm resume [vm_id]

$ sudo qm resume [vm_id] --skiplock true

qm resume VMID [OPTIONS]

VMID
    The unique numeric ID of the virtual machine to resume.

--skiplock
    boolean Skip lock check (deprecated)

The `qm-resume` command is used within the Proxmox Virtual Environment (PVE) to resume a suspended virtual machine (VM). When a VM is suspended, its current state is saved to disk, allowing it to be quickly resumed later. This command takes the VM ID as an argument and restores the VM from its saved state, effectively bringing it back online with minimal downtime. It's a crucial tool for managing VMs in a PVE cluster, enabling administrators to pause and restart VMs as needed for maintenance or resource optimization.

Suspending instead of stopping a VM allows applications and processes running within the VM to continue from where they left off, preserving data and session states. The process involves reading the saved state and restoring it to the VM’s memory and CPU, effectively returning the VM to its previous operating condition.

Keep in mind that the VM must have been previously suspended using the `qm suspend` command before it can be resumed using `qm-resume`. The resume operation requires resources (CPU, memory, storage) to be available on the PVE host. If insufficient resources exist, the command may fail or the VM may start with reduced performance until adequate resources are allocated.

The VM must have been previously suspended using `qm suspend` for `qm resume` to work. Ensure sufficient resources (CPU, memory) are available on the Proxmox host before resuming. Resuming a VM may take some time depending on the size of the saved state and the available I/O bandwidth.

Returns 0 on success, and non-zero on failure.

Resuming a VM requires resources. Be mindful of your PVE cluster's available CPU, memory, and I/O capacity before resuming a large number of VMs simultaneously. Overloading the system can lead to performance degradation or even system instability.

If the resume operation fails, check the PVE host's system logs for error messages. Common causes of failure include insufficient resources, corrupted saved state files, or network connectivity issues.

qm(1), qm suspend(1), qm stop(1), qm start(1)