[SOLVED] Unable to start VM

michelvdriel

Member
May 17, 2020
11
0
21
44
Hi Guys,

I am unable to start one of my (Windows 10) VM's and any help is greatly appreciated.

This morning I turned the VM of through Windows itself.
When I tried starting it up again this evening it gave me an error: ERROR: VM is locked (suspending)

I unlocked it by executing QM unlock 112

After this I get the following error message:
Code:
activating and using 'VM2:vm-112-state-suspend-2020-05-02' as vmstate
can't deactivate LV '/dev/VM2/vm-112-disk-0':   Logical volume VM2/vm-112-disk-0 in use.
can't deactivate LV '/dev/VM2/vm-112-state-suspend-2020-05-02':   Logical volume VM2/vm-112-state-suspend-2020-05-02 in use.
TASK ERROR: start failed: command '/usr/bin/kvm -id 112 -name Win10-training -chardev 'socket,id=qmp,path=/var/run/qemu-server/112.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -chardev 'socket,id=qmp-event,path=/var/run/qmeventd.sock,reconnect=5' -mon 'chardev=qmp-event,mode=control' -pidfile /var/run/qemu-server/112.pid -daemonize -smbios 'type=1,uuid=3d9a9a73-dba8-4943-a981-86b597c5272a' -smp '16,sockets=4,cores=4,maxcpus=16' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000,splash=/usr/share/qemu-server/bootsplash.jpg' -vnc unix:/var/run/qemu-server/112.vnc,password -no-hpet -cpu 'kvm64,+lahf_lm,+sep,+kvm_pv_unhalt,+kvm_pv_eoi,hv_spinlocks=0x1fff,hv_vapic,hv_time,hv_reset,hv_vpindex,hv_runtime,hv_relaxed,hv_synic,hv_stimer,hv_ipi,enforce' -m 32768 -device 'pci-bridge,id=pci.1,chassis_nr=1,bus=pci.0,addr=0x1e' -device 'pci-bridge,id=pci.2,chassis_nr=2,bus=pci.0,addr=0x1f' -device 'vmgenid,guid=3786dfad-ce79-4221-8479-58594e4f3b61' -device 'piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2' -device 'usb-tablet,id=tablet,bus=uhci.0,port=1' -device 'VGA,id=vga,bus=pci.0,addr=0x2' -device 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3' -iscsi 'initiator-name=iqn.1993-08.org.debian:01:237a6bf61244' -drive 'file=/dev/VM2/vm-112-disk-0,if=none,id=drive-ide0,format=raw,cache=none,aio=native,detect-zeroes=on' -device 'ide-hd,bus=ide.0,unit=0,drive=drive-ide0,id=ide0,bootindex=100' -drive 'if=none,id=drive-ide2,media=cdrom,aio=threads' -device 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200' -netdev 'type=tap,id=net0,ifname=tap112i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown' -device 'e1000,mac=D2:22:CD:AE:C3:51,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300' -rtc 'driftfix=slew,base=localtime' -machine 'type=pc+pve0' -global 'kvm-pit.lost_tick_policy=discard' -loadstate /dev/VM2/vm-112-state-suspend-2020-05-02' failed: got timeout

I'm unsure how to proceed. What I did note was the suspended state that was referenced. The machine was issued a clean poweroff command.

Any ideas?

Michel
 
Well... no idea why, but: this morning I tried again to no avail. Then I made an extra backup of my VM. During the backup my VM was started by proxmox and is working as usual.
 

About

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!