Hello,
Currently, when trying to run Windows VMs on Fusion 13.5, I've noticed that the vmware-vmx processes in Activity Monitor show roughly double the Memory that was assigned to each VM - i.e., if I create a new Windows 11 VM and assign 4GB RAM, vmware-vmx shows ~8.05GB in Activity Monitor.
I've found that there have been various threads over the years talking about this, but none of these threads seem to have been 'resolved'. The trick of downgrading the Compatibility level to version 19 still seems to 'work' (in that Activity Monitor shows a realistic value) for Linux VMs.
I can also see that macOS is being reasonably smart about compressing memory: if I stop using the VMs for a few minutes, and then look at the Real Memory column in Activity Monitor and the RSS from `ps aux | grep vmware-vmx`, it looks like the Real memory of each process broadly aligns to what's reported by the guest OS.
But, if I go back to using the VMs, the Compressed Memory deflates, and Real jumps back up again: with 4GB assigned to the VM and the guest reporting 3GB in use, Real/RSS shows ~6GB.
I would raise a support case, but it seems my entitlement doesn't allow me to.
Has anyone ever had official confirmation from VMware support about what is going on?