Red Hat Bugzilla – Bug 814094
libvirt starts to require sending keep-alive messages
Last modified: 2016-11-30 19:30:39 EST
libvirt has been rebased in RHEL 6.3 and now it requires to send keep-alive messages. Virt-who doesn't send them (and probably won't in the future because it would mean to implement event loop), so the connection get closed between two messages, so virt-who is getting "Broken pipe" error.
Disabling keep-alive messages is not possible now because of bug #813819.
Virt-who internal mechanism retries the connection to libvirt after the failure and it succeeds, so this mean no harm, just some unnecessary operations. And it breaks waiting for events from libvirt.
This is bug in invalid. This issue was caused by implementing double-forking in bug #806225. The event loop for interacting with libvirt was created to soon (before the double-fork) and keep-alive messages gets lost somehow. Will be fixed as part of fix in bug #813299, because it's same part of the code.
Closing as NOTABUG.