Bug 967679

Summary: QXL driver crashes RHEL6.4 host VM.
Product: [Fedora] Fedora Reporter: Dave Airlie <airlied>
Component: xorg-x11-drv-qxlAssignee: Alon Levy <alevy>
Status: CLOSED CANTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: airlied, ajax, alevy, awilliam, crobinso, dblechte, ebenes, hdegoede, juzhang, kparal, marcandre.lureau, neilsbb, pbonzini, sandmann, vbocek, xgl-maint
Target Milestone: ---Keywords: CommonBugs
Target Release: ---   
Hardware: i386   
OS: Unspecified   
Whiteboard: https://fedoraproject.org/wiki/Common_F19_bugs#rhel-qxl-crash
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 965101 Environment:
Last Closed: 2013-12-17 19:19:46 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:

Description Dave Airlie 2013-05-28 01:21:25 UTC
Originally reported wrongly, I've reproduced this problem.

No idea how to fix it.

We hit the assert in spice-server that was removed.

((null):3743): SpiceWorker-CRITICAL **: red_worker.c:9306:red_create_surface: Untested path stride >= 0

Alon any idea how we can avoid that?

Comment 1 Dave Airlie 2013-05-28 01:22:40 UTC
to reproduce install F19 in a RHEL6.4 VM under not spice, then switch to spice.

The problem is I don't know of anything we can trigger to avoid using stride >= 0 cases

Comment 2 Hans de Goede 2013-05-28 06:02:01 UTC
(In reply to Dave Airlie from comment #1)
> to reproduce install F19 in a RHEL6.4 VM under not spice, then switch to
> spice.
> 
> The problem is I don't know of anything we can trigger to avoid using stride
> >= 0 cases

AFAIK there is no way to find out if the assert is there or not, so indeed there is nothing the guest can do to avoid it.

I believe this is best fixed on the RHEL side as the assert actually is a spice-server bug there. The RHEL side of this is being tracked in bug 952666

Comment 3 Neil 2013-08-01 01:17:06 UTC
seeing this on x86_64 arch also.

Comment 4 Cole Robinson 2013-12-17 19:19:46 UTC
RHEL6.5 has the fix, and sounds like the opinion is this can't be avoided guest side, so just closing as CANTFIX