Bug 952666
| Summary: | RHEL-7/F-19 does not work on 6.4 qemu-kvm + spice: assert "red_create_surface: Untested path stride >= 0" failed | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Gerd Hoffmann <kraxel> |
| Component: | spice-server | Assignee: | Uri Lublin <uril> |
| Status: | CLOSED ERRATA | QA Contact: | Desktop QE <desktop-qa-list> |
| Severity: | medium | Docs Contact: | |
| Priority: | high | ||
| Version: | 6.4 | CC: | acathrow, airlied, amit.shah, BobLfoot, cfergeau, dblechte, djasa, hdegoede, jkoten, kbaker, lagarcia, marcandre.lureau, mkenneth, pspacek, pvine, todoleza |
| Target Milestone: | rc | Keywords: | ZStream |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | spice-server-0.12.0-14.el6 | Doc Type: | Bug Fix |
| Doc Text: |
Previously, qemu-kvm terminated with the following error message, "((null):3635): SpiceWorker-CRITICAL **: red_worker.c:9306:red_create_surface: Untested path stride >= 0." The spice-server did not allow creation of a surface with "stride >= 0," as this path of code was untested, and no qxl driver did this before. On some systems, spice-server terminated when the qxl driver tried creating a surface with the "stride >= 0" path. With this update, spice-server no longer checks for the "stride >=0" path, and VMs with qxl devices are able to run and use their qxl driver.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-11-21 07:40:18 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: | |||
| Bug Depends On: | 952671 | ||
| Bug Blocks: | 973703 | ||
|
Description
Gerd Hoffmann
2013-04-16 11:59:15 UTC
*** Bug 947536 has been marked as a duplicate of this bug. *** Can someone explain to me how 947536 created 2013-04-02 12:54:57 is a duplicate of 952666 created 2013-04-16 07:59:15. I work mostly with Industrial Controls Software and Linux is only a hobby, but usually the newer is a duplicate of the older not the other way round. At least I hope this gets it addressed. Robert, it's usually done the way you describe it, but in this case, this bug has a link to a patch fixing the bug, so it makes more sense to keep the bug with this link open, and to close the other one as a duplicate. Thanks CHristopher I missed the patch link since it was in the text and not in the attachments sections. So this Patch -{http://cgit.freedesktop.org/spice/spice/commit/?id=2c85436dc6c2e9febecfb84c579e7a50a4a6bd6b}- is to an *.c file which means the maitnainer now needs to incorporate and issue an update rpm. IIRC.
I just deconstructed the spice-server rpm I am using and this patch is in there and still spice does not work with F19. Fedora 19-Beta-TC2 and Centos 6.4 with full updates are still imcompatable if qxl driver is used for video. *** Bug 964305 has been marked as a duplicate of this bug. *** I applied Alon's patch. This seems to solve the problem. Fedora 19 guest now comes (but very slowly). Do we want this in 6.4.z as well? I am still seeing this bug in Centos 6.4 with F19-Beta-RC4, but I suspect that is because Centos 6 is using spice-server-0.12.0-12.el6. I have not found a 0.12.0-14.el6 rpm or src.rpm to date. I also appllied Alon's patch to spice-server-0.12.0-12 and F19 with qxl driver now works on Centos 6.4 aka RHEL 6.4 QE can ack this when Fedora is added as a requirement for Spice. Please talk to Product Management. proposing for 6.4.z after the problem in comment 14 will be addressed. Since RHEL-7 is following F-19 quite close atm, any problems with F-19 will also impact RHEL-7, updating the Summary to reflect this. QE ca not reproduce the problem as reported with RHEL 7.0 builds from May 22 or May 29. Now reproducible on RHEL 7.0, adding QE ack. I confirm that package spice-server-0.12.0-14.el6.x86_64 (brew build 273061, SHA1sum a1f5e9336a9bbfd5ea16f899e0362a02fa7745ec) fixed the problem in our development lab. *** Bug 976204 has been marked as a duplicate of this bug. *** 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-1571.html |