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] Re: [xen-discuss] possible memory-leak in qemu-dm

To: Pasi Kärkkäinen <pasik@xxxxxx>
Subject: Re: [Xen-devel] Re: [xen-discuss] possible memory-leak in qemu-dm
From: Mark Johnson <johnson.nh@xxxxxxxxx>
Date: Wed, 21 Oct 2009 10:54:43 -0400
Cc: Mark Johnson <Mark.Johnson@xxxxxxx>, Florian Manschwetus <florianmanschwetus@xxxxxx>, Xen discuss <xen-discuss@xxxxxxxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
Delivery-date: Wed, 21 Oct 2009 07:55:10 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=VTPtibWOcPQ2yFLVJ+SCKpJiALLz4ez1dZURQpjbTzk=; b=hszf82UiZsfFxnBA2bg1OMUz1FJzngXzUquhJ1kMrcmhibUs5w4nIpTYoXnYMu8O2E Omcg/lAg2EG1Wc8ejGRa1o8AoyT6dUQvnctBN7fG3pAg0WFtvDST4viMOPtNDZ+ckpZb 4qChbEoKhcLMpmrb4PmEMLR1IW92qpNLu5gwo=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=DGVLOv+kgWsgGhOkoJlQeac84Ode9Ur0zHcfj3Wi8Ts71Mm0pTIFe49irwuQcENw0z VZ6jDfXTyUp6l5U/PdDiaF18UC5vtXDUXCIx07lPLzglI4eZrkoNQdiAYqkSmBB1ADx4 3gZMvuMeaaHWcGgb5qNRRn3f8HnND3Y4faPw0=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20091021112427.GD1434@xxxxxxxxxxx>
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: <4ACAF4D7.7000101@xxxxxx> <4ACCB7CA.80700@xxxxxxx> <4ACCD15C.2080003@xxxxxx> <4AD62AA1.10908@xxxxxxx> <4AD64976.7040602@xxxxxx> <20091015102601.GY1434@xxxxxxxxxxx> <4AD6FC67.5040606@xxxxxx> <alpine.DEB.2.00.0910151203320.4001@kaball-desktop> <4AD7066D.2000902@xxxxxx> <20091021112427.GD1434@xxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Wed, Oct 21, 2009 at 7:24 AM, Pasi Kärkkäinen <pasik@xxxxxx> wrote:
> On Thu, Oct 15, 2009 at 01:24:29PM +0200, Florian Manschwetus wrote:
>> >
>> > Was this happening before you applied my patches, but after "fix qemu
>> > memory leak in block interface"?
>> > I am trying to understand if this is a recent regression.
>> It is an older build of xvm-3.4 gate
>> I have to review current patch state and will update accordingly if
>> possible.
>>
>> It was Mark, who told that the problem isn't fixed by the Patch. So I
>> not rushed to update.
>>
>
> Hmm.. wondering if this is opensolaris specific,

It's possible... I looked through our qemu patches and we don't have
any changes in that code path..  So I would be surprised..


> or if it happens also with Linux dom0s.

Has anyone else seen this on 3.4 or unstable?  e.g. boot a rhel3 guest and watch
the memory usage of qemu-dm... You can't miss it if its leaking...



MRJ

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