On Fri, Feb 03, 2012 at 03:04:41AM -0500, Alex Jia wrote: > If you're using libvirt upstream to check it, you need to revoke > commit 6152c74, which fixed memory leak issue on cmdUndefine(), > it's okay without FD leaks if memory leak is fixed, in other > words, you will met FD leaks if you saw the following similar > error information: > > error: Failed to disconnect from the hypervisor, 1 leaked reference(s) This is a sign of some code failing to unref the virStoragePoolPtr or virStorageVolPtr or virConnectPtr object. > It seems libvirt deliberately leaks these FDs, right? I don't think that is delibrate. Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list