From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([140.186.70.92]:47838)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <afaerber@suse.de>) id 1RvtCs-0004DO-1y
	for qemu-devel@nongnu.org; Fri, 10 Feb 2012 11:20:23 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <afaerber@suse.de>) id 1RvtCl-0002lq-N6
	for qemu-devel@nongnu.org; Fri, 10 Feb 2012 11:20:17 -0500
Received: from cantor2.suse.de ([195.135.220.15]:38980 helo=mx2.suse.de)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <afaerber@suse.de>) id 1RvtCk-0002ku-WD
	for qemu-devel@nongnu.org; Fri, 10 Feb 2012 11:20:11 -0500
Message-ID: <4F3543B8.9010107@suse.de>
Date: Fri, 10 Feb 2012 17:20:08 +0100
From: =?ISO-8859-1?Q?Andreas_F=E4rber?= <afaerber@suse.de>
MIME-Version: 1.0
References: <CAEH94LgVhABxRxwQqxwUY_mVVUoXuX+zz34YwKHLVRjXgOfbxg@mail.gmail.com>
	<CAJSP0QVea0XCg67=XkHWuofrMheygi0HCkgPMe5cPtfm20sYsg@mail.gmail.com>
	<CAEH94Li61tpC5=QS6d97gO8GzhoQYcvOg7AmxbD=BLU+YddDdQ@mail.gmail.com>
	<CAJSP0QVe9NG63frfOJhtKfG_LDwz+F=H2f9CFGu1UYyw1LnhCQ@mail.gmail.com>
	<CAEH94Ljyx91ATZzzazjDDZtz1PZu96w6M+kmSy-wawEwLXFvgQ@mail.gmail.com>
In-Reply-To: <CAEH94Ljyx91ATZzzazjDDZtz1PZu96w6M+kmSy-wawEwLXFvgQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [Qemu-devel] Memory: how to determine the max memory size of
 one VM?
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Zhi Yong Wu <zwu.kernel@gmail.com>, Stefan Hajnoczi <stefanha@gmail.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>

Am 10.02.2012 12:23, schrieb Zhi Yong Wu:
> On Fri, Feb 10, 2012 at 7:10 PM, Stefan Hajnoczi <stefanha@gmail.com> w=
rote:
>> On Fri, Feb 10, 2012 at 11:00 AM, Zhi Yong Wu <zwu.kernel@gmail.com> w=
rote:
>>> On Fri, Feb 10, 2012 at 6:35 PM, Stefan Hajnoczi <stefanha@gmail.com>=
 wrote:
>>>> On Fri, Feb 10, 2012 at 9:47 AM, Zhi Yong Wu <zwu.kernel@gmail.com> =
wrote:
>>>>> Today i tried to create one VM with the option "-m 4000", and found=
 it
>>>>> failed with the following errors:
>>>>>
>>>>> Failed to allocate 4194304000 B: Cannot allocate memory
>>>>> Aborted (core dumped)
>>>>
>>>> Did you run on a 32-bit host?
>>> No, it is one x86_64 host.
>>
>> That is weird.  Have you tried strace(1) to find out which system call
>> is failing and why?
> It seems that it failed to call mmap().  ENOMEM

/etc/sysconfig/ulimit on SUSE has a default SOFTVIRTUALLIMIT value of
"80", i.e. 80% of the available physical + swap memory can be allocated
by one process.
For our SLES use cases we applied a simple patch to raise this limit via
RLIMIT_AS (so that, e.g., a 24 GB RAM host can create VMs > -m 20G).

ulimit -Sv can change this value, too.

For upstream QEMU we felt setting proper limits is the responsibility of
a management tool.

Andreas

--=20
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N=FCrnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imend=F6rffer; HRB 16746 AG N=FCrnbe=
rg