[Libvirt-cim] [PATCH] Make NetworkPool use libvirt's virtual network API

Dan Smith danms at us.ibm.com
Fri Jan 4 16:40:00 UTC 2008


KR> It looks like virNetworkFree() doesn't handle NULL pointers.  I think
KR> most of the other libvirt functions do though.

Actually, it looks like it does, it just complains about it.  For some
reason, virConnectClose() quietly returns on a bad pointer, but
virDomainFree() and virNetworkFree() both complain.  I'm not sure it's
a big deal, or worth making free conditional on network!=NULL.  I
imagine at some point we'll wrap the libvirt error handler, which
would allow us to hide this warning.

-- 
Dan Smith
IBM Linux Technology Center
Open Hypervisor Team
email: danms at us.ibm.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 188 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/libvirt-cim/attachments/20080104/76aed498/attachment.sig>


More information about the Libvirt-cim mailing list