Windows 10 VM always starts suspended

Sep 28, 2019
24
4
23
43
I have a Win10 VM on proxmox-ve: 6.0-2 where it always starts in suspended state so I have to click resume as well. I did a "qm config" dump and I'm guessing the vmstate line is the culprit but I'm not sure how to get rid of it:

Code:
# qm config 100
agent: 1,fstrim_cloned_disks=1
balloon: 2048
bios: ovmf
bootdisk: ide0
cores: 22
efidisk0: local-zfs:vm-100-disk-1,size=128K
hostpci0: 0b:00,pcie=1,x-vga=1
ide0: local-zfs:vm-100-disk-0,discard=on,size=200G
machine: pc-q35-3.1
memory: 16384
name: win-bi
net0: virtio=DA:01:58:D1:DD:D7,bridge=vmbr0,firewall=1
numa: 0
ostype: win10
runningmachine: pc-q35-3.1
sata0: local:iso/Windows.iso,media=cdrom,size=4071872K
sata1: local:iso/virtio-win-0.1.171.iso,media=cdrom,size=363020K
scsihw: virtio-scsi-pci
smbios1: uuid=a8af83c1-41eb-4036-af14-cabadefeab30
sockets: 1
usb0: host=0951:16c4
usb1: host=28de:1142,usb3=1
usb2: host=18d1:9400,usb3=1
usb3: host=0b05:17cb
vmgenid: b0385b03-56d6-4a6e-b3be-48c3632e4498
vmstate: local-zfs:vm-100-state-suspend-2019-10-20
 
I'm guessing the vmstate line is the culprit but I'm not sure how to get rid of it:

I'd also guess that, but normally it should get removed after the resume? Or do you always use suspend?

If the VM does a fresh start anyway you could try to do:
Code:
qm set 100 --delete vmstate
and retry.

If that works I'd also cleanup the left over local-zfs:vm-100-state-suspend-2019-10-20 volume, else you can always go back by qm set 100 --vmstate local-zfs:vm-100-state-suspend-2019-10-20 again.
 
I only ever did the suspend the one time. I usually just shutdown from inside the guest and for whatever reason that vmstate doesn't go away.

The qm set command worked to clear the state and the VM starts cleanly from shutdown. Thanks for the quick fix!