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-devel

RE: [Xen-devel] OOM problems

To: John Weekes <lists.xen@xxxxxxxxxxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] OOM problems
From: Ian Pratt <Ian.Pratt@xxxxxxxxxxxxx>
Date: Sat, 13 Nov 2010 08:14:54 +0000
Accept-language: en-US
Acceptlanguage: en-US
Cc: Ian Pratt <Ian.Pratt@xxxxxxxxxxxxx>
Delivery-date: Sat, 13 Nov 2010 00:17:24 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4CDE44E2.2060807@xxxxxxxxxxxxxxxxxx>
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: <4CDE44E2.2060807@xxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcuDCL0T2P+HFBRdSjq44YEiBEl8iAAAbjjw
Thread-topic: [Xen-devel] OOM problems
> On machines running many HVM (stubdom-based) domains, I often see errors
> like this:
> 
> [77176.524094] qemu-dm invoked oom-killer: gfp_mask=0xd0, order=0,
> oom_adj=0

What do the guests use for storage? (e.g. "blktap2 for VHD files on an iscsi 
mounted ext3 volume")

It might be worth looking at /proc/kernel/slabinfo to see if there's anything 
suspicious.

BTW: 24 vCPUs in dom0 seems a excessive, especially if you're using stubdoms. 
You may get better performance by dropping that to e.g. 2 or 3.

Ian


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