On Thu May 19, 2011 at 09:40:41 +0100, Stefan Hajnoczi wrote:
> You are exercising both networking and storage. Have you cut the test
> down to just wget vs cp/rm?
Both seem to leak; but the cp/rm leaks more. Which suggests to me
that we're seeing a leak in the virtio block handling.
> Also why the sleep 10?
Just to keep the machine responsive!
> If you are building qemu-kvm from source you might like to enable
> tracing to track memory allocations in qemu-kvm. For full information
> see qemu-kvm/docs/tracing.txt.
Thanks that was a good read, and your wee recipe was very useful.
I'm now rebuilding with tracing of virtio stuff to see if anything
leaps out at me.
> Feel free to contact me on #qemu (oftc) or #kvm (freenode) IRC if you
> want some pointers, my nick is stefanha.
Thanks a lot.
Steve Kemp
--
Bytemark Hosting
http://www.bytemark.co.uk/
phone UK: 0845 004 3 004
Dedicated Linux hosts from 15ukp ($30) per month
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
