VM Bugs


New Member
Jun 27, 2023
Hello. This issue makes me so irritated and confused all the time.

There is this stupid thing that prevents me from shutting down and restarting VMs:
"trying to acquire lock...
TASK ERROR: can't lock file '/var/lock/qemu-server/lock-103.conf' - got timeout"

"TASK ERROR: VM quit/powerdown failed - got timeout"

So how tf do i kill a VM to completely force it to shutdown? i need to delete this VM to fix disk error on the node Disk, as couple of my VMS located on Disk 1 are down because of full Node Disk, while i have 2 other disks and those VMs works fine. But i can't release any disk space on disk 1 until i have got rid of 1 VM.

Is there any way arround the "lock" issue to force a kill process or anything of the VM? the reset action on proxmox VE works, but it doesn't shut a VM down? and even when the reset are complete, i still can't acquire lock.

I suppose it can't lock file because another process is using the file right? which i suppose must be the VM itself using it, so how tf do i force kill the VM process of a specific VM?
I fixed my issue. For those who wonder i used SSH to kill the VM process, found the process using following:
ps aux | grep "/usr/bin/kvm -id VMID"

And killing the machine using:
kill -9 PID

My issues are now solved.


The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!