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: Florian Manschwetus <florianmanschwetus@xxxxxx>
Subject: Re: [Xen-devel] Re: [xen-discuss] possible memory-leak in qemu-dm
From: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
Date: Thu, 15 Oct 2009 12:04:54 +0100
Cc: Mark Johnson <Mark.Johnson@xxxxxxx>, Xen discuss <xen-discuss@xxxxxxxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 15 Oct 2009 04:04:53 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4AD6FC67.5040606@xxxxxx>
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Alpine 2.00 (DEB 1167 2008-08-23)
On Thu, 15 Oct 2009, Florian Manschwetus wrote:
> Am 15.10.2009 12:26, schrieb Pasi Kärkkäinen:
> > On Wed, Oct 14, 2009 at 11:58:14PM +0200, Florian Manschwetus wrote:
> >> Am 14.10.2009 21:46, schrieb Mark Johnson:
> >>>
> >>> Hi Florian,
> >>>
> >>> Florian Manschwetus wrote:
> >>>> Mark,
> >>>> could you also make a short info howto update, a system I build just
> >>>> yesterday, when the patch is inplace. The older Machine I would have to
> >>>> re-bfu due to changed userspace, but the machine installed yesterday
> >>>> should be fixed with rebuilding and reinstalling xvm packages?
> >>>>
> >>>> Btw, could you sync-up the onnv-3.4 with b124? It is difficult to build
> >>>> b123 with b124, due to missing, with b124 obsolete, headerfiles.
> >>>
> >>> I've sync'd up with the changes in qemu-unstable, and qemu-dm is
> >>> still leaking a ton of memory for HVM guests which don't have PV
> >>> drivers.  So it looks like they don't have a correct fix upstream
> >>> for this.
> >> Uh, if this could be confirmed it is really a huge and ultimately ugly
> >> problem. If I could do anything to help you to fix it, give me some detail.
> >>
> > 
> > Yeah.. what kind of HVM guest is triggering this bug? 
> > How fast it is leaking mem? 
> It is a win2003R2 with exchange2007
> 
> xm uptime tmpexch
> Name                                ID Uptime
> tmpexch                              7 9 days,  3:21:39
> 
> PID USERNAME NLWP PRI NICE  SIZE   RES STATE    TIME    CPU COMMAND
> 2106 xvm         3  13    0 7340M 3807M cpu/4   31.4H  6.57% qemu-dm
> 
> Florian
> 

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.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel