Interesting observation. I have a similar setup and a similar finding: In the Proxmox VM overview the mem utilization is shown as 3.7GB and within HA hardware view it’s only 2.3GB… Don’t know why there’s a difference.
No, they should not be the same.
Inside the VM memory is used by programs running “on” the VM.
Outside the VM memory is used to hold the memory of the inside VM and also to hold the memory used to emulate the VM.
Well, then I wouldn’t expect that on both ends it shows me a total of 4GB (as specified when I created that VM)… If that’s the case I guess it’s a fault on proxmox side, when they show the “memory used to emulate the VM” as part of the whole memory reserved for the VM guest OS.
I have not looked that much into proxmox, but then maybe the guest VM reserved the memory, which proxmox then will see as used, but inside the VM it is still free.
As the above is a container, proxmox shows a usage of about 423MB.
However when the system is a VM, proxmox does not know alot about how it uses memory.
For instance, this is also the case with an OPNsense VM on Proxmox: https://forum.opnsense.org/index.php?topic=33969.0
Apparently it’s possible to install the QEMU Guest Agent in the home-assistant OS. After enabling it in the options of the VM, Proxmox should get more precise information.
I did this with my OPNsense VM and Proxmox has more info.
However, with regards to HAOS, I am not sure if it’s worth it - I guess that on each Supervisor update it will be required to reinstall the QEMU Guest Agent.