VMWare ESXi/VSphere Disable Balloon Segfault in Services Solution

After looking at several deployments of VMWare, we had one deployment where the company enabled balloon mode which is essentially a way to overcommit memory the hostnode(s) don't have. Let's say you have put your database into memory or use a cached service in Apache or haproxy/nginx. VMWare will start taking some portions of these and at some point it corrupts things and the application running will either crash, malfunction or segfault.

Another factor is that OOM will be triggered artificially. Take say a 16G VM that runs on a VMWare ESXi/Vsphere with the EXACT same OS image/kernel, and running the same container. At some point the one with balloon will probably hit OOM and you may never be able to reproduce it on a non-Balloon VM/host.

Balloon is horrible because it feels like the old days of computing with a slow HDD where you have too little RAM and your computer is swapping.

It sounds similar to KSM in KVM but KSM is smart enough to only work with shared pages of duplicated memory. Eg. if you had 200 VMs or containers using duplicated memory (eg. using a certain binary) it will combine those into one memory space to conveniently save memory duplication.

Is my VM even using balloon?

vmware-toolbox-cmd stat balloon 0 MB

You are looking for the number to be 0 but note it doesn't mean it won't start ballooning later on. This is more likely when you have processes that use more memory 1-2G+. Another symptom is that you will likely find the process that is getting ballooned will be slow (eg. even a docker ps or kubectl will be slower than normal).