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-devel] fix for bug 651?

To: "Krysan, Susan" <KRYSANS@xxxxxxxxxx>
Subject: Re: [Xen-devel] fix for bug 651?
From: Steven Hand <Steven.Hand@xxxxxxxxxxxx>
Date: Mon, 10 Jul 2006 15:50:13 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Steven.Hand@xxxxxxxxxxxx
Delivery-date: Mon, 10 Jul 2006 07:50:37 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: Message from "Krysan, Susan" <KRYSANS@xxxxxxxxxx> of "Fri, 07 Jul 2006 13:51:44 EDT." <EF8D308BE33AF54D8934DF26520252D3035042FC@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
>changeset 10546
>looked promising as a fix for bug #651
><http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=3D651>, but I
>can still trigger the OOM killer.   I get a kernel panic out of memory
>error when I do a mem-set of dom0 to 512 on a 32GB system and mem-set of
>dom0 to 256 on 8GB system. 

Cset 10546 just makes it less likely - you'll pretty much always be 
able to trigger oom on linux if you reduce the memory by enough. I 
can't imagine any magic to fix this unfortunately :-)

Best practice is probably simply to empirically determine an approximate 
minimum phys mem and swap setup for the workload/machine you have, and 
then stick above that. 



Xen-devel mailing list

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