Created attachment 739548 [details] Screenshot after anaconda crash. Description of problem: The Fedora 19 RC4 DVD installer crashes during initial installation startup when running in an ESX VM environment. Version-Release number of selected component (if applicable): How reproducible: 100% repeatable Steps to Reproduce: 1. Setup ESX 5.1 running on bare-metal x86_64 hardware 2. Create VM in ESX with configuration listed below. 3. Boot VM from F19alphaRC4 DVD iso. 4. Select "Install Fedora" from boot menu 5. Watch boot messages, starting anaconda, crash as shown in attached screenshot. Actual results: Graphical installer crashes. Expected results: Graphical installer will start. Additional info: The same crash happens if the user selects to use VNC to perform the installation. VM configuration: Memory: 2048MB CPUs: 1 Video card: 1 display, 8MB video memory VMCI device: restricted CD/DVD drive: f19alphaRC4.iso Network adapter: E1000 Hard disk 1: 20GB (SCSI)
Please attach /tmp/syslog and /tmp/anaconda.log from when the error happens to this bug report. Thanks.
Created attachment 739565 [details] /tmp/syslog
Created attachment 739566 [details] /tmnp/anaconda.log
See new attachments.
Created attachment 739573 [details] /tmp/X.log
Created attachment 739574 [details] /tmp/X.log
[ 640.150] (EE) Backtrace: [ 640.170] (EE) 0: Xorg (OsLookupColor+0x129) [0x46e569] [ 640.174] (EE) 1: /lib64/libpthread.so.0 (__restore_rt+0x0) [0x7f5a35ff5f9f] [ 640.195] (EE) 2: /lib64/libc.so.6 (__memcpy_ssse3_back+0x209c) [0x7f5a34d6ed0c] [ 640.215] (EE) 3: /lib64/libpixman-1.so.0 (pixman_rasterize_edges+0xe006) [0x7f5a35b9e6b6] [ 640.220] (EE) 4: /lib64/libpixman-1.so.0 (pixman_image_composite32+0x453) [0x7f5a35b4f063] [ 640.241] (EE) 5: /lib64/libpixman-1.so.0 (pixman_glyph_cache_insert+0xf0) [0x7f5a35b90c50] [ 640.241] (EE) 6: /usr/lib64/xorg/modules/libfb.so (fbComposite+0x3bc) [0x7f5a2e4b553c] [ 640.358] (EE) 7: Xorg (DamageRegionAppend+0x7e6) [0x5209e6] [ 640.359] (EE) 8: Xorg (AddTraps+0x408e) [0x51db8e] [ 640.359] (EE) 9: Xorg (SendErrorToClient+0x3f7) [0x436e17] [ 640.360] (EE) 10: Xorg (_init+0x3aad) [0x429abd] [ 640.362] (EE) 11: /lib64/libc.so.6 (__libc_start_main+0xf5) [0x7f5a34c47b75] [ 640.362] (EE) 12: Xorg (_start+0x29) [0x42671d] [ 640.364] (EE) 13: ? (?+0x29) [0x29] [ 640.364] (EE) [ 640.364] (EE) Segmentation fault at address 0xffefffff
Similar crash occurs under VMware Fusion 5.0.3.
https://admin.fedoraproject.org/updates/FEDORA-2013-7181/xorg-x11-drv-vmware-13.0.1-1.fc19 might well fix this. I'll try and pull it into the next TC, but if you can think of a way to test in the meantime, please do, and add karma to the update!
(In reply to comment #9) > https://admin.fedoraproject.org/updates/FEDORA-2013-7181/xorg-x11-drv-vmware- > 13.0.1-1.fc19 might well fix this. I'll try and pull it into the next TC, > but if you can think of a way to test in the meantime, please do, and add > karma to the update! I've tested and confirmed that the xorg-x11-drv-vmware-13.0.1-1.fc19 rpm stabilizes X11 under ESX. (This test is based on performing the install in VirtualBox, installing the rpm, then moving the vmdk disk image over to ESX. This test does not verify the installer operation. But since X11 from Fedora 19 was previously unstable under ESX, this test demonstrates that this patch is required for Fedora 19 running on ESX for X11 to function. I do not have the infrastructure to rebuild the LiveCD with this rpm to test the installer. When this gets pulled into a TC or RC please update the ticket with the TC/RC number and I will re-test.
*** Bug 957889 has been marked as a duplicate of this bug. ***
Same backtrace with Fedora 19 Alpha on VMware Workstation 9.0.2
Installation using Fedora-19-Beta-TC3-x86_64-netinst.iso under VMware Workstation 9.0.2 works fine.
Great. The update went stable, so we can close this. Thanks.
*** Bug 955812 has been marked as a duplicate of this bug. ***
Confirmed that the beta TC3 correctly starts X11 and anaconda runs in the ESX 5.1 environment. Still testing to determine if this will resolve the ESX purple screen that happens with the alpha TC4.
*** Bug 954176 has been marked as a duplicate of this bug. ***