Might require some action from us, if we're running the backport
somewhere on our infrastructure, and at least possibly for the ones
running it for the test suite.
When virt-manager is connected to libvirtd from wheezy-backports, the
memory usage (both res and virt) of libvirtd on the server goes up by
about a megabyte a minute. It will keep going and eat several gigabytes
of RAM if left alone. Disconnecting virt-manager stops the memory usage
from increasing, but does not lower it back to an acceptable level.
The bug seems to be identical to the one described here, which is
resolved by using a newer version of netcf with libvirtd:
https://bugs.launchpad.net/ubuntu/+source/netcf/+bug/1201938
The libvirtd distributed with wheezy does not have this issue. I'm
assuming it does not make that particular call to libnetcf.
--
To UNSUBSCRIBE, email to debian-backports-request@???
with a subject of "unsubscribe". Trouble? Contact listmaster@???
Archive:
https://lists.debian.org/5371C612.9030204@dhampir.no
--
intrigeri
| GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc
| OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc
