Created attachment 889108 [details] Screenshot showing trace Description of problem: Kernel oops booting a live KDE Version-Release number of selected component (if applicable): kernel-3.15.0-0.rc2.git1.1.fc21.x86_64 How reproducible: Tried only once Steps to Reproduce: 1. Download abovementioned ISO image 2. qemu-system-x86_64 -m 2048 -cdrom Fedora-Live-KDE-x86_64-rawhide-20140423.iso 3. Select Troubleshooting, Check-Media and start Actual results: Didn't see if media check worked or not. Eventually got a kernel trace on the virtual screen Expected results: Normal boot Additional info: Screenshot of the traceback (attached)
qemu version is qemu-1.6.2-1.fc20.x86_64 .
*** Bug 1089095 has been marked as a duplicate of this bug. ***
Created attachment 889430 [details] screenshot showing kernel trace Got the bug again today with the following sequence: "qemu-system-x86_64 -m 2048 -cdrom Fedora-Live-KDE-x86_64-rawhide-20140424.iso ** (qemu-system-x86_64:2580): WARNING **: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. " After the QEMU screen appeared, I selected Troubleshooting and Test and Boot. I also used the TAB key to remove rhgb and quiet. I saw normal console output up to about the high nineties, then the trace appeared. I did not see the media check take place.
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
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 22 kernel bugs. Fedora 22 has now been rebased to 4.2.3-200.fc22. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 23, and are still experiencing this issue, please change the version to Fedora 23. If you experience different issues, please open a new bug report for those.
*********** MASS BUG UPDATE ************** This bug is being closed with INSUFFICIENT_DATA as there has not been a response in over 4 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.