Bug#595711: more specific information

[George Shuklin <amarao@desunote.ru>]

Sad, but still not working - same behavior 

Here simplest test.

1. Set mem=512, maxmem=15GiB (for XCP it is xe vm-memory-limits-set
static-min=512MiB static-max=15GiB dynamic-min=2GiB dynamic-max=2GiB).
2. Boot vm.
3. Disable swap.
4. Run following in python (I test is with not only python, but with C
application with malloc, etc):

>>> file("/proc/meminfo").readlines()[1]
'MemFree:       1924200 kB\n'
>>> a=" "*1024*1024*1024
>>> file("/proc/meminfo").readlines()[1]
'MemFree:        873480 kB\n'
>>> b=" "*1024*1024*512
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
MemoryError
>>> b=" "*1024*1024*256
>>> c=" "*1024*1024*128
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
MemoryError
>>> file("/proc/meminfo").readlines()[1]
'MemFree:        610724 kB\n'
>>> d=" "*1024*1024*64
>>> e=" "*1024*1024*64
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
MemoryError
>>> file("/proc/meminfo").readlines()[1]
'MemFree:        545128 kB\n'
... If we descend to lower values, (about 1-2 MiB), with MemFree about
400-500MiB we will get to OOM killer, rampaging around and killing
randomly anyone (sshd, init, etc).


В Птн, 10/09/2010 в 08:13 +0100, Ian Campbell пишет:
> On Wed, 2010-09-08 at 15:52 +0400, George Shuklin wrote: 
> > My guess was wrong and this patch do not change situation.
> 
> Thanks for the extra info.
> 
> Please could you try the kernel now at
> http://xenbits.xen.org/people/ianc/2.6.26-25+balloon1/
> 
> Compared with +balloon0 I added a patch which I noticed between Debian's
> 2.6.26 kernel and the SLES11 2.6.27 kernel (and XCP kernel) which looked
> relevant.
> 
> > Gentoo kernel:
> > http://code.google.com/p/gentoo-xen-kernel/downloads/list
> 
> Thanks. I'm not familiar enough with Gentoo to know how to turn this
> tarball of patches into a functioning kernel source tree, it looks like
> it depends on a base kernel patchset from elsewhere or something.
> 
> If the above test kernel doesn't fix the issue do you think you could
> create a tarball of the fully patched gentoo source and put it somewhere
> I can get it?
> 
> Thanks,
> Ian.