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
|
Home