Created attachment 714119 [details] X.log Description of problem: Xorg fails to start with spice/qlx on F17 Hosts. Version-Release number of selected component (if applicable): F19 Alpha TC1 (anaconda 19.2) How reproducible: always Steps to Reproduce: 1. Boot Fedora-19-Alpha-TC1-x86_64-DVD.iso, Actual results: Xorg will not star, no anaconda, etc. Expected results: No errors. Additional info: [ 121.321] resizing primary to 1024x768 [ 121.333] primary is 0x29e1260 [ 121.498] (EE) [ 121.498] (EE) Backtrace: [ 121.503] (EE) 0: Xorg (OsLookupColor+0x129) [0x46e569] [ 121.504] (EE) 1: /lib64/libpthread.so.0 (__restore_rt+0x0) [0x7f092e1a6f9f] [ 121.536] (EE) 2: /lib64/libc.so.6 (__memcpy_sse2+0xa0) [0x7f092ce65bf0] [ 121.536] (EE) 3: /usr/lib64/xorg/modules/drivers/qxl_drv.so (_init+0x3b44) [0x7f092bdffe84] [ 121.537] (EE) 4: /usr/lib64/xorg/modules/drivers/qxl_drv.so (_init+0x44c1) [0x7f092be01211] [ 121.538] (EE) 5: /usr/lib64/xorg/modules/drivers/qxl_drv.so (_init+0x493c) [0x7f092be01acc] [ 121.538] (EE) 6: /usr/lib64/xorg/modules/drivers/qxl_drv.so (_init+0x17de2) [0x7f092be283f2] [ 121.541] (EE) 7: Xorg (miDCInitialize+0xb0a) [0x57601a] [ 121.542] (EE) 8: Xorg (miFillUniqueSpanGroup+0x11bf) [0x5855af] [ 121.543] (EE) 9: Xorg (miFillUniqueSpanGroup+0x225b) [0x58774b] [ 121.544] (EE) 10: Xorg (DamageReportDamage+0x134) [0x51f3b4] [ 121.544] (EE) 11: Xorg (DamageReportDamage+0x4a6) [0x51f8e6] [ 121.545] (EE) 12: Xorg (DamageReportDamage+0x618) [0x51fe88] [ 121.546] (EE) 13: Xorg (DamageRegionAppend+0x1b40) [0x522f40] [ 121.547] (EE) 14: Xorg (miPaintWindow+0x1d1) [0x5769c1] [ 121.547] (EE) 15: Xorg (miWindowExposures+0x1d5) [0x577295] [ 121.548] (EE) 16: Xorg (miHandleValidateExposures+0x68) [0x58c628] [ 121.549] (EE) 17: Xorg (SetRootClip+0x1d0) [0x4659b0] [ 121.555] (EE) 18: Xorg (RamDacHandleColormaps+0x744) [0x4c9a94] [ 121.556] (EE) 19: /usr/lib64/xorg/modules/drivers/qxl_drv.so (_init+0x2dce) [0x7f092bdfe44e] [ 121.557] (EE) 20: Xorg (xf86PruneDuplicateModes+0x1b9a) [0x4c757a] [ 121.557] (EE) 21: Xorg (xf86Wakeup+0x3af) [0x4862ff] [ 121.558] (EE) 22: Xorg (WakeupHandler+0x6d) [0x43b03d] [ 121.559] (EE) 23: Xorg (WaitForSomething+0x1af) [0x46616f] [ 121.560] (EE) 24: Xorg (SendErrorToClient+0xe1) [0x436b01] [ 121.560] (EE) 25: Xorg (_init+0x3aad) [0x429abd] [ 121.562] (EE) 26: /lib64/libc.so.6 (__libc_start_main+0xf5) [0x7f092cdf8b75] [ 121.562] (EE) 27: Xorg (_start+0x29) [0x42671d] [ 121.563] (EE) 28: ? (?+0x29) [0x29] [ 121.564] (EE) [ 121.564] (EE) Segmentation fault at address 0x7f0921c85394 [ 121.564] Fatal server error: [ 121.564] Caught signal 11 (Segmentation fault). Server aborting [ 121.564] [ 121.564] (EE) Please consult the Fedora Project support at http://wiki.x.org for help. [ 121.564] (EE) Please also check the log file at "/tmp/X.log" for additional information. [ 121.564] (EE) [ 122.053] Server terminated with error (1). Closing log file.
Created attachment 714120 [details] anaconda.log
Created attachment 714121 [details] program.log
Created attachment 714123 [details] syslog file
The criteria only require virtualization to work at Beta, and then only N on N and N on N-1, not N on N-2. For me, both 19 on 19 and 19 on 18 work at present. So I'm -1 to this.
I looked at this issue again, and found that it did not affect all guests just one (i did not test all guest yet), and for the affected one, adding 'selinux=0' boot parameter fixed the issue. I don't known why selinux selected that guest in particular for failing, it has a lot of AVCs. The other guests booted fine with the defaults boot parameters. I'm also -1 to this now, since it is not even a general issue.
Discussed at 2013-03-27 blocker review meeting: http://meetbot.fedoraproject.org/fedora-blocker-review/2013-03-27/f19alpha-blocker-review-3.2013-03-27-16.01.log.txt . Rejected as a blocker per criteria and comment #5.
Re-assigning to correct component; are you still seeing this one? Any more useful info on the affected VM?
> are you still seeing this one? Any more useful info on the affected VM? no, and that is a good thing. maybe this can be closed, i will re-open if i encounter it again.
OK, let's go with that. Thanks!