Windows Server Guest suddenly stop after Proxmox 6 upgrade

[jggundin]

Hi,

I have recently upgraded from Proxmox 5.4 to 6 following the official doc upgrade guide. Also upgraded zfs pool to 0.8.1.
After that some windows server 2016 guests randomly stop.
Tried to re-license windows and also to upgrade virtio-win drivers to latest version 0.1.171 but the problem persists.
Linux guests are working fine.

Any idea of what to check?

root@plumbus:~# pveversion -v
proxmox-ve: 6.0-2 (running kernel: 5.0.18-1-pve)
pve-manager: 6.0-5 (running version: 6.0-5/f8a710d7)
pve-kernel-5.0: 6.0-6
pve-kernel-helper: 6.0-6
pve-kernel-4.15: 5.4-6
pve-kernel-5.0.18-1-pve: 5.0.18-1
pve-kernel-5.0.15-1-pve: 5.0.15-1
pve-kernel-4.15.18-18-pve: 4.15.18-44
pve-kernel-4.15.18-9-pve: 4.15.18-30
ceph-fuse: 12.2.11+dfsg1-2.1
corosync: 3.0.2-pve2
criu: 3.11-3
glusterfs-client: 5.5-3
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.10-pve1
libpve-access-control: 6.0-2
libpve-apiclient-perl: 3.0-2
libpve-common-perl: 6.0-3
libpve-guest-common-perl: 3.0-1
libpve-http-server-perl: 3.0-2
libpve-storage-perl: 6.0-6
libqb0: 1.0.5-1
lvm2: 2.03.02-pve3
lxc-pve: 3.1.0-61
lxcfs: 3.0.3-pve60
novnc-pve: 1.0.0-60
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.0-5
pve-cluster: 6.0-4
pve-container: 3.0-5
pve-docs: 6.0-4
pve-edk2-firmware: 2.20190614-1
pve-firewall: 4.0-6
pve-firmware: 3.0-2
pve-ha-manager: 3.0-2
pve-i18n: 2.0-2
pve-qemu-kvm: 4.0.0-3
pve-xtermjs: 3.13.2-1
qemu-server: 6.0-7
smartmontools: 7.0-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.1-pve1

root@plumbus:/etc# cat pve/qemu-server/221.conf
agent: 1
balloon: 0
bootdisk: ide0
cores: 2
cpu: Broadwell,flags=+pcid
ide0: local-zfs:vm-221-disk-0,cache=writeback,discard=on,iops_rd=1000,iops_rd_max=1000,iops_wr=1000,iops_wr_max=1000,mbps_rd=50,mbps_rd_max=100,mbps_wr=50,mbps_wr_max=100,size=30G,ssd=1
ide2: iso:iso/virtio-win-0.1.171.iso,media=cdrom,size=363020K
memory: 8192
name: WinServer2016ATServerCom2
net0: e1000=2A:00:61:1C:1E:52,bridge=vmbr0,rate=200
numa: 1
onboot: 1
ostype: win10
scsihw: virtio-scsi-pci
smbios1: uuid=0167ba22-39c8-4ef2-ad97-95b064f1151e
sockets: 2
vmgenid: d7abdcfa-0add-4b19-a458-ee19dafc757e

 

[Stefan_R]

Can you define "suddenly stop"?
Do your logs show anything? (journalctl -u 'pve*' -e)

 

[jggundin]

Can you define "suddenly stop"?
Do your logs show anything? (journalctl -u 'pve*' -e)

I believe the VM fall down about 1:41. (I have a log every minute on windows event viewer).

Aug 07 01:39:02 plumbus pveproxy[12478]: worker 4976 finished
Aug 07 01:39:02 plumbus pveproxy[12478]: starting 1 worker(s)
Aug 07 01:39:02 plumbus pveproxy[12478]: worker 7346 started
Aug 07 01:39:05 plumbus pveproxy[7006]: worker exit
Aug 07 01:40:00 plumbus systemd[1]: Starting Proxmox VE replication runner...
Aug 07 01:40:01 plumbus systemd[1]: pvesr.service: Succeeded.
Aug 07 01:40:01 plumbus systemd[1]: Started Proxmox VE replication runner.
Aug 07 01:41:00 plumbus systemd[1]: Starting Proxmox VE replication runner...
Aug 07 01:41:01 plumbus systemd[1]: pvesr.service: Succeeded.
Aug 07 01:41:01 plumbus systemd[1]: Started Proxmox VE replication runner.
Aug 07 01:42:00 plumbus systemd[1]: Starting Proxmox VE replication runner...
Aug 07 01:42:01 plumbus systemd[1]: pvesr.service: Succeeded.
Aug 07 01:42:01 plumbus systemd[1]: Started Proxmox VE replication runner.
Aug 07 01:42:23 plumbus pvedaemon[46218]: <root@pam> successful auth for user 'root@pam'
Aug 07 01:43:00 plumbus systemd[1]: Starting Proxmox VE replication runner...
Aug 07 01:43:01 plumbus systemd[1]: pvesr.service: Succeeded.
Aug 07 01:43:01 plumbus systemd[1]: Started Proxmox VE replication runner.
Aug 07 01:43:53 plumbus pvedaemon[45454]: <root@pam> successful auth for user 'root@pam'
Aug 07 01:44:00 plumbus systemd[1]: Starting Proxmox VE replication runner...
Aug 07 01:44:01 plumbus systemd[1]: pvesr.service: Succeeded.
Aug 07 01:44:01 plumbus systemd[1]: Started Proxmox VE replication runner.
Aug 07 01:45:00 plumbus systemd[1]: Starting Proxmox VE replication runner...
Aug 07 01:45:01 plumbus systemd[1]: pvesr.service: Succeeded.
Aug 07 01:45:01 plumbus systemd[1]: Started Proxmox VE replication runner.
Aug 07 01:45:14 plumbus pveproxy[16164]: worker exit
Aug 07 01:45:15 plumbus pveproxy[12478]: worker 16164 finished
Aug 07 01:45:15 plumbus pveproxy[12478]: starting 1 worker(s)
Aug 07 01:45:15 plumbus pveproxy[12478]: worker 19570 started
Aug 07 01:45:39 plumbus pvedaemon[56634]: <root@pam> starting task UPID:plumbus:0000BDDD:01F6846E:5D4A1123:vncproxy:101:root@pam:
Aug 07 01:45:39 plumbus pvedaemon[48605]: starting vnc proxy UPID:plumbus:0000BDDD:01F6846E:5D4A1123:vncproxy:101:root@pam:
Aug 07 01:45:39 plumbus pveproxy[34061]: worker exit
Aug 07 01:45:57 plumbus pvedaemon[45454]: <root@pam> successful auth for user 'root@pam'
Aug 07 01:46:00 plumbus systemd[1]: Starting Proxmox VE replication runner...
Aug 07 01:46:01 plumbus systemd[1]: pvesr.service: Succeeded.

 

[Stefan_R]

Log looks normal. Still, can you define "suddenly stop" - do the VMs shut down, do they crash, bluescreen, just turn off, etc... Maybe the event viewer in Windows can tell you more about it?