<08761DCA-B8FA-41C8-A839-52E09BC06824@xxxxxxx>; 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 -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html