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] domU die by hand of oom-killer

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] domU die by hand of oom-killer
From: chrysn <chrysn@xxxxxxxx>
Date: Wed, 03 Oct 2007 00:19:25 +0200
Delivery-date: Tue, 02 Oct 2007 15:20:37 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Openpgp: id=25D3E6FD; url=http://www.amsuess.com/christian/pgp
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv: Gecko/20070326 Thunderbird/ Mnenhy/

as per suggestion from irc, i post this here:

i have a debian etch dom0 with 3gb ram, plenty of swap space, and xen
i used to have a mixed setup of modified and unmodified linux domU, but
i changed to running all unmodified when the last 2gb of my current 3gb
ram arrived.

two days after changing to the pae-build of xen and un-modifying the
guests (something broke in the transition; unmodified guests are easier
to maintain), single domU started to freeze; it turned out that the
out-of-memory killer killed qemu-dm or its python parent (both happened).

the dom0 has 391mb of ram at its disposition and an additional 1gb swap
space. top says none of the processes is using more than 1.5% memory
under normal observation.

any ideas on what makes those processes eat up much more memory (at
least i guess they do, unless the oom killer went rogue) and how to
prevent it?

logs are attached
xen version is "3.0.3-1 (Debian 3.0.3-0-2)"


Attachment: logs.tar.bz2
Description: application/bzip

Xen-users mailing list
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] domU die by hand of oom-killer, chrysn <=