Proxmox shows wrong stats about memory
- Thread starter asmar
- Start date
If you are comparing the memory usage inside VM with what Proxmox GUI shows, i dont think it will ever match exact. The memory stat on GUI shows usage by the node itself that includes memory used by VM, Hypervisors, underlying services etc. Are those VMs with fixed memory?
May be run something like htop to see what services in Proxmox node taking up those extra memory.
#apt-get install htop
#apt-get install htop
If you completely shut down the openVZ VM or the other VM does the memory usage displayed on GUI changes?
I'm pasting a few more details here in case it helps. All commands are inside the VM:
root@kolab1:~# free -m
total used free shared buffers cached
Mem: 8192 7315 876 0 0 6362
-/+ buffers/cache: 953 7238
Swap: 4096 0 4096
root@kolab1:~# cat /proc/meminfo
MemTotal: 8388608 kB
MemFree: 914332 kB
Cached: 6515244 kB
Buffers: 0 kB
Active: 3179476 kB
Inactive: 4237808 kB
Active(anon): 828688 kB
Inactive(anon): 73352 kB
Active(file): 2350788 kB
Inactive(file): 4164456 kB
Unevictable: 0 kB
Mlocked: 0 kB
SwapTotal: 4194304 kB
SwapFree: 4194304 kB
Dirty: 284 kB
Writeback: 0 kB
AnonPages: 902040 kB
Shmem: 3400 kB
Slab: 56980 kB
SReclaimable: 18288 kB
SUnreclaim: 38692 kB
root@kolab1:~# vmstat -s
8388608 K total memory
7464748 K used memory
3171400 K active memory
4238064 K inactive memory
923860 K free memory
0 K buffer memory
6515256 K swap cache
4194304 K total swap
0 K used swap
4194304 K free swap
32025 non-nice user cpu ticks
0 nice user cpu ticks
5930 system cpu ticks
6836340 idle cpu ticks
147 IO-wait cpu ticks
0 IRQ cpu ticks
0 softirq cpu ticks
0 stolen cpu ticks
1230440 pages paged in
34478932 pages paged out
184534 pages swapped in
266262 pages swapped out
0 interrupts
5013340 CPU context switches
1424980126 boot time
14072 forks
root@kolab1:~#
root@kolab1:~# free -m
total used free shared buffers cached
Mem: 8192 7315 876 0 0 6362
-/+ buffers/cache: 953 7238
Swap: 4096 0 4096
root@kolab1:~# cat /proc/meminfo
MemTotal: 8388608 kB
MemFree: 914332 kB
Cached: 6515244 kB
Buffers: 0 kB
Active: 3179476 kB
Inactive: 4237808 kB
Active(anon): 828688 kB
Inactive(anon): 73352 kB
Active(file): 2350788 kB
Inactive(file): 4164456 kB
Unevictable: 0 kB
Mlocked: 0 kB
SwapTotal: 4194304 kB
SwapFree: 4194304 kB
Dirty: 284 kB
Writeback: 0 kB
AnonPages: 902040 kB
Shmem: 3400 kB
Slab: 56980 kB
SReclaimable: 18288 kB
SUnreclaim: 38692 kB
root@kolab1:~# vmstat -s
8388608 K total memory
7464748 K used memory
3171400 K active memory
4238064 K inactive memory
923860 K free memory
0 K buffer memory
6515256 K swap cache
4194304 K total swap
0 K used swap
4194304 K free swap
32025 non-nice user cpu ticks
0 nice user cpu ticks
5930 system cpu ticks
6836340 idle cpu ticks
147 IO-wait cpu ticks
0 IRQ cpu ticks
0 softirq cpu ticks
0 stolen cpu ticks
1230440 pages paged in
34478932 pages paged out
184534 pages swapped in
266262 pages swapped out
0 interrupts
5013340 CPU context switches
1424980126 boot time
14072 forks
root@kolab1:~#
When using another piece of really nice script (https://raw.githubusercontent.com/pixelb/ps_mem/master/ps_mem.py) I'm taking the proper results but GUI still shows the wrong:
root@kolab1:~# python ps_mem.py
Private + Shared = RAM used Program
116.0 KiB + 19.0 KiB = 135.0 KiB logger
232.0 KiB + 18.0 KiB = 250.0 KiB mysqld_safe
224.0 KiB + 96.5 KiB = 320.5 KiB upstart-socket-bridge
320.0 KiB + 36.5 KiB = 356.5 KiB xinetd
324.0 KiB + 42.5 KiB = 366.5 KiB cron
284.0 KiB + 118.5 KiB = 402.5 KiB upstart-udev-bridge
608.0 KiB + 145.5 KiB = 753.5 KiB master
472.0 KiB + 360.0 KiB = 832.0 KiB udevd (3)
780.0 KiB + 69.0 KiB = 849.0 KiB idled
672.0 KiB + 223.5 KiB = 895.5 KiB pickup
824.0 KiB + 129.0 KiB = 953.0 KiB notifyd
816.0 KiB + 243.5 KiB = 1.0 MiB qmgr
948.0 KiB + 169.5 KiB = 1.1 MiB init
976.0 KiB + 212.5 KiB = 1.2 MiB ptloader
1.1 MiB + 131.5 KiB = 1.2 MiB nmbd
1.1 MiB + 176.5 KiB = 1.3 MiB lmtpd
1.3 MiB + 54.5 KiB = 1.4 MiB rsyslogd
1.4 MiB + 55.5 KiB = 1.4 MiB bash
1.2 MiB + 292.5 KiB = 1.5 MiB tlsmgr
1.8 MiB + 118.5 KiB = 1.9 MiB cyrus-master
1.8 MiB + 371.5 KiB = 2.2 MiB sshd (2)
1.6 MiB + 1.2 MiB = 2.8 MiB smbd (2)
3.5 MiB + 269.0 KiB = 3.8 MiB freshclam
8.0 MiB + 1.4 MiB = 9.4 MiB pop3d (8)
11.7 MiB + 370.5 KiB = 12.1 MiB /usr/sbin/postg
12.3 MiB + 100.0 KiB = 12.4 MiB named
16.1 MiB + 656.0 KiB = 16.7 MiB kolab-saslauthd
18.5 MiB + 347.5 KiB = 18.9 MiB ns-slapd
1.8 MiB + 17.7 MiB = 19.5 MiB /usr/sbin/spamd
20.4 MiB + 239.5 KiB = 20.7 MiB miniserv.pl
22.1 MiB + 3.5 MiB = 25.6 MiB imapd (16)
20.0 MiB + 7.9 MiB = 28.0 MiB kolabd (2)
3.3 MiB + 35.1 MiB = 38.4 MiB spamd child (2)
45.9 MiB + 16.3 MiB = 62.2 MiB wallaced (25)
82.0 MiB + 230.0 KiB = 82.3 MiB mysqld
117.0 MiB + 14.0 MiB = 130.9 MiB apache2.prefork (7)
77.6 MiB + 65.3 MiB = 142.8 MiB /usr/sbin/amavi (3)
293.7 MiB + 261.0 KiB = 293.9 MiB clamd
---------------------------------
940.4 MiB
=================================
root@kolab1:~#
root@kolab1:~# python ps_mem.py
Private + Shared = RAM used Program
116.0 KiB + 19.0 KiB = 135.0 KiB logger
232.0 KiB + 18.0 KiB = 250.0 KiB mysqld_safe
224.0 KiB + 96.5 KiB = 320.5 KiB upstart-socket-bridge
320.0 KiB + 36.5 KiB = 356.5 KiB xinetd
324.0 KiB + 42.5 KiB = 366.5 KiB cron
284.0 KiB + 118.5 KiB = 402.5 KiB upstart-udev-bridge
608.0 KiB + 145.5 KiB = 753.5 KiB master
472.0 KiB + 360.0 KiB = 832.0 KiB udevd (3)
780.0 KiB + 69.0 KiB = 849.0 KiB idled
672.0 KiB + 223.5 KiB = 895.5 KiB pickup
824.0 KiB + 129.0 KiB = 953.0 KiB notifyd
816.0 KiB + 243.5 KiB = 1.0 MiB qmgr
948.0 KiB + 169.5 KiB = 1.1 MiB init
976.0 KiB + 212.5 KiB = 1.2 MiB ptloader
1.1 MiB + 131.5 KiB = 1.2 MiB nmbd
1.1 MiB + 176.5 KiB = 1.3 MiB lmtpd
1.3 MiB + 54.5 KiB = 1.4 MiB rsyslogd
1.4 MiB + 55.5 KiB = 1.4 MiB bash
1.2 MiB + 292.5 KiB = 1.5 MiB tlsmgr
1.8 MiB + 118.5 KiB = 1.9 MiB cyrus-master
1.8 MiB + 371.5 KiB = 2.2 MiB sshd (2)
1.6 MiB + 1.2 MiB = 2.8 MiB smbd (2)
3.5 MiB + 269.0 KiB = 3.8 MiB freshclam
8.0 MiB + 1.4 MiB = 9.4 MiB pop3d (8)
11.7 MiB + 370.5 KiB = 12.1 MiB /usr/sbin/postg
12.3 MiB + 100.0 KiB = 12.4 MiB named
16.1 MiB + 656.0 KiB = 16.7 MiB kolab-saslauthd
18.5 MiB + 347.5 KiB = 18.9 MiB ns-slapd
1.8 MiB + 17.7 MiB = 19.5 MiB /usr/sbin/spamd
20.4 MiB + 239.5 KiB = 20.7 MiB miniserv.pl
22.1 MiB + 3.5 MiB = 25.6 MiB imapd (16)
20.0 MiB + 7.9 MiB = 28.0 MiB kolabd (2)
3.3 MiB + 35.1 MiB = 38.4 MiB spamd child (2)
45.9 MiB + 16.3 MiB = 62.2 MiB wallaced (25)
82.0 MiB + 230.0 KiB = 82.3 MiB mysqld
117.0 MiB + 14.0 MiB = 130.9 MiB apache2.prefork (7)
77.6 MiB + 65.3 MiB = 142.8 MiB /usr/sbin/amavi (3)
293.7 MiB + 261.0 KiB = 293.9 MiB clamd
---------------------------------
940.4 MiB
=================================
root@kolab1:~#
Hi,
I have a similar problem in my proxmox environmet. I have Windows 2008 and linux virtual servers running.
On the windows side the GUI always shows "more" memory than the actual ram usage.
On the linux side always shows the "exact" memory usage.
See the pictures, this happends in every server that I built.
Im using Proxmox 3.4-1.
Any help to understand this will be appreciated.
Tks!
I have a similar problem in my proxmox environmet. I have Windows 2008 and linux virtual servers running.
On the windows side the GUI always shows "more" memory than the actual ram usage.
On the linux side always shows the "exact" memory usage.
See the pictures, this happends in every server that I built.
Im using Proxmox 3.4-1.
Any help to understand this will be appreciated.
Tks!
Do you have latest guest tools installed on the windows server? https://fedoraproject.org/wiki/Windows_Virtio_Drivers#Direct_download
Is memory statically allocated or by means of balloon driver?
Is memory statically allocated or by means of balloon driver?
Last edited:
Hi,
download the iso and transfer them to the pve-node (e.g. /var/lib/vz/template/iso/ ).
Connect the iso with the VM-cdrom and you can install the ballon driver in windows via hardware (unknown pci device), update driver...
Udo
http://pve.proxmox.com/wiki/Windows...l_additional_VirtIO_drivers_on_running_System
It's for Win7 but should also work the same way for your version, iirc.
It's for Win7 but should also work the same way for your version, iirc.
Thanks a lot both of you. (Udo and Proxmox)
I understand, I updated the driver since it was already in the system, nothing change in my proxmox environment. Of course I shutted down the machine and rebooted.
Another thing, when the machines (Win2k8) started to use apps, the memory is increase (of course) but in Proxmox shows almost pretty the same. See picture 3.
Any idea...
I understand, I updated the driver since it was already in the system, nothing change in my proxmox environment. Of course I shutted down the machine and rebooted.
Another thing, when the machines (Win2k8) started to use apps, the memory is increase (of course) but in Proxmox shows almost pretty the same. See picture 3.
Any idea...
I'd installed Windows 2019 as VM,
Then added Baloon driver and runned Baloon service.
Rebooting of VM doesn't helps. I'm added and other drivers too, All for from directory 2k19.
Windows using just ~ 4GB. But ProxMox shows 97% of available 32Gb for that machine.
Can you advice something?
Drivers from Virtio-win 20.05.2019
Then added Baloon driver and runned Baloon service.
Rebooting of VM doesn't helps. I'm added and other drivers too, All for from directory 2k19.
Windows using just ~ 4GB. But ProxMox shows 97% of available 32Gb for that machine.
Can you advice something?
Drivers from Virtio-win 20.05.2019
