Windows 10 clients supends or stops randomly

[zolpol]

Hi there!

We'h started use Proxmox to virtualize our system. In March, we made a test everything worked fine. But now, Windows 10 VMs randomly started to stop or suppend.
At the summary page the VMs eats up all their RAM before stop. Maybe baloon driver? Or something with the kernel?

Thanks for your help.

 

[Moayad]

Hi,

Did you enabled sleeping mode in the VM?

 

[zolpol]

Sleeping and suspend not allowed to clients. Also users can't turn off, or suspend the VMs, it's controlled by GPO.

Check the png please, no one used that VM, but eats up all RAM. Then turned off itself.

 

[Moayad]

Please post the VM config qm config <VMID> and pveversion -v as well.

 

[zolpol]

qm config:


agent: 1
audio0: device=ich9-intel-hda,driver=spice
boot: order=scsi0;net0
cores: 4
memory: 8192
name: DESKVIRT01
net0: virtio=D64:00:E7:8D:07,bridge=vmbr0
numa: 0
onboot: 1
ostype: win10
scsi0: local-lvm:vm-102-disk-0,cache=writeback,size=80G
scsihw: virtio-scsi-pci
smbios1: uuid=cb97dac5-2d0f-4dbe-934b-612be71b6902
sockets: 1
vga: qxl
vmgenid: 66ce6465-bd7e-473d-99f1-e6011993a391

pveversion -v:


proxmox-ve: 6.2-2 (running kernel: 5.4.65-1-pve)
pve-manager: 6.2-15 (running version: 6.2-15/48bd51b6)
pve-kernel-5.4: 6.2-7
pve-kernel-helper: 6.2-7
pve-kernel-5.4.65-1-pve: 5.4.65-1
pve-kernel-5.4.34-1-pve: 5.4.34-2
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.4-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.16-pve1
libproxmox-acme-perl: 1.0.5
libpve-access-control: 6.1-3
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.2-4
libpve-guest-common-perl: 3.1-3
libpve-http-server-perl: 3.0-6
libpve-storage-perl: 6.2-10
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.3-1
lxcfs: 4.0.3-pve3
novnc-pve: 1.1.0-1
proxmox-backup-client: 1.0.1-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.3-10
pve-cluster: 6.2-1
pve-container: 3.2-2
pve-docs: 6.2-6
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-3
pve-firmware: 3.1-3
pve-ha-manager: 3.1-1
pve-i18n: 2.2-2
pve-qemu-kvm: 5.1.0-6
pve-xtermjs: 4.7.0-2
qemu-server: 6.2-19
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
zfsutils-linux: 0.8.4-pve2

 

[zolpol]

Now, only just 11 VMs went down. RAM usage rise up, and done...

 

[zolpol]

I made a test with a VM, I'v removed all virto drivers, reboot and I intalled the drivers without Baloon drivers, but no luck...

Any advice or solution?

 

[Moayad]

Have you enough memory for all 26 VMs?

 

[zolpol]

Have you enough memory for all 26 VMs?

Yes I have. 512GB RAM in the server. VMs get only 8GB...

 

[zolpol]

In the event viewer:

Napló neve: System
Forrás: Microsoft-Windows-WER-SystemErrorReporting
Dátum: 2020. 11. 19. 9:10:18
Eseményazonosító:1001
Feladatkategória:Nincs
Szint: Hiba
Kulcsszavak: Klasszikus
Felhasználó: n.a.
Számítógép: VirtuDesk26
Leírás:
Az operációs rendszer hibaellenőrzés céljából újraindította a számítógépet. A művelet a következő volt: 0x0000005c (0x0000000000000201, 0xfffff78fc00014f8, 0xffffffffc0000001, 0x0000000000000000). A memóriakép mentve a következő fájlba: C:\Windows\MEMORY.DMP. Jelentés azonosítója: 8325df2e-bfc4-4c3d-b730-b97a6c9d06a3.
Esemény XML:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" />
<EventID Qualifiers="16384">1001</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2020-11-19T08:10:18.6310504Z" />
<EventRecordID>3948</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>System</Channel>
<Computer>VirtuDesk26.szeplastad.local</Computer>
<Security />
</System>
<EventData>
<Data Name="param1">0x0000005c (0x0000000000000201, 0xfffff78fc00014f8, 0xffffffffc0000001, 0x0000000000000000)</Data>
<Data Name="param2">C:\Windows\MEMORY.DMP</Data>
<Data Name="param3">8325df2e-bfc4-4c3d-b730-b97a6c9d06a3</Data>
</EventData>
</Event>

Something with the RAM management...

Linux based VMs are working fine.

 

[zolpol]

From qemu112 already died once.
From 102 to 111 same up time, but some of them suspended theriself, and the RAM usege over 90%

So any solution? Or am I the only one with this problem? I don't think so...

All of them Windows 10 PRO machines.

 

[Moayad]

Hi again,

So any solution? Or am I the only one with this problem? I don't think so...

Its happen on other node or only pve2 node?


The || Icon means that the VM is in sleep mode, that only happen when QEMU knows about a sleeping the VM, i.e Windows did a ACPI thing. Please check your VM settings if the sleep mode is enabled again.

 

[zolpol]

No more nodes, just pve2. pve1 was the test node earlier.

Yes I know what means the pause sign. It happends randomly with random VMs. Not enabled the sleeping for the Windows VMs.

Now, some of the VMs just died.

RAM usages goes up, and the VM dies..

 

[cooldar]

did you manage to solve the problem? I am having the exact same problem.
cpu would suddently spike and shuts down. pve just shows that the process got terminated by signal 15.
if I go windows log, I see the same error event as you

 

[jameswang]

Hi again,


Its happen on other node or only pve2 node?


The || Icon means that the VM is in sleep mode, that only happen when QEMU knows about a sleeping the VM, i.e Windows did a ACPI thing. Please check your VM settings if the sleep mode is enabled again.

Thank you. Changed Win10 VM's sleep mode to 'Never' fixed it.