This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] Re: libxenlight and memory for domain creation

To: Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>
Subject: [Xen-devel] Re: libxenlight and memory for domain creation
From: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
Date: Mon, 7 Dec 2009 17:53:13 +0000
Cc: "Xen-Devel \(E-mail\)" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Stefano Stabellini <Stefano.Stabellini@xxxxxxxxxxxxx>
Delivery-date: Mon, 07 Dec 2009 09:49:28 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <deeb3783-690f-43c3-8b90-f27fe073e34d@default>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <deeb3783-690f-43c3-8b90-f27fe073e34d@default>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Alpine 2.00 (DEB 1167 2008-08-23)
On Mon, 7 Dec 2009, Dan Magenheimer wrote:
> Hi Stefano (and other libxenlight developers) --
> I was wondering about how libxenlight does physical memory
> management and perused the code a bit.
> From what I see, it appears that libxenlight is completely
> ignorant of a machine's physical memory utilization, so
> I assume this must be handled/managed by higher level tools?
> (If I'm wrong about this, could you point me to the code
> that determines if there is enough physical memory available?)
> Also, I see that libxenlight handles the "memory" VM config
> parameter but not "maxmem".  Is this intentional?
One of the (few) missing pieces in libxenlight is memory management,
this is the reason why you cannot find anything related to memory at
the moment.

Libxenlight will never implement complicated algorithms to relocate the
available memory across multiple VMs, but it definitely should implement
the low level functions to change memory and maxmem in a guest.

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>