W2016 VMs crash during backup

frantek

Well-Known Member
May 30, 2009
165
7
58
Hi,

I've two W2016 VMs on a single PVE 5.1-36 node. The first, a DC, crashed since the first backup during the backup. The backup most time completes. What I see is most likely a bluescreen but 95% of the console is black only about the first 5% are blue and nothing is readable. A reset does not fix this. I've to turn the VM off and back on to fix this. The VMs use for everything possible (e.g. storage, networking etc.) KVM drivers. Today the second VM, a Exchange server, crashed while backup. This is the current (300 restarted, 301 crashed in backup state) config of the VMs:

Code:
root@pve01:/etc/pve/qemu-server# cat 300.conf
bootdisk: virtio0
cores: 2
ide2: local:iso/virtio-win-0.1.139.iso,media=cdrom,size=166650K
memory: 16384
name: DC001
net0: virtio=DE:85:9C:AB:3E:EA,bridge=vmbr0
numa: 0
ostype: win10
scsihw: virtio-scsi-pci
smbios1: uuid=edc9b6a2-2e4d-429c-b6fa-c2d6e2cfa1e9
sockets: 2
vga: vmware
virtio0: local-lvm:vm-300-disk-1,size=120G
virtio1: local-lvm:vm-300-disk-2,size=500G

root@pve01:/etc/pve/qemu-server# cat 301.conf
bootdisk: virtio0
cores: 5
ide2: local:iso/msx.iso,media=cdrom,size=5508M
lock: backup
memory: 26624
name: MSX001
net0: virtio=86:B0:6C:64:D9:81,bridge=vmbr0
numa: 0
ostype: win10
parent: Sicherung001
scsihw: virtio-scsi-pci
smbios1: uuid=dc19fd42-795a-4715-ab25-3baa41a2fc9c
sockets: 2
vga: vmware
virtio0: local-lvm:vm-301-disk-1,size=120G
virtio1: local-lvm:vm-301-disk-2,size=200G
virtio2: local-lvm:vm-301-disk-3,size=100G

[Sicherung001]
bootdisk: virtio0
cores: 4
ide2: local:iso/msx.iso,media=cdrom,size=5508M
memory: 20480
name: MSX001
net0: virtio=86:B0:6C:64:D9:81,bridge=vmbr0
numa: 0
ostype: win10
scsihw: virtio-scsi-pci
smbios1: uuid=dc19fd42-795a-4715-ab25-3baa41a2fc9c
snaptime: 1500991429
sockets: 2
vga: vmware
virtio0: local-lvm:vm-301-disk-1,size=120G
virtio1: local-lvm:vm-301-disk-2,size=100G

What can I do to investigate and fix this?

Update: I've checked the event log and there is just no error at all.

TIA
Matthias
 
Last edited:
If your virtio drivers are not updated to the latest version, you could try updating those. You can try changing virtual hard disk from virtio to scsi. If you have kernel 4.13 you can try to donwgrade to version 4.10
 

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!