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: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Re: [xen-discuss] possible memory-leak in qemu-dm
From: Mark Johnson <johnson.nh@xxxxxxxxx>
Date: Thu, 15 Oct 2009 07:30:23 -0400
Cc: Mark Johnson <Mark.Johnson@xxxxxxx>, Florian Manschwetus <florianmanschwetus@xxxxxx>, Xen discuss <xen-discuss@xxxxxxxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 15 Oct 2009 04:30:52 -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; bh=7zy2581NTQfsAIxD74s6RaFIV0RvGUZhppBX7GOHQ/I=; b=IhmzRTFvagEmWz36GDmTtT4PZUqIL8WzRN/BNysE7zDjhZZ4wseKG2v6/5mrA2v0Wp P4hFoWLODfJgdNFFVw9s0Ydmf81T+U2hsynyGbGyxSklH0SCxCXNLYlX/rw0uv0tFcvG +1GjXoiQTgflp+Z2bAhzMpWP+t9nyHRz5FLNg=
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; b=wEeyDvSkcoI9utR4i8iHWi0UVZpyV06q5dERj72eXYDhpsUQ20Jb8Q7RJuYq7DreOD CpTsSnYf8EO/q33KBjdvFsa7huesgIXnOnNiA5nytq/bkQFcddQSj4K5kbOrGrx83YkL wLxxYt2lX1G0l/AvVS4hgmg19UNjjjKia23DA=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <alpine.DEB.2.00.0910151203320.4001@kaball-desktop>
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Thu, Oct 15, 2009 at 7:04 AM, Stefano Stabellini
<stefano.stabellini@xxxxxxxxxxxxx> 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.

I'm not sure when it first showed up...  It exists in current qemu-xen-3.4 bits.

I've updated the qemu bits to the latest qemu-xen-unstable bits (basically
running qemu-xen-unstable with xen 3.4) including your patches, and
qemu-dm is still leaking memory with a HVM guest with no PV drivers..

Tried a couple of different HVM guests with the same results..




MRJ

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