From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leszek Urbanski Subject: Re: Huge memory leak in virtio, see kvm-Bugs-2989366 Date: Wed, 21 Apr 2010 09:53:10 +0200 Message-ID: <20100421075310.GA19155@moo.pl> References: <20100420222956.GA13218@moo.pl> <08761DCA-B8FA-41C8-A839-52E09BC06824@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Cc: kvm@vger.kernel.org To: Alexander Graf Return-path: Received: from moo.pl ([217.149.240.132]:65451 "EHLO moo.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752450Ab0DUHxO (ORCPT ); Wed, 21 Apr 2010 03:53:14 -0400 Content-Disposition: inline In-Reply-To: <08761DCA-B8FA-41C8-A839-52E09BC06824@suse.de> Sender: kvm-owner@vger.kernel.org List-ID: <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. -- Leszek "Tygrys" Urbanski, SCSA, SCNA "Unix-to-Unix Copy Program;" said PDP-1. "You will never find a more wretched hive of bugs and flamers. We must be cautious." -- DECWARS http://cygnus.moo.pl/ -- Cygnus High Altitude Balloon