Description of problem: There is a small leak in fence_xvmd The fix looks like the following: --- cluster/fence/agents/xvm/virt.c 2006/11/03 15:58:56 1.3 +++ cluster/fence/agents/xvm/virt.c 2007/07/30 16:14:18 1.3.2.1 @@ -108,6 +108,7 @@ /* We have all the locally running domains & states now */ /* Sort */ + free(d_ids); qsort(&vl->vm_states[0], vl->vm_count, sizeof(vl->vm_states[0]), _compare_virt); return vl; Unfortunately, this is insufficient, as there is a much larger memory leak in libvirt as in bug #250146
Created attachment 160263 [details] Patch for leak in virt.c
Created attachment 160272 [details] New patch
Not calling virDomainDestroy() on the domain also had a side effect of keeping references open on the connection handle, causing virConnectClose() to not complete successfully; the second patch fixes that. Combined with the change to libvirt.c in bug #250146, this issue is resolved.
Patch in RHEL5 RHEL51 and HEAD
Removing dependency on the libvirt memory leak since we're going to ship these fixes irrespective of libvirt's status.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2007-0575.html