From: Avi Kivity <avi@redhat.com>
To: Tanel Kokk <tanel.kokk@gmail.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 11:35:49 +0200 [thread overview]
Message-ID: <4B2363F5.5020103@redhat.com> (raw)
In-Reply-To: <4B236118.6090305@gmail.com>
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).
> 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?
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2009-12-12 9:35 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 [this message]
2009-12-12 10:11 ` Tanel Kokk
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=4B2363F5.5020103@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=tanel.kokk@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.