Bug 1715949

Summary: With RHEL 8.0 GA guest on Server 2016 (Hyper V) X fails with Segfaults
Product: Red Hat Enterprise Linux 8 Reporter: Adi Padhye <apadhye>
Component: xorg-x11-serverAssignee: Adam Jackson <ajax>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: high Docs Contact:
Priority: high    
Version: 8.0CC: ajax, alex.williamson, apadhye, csoriano, desktop-qa-list, jkachuck, knoel, tpelka
Target Milestone: rcKeywords: OtherQA
Target Release: 8.1Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Windows   
Whiteboard:
Fixed In Version: xorg-x11-server-1.20.3-8.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-11-05 21:04:04 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:    
Bug Blocks: 1654309, 1660905, 1666909, 1710589    

Description Adi Padhye 2019-05-31 17:47:52 UTC
Description of problem:
With RHEL 8.0 GA guest on Server 2016 (Hyper V) X fails with Segfaults

Please also refer to the BZ Bug 1650492 for details and same issue with RHEL 7.6 GA build

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 8 Joseph Kachuck 2019-07-24 17:44:47 UTC
Hello Nvidia,
Please download the test packages from:
http://people.redhat.com/jkachuck/.1715949/

Please note these may be removed in 3 days.

Thank You
Joe Kachuck

Comment 9 Joseph Kachuck 2019-08-08 15:11:45 UTC
Hello Nvidia,
if this is requested for Z stream. Please provide a client impact statement. Please confirm what a client would see if the field from this issue.
Please also provide what it would mean if this waited for RHEL 8.1.

Thank You
Joe Kachuck

Comment 10 Adi Padhye 2019-08-20 22:15:57 UTC
Hi Joe - we were able to verify the xorg patches you provided and the issue is no longer seen. Anyway to get these patches back into RHEL 8.0 via zstream process? Thanks!

Comment 11 Joseph Kachuck 2019-08-21 15:10:13 UTC
Hello Adi,
To request this for Z stream please respond to comment 9.

Thank You
Joe Kachuck

Comment 12 Adi Padhye 2019-08-21 21:18:09 UTC
(In reply to Joseph Kachuck from comment #9)
> Hello Nvidia,
> if this is requested for Z stream. Please provide a client impact statement.
> Please confirm what a client would see if the field from this issue.
> Please also provide what it would mean if this waited for RHEL 8.1.
> 
> Thank You
> Joe Kachuck

Hi Joe -

We are requesting for a Z stream update for RHEL 8.0.
The impact would be customers running RHEL 8.0 VM on hyper-v host will see X fails to start with segmentation fault. Thus making the configuration unusable.
Your updated Xorg patches resolves the issue, waiting until RHEL 8.1 for this means the current RHEL 8.0 will be a unusable configuration for such users. 

Let me know if you need any further details. Thanks again for consideration.

Regards,
Adi

Comment 13 Joseph Kachuck 2019-08-22 13:53:01 UTC
Hello Adi,
From the current justification this would appear to be adding functionality. Is this something that works sometimes and then fails?
Errata stream is only for urgent/critical bugs, at current this would not meet this. This will not be approved for Z stream.

Do you have any clients with a bug currently open with Red Hat on this issue?

Thank You
Joe Kachuck

Comment 14 Adi Padhye 2019-09-19 13:32:02 UTC
Joe - given what we discussed in previous calls, we are okay with not getting the zstream update for this. Thanks!

Comment 15 Adi Padhye 2019-10-23 13:57:03 UTC
Just to update, we verified the fix in RHEL 8.1 snapshot 4.

Comment 17 errata-xmlrpc 2019-11-05 21:04:04 UTC
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://access.redhat.com/errata/RHBA-2019:3412