Bug 952666 – RHEL-7/F-19 does not work on 6.4 qemu-kvm + spice: assert "red_create_surface: Untested path stride >= 0" failed

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 952666 - RHEL-7/F-19 does not work on 6.4 qemu-kvm + spice: assert "red_create_surface: Untested path stride >= 0" failed

Summary:	RHEL-7/F-19 does not work on 6.4 qemu-kvm + spice: assert "red_create_surface...

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Linux 6
Classification:	Red Hat
Component:	spice-server (Show other bugs)
Sub Component:
Version:	6.4
Hardware:	Unspecified Unspecified

Priority	high Severity medium
Target Milestone:	rc
Target Release:	---
Assigned To:	Uri Lublin
QA Contact:	Desktop QE
Docs Contact:

URL:
Whiteboard:
Keywords:	ZStream

Duplicates:	947536 964305 976204 (view as bug list)
Depends On:	952671
Blocks:	973703
	Show dependency tree / graph

Reported:	2013-04-16 07:59 EDT by Gerd Hoffmann
Modified:	2013-11-21 02:40 EST (History)
CC List:	16 users (show)

See Also:
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 02:40:18 EST
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHBA-2013:1571	normal	SHIPPED_LIVE	spice-server bug fix and enhancement update	2013-11-20 16:39:57 EST

Groups: None (edit)

Description Gerd Hoffmann 2013-04-16 07:59:15 EDT

Description of problem:
qemu-kvm aborts with this message:
((null):3635): SpiceWorker-CRITICAL **: red_worker.c:9306:red_create_surface: Untested path stride >= 0

Version-Release number of selected component (if applicable):
spice-server-0.12.0-12.el6.x86_64

How reproducible:
100%

Steps to Reproduce:
Boot Fedora 19 Alpha live iso in qemu-kvm, with -vga qxl
  
Additional info:
<hans>
So we would need to add:
http://cgit.freedesktop.org/spice/spice/commit/?id=2c85436dc6c2e9febecfb84c579e7a50a4a6bd6b 
</hans>

Comment 1 Gerd Hoffmann 2013-04-18 03:37:23 EDT

*** Bug 947536 has been marked as a duplicate of this bug. ***

Comment 2 Robert Lightfoot 2013-04-18 05:38:27 EDT

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.

Comment 3 Christophe Fergeau 2013-04-18 05:50:08 EDT

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.

Comment 4 Robert Lightfoot 2013-04-18 05:56:16 EDT

Thanks CHristopher I missed the patch link since it was in the text and not in the attachments sections.

Comment 5 Robert Lightfoot 2013-04-19 14:54:25 EDT

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.

Comment 6 Robert Lightfoot 2013-04-20 11:13:23 EDT

I just deconstructed the spice-server rpm I am using and this patch is in there and still spice does not work with F19.

Comment 7 Robert Lightfoot 2013-05-03 18:37:37 EDT

Fedora 19-Beta-TC2 and Centos 6.4 with full updates are still imcompatable if qxl driver is used for video.

Comment 8 Christophe Fergeau 2013-05-17 15:57:38 EDT

*** Bug 964305 has been marked as a duplicate of this bug. ***

Comment 10 Uri Lublin 2013-05-19 05:47:04 EDT

I applied Alon's patch.
This seems to solve the problem.
Fedora 19 guest now comes (but very slowly).

Comment 11 Christophe Fergeau 2013-05-21 05:31:46 EDT

Do we want this in 6.4.z as well?

Comment 12 Robert Lightfoot 2013-05-23 21:40:23 EDT

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.

Comment 13 Robert Lightfoot 2013-05-24 08:33:22 EDT

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

Comment 14 Paul Vine 2013-05-28 08:02:24 EDT

QE can ack this when Fedora is added as a requirement for Spice. Please talk to Product Management.

Comment 15 David Blechter 2013-05-28 08:11:46 EDT

proposing for 6.4.z after the problem in comment 14 will be addressed.

Comment 21 Hans de Goede 2013-05-29 06:32:50 EDT

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.

Comment 23 Paul Vine 2013-05-30 13:10:23 EDT

QE ca not reproduce the problem as reported with RHEL 7.0 builds from May 22 or May 29.

Comment 24 Paul Vine 2013-06-12 07:28:52 EDT

Now reproducible on RHEL 7.0, adding QE ack.

Comment 27 Petr Spacek 2013-06-18 03:36:44 EDT

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.

Comment 28 Christophe Fergeau 2013-06-20 03:33:23 EDT

*** Bug 976204 has been marked as a duplicate of this bug. ***

Comment 31 errata-xmlrpc 2013-11-21 02:40:18 EST

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

Note You need to log in before you can comment on or make changes to this bug.