|Summary:||[abrt] crash in qemu-system-x86-2:0.12.3-8.fc13: raise: Process /usr/bin/qemu was killed by signal 6 (SIGABRT)|
|Product:||[Fedora] Fedora||Reporter:||Tobias Mueller <fedora-bugs>|
|Component:||qemu||Assignee:||Justin M. Forbes <jforbes>|
|Status:||CLOSED WONTFIX||QA Contact:||Fedora Extras Quality Assurance <extras-qa>|
|Version:||13||CC:||amit.shah, berrange, dwmw2, ehabkost, gcosta, itamar, jaswinder, jforbes, knoel, markmc, ondrejj, scottt.tw, virt-maint|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2011-06-27 19:22:16 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
Description Tobias Mueller 2010-07-03 10:11:10 UTC
abrt 1.1.1 detected a crash. architecture: x86_64 Attached file: backtrace cmdline: qemu -monitor stdio -m 1G -kernel /opt/ubuntu/boot/vmlinuz-2.6.32-21-generic -initrd /opt/ubuntu/boot/initrd.img-2.6.32-21-generic -hda fat:ro:/opt/ubuntu/ -runas muelli comment: the vvfat code is apparently very bad in this qemu version. component: qemu crash_function: raise executable: /usr/bin/qemu global_uuid: 23bf651733da5a57409e074d58435b692939bec8 kernel: 188.8.131.52-124.fc13.x86_64 package: qemu-system-x86-2:0.12.3-8.fc13 rating: 4 reason: Process /usr/bin/qemu was killed by signal 6 (SIGABRT) release: Fedora release 13 (Goddard) How to reproduce ----- 1. qemu -monitor stdio -m 1G -kernel /opt/ubuntu/boot/vmlinuz-2.6.32-21-generic -initrd /opt/ubuntu/boot/initrd.img-2.6.32-21-generic -hda fat:ro:/opt/ubuntu/ -runas muelli 2. it seems to be fixed in git though 3.
Comment 1 Tobias Mueller 2010-07-03 10:11:14 UTC
Created attachment 429239 [details] File: backtrace
Comment 2 Avi Kivity 2010-07-03 17:17:25 UTC
Your best bet is to stay away from fat: drives. They're buggy and likely to stay this way.
Comment 3 Karel Klíč 2010-11-09 14:10:45 UTC
*** Bug 623160 has been marked as a duplicate of this bug. ***
Comment 4 Bug Zapper 2011-06-01 14:52:08 UTC
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '13'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Comment 5 Bug Zapper 2011-06-27 19:22:16 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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. Thank you for reporting this bug and we are sorry it could not be fixed.