Bug 1244869
Summary: | High Resolution Multi-Monitor Windows Guest freeze | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Sandy Stutsman <sstutsma> |
Component: | mingw-virt-viewer | Assignee: | Default Assignee for SPICE Bugs <rh-spice-bugs> |
Status: | CLOSED ERRATA | QA Contact: | SPICE QE bug list <spice-qe-bugs> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.6.0 | CC: | bgraveno, cfergeau, dblechte, djasa, fidencio, gklein, lsurette, rbalakri, sherold, spice-qe-bugs, tpelka, uril, yeylon, ykaul |
Target Milestone: | ovirt-3.6.0-rc | ||
Target Release: | 3.6.0 | ||
Hardware: | x86_64 | ||
OS: | All | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Prior to this update, Microsoft Windows virtual machines with multi-monitor setup in some cases waited for an image that had already been deleted, which caused the client to become unresponsive. With this update, reference counting has been added to channel images in the client and thread safety has been improved for image caching in the server. As a result, Windows virtual machines no longer hang due to the mentioned reasons.
|
Story Points: | --- |
Clone Of: | 1235442 | Environment: | |
Last Closed: | 2016-03-09 20:11:20 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | Spice | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1235442, 1247749 | ||
Bug Blocks: | 1235443 |
Comment 1
Fabiano FidĂȘncio
2015-07-23 09:22:46 UTC
The following commits fix the freeze: https://bugzilla.redhat.com/show_bug.cgi?id=1235442 http://cgit.freedesktop.org/spice/spice-gtk/commit/?id=c9d4773a666e00f347969981d2176708471ec0c7 https://bugzilla.redhat.com/show_bug.cgi?id=1235443 http://cgit.freedesktop.org/spice/spice/commit/?id=e4a42e50c2d0558583301309feb6f349ca4af0c5 Per David, I'm going to clone this for 6.8 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. https://rhn.redhat.com/errata/RHEA-2016-0377.html |