From mboxrd@z Thu Jan  1 00:00:00 1970
From: Matthew Daley <mattd@bugfuzz.com>
Subject: Re: Possible memory leak in qemu-dm (qemu-dm swapping
 20GB+, adding 2gb+ per day)
Date: Fri, 22 Nov 2013 14:49:50 +1300
Message-ID: <CAD3CanfEZckC+aU_edZ+cG+VgKBBRVcriO_p9NmwNAaj2dc4LA@mail.gmail.com>
References: <CE27EA8C-83B1-47A4-8667-830C961F329E@bivald.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: quoted-printable
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <CE27EA8C-83B1-47A4-8667-830C961F329E@bivald.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Niklas Bivald <niklas@bivald.com>
Cc: ilon@medinet.se, xen-devel@lists.xensource.com, ian.jackson@eu.citrix.com, roger.pau@citrix.com
List-Id: xen-devel@lists.xenproject.org

On Thu, Nov 21, 2013 at 3:57 AM, Niklas Bivald <niklas@bivald.com> wrote:
> Hi,
>
> Me and another sysadmin has independently been researching a problem where
> DomU randomly locks (Can=92t reach it via xl console, no ping / SSH
> connection, shown as stuck in running-state in xentop) on two of our
> separate machines (installed completely independently):
>
> Dom0:
> Debian 7.0 with Xen version: 4.1.4 and xen-utils 4.1.4-3+deb7u1
> Debian 7.1 with Xen version: 4.1
>
> DomU:
> Debian 7.0
> Debian 7.1(.3)
>
> Common denominator appears to be qemu-dm consuming (leaking?) memory until
> the Dom0 swaps. When the Dom0 swap is full, the domU appears to be locked
> (see above) Dom0, at which time a hard reboot a.ka. xl destroy + xl create
> is the only way to get it back. This *could* be related to "[Xen-devel]
> qemu-system-i386: memory leak?"
> http://xen.markmail.org/message/chqpifrj46lxdxx2

It would seem that the issue Roger fixed in upstream Qemu with the
patch linked in his reply (
http://lists.nongnu.org/archive/html/qemu-devel/2012-12/msg03677.html
) could indeed be the problem here.

Either way, that patch never made it into qemu-traditional, which
still suffers the same original problem (see
http://xenbits.xen.org/gitweb/?p=3Dqemu-xen-unstable.git;a=3Dblob;f=3Dhw/xe=
n_disk.c;h=3Dee8d36f9dbf3c754232d528485cbeff1fd66504e;hb=3DHEAD#l159
).

I'm not certain what the status of -traditional is, but surely it
should be backported in?

- Matthew