From: Tanel Kokk <tanel.kokk@gmail.com>
To: Thomas Mueller <thomas@chaschperli.ch>
Cc: kvm@vger.kernel.org
Subject: Re: In kvm, a single process cannot allocate more than 3.6GB ram. Why?
Date: Fri, 11 Dec 2009 12:14:27 +0200 [thread overview]
Message-ID: <4B221B83.8090606@gmail.com> (raw)
In-Reply-To: <hft4ts$ls$1@ger.gmane.org>
On 12/11/09 11:55, Thomas Mueller wrote:
>
>
>
> Am Fri, 11 Dec 2009 11:03:27 +0200 schrieb Tanel Kokk:
>
>> 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?
>>
>
> just some thoughts:
>
> * is qemu/kvm 64bit?
# file /usr/bin/kvm
/usr/bin/kvm: ELF 64-bit LSB executable, x86-64, version 1 (SYSV),
dynamically linked (uses shared libs), for GNU/Linux 2.6.8, stripped
> * check "ulimit -a" on console if a process is limited on memory usage
> (config file /etc/security/limits.conf)
# ulimit -a
core file size (blocks, -c) unlimited
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 53248
max locked memory (kbytes, -l) unlimited
max memory size (kbytes, -m) unlimited
open files (-n) 99999
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) unlimited
real-time priority (-r) 0
stack size (kbytes, -s) unlimited
cpu time (seconds, -t) unlimited
max user processes (-u) 4096
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited
Tanel
next prev parent reply other threads:[~2009-12-11 10:14 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 [this message]
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
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=4B221B83.8090606@gmail.com \
--to=tanel.kokk@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=thomas@chaschperli.ch \
/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