It seems that using virt-manager client > 1.0.0 causes the libvirtd
process to behave normally (no high cpu and no more memory leak).
You'll get this with Debian testing (Jessie) or Ubuntu 14.
It is possible to download from here
https://fedorahosted.org/released/virt-manager/virt-manager-1.0.1.tar.gz
and get it going on wheezy, although it's a bit of a PITA.
Forget about 1.1.0 as it requires newer gtk.
As for this bug, I believe there is still something that needs
addressing on the libvirtd server side, that allows the virt-manager
client <1.0.0 to upset it .
--
Chris Lewis
Systems Administrator
Inview Technology Ltd.
T: +44 (0) 1606 812500
M: +44 (0) 7980 446907
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
