Hello there, I found this thread which is no longer accepting replies, it is marked solved but the solution is not there even though @Dunuin appeared to be reporting the same symptom at the very bottom of the thread with no solution. This was in 2020: https://forum.opnsense.org/index.php?topic=15708.0
Just wondering what the fix is, because I have posted about this same problem, but on Proxmox forums instead.. Screenshots of my problem are also included https://forum.proxmox.com/threads/wrong-memory-usage-reported-in-proxmox-interface-even-with-ballooning-off.135324/
This is happening regardless of ballooning settings and I'm frustrated for the exact same reason as @Dunuin at the bottom of the archived thread
Thanks very much for any assistance! I can't attach the screenshots, you need to click the Proxmox forum link, this forum is saying my pictures are too big
The RAM assignment you make in Proxmox is static. OPNsense thinks it's running on some hardware with say, 4G of physical memory and reports that it is using such and such many M of that, currently.
I don't see the inconsistency here. This is how hypervisors and VMs work unless the guest brings explicit support for dynamic allocation.
Okay, thank you, I'm still a bit unsure on why OPNsense not reporting properly but all other OSes are.. Maybe it's a weird FreeBSD thing?
My Pi Hole instance which is working properly doesn't report such inconsistencies https://i.imgur.com/nL5QB8q.png
It shows only 10% of the 512MB allocation in use, and so does Proxmox dashboard. OPNsense on the other hand shows 90% usage in Proxmox dash and only 10% usage in OPNsense dashboard & shell.. So I'm not entirely sure what to think anymore
Did you try to install the os-qemu-guest-agent plugin in OPNsense?
Yes, it is running in both OPNsense and enabled in Proxmox - it's one of the first things I tried, right off the bat sadly: https://imgur.com/a/xsKp3HR
Thank you kindly for your help!
I don't see an issue here, this behavior is completely normal and as expected. Same "issue" happens on my install. And besides of that, I think the answer has already been given in the proxmox thread.