Bug 731673
Summary: | virsh # start domain1 --console hang there at the third time | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | yanbing du <ydu> |
Component: | libvirt | Assignee: | Daniel Berrangé <berrange> |
Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | medium | Docs Contact: | |
Priority: | high | ||
Version: | 6.2 | CC: | bsarathy, dallan, dyuan, jeder, mzhan, rwu, veillard, whuang |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | libvirt-0.9.4-8.el6 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2011-12-06 11:27:05 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 716393 |
Description
yanbing du
2011-08-18 10:17:41 UTC
There are multiple fixes in upstream GIT. We need all of the changes to daemon/ and src/rpc which impact streams, upto and including this final change: commit b3fb288e52b7d0a0e58ab0e0bcac970436832d04 Author: Daniel P. Berrange <berrange> Date: Wed Aug 31 17:42:58 2011 +0100 Fix tracking of RPC messages wrt streams Reproduced this bug with libvirt-0.9.4-7.el6, "virsh # start domain1 --console" will hang at the 3rd time. Verified PASS with libvirt-0.9.4-9.el6, "virsh # start domain1 --console" run normally for 5 times. But there are still some errors in libvirtd.log at the guest "power down": 15:48:44.185: 10072: error : daemonStreamEvent:208 : stream had I/O failure 15:48:44.186: 10072: error : virFDStreamUpdateCallback:111 : internal error stream is not open 15:48:44.186: 10072: error : qemuMonitorIO:577 : internal error End of file from monitor 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-2011-1513.html |