qm-reset

Reset a virtual machine

$ qm reset [vm_id]

$ qm reset --skiplock [true] [vm_id]

qm reset [OPTIONS]

    Required. The numeric ID of the virtual machine to reset. VMIDs are unique within a Proxmox VE cluster.

--skiplock
    Skips checks if the VM is locked. Use with extreme caution.

The `qm reset` command forcibly resets a Proxmox Virtual Environment (PVE) virtual machine. This command is equivalent to pressing the reset button on a physical server. It should be used only as a last resort when a VM is unresponsive and cannot be shut down cleanly using `qm shutdown` or `qm stop`. It should be avoided whenever possible because it can potentially lead to data corruption or inconsistencies within the guest operating system. The command sends a signal to the VM's process to restart it immediately. It's important to understand the potential risks associated with using `qm reset` before executing it.

Using `qm reset` can lead to data loss and inconsistencies within the guest operating system. It is strongly recommended to try `qm shutdown` or `qm stop` first. Using `--skiplock` bypasses safety mechanisms, increasing the chance of errors, use it with extreme caution.

If `qm reset` fails, it might indicate a deeper problem with the VM or the Proxmox VE host. Check the Proxmox VE logs (`/var/log/pveproxy/access.log`, `/var/log/syslog`, `/var/log/pvedaemon/qemu-server.log`) for more detailed error messages. It might be necessary to investigate the underlying KVM process directly.

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