[SOLVED] PVE 7. unclocking VM's still tricky

[diversity]

root@pverdrmain:/etc/pve# qm unlock 105
trying to acquire lock...
can't lock file '/var/lock/qemu-server/lock-105.conf' - got timeout
root@pverdrmain:/etc/pve#

tried to shut down a VM but it got stuck. So I wanted to 'stop' it but it got a can't get lock error.

I tried searching and found the above command. Did not seem to help.

Any chance that the proxmox code will get more power over locked VM's?

 

[Stefan_R]

A VM stuck in a "locked" mode means something is fundamentally gone wrong. No, this will always stay as an advanced "yes I know what I'm doing" feature.

In your case, the unlock command saw that some other task was still accessing the config file. Stop any other tasks on this VMID (like, a restore or the "stop" task) by double-clicking them in the task list at the bottom of the GUI and clicking "Stop". Then the command you posted should work in removing the lock.

Keep in mind that your VM is now in an undefined state, with no guarantees - it's up to you to ensure it is actually safe to 'unlock' that VM.