public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Tanel Kokk <tanel.kokk@gmail.com>
To: Avi Kivity <avi@redhat.com>
Cc: kvm@vger.kernel.org
Subject: Re: In kvm, a single process cannot allocate more than 3.6GB ram. Why?
Date: Sat, 12 Dec 2009 12:11:00 +0200	[thread overview]
Message-ID: <4B236C34.9010302@gmail.com> (raw)
In-Reply-To: <4B2363F5.5020103@redhat.com>

On 12/12/09 11:35, Avi Kivity wrote:
> On 12/12/2009 11:23 AM, Tanel Kokk wrote:
>> On 12/12/09 10:55, Avi Kivity wrote:
>>   
>>> On 12/11/2009 11:03 AM, Tanel Kokk wrote:
>>>     
>>>> Does anybody have a glue why process are not able to allocate more than
>>>> 3.6GB memory ?
>>>>
>>>> What should i do to allow process allocate more than 3.6GB memory?
>>>> Is it
>>>> possible at all?
>>>>
>>>>        
>>> A guest or host process?  And what happens when you try?
>>>      
>> guest process
>>
>> We discovered that if postgres process (on guest) used to use only 3.6GB
>> memory regardless of guest had 8GB memory in common.
>>
>>    
> 
> 
> That's probably a postgres configuration error (or you're using 32-bit
> postgres).

postgres is 64bit:
root@lu2-kvm-db1 ~]# file /usr/lib/postgresql/8.3/bin/postgres
/usr/lib/postgresql/8.3/bin/postgres: ELF 64-bit LSB executable, x86-64,
version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux
2.6.8, not stripped

> 
> 
>> Then I made simple python script, which just eat memory:
>> ------------------------------------
>> #!/usr/bin/python
>> import time, random
>>
>> i = 0
>> while (i<  100000000):
>>      a[i] = random.random()
>>      i = i + 1
>>
>> time.sleep(600)
>> ------------------------------------
>> And I get python MemoryError, when script has devoured about 3.6GB ram
>>    
> 
> 
> Doesn't mean much - Python may allocate a lot more memory when extending
> the array.
> 
> What does 'cat /proc/meminfo' in the guest say?
> 

[root@lu2-kvm-db1 ~]# cat /proc/meminfo
MemTotal:       10267308 kB
MemFree:          228944 kB
Buffers:           19680 kB
Cached:          6069524 kB
SwapCached:            0 kB
Active:          8175200 kB
Inactive:        1374884 kB
Active(anon):    3238044 kB
Inactive(anon):   544104 kB
Active(file):    4937156 kB
Inactive(file):   830780 kB
Unevictable:           0 kB
Mlocked:               0 kB
SwapTotal:             0 kB
SwapFree:              0 kB
Dirty:             15968 kB
Writeback:             0 kB
AnonPages:       3461108 kB
Mapped:           327816 kB
Slab:             171452 kB
SReclaimable:     121756 kB
SUnreclaim:        49696 kB
PageTables:       244268 kB
NFS_Unstable:          0 kB
Bounce:                0 kB
WritebackTmp:          0 kB
CommitLimit:     8727208 kB
Committed_AS:    6056168 kB
VmallocTotal:   34359738367 kB
VmallocUsed:       38180 kB
VmallocChunk:   34359645255 kB
DirectMap4k:        4032 kB
DirectMap2M:    10481664 kB

Tanel

  reply	other threads:[~2009-12-12 10:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-11  9:03 In kvm, a single process cannot allocate more than 3.6GB ram. Why? Tanel Kokk
2009-12-11  9:55 ` Thomas Mueller
2009-12-11 10:14   ` Tanel Kokk
2009-12-12  8:55 ` Avi Kivity
2009-12-12  9:23   ` Tanel Kokk
2009-12-12  9:35     ` Avi Kivity
2009-12-12 10:11       ` Tanel Kokk [this message]
2009-12-13 10:04         ` Avi Kivity
2009-12-13 11:30           ` Tanel Kokk
2009-12-13 11:32             ` Avi Kivity

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4B236C34.9010302@gmail.com \
    --to=tanel.kokk@gmail.com \
    --cc=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox