Server reporting wrong RAM for host vs container, when installed in a Proxmox VM #492

New Issue

2025-10-31T15:13:24-05:00

GiteaMirror commented

2025-10-31 15:13:24 -05:00

Originally created by @supermarkert on GitHub (Jul 30, 2025).

I've created a Debian VM (in Proxmox), with 2 CPU and 8 GB RAM.
I've installed Docker, and installed the Periphery agent - systemd, and added it to my Komodo install.

Komodo is reporting that the System host has only 1.73 GB memory, but is correctly showing the Container usage as percentage of 8 GB.

Originally created by @supermarkert on GitHub (Jul 30, 2025). I've created a Debian VM (in Proxmox), with 2 CPU and 8 GB RAM. I've installed Docker, and installed the Periphery agent - systemd, and added it to my Komodo install. Komodo is reporting that the System host has only 1.73 GB memory, but is correctly showing the Container usage as percentage of 8 GB. <img width="1142" height="844" alt="Image" src="https://github.com/user-attachments/assets/ca5446c9-a82e-4fd0-9d8a-33349254e6a5" />

GiteaMirror added the bug label 2025-10-31 15:13:24 -05:00

GiteaMirror commented

2025-10-31 15:13:26 -05:00

@supermarkert commented on GitHub (Jul 30, 2025):

Not sure what changed, but I needed to make several adjustments/restores of this install, and when starting over (mostly from scratch), the issue is no longer present. Weird. No further logs are available.

@supermarkert commented on GitHub (Jul 30, 2025): Not sure what changed, but I needed to make several adjustments/restores of this install, and when starting over (mostly from scratch), the issue is no longer present. Weird. No further logs are available.

GiteaMirror commented

2025-10-31 15:13:26 -05:00

@supermarkert commented on GitHub (Jul 31, 2025):

Well, after several reboots of the host (and adjustments of RAM up to 12 GB), the problem has returned. So it seems to be a recurring problem. Komodo thinks the Host system only has 3.6 GB of Memory, but properly identifies the container as it's usage of 12 GB. The bigger issue is that this affects Memory alerts, because Komodo warns me if the RAM usage is over % of the 3.6 GB, and not the real 12 GB.
I'm vaguely aware of how memory Ballooning works with VMs, but the ultimate question is, where does Komodo get the ~12 GB number from that's used for the Container allocation? Because that's the correct (maximum) RAM allocated to the VM.

@supermarkert commented on GitHub (Jul 31, 2025): Well, after several reboots of the host (and adjustments of RAM up to 12 GB), the problem has returned. So it seems to be a recurring problem. Komodo thinks the Host system only has 3.6 GB of Memory, but properly identifies the container as it's usage of 12 GB. The bigger issue is that this affects Memory alerts, because Komodo warns me if the RAM usage is over % of the 3.6 GB, and not the real 12 GB. I'm vaguely aware of how memory Ballooning works with VMs, but the ultimate question is, where does Komodo get the ~12 GB number from that's used for the Container allocation? Because that's the correct (maximum) RAM allocated to the VM. <img width="1204" height="855" alt="Image" src="https://github.com/user-attachments/assets/2229fc86-07b5-4e18-8e30-76b621e1e300" />

GiteaMirror commented

2025-10-31 15:13:26 -05:00

@mbecker20 commented on GitHub (Aug 30, 2025):

Komodo gets all system stats using the sysinfo rust crate

@mbecker20 commented on GitHub (Aug 30, 2025): Komodo gets all system stats using the [sysinfo rust crate](https://github.com/GuillaumeGomez/sysinfo)