[Bug 1451598] Re: Libvirt spams libvirt.log with virNetSocketReadWire and similar errors

[Dave Chiluk]

@serge rmadison is still showing 0.9.8-2ubuntu17.21 in updates.  Which
means nothing has been released.  Did you incorrectly move this to Fix
Released?

** Changed in: libvirt (Ubuntu Precise)
     Assignee: (unassigned) => Dave Chiluk (chiluk)

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1451598

Title:
  Libvirt spams libvirt.log with virNetSocketReadWire and similar errors

Status in libvirt package in Ubuntu:
  Fix Released
Status in libvirt source package in Precise:
  New

Bug description:
  [Impact]
  Libvirt spams /var/log/libvirt/libvirtd.log logs with
  2014-11-19 14:31:15.787+0000: 46611: warning : qemuOpenVhostNet:493 : Unable to open vhost-net. Opened so far 0, requested 1
  2014-11-19 15:18:36.735+0000: 46610: error : virNetSocketReadWire:1377 : End of file while reading data: Input/output error
  2014-11-21 20:56:04.275+0000: 46610: error : virNetSocketReadWire:1377 : End of file while reading data: Input/output error
  2014-11-23 11:31:34.321+0000: 46610: error : virNetlinkEventCallback:340 : nl_recv returned with error: No buffer space available
  2014-11-18 14:47:28.882+0000: 47095: error : qemuMonitorIO:615 : internal error: End of file from monitor

  [Test Case]
  1. Create a precise host
  2. Create a number of kvm guests on that host using libvirt.
  3. $ sudo killall kvm
  4. See errors in log.

  [Regression Potential]
  * This is a backport of the upstream fix 89563efc0209b.  So there is possibility that I screwed up the backport.  However, I think I understand the error cleanup code in  this area of libvirt, and have modeled the backport after that cleanup code.
  * This patch has been tested, and does not appear to adversely affect libvirt functionality other than decreasing the number of warning messages.

  [Other Info]
  * This patch does not solve all the warning errors, but it does clean up a significant number of them *(about half given the above test case).  This level of libvirt is pretty terrible with spamming it's logs.  This level of libvirt also does not have a good interface that does all the reading and writing of the socket, so each function handles the reads and writes directly which results in lots of different error paths.
  * Upstream commit is available here.
  http://libvirt.org/git/?p=libvirt.git;a=commit;h=89563efc0209b854d2b2e554423423d7602acdbd
  * Trusty and newer already have this fix and many more.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1451598/+subscriptions