vhostmd in the default configuration runs "virsh dominfo 0", which only makes sense for Xen. For other hypervisors, it causes libvirtd to return an error message. Unfortunately, this provokes a very bad memory leak in libvirtd: https://bugzilla.redhat.com/show_bug.cgi?id=528162 You just need a more recent version of libvirtd which includes the following commit: http://libvirt.org/git/?p=libvirt.git;a=commit;h=c6f1459eb998619ab21a92d9bb8... With the latest libvirt, I'm not able to make either vhostmd or libvirt(d) leak memory, but I'm going to run it all overnight just to make sure. Rich. -- Richard Jones, Emerging Technologies, Red Hat http://et.redhat.com/~rjones virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://et.redhat.com/~rjones/virt-top -- To unsubscribe, e-mail: vhostmd+unsubscribe@opensuse.org For additional commands, e-mail: vhostmd+help@opensuse.org
On Fri, Oct 09, 2009 at 05:13:46PM +0100, Richard W.M. Jones wrote:
With the latest libvirt, I'm not able to make either vhostmd or libvirt(d) leak memory, but I'm going to run it all overnight just to make sure.
I ran it over the weekend to make sure, and there was no noticable increase in memory usage in either vhostmd or libvirtd. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://et.redhat.com/~rjones/virt-top -- To unsubscribe, e-mail: vhostmd+unsubscribe@opensuse.org For additional commands, e-mail: vhostmd+help@opensuse.org
participants (1)
-
Richard W.M. Jones