Search results

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..

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.

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...

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

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?

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

qm config: agent: 1 audio0: device=ich9-intel-hda,driver=spice boot: order=scsi0;net0 cores: 4 memory: 8192 name: DESKVIRT01 net0: virtio=D6:D4: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...

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.

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...