WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] Memory problems persist... Cannot allocate memory

To: Pasi Kärkkäinen <pasik@xxxxxx>
Subject: Re: [Xen-users] Memory problems persist... Cannot allocate memory
From: Andrew Lyon <andrew.lyon@xxxxxxxxx>
Date: Wed, 27 Jan 2010 21:23:32 +0000
Cc: James Pifer <jep@xxxxxxxxxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 27 Jan 2010 13:24:28 -0800
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=j9bwZyd4T39WoTVF/dtMZ86CfWg3Mg8q2gxB9CJTUdY=; b=BL0uq2+2iwomCvpbMelpRvLfnROIomnjDWvhqzcnyrkGdM9HLmdCbj3zjtCvjlygFl f8XwHBHI2bTZ/AfP/LT4s7+2iioTc74Ds/9ByT0s4NBxHd6HsClWkem5EfeELb7tTI3F MDX7ZRs/8deBXrRcvUnu5A5wYx2r/MAlwr7zM=
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=PP0xIThMhj4e1lx0mubh5QuAgT4IQvcys52e8+DoQsdeh4B0+/JMAY0VST6WzGYosE Z/RdoEi9jcgJQxzU6t/5JwN6uMf/4PxFzidFVrNg4PzTBWL9GzRt/ltg3Ma+/9Jy4ECN DM4LaUbpCdQHw7e9K3BgcQxv4QD2q8nq6DPWQ=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20100127202235.GT2861@xxxxxxxxxxx>
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: <32936604.7.1264415147258.JavaMail.root@xxxxxxxxxxxx> <1264617382.15432.5.camel@xxxxxxxxxxxxxxxxxxxxxxxx> <20100127202235.GT2861@xxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
On Wed, Jan 27, 2010 at 8:22 PM, Pasi Kärkkäinen <pasik@xxxxxx> wrote:
> On Wed, Jan 27, 2010 at 01:36:21PM -0500, James Pifer wrote:
>> > Hello,
>> >
>> > If you set "dom0_mem=4096M" try to set "dom0_min_mem=4096" in 
>> > xend-config.sxp
>> > You said that the system ran a long time before showing "can't allocate 
>> > memory"
>> > it could be a problem with memory fragmentation or a memory leak.
>> > I saw something about that setting a long time ago, but I always use it.
>> >
>>
>> So you always set the dom0_min_mem equal to what you set the kernel
>> parameter to? I'll keep that in mind. I can't change anything right now
>> because I've opened a ticket with Novell and waiting to hear back.
>>
>
> Let us know how it goes..
>
>> The strange thing right now is, there's free memory in dom0, free memory
>> in swap, and a lot of free ram in xm (from xm info).
>>
>
> Definitely sounds like a bug.. Just don't reboot the box before they
> get what they need to debug it :)
>
> -- Pasi
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
>

I think I may have hit a similar bug running 3.4.2 , while testing
save/restore/migrate I occasionally got "unable to allocate memory"
errors and the domU failed to restore or migrate successfully, but
immediately trying to start the same vm on the same system was
successful, and having restarted it I was able to migrate it between
two servers several times.

So it appears that sometimes Xen will error that it cannot allocate
memory, but a subsequent request for the same amount of memory is
successful.

Andy

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users