From: Avi Kivity <avi@redhat.com>
To: Leszek Urbanski <tygrys@moo.pl>
Cc: Alexander Graf <agraf@suse.de>, kvm@vger.kernel.org
Subject: Re: Huge memory leak in virtio, see kvm-Bugs-2989366
Date: Wed, 21 Apr 2010 11:25:58 +0300 [thread overview]
Message-ID: <4BCEB696.2030009@redhat.com> (raw)
In-Reply-To: <20100421075310.GA19155@moo.pl>
On 04/21/2010 10:53 AM, Leszek Urbanski wrote:
> <08761DCA-B8FA-41C8-A839-52E09BC06824@suse.de>; from Alexander Graf on Wed, Apr 21, 2010 at 00:51:21 +0200
>
>
>>> -039b9000-5ccd0000 rw-p 00000000 00:00 0
>>> +039b9000-65803000 rw-p 00000000 00:00 0
>>>
>>> (a heap leak?)
>>>
>>> I'm willing to debug further. The problem is 100% reproducible.
>>>
>> Certainly something malloc()'ed. It'd be great to send this through valgrind. Thanks to KVM the guest still runs natively, so the slowdown isn't _that_ bug through it. I'm also not a valgrind expert, but IIRC there was a separate memory allocation module.
>>
> Unfortunately, KVM guests with virtio won't even finish booting with valgrind.
> The guest's kernel complains about I/O errors in the first sectors of the
> virtio root device.
>
>
You can try glibc's malloc tracing, see libc's mtrace().
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-04-21 8:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-20 22:29 Huge memory leak in virtio, see kvm-Bugs-2989366 Leszek Urbanski
2010-04-20 22:51 ` Alexander Graf
2010-04-21 7:53 ` Leszek Urbanski
2010-04-21 8:25 ` Avi Kivity [this message]
2010-04-21 1:58 ` Ryan Harper
2010-04-21 6:08 ` Michael Tokarev
2010-04-21 13:29 ` Leszek Urbanski
2010-04-21 18:39 ` Stefan Hajnoczi
2010-04-21 14:32 ` Ryan Harper
2010-04-21 18:27 ` [PATCH] block: Free iovec arrays allocated by multiwrite_merge() Stefan Hajnoczi
2010-04-21 18:35 ` Ryan Harper
2010-04-21 18:43 ` Brian Jackson
2010-04-21 19:59 ` Leszek Urbanski
2010-04-21 20:03 ` Ryan Harper
2010-04-21 20:13 ` Leszek Urbanski
2010-04-25 12:36 ` Avi Kivity
2010-04-25 13:27 ` Stefan Hajnoczi
2010-04-25 13:35 ` Avi Kivity
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=4BCEB696.2030009@redhat.com \
--to=avi@redhat.com \
--cc=agraf@suse.de \
--cc=kvm@vger.kernel.org \
--cc=tygrys@moo.pl \
/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.