Bug 890297
Summary: | libvirtd.log will get an I/O error when close a virt-viewer guest terminal | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | EricLee <bili> |
Component: | virt-viewer | Assignee: | Daniel Berrangé <berrange> |
Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6.4 | CC: | acathrow, cfergeau, cwei, dallan, dblechte, dyuan, jtomko, lnovich, marcandre.lureau, mjenner, mzhan, tzheng |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | virt-viewer-0.5.6-6.el6 | Doc Type: | Bug Fix |
Doc Text: |
Cause:
Close a virt-viewer guest terminal
Consequence:
libvirtd.log will get an I/O error
Fix:
Unregister libvirt events and callbacks on dispose
Result:
There is no longer I/O error in the libvirtd log when closing virt-viewer.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2013-11-21 08:06:09 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
EricLee
2012-12-26 08:59:18 UTC
Libvirtd is just saying it got EOF on a socket. The only thing that could perhaps be considered to be a bug is that libvirtd is a bit too laud (warning could be enough) and reporting the EOF as EIO is a bit confusing too. IMO this is a supportability issue as I think these errors might be confusing to users. This error is caused by virt-viewer not cleaning up the callbacks and events when disconnecting. Upstream patch: https://www.redhat.com/archives/virt-tools-list/2013-July/msg00136.html I can reproduce this issue with: virt-viewer-0.5.6-2.el6.x86_64 Tested with: virt-viewer-0.5.6-6.el6.x86_64 After close virt-viewer,there is no such Input/output error info in libvirtd.log.So move the bug to VERIFIED. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2013-1578.html |