All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Manschwetus <florianmanschwetus@gmx.de>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: Mark Johnson <Mark.Johnson@Sun.COM>,
	Xen discuss <xen-discuss@opensolaris.org>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Re: [xen-discuss] possible memory-leak in qemu-dm
Date: Thu, 15 Oct 2009 13:24:29 +0200	[thread overview]
Message-ID: <4AD7066D.2000902@gmx.de> (raw)
In-Reply-To: <alpine.DEB.2.00.0910151203320.4001@kaball-desktop>


[-- Attachment #1.1: Type: text/plain, Size: 2072 bytes --]

Am 15.10.2009 13:04, schrieb Stefano Stabellini:
> 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.
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.

Florian


[-- Attachment #1.2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 3686 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

  reply	other threads:[~2009-10-15 11:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4ACAF4D7.7000101@gmx.de>
     [not found] ` <4ACCB7CA.80700@sun.com>
     [not found]   ` <4ACCD15C.2080003@gmx.de>
     [not found]     ` <4AD62AA1.10908@sun.com>
2009-10-14 21:58       ` [xen-discuss] possible memory-leak in qemu-dm Florian Manschwetus
2009-10-15 10:26         ` Pasi Kärkkäinen
2009-10-15 10:41           ` Florian Manschwetus
2009-10-15 11:04             ` Stefano Stabellini
2009-10-15 11:24               ` Florian Manschwetus [this message]
2009-10-21 11:24                 ` Pasi Kärkkäinen
2009-10-21 14:54                   ` Mark Johnson
2009-10-21 15:00                     ` Stefano Stabellini
2009-11-06 16:17                     ` Mark Price
2009-10-15 11:30               ` Mark Johnson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4AD7066D.2000902@gmx.de \
    --to=florianmanschwetus@gmx.de \
    --cc=Mark.Johnson@Sun.COM \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=xen-discuss@opensolaris.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.