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-users] Memory problems persist... Cannot allocate memory

To: Xen List <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] Memory problems persist... Cannot allocate memory
From: James Pifer <jep@xxxxxxxxxxxxxxxx>
Date: Wed, 30 Dec 2009 23:39:20 -0500
Delivery-date: Wed, 30 Dec 2009 19:39:47 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
I have always had a problem with my xen servers having memory problems
after a random period of time. For example, even if there's free memory
available, if you try to add a new domU or restart one, virt-manager
says it can't allocate memory. I was really hoping I had gotten past
this issue on my latest SLES11 servers running xen 3.4 by specifying
domU memory and disabling ballooning. 

Unfortunately the problem has reappeared on one of these servers. My
only solution is a restart, which affects 12-15 servers. Are others
having this problem? There has to be a resolution to this. 

I will try restarting xend and see if that resolves it, but I need to
wait until I can restart dom0 in case it completely hoses it. 

I also just made another post that has me scared to death where I
completely lost a whole domU from my ocfs2 volume when I rebooted a
server, so I'm a bit gun shy right now!


Xen-users mailing list