Windows 2012R2 Terminal Server QEMU Agent Crash during backup

[Jean-Luc Boyer]

Hello,

We migrated a virtual machine (Windows 2012 R2 Terminal Server) from Hyper-V to Proxmox 5.1. The machine contains two hard drives (C: 180G / D: 650G) in two RAW files. The problem occurs when we perform a backup. The QEMU-GA agent (vitio-win-0.1.141.iso) is well installed and working well. We are able to 'ping' Proxmox to the virtual machine with the 'qm agent 300 ping' command. We perform backups on an NFS. We have other Windows 2008R2 / 2012R2 machines and everything works fine.

There seems to be a problem with the QEMU-GA.EXE agent but we do not know how to fix the problem. When we request a backup to Proxmox from the VM, the agent service stops and the QEMU Guest Agent VSS provider service works. We have to restart the first and stop the second one.

In the events, we have Application error for the agent (error 1000) and two events 1001 (APPCRASH).

Has anyone ever experienced this problem?

Thank you!

Our Proxmox info :

proxmox-ve: 5.1-26 (running kernel: 4.13.4-1-pve)
pve-manager: 5.1-36 (running version: 5.1-36/131401db)
pve-kernel-4.13.4-1-pve: 4.13.4-26
pve-kernel-4.10.15-1-pve: 4.10.15-15
pve-kernel-4.10.17-3-pve: 4.10.17-23
libpve-http-server-perl: 2.0-6
lvm2: 2.02.168-pve6
corosync: 2.4.2-pve3
libqb0: 1.0.1-1
pve-cluster: 5.0-15
qemu-server: 5.0-17
pve-firmware: 2.0-3
libpve-common-perl: 5.0-20
libpve-guest-common-perl: 2.0-13
libpve-access-control: 5.0-7
libpve-storage-perl: 5.0-16
pve-libspice-server1: 0.12.8-3
vncterm: 1.5-2
pve-docs: 5.1-12
pve-qemu-kvm: 2.9.1-2
pve-container: 2.0-17
pve-firewall: 3.0-3
pve-ha-manager: 2.0-3
ksm-control-daemon: 1.2-2
glusterfs-client: 3.8.8-1
lxc-pve: 2.1.0-2
lxcfs: 2.0.7-pve4
criu: 2.11.1-1~bpo90
novnc-pve: 0.6-4
smartmontools: 6.5+svn4324-1
zfsutils-linux: 0.7.3-pve1~bpo9

VM configuration :

agent: 1
bios: ovmf
boot: c
bootdisk: virtio0
cores: 6
cpu: host
ide2: data0:iso/virtio-win-0.1.141.iso,media=cdrom,size=309208K
memory: 122880
name: PATTY
net0: virtio=0a:a2:e0:d8:40:f3,bridge=vmbr5,link_down=1
numa: 1
ostype: win8
scsihw: virtio-scsi-pci
smbios1: uuid=adad9dcb-c5a1-4ed5-bff8-12de2dd39004
sockets: 2
virtio0: data0:300/vm-300-disk-1.raw,size=180G
virtio1: data0:300/vm-300-disk-2.raw,size=650G

 

[GadgetPig]

Are you on pve-no subscription or production repo? I am using pve-nosubscription and have newer packages:

Spoiler: pveversion -v

root@proxmox1:~# pveversion -v
proxmox-ve: 5.1-30 (running kernel: 4.13.8-3-pve)
pve-manager: 5.1-38 (running version: 5.1-38/1e9bc777)
pve-kernel-4.13.8-2-pve: 4.13.8-28
pve-kernel-4.13.8-3-pve: 4.13.8-30
libpve-http-server-perl: 2.0-7
lvm2: 2.02.168-pve6
corosync: 2.4.2-pve3
libqb0: 1.0.1-1
pve-cluster: 5.0-19
qemu-server: 5.0-17
pve-firmware: 2.0-3
libpve-common-perl: 5.0-22
libpve-guest-common-perl: 2.0-13
libpve-access-control: 5.0-7
libpve-storage-perl: 5.0-17
pve-libspice-server1: 0.12.8-3
vncterm: 1.5-3
pve-docs: 5.1-12
pve-qemu-kvm: 2.9.1-3
pve-container: 2.0-17
pve-firewall: 3.0-5
pve-ha-manager: 2.0-4
ksm-control-daemon: 1.2-2
glusterfs-client: 3.8.8-1
lxc-pve: 2.1.1-2
lxcfs: 2.0.8-1
criu: 2.11.1-1~bpo90
novnc-pve: 0.6-4
smartmontools: 6.5+svn4324-1
zfsutils-linux: 0.7.3-pve1~bpo9​

 

[tom]

the kernel 4.13.4-1 has generally issue with windows, please upgrade to latest kernel (check other threads).

 

[Jean-Luc Boyer]

Hi ! Thanks for the fast answer.
Yes i have a Subscription with proxmox. I'll try today to upgrade the kernel on my host and i'll give you a feedback ASAP.

Thanks again!

 

[Jean-Luc Boyer]

Hello,
We upgraded our proxmox 5.1 host to the latest version of the kernel and it still does not fix our problem. The QEMU-GA.EXE agent still has a problem and stops working.

How can I diagnose the QEMU agent?

Thank you!

 

[Jean-Luc Boyer]

We try this (see the screenshot). What's that mean?

 

[Jean-Luc Boyer]

We found the problem. Our RDS server contains the OS as well as the User Disk Profile (UPD) on another drive. This prevents snapshots from this server.

After all this time!

Thank you!!