VMWare 7 vs Proxmox 9.1 host memory helpers

[baalkor]

Dear community,

I'm writing to you because we've finalized our migration from VMWare to proxmox. There was a lot to say but here I'm gonna focus on only one little thing.
We had a machine that was configured with 80 GB of RAM and 15 CPU.
Occasionally it would trigger memory warning on vCenter but that's pretty much it. it ran without any intervention from our team.
We did migrate it to Proxmox with the same configuration, and now we had to intervene a lot to help with memory usage.
1. The systemd-oom is triggered at one point and kill the application
2. The /proc/meminfo show that all memory is eaten up
3. To workaround this, we had to add swap up to 10GiB of to get an insight of the perfect value for the memory.
4. No ballooning is configured on Proxmox
5. looking at the VMWare info, memory consumption didn't changed between two platform

My question is then why on VMware is ran kind of ok while on Proxmox it would get killed by an Out-of-memory ? In other words, is there a technology on VMWare that would help a VM while there is an memory error ?

Thanks

 

[Heracleos]

I assume you have installed the virtio guests.
Have you tried enabling NUMA on the VM (obviously, if your physical host has two sockets and supports NUMA) to see if that changes anything?

 

[Impact]

Please share this

free -h
arc_summary -s arc
grep -sRE "^(memory|balloon)" /etc/pve | uniq
top -co%MEM

a picture of node > Summary and some of your system logs.

 

[baalkor]

Unfortunetly it's a mono socket. I did enable it thinking that I would still be able to have hot plug CPU/Memory but it seems it make no sense. No NUMA isn't enabled on the VM