New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
Wow, definitively no idea.
Have you tried reinstalling?
What happens if you kill vmtoolsd?
I've reinstalled several times =D
ps_mem.py output:
free -m output:
htop output:
http://i.imgur.com/ZOYod.png
Well, no.
I think you must check with your provider, or try another OS.
As I showed you, there is some memory ballonning in vmware, and probably is being used. But maybe someone with experience in vmware can give more help.
My VPS memory usage seem like this:
Here is an explaination from the support, it's new for me Was he right?
He is assuming you don't know what the -/+ buffers/cache column means, tell him that even the RAM usage excluding the cache'd is increasing. He's basically explained what I think you already know, which is to look at the buffers -/+ column, and you posted that even that column is increasing.
Yes, my explanation isn't the best which is why I tend to stay away from these threads but ya know!
+1
Tell them that you are not an idiot, lol
I've sent them an email with free -m screenshot and tell them which is mem cache and which is real mem )
Just append idiot with a swear word of your choice :P
Hmm.. I don't know if this is 100% correct anyway here goes,
OpenVZ uses a shared kernel where every VM uses 1 Kernel (shares it), because of this the memory usage of each VM is quiet low and hence minimal templates and installs are possible of various OS's.
While on VMWare or KVM, where virtulization is near dedicated, where the kernel is not shared, the memory usage cannot be pulled down to what it can be on openVZ, as each VM has it's own Kernel, just like a dedicated server.
Indeed but not 700MB, http://www.lowendtalk.com/discussion/comment/19242#Comment_19242.
@Infinity : whoops ! I missed that :O