From mboxrd@z Thu Jan  1 00:00:00 1970
From: Olaf Hering <olaf@aepfle.de>
Subject: Re: xl.cfg, memory options clarification
Date: Fri, 9 Mar 2012 15:59:58 +0100
Message-ID: <20120309145958.GA14188@aepfle.de>
References: <4F5A179F.8060608@citrix.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
Content-Disposition: inline
In-Reply-To: <4F5A179F.8060608@citrix.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Anthony PERARD <anthony.perard@citrix.com>
Cc: Ian Jackson <ian.jackson@eu.citrix.com>, xen-devel@lists.xensource.com, Stefano Stabellini <stefano.stabellini@citrix.com>, Ian Campbell <ian.campbell@citrix.com>
List-Id: xen-devel@lists.xenproject.org

On Fri, Mar 09, Anthony PERARD wrote:

> I though "memory" is the amount of RAM that a guest will have. So qemu
> upstream will have this value as an amount of RAM and when qemu ask for the
> videoram, ...

maxmem= is the amount of memory the guest OS thinks it has, the one it
has to configure itself for. Think of it as a virtual memory stick with
capacity n GiB.
memory= is the amount of memory the balloon driver in the guest OS is
supposed to leave for the guest OS.

Olaf