Windows 11 VM kernel panic diagnosis

jonsley

Member
Jul 26, 2023
8
2
8
Hello I have a windows 11 VM that frequently goes into guest panic state. I can't figure out why. Here are my strace, dbg output etc. Can anyone familiar with diagnosing these things give me a direction to go down? Thanks in adavance!

Code:
proxmox-ve: 8.4.0 (running kernel: 6.8.12-12-pve)
pve-manager: 8.4.5 (running version: 8.4.5/57892e8e686cb35b)
proxmox-kernel-helper: 8.1.1
proxmox-kernel-6.8.12-12-pve-signed: 6.8.12-12
proxmox-kernel-6.8: 6.8.12-12
amd64-microcode: 3.20240820.1~deb12u1
ceph-fuse: 16.2.15+ds-0+deb12u1
corosync: 3.1.9-pve1
criu: 3.17.1-2+deb12u1
glusterfs-client: 10.3-5
ifupdown: residual config
ifupdown2: 3.2.0-1+pmx11
libjs-extjs: 7.0.0-5
libknet1: 1.30-pve2
libproxmox-acme-perl: 1.6.0
libproxmox-backup-qemu0: 1.5.2
libproxmox-rs-perl: 0.3.5
libpve-access-control: 8.2.2
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.1.2
libpve-cluster-perl: 8.1.2
libpve-common-perl: 8.3.2
libpve-guest-common-perl: 5.2.2
libpve-http-server-perl: 5.2.2
libpve-network-perl: 0.11.2
libpve-rs-perl: 0.9.4
libpve-storage-perl: 8.3.6
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 6.0.0-1
lxcfs: 6.0.0-pve2
novnc-pve: 1.6.0-2
proxmox-backup-client: 3.4.3-1
proxmox-backup-file-restore: 3.4.3-1
proxmox-backup-restore-image: 0.7.0
proxmox-firewall: 0.7.1
proxmox-kernel-helper: 8.1.1
proxmox-mail-forward: 0.3.3
proxmox-mini-journalreader: 1.5
proxmox-offline-mirror-helper: 0.6.7
proxmox-widget-toolkit: 4.3.12
pve-cluster: 8.1.2
pve-container: 5.2.7
pve-docs: 8.4.0
pve-edk2-firmware: not correctly installed
pve-esxi-import-tools: 0.7.4
pve-firewall: 5.1.2
pve-firmware: 3.16-3
pve-ha-manager: 4.0.7
pve-i18n: 3.4.5
pve-qemu-kvm: 9.2.0-7
pve-xtermjs: 5.5.0-2
qemu-server: 8.4.1
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.8-pve1

VM Config
Code:
agent: 1
args: -cpu host,hv_passthrough,level=30
balloon: 0
bios: seabios
boot: order=scsi0;net0
cores: 16
machine: pc-q35-5.1
memory: 32000
meta: creation-qemu=9.2.0,ctime=1748581449
name: windowsiot
net0: virtio=BC:24:11:73:4B:55,bridge=vmbr0,firewall=1
numa: 0
ostype: win11
scsi0: local:101/vm-101-disk-0.qcow2,discard=on,iothread=1,size=300G
scsihw: virtio-scsi-pci
smbios1: uuid=57d671ef-f20e-4a43-8433-297f0e402c37
sockets: 1
tpmstate0: local:101/vm-101-disk-1.raw,size=17K,version=v2.0
vga: virtio
vmgenid: 31522d6d-be6f-40d5-9212-c9119df56668

strace output 10sec
Code:
strace -c -p $(cat /var/run/qemu-server/101.pid)
strace: Process 519705 attached
^Cstrace: Process 519705 detached
% time     seconds  usecs/call     calls    errors syscall
------ ----------- ----------- --------- --------- ----------------
 42.44    0.003261           0      3545           ppoll
 29.45    0.002263           0      5736           write
 13.63    0.001047           0      2543           recvmsg
 13.00    0.000999           0      2675           read
  0.65    0.000050           1        50           sendmsg
  0.30    0.000023           2        11           close
  0.30    0.000023           2        11           accept4
  0.14    0.000011           0        22           fcntl
  0.08    0.000006           0        11           getsockname
------ ----------- ----------- --------- --------- ----------------
100.00    0.007683           0     14604           total