This patch is one alternative to solve the problem detailed in:
https://bugzilla.redhat.com/show_bug.cgi?id=816465
Some other unidentified library in use by libvirtd (in another thread)
is apparently temporarily binding to a NETLINK_ROUTE raw socket with
an address of "pid of libvirtd" during startup.
Can you identify this library. It should be possible to do so using
systemtap without all that much trouble. I'd rather we knew exactly
what was causing the problem, before we consider fixes or workarounds
Daniel
--
|: