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


Re: [Xen-users] More memory problems.

To: James Pifer <jep@xxxxxxxxxxxxxxxx>
Subject: Re: [Xen-users] More memory problems.
From: J <dreadpiratejeff@xxxxxxxxx>
Date: Tue, 6 Oct 2009 15:21:27 -0400
Cc: Xen List <xen-users@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 06 Oct 2009 12:22:09 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=Be3s4rBX7zvgrtZB/l4tKIclNGwJtQXMf6/rTYM4nzc=; b=hKN103D+OLCuaU+jJHAbp1Xf4QZsAP3XD9/Mh5nDNgC1LhNtB3F8kZes4a30CuIsHj fuEH9sCawwcwSsMGc5llmmpAv4E7hm2e4GcLhtHmHIix6i3M9XrEkiBUfbe2LhjxFlDa dB6I0osw9Nd5/Lothc1Lae5mlk37OsqEsGGtk=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=YQgRYZLDQzYrxdVmYnjgLNwXSV+tVrOgybu6sMUj+lI/RiY6AFizuvnPZf5MAvozGX QcIjeX0XVCob/Gwje1bpMxf1RL07IVR9Yr3GsQK16eOoL8o7oAdlJnP8fYI2dBLAM6Qs Qdhfe0wUEcK6JI4iVwOGQkaB8CbgGsc9AdbU8=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1254856251.22919.7.camel@xxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <1254856251.22919.7.camel@xxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
On Tue, Oct 6, 2009 at 15:10, James Pifer <jep@xxxxxxxxxxxxxxxx> wrote:
> I have several xen servers running on SLES10SP2. I occasionally have
> problems with allocating memory. When this happens the only fix I know
> of is to shut down all the domUs and restart the server. Or at least
> xend, which affects many of my domUs.
> I have this problem on two servers right now. One of them has plenty of
> free memory available. See below:

> When I try to start a domU I get:
> # xm start lakvre05
> Error: [Errno 12] Cannot allocate memory
> Usage: xm start <DomainName>
> Start a Xend managed domain
>  -p, --paused                   Do not unpause domain after starting
> it
>  -c, --console_autoconnect      Connect to the console after the
> domain
>                                 is created
> Any suggestions for working around this or is restarting xend the only
> option?

add dom0_mem=XXXM to the Xen entry (on the first line for this boot
option) in menu.lst.

Make XXX something rational for Dom0... I usually set dom0 on my
systems to 512M or 1024M depending on how much physical ram the system

That usually fixed the problem for me.  The problem is or was (not
sure if it was ever actually fixed) in the code that handles
ballooning the memory.  After a while, Xen will just stop shrinking
Dom0's memory allocation, OR, it's a race and the freeing of memory
from Dom0 happens slower than the allocating of memory for the new

Then it gets stuck and the only fix, as you've mentioned, is to reboot.

So limiting Dom0's memory allocation to something small leaves the
rest of the system memory unallocated and unused and thus free for
handing out to DomUs.

This can also happen if you have a lot of DomUs being installed and
deleted, or stopped and started frequently.



Stephen Leacock  - "I detest life-insurance agents: they always argue
that I shall some day die, which is not so." -

Xen-users mailing list

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