Win11 can't boot after shutdown

M

miran

New Member
Nov 25, 2022
5
0
1
After I shutdown a Win 11 VM it won't boot again if I don't restart the server. No idea where or how to look for a solution.

swtpm_setup: Not overwriting existing state file.
TASK ERROR: start failed: command '/usr/bin/kvm -id 111 -name 'Win11,debug-threads=on' -no-shutdown -chardev 'socket,id=qmp,path=/var/run/qemu-server/111.qmp,server=on,wait=off' -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/111.pid -daemonize -smbios 'type=1,uuid=e29e5a04-fea2-4aa4-9f4b-10b71aeaf180' -drive 'if=pflash,unit=0,format=raw,readonly=on,file=/usr/share/pve-edk2-firmware//OVMF_CODE_4M.secboot.fd' -drive 'if=pflash,unit=1,format=raw,id=drive-efidisk0,size=540672,file=/dev/zvol/main-zfs/vm-111-disk-0' -smp '6,sockets=1,cores=6,maxcpus=6' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000,splash=/usr/share/qemu-server/bootsplash.jpg' -vnc 'unix:/var/run/qemu-server/111.vnc,password=on' -no-hpet -cpu 'Broadwell,enforce,hv_ipi,hv_relaxed,hv_reset,hv_runtime,hv_spinlocks=0x1fff,hv_stimer,hv_synic,hv_time,hv_vapic,hv_vendor_id=proxmox,hv_vpindex,kvm=off,+kvm_pv_eoi,+kvm_pv_unhalt,+pcid,vendor=GenuineIntel' -m 16384 -readconfig /usr/share/qemu-server/pve-q35-4.0.cfg -device 'vmgenid,guid=e96e1c17-89c3-4e36-b510-709b14867848' -device 'usb-tablet,id=tablet,bus=ehci.0,port=1' -device 'vfio-pci,host=0000:81:00.0,id=hostpci0.0,bus=ich9-pcie-port-1,addr=0x0.0,multifunction=on' -device 'vfio-pci,host=0000:81:00.1,id=hostpci0.1,bus=ich9-pcie-port-1,addr=0x0.1' -chardev 'socket,id=tpmchar,path=/var/run/qemu-server/111.swtpm' -tpmdev 'emulator,id=tpmdev,chardev=tpmchar' -device 'tpm-tis,tpmdev=tpmdev' -device 'virtio-vga,id=vga,bus=pcie.0,addr=0x1' -chardev 'socket,path=/var/run/qemu-server/111.qga,server=on,wait=off,id=qga0' -device 'virtio-serial,id=qga0,bus=pci.0,addr=0x8' -device 'virtserialport,chardev=qga0,name=org.qemu.guest_agent.0' -device 'virtio-serial,id=spice,bus=pci.0,addr=0x9' -chardev 'spicevmc,id=vdagent,name=vdagent' -device 'virtserialport,chardev=vdagent,name=com.redhat.spice.0' -spice 'tls-port=61001,addr=127.0.0.1,tls-ciphers=HIGH,seamless-migration=on' -device 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3,free-page-reporting=on' -iscsi 'initiator-name=iqn.1993-08.org.debian:01:a661fd35289a' -device 'virtio-scsi-pci,id=scsihw0,bus=pci.0,addr=0x5' -drive 'file=/dev/zvol/main-zfs/vm-111-disk-1,if=none,id=drive-scsi0,cache=writeback,discard=on,format=raw,aio=io_uring,detect-zeroes=unmap' -device 'scsi-hd,bus=scsihw0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0,id=scsi0,bootindex=100' -netdev 'type=tap,id=net0,ifname=tap111i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on' -device 'virtio-net-pci,mac=F6:67:0D:09:B4:4B,netdev=net0,bus=pci.0,addr=0x12,id=net0' -rtc 'driftfix=slew,base=localtime' -machine 'type=pc-q35-7.0+pve0' -global 'kvm-pit.lost_tick_policy=discard'' failed: got timeout
 
Hi,

thanks for the reply.
This is the config
Code: 
agent: 1
balloon: 4096
bios: ovmf
boot: order=scsi0
cores: 6
cpu: Broadwell,flags=+pcid
efidisk0: main-zfs:vm-111-disk-0,efitype=4m,pre-enrolled-keys=1,size=1M
hostpci0: 0000:81:00,pcie=1,x-vga=1
machine: pc-q35-7.0
memory: 16384
meta: creation-qemu=7.0.0,ctime=1667741768
name: Win11
net0: virtio=F6:67:0D:09:B4:4B,bridge=vmbr0,firewall=1
numa: 0
ostype: win11
scsi0: main-zfs:vm-111-disk-1,cache=writeback,discard=on,size=64G
scsihw: virtio-scsi-pci
smbios1: uuid=e29e5a04-fea2-4aa4-9f4b-10b71aeaf180
sockets: 1
tpmstate0: main-zfs:vm-111-disk-2,size=4M,version=v2.0
vga: virtio
vmgenid: e96e1c17-89c3-4e36-b510-709b14867848
 
Hello,

Thank you for the VM config, looks like the VM has a PCI passed through it's a GPU? and which version of PVE you are using (pveversion -v)?

Can you also please check the Syslog what will say when you start the win11 VM?
 
Yes, it's a GPU and it works.
Vrsions:
Code: 
proxmox-ve: 7.3-1 (running kernel: 5.15.74-1-pve)
pve-manager: 7.3-3 (running version: 7.3-3/c3928077)
pve-kernel-5.15: 7.2-14
pve-kernel-helper: 7.2-14
pve-kernel-5.13: 7.1-9
pve-kernel-5.15.74-1-pve: 5.15.74-1
pve-kernel-5.15.64-1-pve: 5.15.64-1
pve-kernel-5.15.60-1-pve: 5.15.60-1
pve-kernel-5.15.53-1-pve: 5.15.53-1
pve-kernel-5.15.39-4-pve: 5.15.39-4
pve-kernel-5.15.39-3-pve: 5.15.39-3
pve-kernel-5.13.19-6-pve: 5.13.19-15
pve-kernel-5.13.19-2-pve: 5.13.19-4
ceph-fuse: 15.2.15-pve1
corosync: 3.1.7-pve1
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve2
libproxmox-acme-perl: 1.4.2
libproxmox-backup-qemu0: 1.3.1-1
libpve-access-control: 7.2-5
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.2-8
libpve-guest-common-perl: 4.2-3
libpve-http-server-perl: 4.1-5
libpve-storage-perl: 7.2-12
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.0-3
lxcfs: 4.0.12-pve1
novnc-pve: 1.3.0-3
proxmox-backup-client: 2.2.7-1
proxmox-backup-file-restore: 2.2.7-1
proxmox-mini-journalreader: 1.3-1
proxmox-offline-mirror-helper: 0.5.0-1
proxmox-widget-toolkit: 3.5.3
pve-cluster: 7.3-1
pve-container: 4.4-2
pve-docs: 7.3-1
pve-edk2-firmware: 3.20220526-1
pve-firewall: 4.2-7
pve-firmware: 3.5-6
pve-ha-manager: 3.5.1
pve-i18n: 2.8-1
pve-qemu-kvm: 7.1.0-4
pve-xtermjs: 4.16.0-1
qemu-server: 7.3-1
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.8.0~bpo11+2
vncterm: 1.7-1
zfsutils-linux: 2.1.6-pve1

This is from the Syslog on a successful boot:
Code: 
Nov 25 15:21:10 pve pvedaemon[5594]: <root@pam> starting task UPID:pve:0003053C:00081E07:6380CF56:qmstart:111:root@pam:
Nov 25 15:21:10 pve pvedaemon[197948]: start VM 111: UPID:pve:0003053C:00081E07:6380CF56:qmstart:111:root@pam:
Nov 25 15:21:10 pve systemd[1]: Started 111.scope.
Nov 25 15:21:10 pve systemd-udevd[198037]: Using default interface naming scheme 'v247'.
Nov 25 15:21:10 pve systemd-udevd[198037]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Nov 25 15:21:10 pve kernel: device tap111i0 entered promiscuous mode
Nov 25 15:21:10 pve systemd-udevd[198054]: Using default interface naming scheme 'v247'.
Nov 25 15:21:10 pve systemd-udevd[198054]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Nov 25 15:21:10 pve systemd-udevd[198054]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Nov 25 15:21:10 pve systemd-udevd[198037]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Nov 25 15:21:10 pve kernel: vmbr0: port 6(fwpr111p0) entered blocking state
Nov 25 15:21:10 pve kernel: vmbr0: port 6(fwpr111p0) entered disabled state
Nov 25 15:21:10 pve kernel: device fwpr111p0 entered promiscuous mode
Nov 25 15:21:10 pve kernel: vmbr0: port 6(fwpr111p0) entered blocking state
Nov 25 15:21:10 pve kernel: vmbr0: port 6(fwpr111p0) entered forwarding state
Nov 25 15:21:10 pve kernel: fwbr111i0: port 1(fwln111i0) entered blocking state
Nov 25 15:21:10 pve kernel: fwbr111i0: port 1(fwln111i0) entered disabled state
Nov 25 15:21:10 pve kernel: device fwln111i0 entered promiscuous mode
Nov 25 15:21:10 pve kernel: fwbr111i0: port 1(fwln111i0) entered blocking state
Nov 25 15:21:10 pve kernel: fwbr111i0: port 1(fwln111i0) entered forwarding state
Nov 25 15:21:10 pve kernel: fwbr111i0: port 2(tap111i0) entered blocking state
Nov 25 15:21:10 pve kernel: fwbr111i0: port 2(tap111i0) entered disabled state
Nov 25 15:21:10 pve kernel: fwbr111i0: port 2(tap111i0) entered blocking state
Nov 25 15:21:10 pve kernel: fwbr111i0: port 2(tap111i0) entered forwarding state
Nov 25 15:21:15 pve kernel: vfio-pci 0000:81:00.0: enabling device (0100 -> 0103)
Nov 25 15:21:15 pve kernel: vfio-pci 0000:81:00.0: vfio_ecap_init: hiding ecap 0x1e@0x258
Nov 25 15:21:15 pve kernel: vfio-pci 0000:81:00.0: vfio_ecap_init: hiding ecap 0x19@0x900
Nov 25 15:21:16 pve pvedaemon[5594]: <root@pam> end task UPID:pve:0003053C:00081E07:6380CF56:qmstart:111:root@pam: OK

Shutdown from Windows:
Code: 
Nov 25 15:25:43 pve kernel:  zd16: p1 p2 p3 p4
Nov 25 15:25:43 pve kernel: fwbr111i0: port 2(tap111i0) entered disabled state
Nov 25 15:25:43 pve kernel: fwbr111i0: port 1(fwln111i0) entered disabled state
Nov 25 15:25:43 pve kernel: vmbr0: port 6(fwpr111p0) entered disabled state
Nov 25 15:25:43 pve kernel: device fwln111i0 left promiscuous mode
Nov 25 15:25:43 pve kernel: fwbr111i0: port 1(fwln111i0) entered disabled state
Nov 25 15:25:43 pve kernel: device fwpr111p0 left promiscuous mode
Nov 25 15:25:43 pve kernel: vmbr0: port 6(fwpr111p0) entered disabled state
Nov 25 15:25:44 pve qmeventd[4826]: read: Connection reset by peer
Nov 25 15:25:44 pve qmeventd[298555]: Starting cleanup for 111
Nov 25 15:25:44 pve qmeventd[298555]: Finished cleanup for 111
Nov 25 15:25:45 pve systemd[1]: 111.scope: Succeeded.
Nov 25 15:25:45 pve systemd[1]: 111.scope: Consumed 3min 14.890s CPU time.

This is the syslog of o boot failure:
Code: 
Nov 25 13:19:02 pve pvedaemon[1236861]: start VM 111: UPID:pve:0012DF7D:0076E2EA:6380B2B6:qmstart:111:root@pam:
Nov 25 13:19:02 pve pvedaemon[934120]: <root@pam> starting task UPID:pve:0012DF7D:0076E2EA:6380B2B6:qmstart:111:root@pam:
Nov 25 13:19:02 pve systemd[1]: Started 111.scope.
Nov 25 13:19:03 pve systemd-udevd[1236939]: Using default interface naming scheme 'v247'.
Nov 25 13:19:03 pve systemd-udevd[1236939]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Nov 25 13:19:03 pve kernel: device tap111i0 entered promiscuous mode
Nov 25 13:19:03 pve systemd-udevd[1236955]: Using default interface naming scheme 'v247'.
Nov 25 13:19:03 pve systemd-udevd[1236955]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Nov 25 13:19:03 pve systemd-udevd[1236955]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Nov 25 13:19:03 pve systemd-udevd[1236939]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Nov 25 13:19:03 pve kernel: vmbr0: port 7(fwpr111p0) entered blocking state
Nov 25 13:19:03 pve kernel: vmbr0: port 7(fwpr111p0) entered disabled state
Nov 25 13:19:03 pve kernel: device fwpr111p0 entered promiscuous mode
Nov 25 13:19:03 pve kernel: vmbr0: port 7(fwpr111p0) entered blocking state
Nov 25 13:19:03 pve kernel: vmbr0: port 7(fwpr111p0) entered forwarding state
Nov 25 13:19:03 pve kernel: fwbr111i0: port 1(fwln111i0) entered blocking state
Nov 25 13:19:03 pve kernel: fwbr111i0: port 1(fwln111i0) entered disabled state
Nov 25 13:19:03 pve kernel: device fwln111i0 entered promiscuous mode
Nov 25 13:19:03 pve kernel: fwbr111i0: port 1(fwln111i0) entered blocking state
Nov 25 13:19:03 pve kernel: fwbr111i0: port 1(fwln111i0) entered forwarding state
Nov 25 13:19:03 pve kernel: fwbr111i0: port 2(tap111i0) entered blocking state
Nov 25 13:19:03 pve kernel: fwbr111i0: port 2(tap111i0) entered disabled state
Nov 25 13:19:03 pve kernel: fwbr111i0: port 2(tap111i0) entered blocking state
Nov 25 13:19:03 pve kernel: fwbr111i0: port 2(tap111i0) entered forwarding state
Nov 25 13:19:11 pve pvedaemon[934120]: VM 111 qmp command failed - VM 111 qmp command 'query-proxmox-support' failed - got timeout
Nov 25 13:19:19 pve pvestatd[5444]: VM 111 qmp command failed - VM 111 qmp command 'query-proxmox-support' failed - unable to connect to VM 111 qmp socket - timeout after 51 retries
Nov 25 13:19:22 pve pvestatd[5444]: status update time (11.369 seconds)
Nov 25 13:19:30 pve pvestatd[5444]: VM 111 qmp command failed - VM 111 qmp command 'query-proxmox-support' failed - unable to connect to VM 111 qmp socket - timeout after 51 retries
Nov 25 13:19:32 pve pvedaemon[1236861]: start failed: command '/usr/bin/kvm -id 111 -name 'Win11,debug-threads=on' -no-shutdown -chardev 'socket,id=qmp,path=/var/run/qemu-server/111.qmp,server=on,wait=off' -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/111.pid -daemonize -smbios 'type=1,uuid=e29e5a04-fea2-4aa4-9f4b-10b71aeaf180' -drive 'if=pflash,unit=0,format=raw,readonly=on,file=/usr/share/pve-edk2-firmware//OVMF_CODE_4M.secboot.fd' -drive 'if=pflash,unit=1,format=raw,id=drive-efidisk0,size=540672,file=/dev/zvol/main-zfs/vm-111-disk-0' -smp '6,sockets=1,cores=6,maxcpus=6' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000,splash=/usr/share/qemu-server/bootsplash.jpg' -vnc 'unix:/var/run/qemu-server/111.vnc,password=on' -no-hpet -cpu 'Broadwell,enforce,hv_ipi,hv_relaxed,hv_reset,hv_runtime,hv_spinlocks=0x1fff,hv_stimer,hv_synic,hv_time,hv_vapic,hv_vendor_id=proxmox,hv_vpindex,kvm=off,+kvm_pv_eoi,+kvm_pv_unhalt,+pcid,vendor=GenuineIntel' -m 16384 -readconfig /usr/share/qemu-server/pve-q35-4.0.cfg -device 'vmgenid,guid=e96e1c17-89c3-4e36-b510-709b14867848' -device 'usb-tablet,id=tablet,bus=ehci.0,port=1' -device 'vfio-pci,host=0000:81:00.0,id=hostpci0.0,bus=ich9-pcie-port-1,addr=0x0.0,multifunction=on' -device 'vfio-pci,host=0000:81:00.1,id=hostpci0.1,bus=ich9-pcie-port-1,addr=0x0.1' -chardev 'socket,id=tpmchar,path=/var/run/qemu-server/111.swtpm' -tpmdev 'emulator,id=tpmdev,chardev=tpmchar' -device 'tpm-tis,tpmdev=tpmdev' -device 'virtio-vga,id=vga,bus=pcie.0,addr=0x1' -chardev 'socket,path=/var/run/qemu-server/111.qga,server=on,wait=off,id=qga0' -device 'virtio-serial,id=qga0,bus=pci.0,addr=0x8' -device 'virtserialport,chardev=qga0,name=org.qemu.guest_agent.0' -device 'virtio-serial,id=spice,bus=pci.0,addr=0x9' -chardev 'spicevmc,id=vdagent,name=vdagent' -device 'virtserialport,chardev=vdagent,name=com.redhat.spice.0' -spice 'tls-port=61001,addr=127.0.0.1,tls-ciphers=HIGH,seamless-migration=on' -device 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3,free-page-reporting=on' -iscsi 'initiator-name=iqn.1993-08.org.debian:01:a661fd35289a' -device 'virtio-scsi-pci,id=scsihw0,bus=pci.0,addr=0x5' -drive 'file=/dev/zvol/main-zfs/vm-111-disk-1,if=none,id=drive-scsi0,cache=writeback,discard=on,format=raw,aio=io_uring,detect-zeroes=unmap' -device 'scsi-hd,bus=scsihw0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0,id=scsi0,bootindex=100' -netdev 'type=tap,id=net0,ifname=tap111i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on' -device 'virtio-net-pci,mac=F6:67:0D:09:B4:4B,netdev=net0,bus=pci.0,addr=0x12,id=net0' -rtc 'driftfix=slew,base=localtime' -machine 'type=pc-q35-7.0+pve0' -global 'kvm-pit.lost_tick_policy=discard'' failed: got timeout
Nov 25 13:19:32 pve pvedaemon[934120]: <root@pam> end task UPID:pve:0012DF7D:0076E2EA:6380B2B6:qmstart:111:root@pam: start failed: command '/usr/bin/kvm -id 111 -name 'Win11,debug-threads=on' -no-shutdown -chardev 'socket,id=qmp,path=/var/run/qemu-server/111.qmp,server=on,wait=off' -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/111.pid -daemonize -smbios 'type=1,uuid=e29e5a04-fea2-4aa4-9f4b-10b71aeaf180' -drive 'if=pflash,unit=0,format=raw,readonly=on,file=/usr/share/pve-edk2-firmware//OVMF_CODE_4M.secboot.fd' -drive 'if=pflash,unit=1,format=raw,id=drive-efidisk0,size=540672,file=/dev/zvol/main-zfs/vm-111-disk-0' -smp '6,sockets=1,cores=6,maxcpus=6' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000,splash=/usr/share/qemu-server/bootsplash.jpg' -vnc 'unix:/var/run/qemu-server/111.vnc,password=on' -no-hpet -cpu 'Broadwell,enforce,hv_ipi,hv_relaxed,hv_reset,hv_runtime,hv_spinlocks=0x1fff,hv_stimer,hv_synic,hv_time,hv_vapic,hv_vendor_id=proxmox,hv_vpindex,kvm=off,+kvm_pv_eoi,+kvm_pv_unhalt,+pcid,vendor=GenuineIntel' -m 16384 -readconfig /usr/share/qemu-server/pve-q35-4.0.cfg -device 'vmgenid,guid=e96e1c17-89c3-4e36-b510-709b14867848' -device 'usb-tablet,id=tablet,bus=ehci.0,port=1' -device 'vfio-pci,host=0000:81:00.0,id=hostpci0.0,bus=ich9-pcie-port-1,addr=0x0.0,multifunction=on' -device 'vfio-pci,host=0000:81:00.1,id=hostpci0.1,bus=ich9-pcie-port-1,addr=0x0.1' -chardev 'socket,id=tpmchar,path=/var/run/qemu-server/111.swtpm' -tpmdev 'emulator,id=tpmdev,chardev=tpmchar' -device 'tpm-tis,tpmdev=tpmdev' -device 'virtio-vga,id=vga,bus=pcie.0,addr=0x1' -chardev 'socket,path=/var/run/qemu-server/111.qga,server=on,wait=off,id=qga0' -device 'virtio-serial,id=qga0,bus=pci.0,addr=0x8' -device 'virtserialport,chardev=qga0,name=org.qemu.guest_agent.0' -device 'virtio-serial,id=spice,bus=pci.0,addr=0x9' -chardev 'spicevmc,id=vdagent,name=vdagent' -device 'virtserialport,chardev=vdagent,name=com.redhat.spice.0' -spice 'tls-port=61001,addr=127.0.0.1,tls-ciphers=HIGH,seamless-migration=on' -device 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3,free-page-reporting=on' -iscsi 'initiator-name=iqn.1993-08.org.debian:01:a661fd35289a' -device 'virtio-scsi-pci,id=scsihw0,bus=pci.0,addr=0x5' -drive 'file=/dev/zvol/main-zfs/vm-111-disk-1,if=none,id=drive-scsi0,cache=writeback,discard=on,format=raw,aio=io_uring,detect-zeroes=unmap' -device 'scsi-hd,bus=scsihw0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0,id=scsi0,bootindex=100' -netdev 'type=tap,id=net0,ifname=tap111i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on' -device 'virtio-net-pci,mac=F6:67:0D:09:B4:4B,netdev=net0,bus=pci.0,addr=0x12,id=net0' -rtc 'driftfix=slew,base=localtime' -machine 'type=pc-q35-7.0+pve0' -global 'kvm-pit.lost_tick_policy=discard'' failed: got timeout
Nov 25 13:19:33 pve pvestatd[5444]: status update time (11.363 seconds)
Nov 25 13:19:36 pve pvedaemon[934120]: VM 111 qmp command failed - VM 111 qmp command 'query-proxmox-support' failed - unable to connect to VM 111 qmp socket - timeout after 52 retries
Nov 25 13:19:41 pve pvestatd[5444]: VM 111 qmp command failed - VM 111 qmp command 'query-proxmox-support' failed - unable to connect to VM 111 qmp socket - timeout after 51 retries
Nov 25 13:19:45 pve pvestatd[5444]: status update time (11.346 seconds)
Nov 25 13:19:49 pve kernel: vfio-pci 0000:81:00.0: vfio_ecap_init: hiding ecap 0x1e@0x258
Nov 25 13:19:49 pve kernel: vfio-pci 0000:81:00.0: vfio_ecap_init: hiding ecap 0x19@0x900
Nov 25 13:19:50 pve kernel: fwbr111i0: port 2(tap111i0) entered disabled state
Nov 25 13:19:50 pve kernel: fwbr111i0: port 1(fwln111i0) entered disabled state
Nov 25 13:19:50 pve kernel: vmbr0: port 7(fwpr111p0) entered disabled state
Nov 25 13:19:50 pve kernel: device fwln111i0 left promiscuous mode
Nov 25 13:19:50 pve kernel: fwbr111i0: port 1(fwln111i0) entered disabled state
Nov 25 13:19:50 pve kernel: device fwpr111p0 left promiscuous mode
Nov 25 13:19:50 pve kernel: vmbr0: port 7(fwpr111p0) entered disabled state
Nov 25 13:19:51 pve kernel:  zd16: p1 p2 p3 p4
Nov 25 13:19:51 pve pvestatd[5444]: VM 111 qmp command failed - VM 111 qmp command 'query-proxmox-support' failed - unable to connect to VM 111 qmp socket - Connection refused
Nov 25 13:19:53 pve systemd[1]: 111.scope: Succeeded.
Nov 25 13:19:53 pve systemd[1]: 111.scope: Consumed 48.072s CPU time.

There were also a couple of lines like this, because the remote pbs is online only at night for the backup schedule. Don't know how to get rid of this in the Syslog.
Code: 
Nov 25 13:19:45 pve pvestatd[5444]: pbs-remote: error fetching datastores - 500 Can't connect to 192.168.110.82:8007 (No route to host)
 
Hello,

Can you try to shut down the VM by setting more timeout, see the below command?

Bash: 
qm shutdown 111 --timeout 200

If the above idea does not help, I would try to unplug the GPU passthrough from Win 11 in order to narrow down the issue if the issue related to the GPU.
 
You must log in or register to reply here.
Top Bottom