cloudmin OpenVZ memory allocation bug

Submitted by helpmin on Fri, 06/24/2011 - 23:35

It looks like that Cloudmin always assign the same value for vmguarpages and oomguarpages (roughly 100MB). I checked this for a 1GB and 2GB container.

This is probably a bug, right?

Status: 
Closed (fixed)

Comments

Submitted by JamieCameron on Sat, 06/25/2011 - 11:27

Yes .. in the case where a memory limit is set, vmguarpages should be set the same as privvmpages to be consistent with what I wrote in your other ticket about memory over-allocation.

I will fix this in the next Cloudmin release.

Submitted by helpmin on Thu, 06/30/2011 - 20:14

Cloudmin 5.6: The barrier is still 100MB even though the memory limit is unlimited.

Submitted by helpmin on Fri, 07/01/2011 - 01:18

I also want to point that this is probably a critical issue to only assign 100MB of guaranteed memory to a container with 4GB memory limit.

Submitted by JamieCameron on Fri, 07/01/2011 - 13:18

So in Cloudmin 5.6, new VMs will get their guaranteed memory set to the same as the maximum memory.

In 5.7, you will be able to adjust the guaranteed memory separately..

Submitted by helpmin on Fri, 07/01/2011 - 17:24

I tested new VMs, checked user bean counters and still saw the 100MB barrier.

Submitted by JamieCameron on Fri, 07/01/2011 - 17:43

Is vmguarpages set in the container's OpenVZ config file?

Submitted by helpmin on Sat, 07/02/2011 - 03:10

Yes, it is set, but only to roughly 120MB (33792 pages)

Submitted by JamieCameron on Sat, 07/02/2011 - 19:09

Did you set the regular memory limit to "unlimited" initially? Cloudmin 5.6 just sets to guaranteed limit to 128M in this case ... only if you set an actual memory limit will the guaranteed memory be set to the same thing.

Submitted by helpmin on Sat, 07/02/2011 - 19:38

Yes, I did. But shouldn't the guaranteed memory be higher for unlimited as well? 128M seems kind of very low? Or is this something you are going to fix with In 5.7, you will be able to adjust the guaranteed memory separately..

Submitted by JamieCameron on Sat, 07/02/2011 - 20:57

Yes, the proper fix will be in cloudmin 5.7 - the 128mb setting is just a quick hack to avoid leaving the guaranteed memory unset.

Submitted by helpmin on Sun, 07/03/2011 - 00:51

Understand, will wait for 5.7 and then test with Centos 6.0 extensively :-)

Submitted by Issues on Sun, 07/17/2011 - 02:32

Automatically closed -- issue fixed for 2 weeks with no activity.