Bug 746950
Summary: | spice-server: channel_event deadlock on reset + timeout | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Alon Levy <alevy> |
Component: | spice-server | Assignee: | Uri Lublin <uril> |
Status: | CLOSED ERRATA | QA Contact: | Desktop QE <desktop-qa-list> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.1 | CC: | acathrow, berrange, cfergeau, cmeadors, dblechte, ddumas, djasa, mkenneth, mkrcmari, pvine, tpelka |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | spice-server-0.8.2-5 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2011-12-06 15:22:01 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: |
Description
Alon Levy
2011-10-18 11:34:20 UTC
fixed with this brew build, verified using the procedure in the bug description. https://brewweb.devel.redhat.com/taskinfo?taskID=3734350 Alon commit pushed to 0.8 branch in upstream. Hmm, I was just going to complain that my brew build didn't enter the RHEL-6.2-candidate group/tag, but I guess it just took some time. There it is, moving to MODIFIED. I've tried to verify according to steps, however with spice-server-0.8.2-5 I can get: (qemu) system_reset (qemu) red_wait_outgoing_item: blocked #For about 2 minutes, qemu monitor is not responsive flush_cursor_commands: flush cursor timeout (qemu) #Qemu monitor is responsive again Is this expected correct behaviour? (Just making sure), Thanks. (In reply to comment #11) > I've tried to verify according to steps, however with spice-server-0.8.2-5 I > can get: > (qemu) system_reset > (qemu) red_wait_outgoing_item: blocked > #For about 2 minutes, qemu monitor is not responsive > flush_cursor_commands: flush cursor timeout > (qemu) > #Qemu monitor is responsive again > > Is this expected correct behaviour? (Just making sure), Thanks. These are two seperate issues. What you are seeing is a timeout entirely in spice-server that has not been addressed, it's actually part of the solution to a possible temporary delay (albiet not optimal). After the timeout the disconnection happens (you'll see the remaining channels are still there with info spice before and after). So in short yes, this is the expected correct behavior, and another non blocker bz is probably in order. Alon 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-1634.html After a consultation with Marian, we've decided that no ongoing testing is needed. |