Ubuntu
libvirt package

Libvirt spams libvirt.log with virNetSocketReadWire and similar errors

Bug #1451598 reported by Dave Chiluk
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
libvirt (Ubuntu)
Fix Released
Medium
Dave Chiluk
Ubuntu precise-updates
Precise
Fix Released
Medium
Dave Chiluk

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.

See original description
Revision history for this message
Dave Chiluk (chiluk) wrote :

It should be noted this fix is already in trusty and newer.

description: updated
Dave Chiluk (chiluk)
Changed in libvirt (Ubuntu):
importance: Undecided → Low
status: New → Confirmed
Revision history for this message
Dave Chiluk (chiluk) wrote :

I know this debdiff does not fix all the errors, but it does alleviate some of them. I'd like to get this single backported commit integrated since I'm not sure if I will be able to find time to fix the remaining errors.

For those of you having issue with this, I greatly suggest moving to trusty, as these errors are significantly cleaned up there.

Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

The attachment "lp1451598.precise.debdiff" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.]

tags: added: patch
Dave Chiluk (chiluk)
description: updated
Serge Hallyn (serge-hallyn)
Changed in libvirt (Ubuntu):
status: Confirmed → Fix Released
importance: Low → Medium
Changed in libvirt (Ubuntu Precise):
importance: Undecided → Medium
Dave Chiluk (chiluk)
description: updated
Revision history for this message
Dave Chiluk (chiluk) wrote :

@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: nobody → Dave Chiluk (chiluk)
Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

@chiluk

the fix released is for the development version. The precise status is still 'new'.

Revision history for this message
Chris J Arges (arges) wrote : Please test proposed package

Hello Dave, or anyone else affected,

Accepted libvirt into precise-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libvirt/0.9.8-2ubuntu17.22 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in libvirt (Ubuntu Precise):
status: New → Fix Committed
tags: added: verification-needed
Revision history for this message
Dave Chiluk (chiluk) wrote :

Verification-done. I did not see any issues.

tags: added: verification-done
removed: verification-needed
Dave Chiluk (chiluk)
Changed in libvirt (Ubuntu Precise):
status: Fix Committed → Fix Released
Chris J Arges (arges)
Changed in libvirt (Ubuntu Precise):
status: Fix Released → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package libvirt - 0.9.8-2ubuntu17.22

---------------
libvirt (0.9.8-2ubuntu17.22) precise; urgency=medium

  * Quiet some of the following errors.
    "error : virNetSocketReadWire:1006 : End of file while reading data:
     Input/output error" (LP: #1451598)

 -- Dave Chiluk <email address hidden> Tue, 24 Mar 2015 18:01:03 -0500

Changed in libvirt (Ubuntu Precise):
status: Fix Committed → Fix Released
Revision history for this message
Chris J Arges (arges) wrote : Update Released

The verification of the Stable Release Update for libvirt has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.