macvtap: log an error if on failure to connect to netlink socket
macvtap: log an error if on failure to connect to netlink socket

A bug in libnl (see https://bugzilla.redhat.com/show_bug.cgi?id=677724
and https://bugzilla.redhat.com/show_bug.cgi?id=677725) makes it very
easy to create a failure to connect to the netlink socket when trying
to open a macvtap network device ("type='direct'" in domain interface
XML). When that error occurred (during a call to libnl's nl_connect()
from libvirt's nlComm(), there was no log message, leading virsh (for
example) to report "unknown error".

There were two other cases in nlComm where an error in a libnl
function might return with failure but no error reported. In all three
cases, this patch logs a message which will hopefully be more useful.

Note that more detailed information about the failure might be
available from libnl's nl_geterror() function, but it calls
strerror(), which is not threadsafe, so we can't use it.
(cherry picked from commit 12775d9491f0d98de6eb4593be4cacfaff1c4e47)

Signed-off-by: Steve Hodgson <eb20a6615749cf04ff61aa37e18f749ed6d01446@solarflare.com>

sshah-solarflare/Libvirt-PCI-passthrough-,sshah-solarflare/Libvirt-PCI-passthrough-,sshah-solarflare/Libvirt-PCI-passthrough-,sshah-solarflare/Libvirt-PCI-passthrough-,sshah-solarflare/Libvirt-PCI-passthrough-