[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] xl.cfg, memory options clarification

To: Anthony PERARD <anthony.perard@xxxxxxxxxx>
From: Olaf Hering <olaf@xxxxxxxxx>
Date: Fri, 9 Mar 2012 15:59:58 +0100
Cc: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, Stefano Stabellini <stefano.stabellini@xxxxxxxxxx>, Ian Campbell <ian.campbell@xxxxxxxxxx>
Delivery-date: Fri, 09 Mar 2012 15:00:25 +0000
List-id: Xen developer discussion <xen-devel.lists.xen.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

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel

References:
- [Xen-devel] xl.cfg, memory options clarification
  - From: Anthony PERARD

Prev by Date: Re: [Xen-devel] Need help with qemu args debug
Next by Date: [Xen-devel] [PATCH] tapdisk2: initialize 'name' parameter of BLKTAP2_IOCTL_CREATE_DEVICE
Previous by thread: [Xen-devel] xl.cfg, memory options clarification
Next by thread: Re: [Xen-devel] xl.cfg, memory options clarification
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.