Bug 1085074

Summary: Xorg does not start under Xen PV/HVM guests
Product: [Fedora] Fedora Reporter: Konrad Rzeszutek Wilk <ketuzsezr>
Component: xorg-x11-driversAssignee: X/OpenGL Maintenance List <xgl-maint>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: boris.ostrovsky, jana, john.haxby, pasik, raistlin, xgl-maint
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 11:19:19 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 Konrad Rzeszutek Wilk 2014-04-07 18:14:47 UTC
Description of problem:

On the VNC view I see:
Fatal IO error 0 (Success) on X server:1 

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

Downloaded from:
https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/x86_64/os/LiveOS/

Which shows todays date.


How reproducible:
100%



Steps to Reproduce:

1) Boot Fedora with Xen.
2) Download the 'vmlinuz' and 'initrd.img' image. 
3) Create this file (say test.cfg)
extra="root=live:http://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/x86_64/os/LiveOS/squashfs.img  repo=http://dl.fedorapr
oject.org/pub/fedora/linux/development/rawhide/x86_64/os"
kernel="vmlinuz"
ramdisk="initrd.img"
memory=1024
maxmem=2048
maxvcpus = 2
vcpus = 2
name = "rawhide-64"
vif = [ 'mac=00:0f:4b:01:00:87,bridge=switch' ]
disk= ['phy:/dev/guests/rawhide-64,hda,w']
vfb = [ 'vnc=1, vnclisten=0.0.0.0,vncunused=1']

4). Setup a bridge (in this case called 'switch').

5). xl create -c test.cfg

Actual results:
If I try to start 'Xorg' in the console I get:

X.Org X Server 1.15.0
Release Date: 2013-12-27
X Protocol Version 11, Revision 0
Build Operating System:  3.12.8-300.fc20.x86_64 
Current Operating System: Linux g-f19.dumpdata.com 3.15.0-0.rc0.git9.1.fc21.x86_
64 #1 SMP Thu Apr 3 20:11:16 UTC 2014 x86_64
Kernel command line: root=live:http://dl.fedoraproject.org/pub/fedora/linux/deve
lopment/rawhide/x86_64/os/LiveOS/squashfs.img  repo=http://dl.fedoraproject.org/
pub/fedora/linux/development/rawhide/x86_64/os
Build Date: 28 February 2014  02:09:21AM
Build ID: xorg-x11-server 1.15.0-5.fc21 
Current version of pixman: 0.32.0
        Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,

...
Initializing built-in extension DRI2
Loading extension GLX
(EE) BUG: triggered 'if (dev->ptrfeed != ((void *)0))'
(EE) BUG: devices.c:1475 in InitPtrFeedbackClassDeviceStruct()
(EE) 
(EE) Backtrace:
(EE) 0: Xorg (InitPtrFeedbackClassDeviceStruct+0x50) [0x42e210]
(EE) 1: /usr/lib64/xorg/modules/input/evdev_drv.so (_init+0x1c0b) [0x7f73d772dc7b]
(EE) 2: /usr/lib64/xorg/modules/input/evdev_drv.so (_init+0x3c33) [0x7f73d7731f93]
(EE) 3: Xorg (ActivateDevice+0x4a) [0x42d64a]
(EE) 4: Xorg (xf86NewInputDevice+0x1f3) [0x485a43]
(EE) 5: Xorg (config_fini+0xafb) [0x49bd3b]
(EE) 6: Xorg (config_fini+0x1063) [0x49ce73]
(EE) 7: Xorg (config_init+0x9) [0x49ae49]
(EE) 8: Xorg (InitInput+0xb4) [0x479464]
(EE) 9: Xorg (remove_fs_handlers+0x3d9) [0x43c719]
(EE) 10: /lib64/libc.so.6 (__libc_start_main+0xf5) [0x7f73e1551e95]
(EE) 11: Xorg (_start+0x29) [0x426c8e]
(EE) 12: ? (?+0x29) [0x29]
(EE) 

Expected results:

none of the (EE).

Additional info:

Comment 1 Konrad Rzeszutek Wilk 2014-04-14 15:52:57 UTC
And under HVM, so with the Cirrus Framebuffer I get Xorg to die too.

I presume this problem would then also show up with KVM, but I don't have the time right now to try it out.

Comment 2 Jana Saout 2014-06-02 11:47:03 UTC
Invalid bug check hit, fixed upstream:

http://cgit.freedesktop.org/xorg/xserver/commit/dix/devices.c?id=6a848122def0f2a439e21c50f22814db11760132

Comment 3 Konrad Rzeszutek Wilk 2014-06-04 19:52:41 UTC
Hey Jana,

Fantastic! Thank you for the update.

Comment 4 Boris Ostrovsky 2014-06-09 17:42:25 UTC
Yes, I can confirm that this fixes the problem. Or at least that build 1.15.99.903 (which includes the above fix) does not exhibit this issue anymore with PV guests.

Comment 5 Jaroslav Reznik 2015-03-03 15:40:31 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22

Comment 6 Fedora End Of Life 2016-07-19 11:19:19 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.