VM unexpectedly stops

[Mikael]

HI

I have some issues that on two occations two different VM's running windows server 2019 stops with no indication that I can find in the guest's logs on why it have happened.
In syslog on the time it happens I found this log entry:

Feb 25 05:42:11 rdc-prox08 QEMU[12126]: kvm: ../hw/scsi/scsi-disk.c:357: scsi_dma_complete: Assertion `r->req.aiocb != NULL' failed.
Feb 22 08:11:59 rdc-prox07 QEMU[1341645]: kvm: ../block/block-backend.c:1475: blk_aio_write_entry: Assertion `!qiov || qiov->size == acb->bytes' failed.

The VM's goes offline and can be started without any issues.
Both hosts are running the same version of proxmox and the VM's are running the same driver versions from "virtio-win-0.1.208.iso"

root@rdc-prox08:~# pveversion -v
proxmox-ve: 7.0-2 (running kernel: 5.11.22-4-pve)
pve-manager: 7.0-11 (running version: 7.0-11/63d82f4e)
pve-kernel-5.11: 7.0-7
pve-kernel-helper: 7.0-7
pve-kernel-5.11.22-4-pve: 5.11.22-8
ceph-fuse: 15.2.14-pve1
corosync: 3.1.2-pve2
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.21-pve1
libproxmox-acme-perl: 1.3.0
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.0-4
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.0-6
libpve-guest-common-perl: 4.0-2
libpve-http-server-perl: 4.0-2
libpve-storage-perl: 7.0-10
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.9-4
lxcfs: 4.0.8-pve2
novnc-pve: 1.2.0-3
proxmox-backup-client: 2.0.9-2
proxmox-backup-file-restore: 2.0.9-2
proxmox-mini-journalreader: 1.2-1
proxmox-widget-toolkit: 3.3-6
pve-cluster: 7.0-3
pve-container: 4.0-9
pve-docs: 7.0-5
pve-edk2-firmware: 3.20200531-1
pve-firewall: 4.2-2
pve-firmware: 3.3-1
pve-ha-manager: 3.3-1
pve-i18n: 2.5-1
pve-qemu-kvm: 6.0.0-3
pve-xtermjs: 4.12.0-1
qemu-server: 7.0-13
smartmontools: 7.2-1
spiceterm: 3.2-2
vncterm: 1.7-1
zfsutils-linux: 2.0.5-pve1

Have anyone seen this issue before?

 

[Dunuin]

Did you check the hosts syslog for OOM messages? Most of the time when a VM crashes it was killed by the host because the memory was overprovisioned.

 

[Mikael]

I checked now and I cannot find any OOM messages in syslog. That should not be our issue as we use about 70% of the total ram according to "Summary" dashboard.