VM Start failed: command '/usr/bin/kvm after the VM hibernated

Perrocatalan

New Member
Aug 20, 2024
1
0
1
Hello,

I have problems with two VM after I put them to Hibernate they never started again. The first problem was that both VM got locked, after I read in this forum, I found a code to unlock those VM

qm unlock 101

qm unlock 103

With those VM unlocked I tried to start and both present this error

TASK ERROR: start failed: command '/usr/bin/kvm -id 101 -name DesarrolloPlus -chardev 'socket,id=qmp,path=/var/run/qemu-server/101.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/101.pid -daemonize -smbios 'type=1,uuid=bc6b2d91-1722-4add-8560-e4bd6553b77d' -smp '4,sockets=1,cores=4,maxcpus=4' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000,splash=/usr/share/qemu-server/bootsplash.jpg' -vnc unix:/var/run/qemu-server/101.vnc,password -no-hpet -cpu 'host,+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_tlbflush,hv_ipi' -m 28677 -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=684ac586-993d-497a-beb3-81bec5d113f6' -device 'piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2' -readconfig /usr/share/qemu-server/pve-usb.cfg -device 'nec-usb-xhci,id=xhci,bus=pci.1,addr=0x1b' -device 'usb-tablet,id=tablet,bus=uhci.0,port=1' -device 'usb-host,vendorid=0x0bc2,productid=0x3321,id=usb0' -device 'usb-host,vendorid=0x1058,productid=0x1048,id=usb1' -device 'usb-host,vendorid=0x0480,productid=0xa007,id=usb2' -device 'usb-host,bus=xhci.0,vendorid=0x14cd,productid=0x6116,id=usb3' -chardev 'spicevmc,id=usbredirchardev4,name=usbredir' -device 'usb-redir,chardev=usbredirchardev4,id=usbredirdev4,bus=ehci.0' -device 'VGA,id=vga,bus=pci.0,addr=0x2' -chardev 'socket,path=/var/run/qemu-server/101.qga,server,nowait,id=qga0' -device 'virtio-serial,id=qga0,bus=pci.0,addr=0x8' -device 'virtserialport,chardev=qga0,name=org.qemu.guest_agent.0' -device 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3' -iscsi 'initiator-name=iqn.1993-08.org.debian:01:3bf6caa31b6a' -drive 'file=/var/lib/vz/template/iso/virtio-win-0.1.221.iso,if=none,id=drive-ide0,media=cdrom,aio=threads' -device 'ide-cd,bus=ide.0,unit=0,drive=drive-ide0,id=ide0,bootindex=200' -drive 'file=/var/lib/vz/template/iso/SW_DVD9_Win_Server_STD_CORE_2016_64Bit_Spanish_-4_DC_STD_MLF_X21-70529.ISO,if=none,id=drive-ide2,media=cdrom,aio=threads' -device 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=201' -device 'ahci,id=ahci0,multifunction=on,bus=pci.0,addr=0x7' -drive 'file=/dev/pve/vm-101-disk-0,if=none,id=drive-sata0,format=raw,cache=none,aio=native,detect-zeroes=on' -device 'ide-hd,bus=ahci0.0,drive=drive-sata0,id=sata0,bootindex=100' -netdev 'type=tap,id=net0,ifname=tap101i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown' -device 'e1000,mac=DE:F2:1F:80:D3:03,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300' -rtc 'driftfix=slew,base=localtime' -machine 'type=pc' -global 'kvm-pit.lost_tick_policy=discard' -loadstate /dev/pve/vm-101-state-suspend-2024-07-16' failed: got timeout

The configuration of the VM 101 is the next one


agent: 1

bootdisk: sata0

cores: 4

cpu: host

ide0: local:iso/virtio-win-0.1.221.iso,media=cdrom,size=519030K

ide2: local:iso/SW_DVD9_Win_Server_STD_CORE_2016_64Bit_Spanish_-4_DC_STD_MLF_X21-70529.ISO,media=cdrom,size=6257074K

memory: 28677

name: DesarrolloPlus

net0: e1000=DE:F2:1F:80:D3:03,bridge=vmbr0

numa: 0

onboot: 1

ostype: win10

runningmachine: pc-i440fx-4.0

sata0: local-lvm:vm-101-disk-0,size=500G

scsihw: virtio-scsi-pci

smbios1: uuid=bc6b2d91-1722-4add-8560-e4bd6553b77d

sockets: 1

usb0: host=0bc2:3321

usb1: host=1058:1048

usb2: host=0480:a007

usb3: host=14cd:6116,usb3=1

usb4: spice

vmgenid: 684ac586-993d-497a-beb3-81bec5d113f6

vmstate: local-lvm:vm-101-state-suspend-2024-07-16


In some thread of the forum I read that wait at least 3 hours and try again to start the VM works, but it didn’t .

I don’t know if anyone could help me to start again at least one of this VM.

Thanks in advance.
 

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!