Description of problem: Happens every second run Version-Release number of selected component: qemu-system-x86-1.6.1-3.fc20 Additional info: reporter: libreport-2.1.11 backtrace_rating: 4 cmdline: /usr/bin/qemu-system-x86_64 -machine accel=kvm -cpu host -smp 1,cores=2 -m 3000 -hda disk_images/win8.img -net nic,model=virtio -net user -rtc base=localtime -sdl crash_function: address_space_unmap executable: /usr/bin/qemu-system-x86_64 kernel: 3.12.8-300.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (8 frames) #5 address_space_unmap #6 dma_bdrv_unmap #7 dma_bdrv_cb #8 bdrv_co_em_bh #9 aio_bh_poll #10 aio_poll #11 aio_ctx_dispatch #14 main_loop_wait
Created attachment 853451 [details] File: backtrace
Created attachment 853452 [details] File: cgroup
Created attachment 853453 [details] File: core_backtrace
Created attachment 853454 [details] File: dso_list
Created attachment 853455 [details] File: environ
Created attachment 853456 [details] File: limits
Created attachment 853457 [details] File: maps
Created attachment 853458 [details] File: open_fds
Created attachment 853459 [details] File: proc_pid_status
Created attachment 853460 [details] File: var_log_messages
*** Bug 1056262 has been marked as a duplicate of this bug. ***
I can't upload the coredump (it's 3GB and probably contains confidential data), but I'll try to get the debuginfos updated next time I hit this.
(In reply to Dimitris from comment #12) > I can't upload the coredump (it's 3GB and probably contains confidential > data), but I'll try to get the debuginfos updated next time I hit this. No need to upload the core file. There is enough information in the report.
(In reply to Richard W.M. Jones from comment #13) > (In reply to Dimitris from comment #12) > > I can't upload the coredump (it's 3GB and probably contains confidential > > data), but I'll try to get the debuginfos updated next time I hit this. > > No need to upload the core file. There is enough information > in the report. Debuginfo *does* seem to be missing actually ...
Hmm, I can't find a way to make abrt add to this report, or even create a new one. I have some time to let it do the debuginfo install now. Any pointers?
If you can dig the original coredump out of /var/spool/abrt then you can run: gdb /usr/bin/qemu-system-x86_64 core gdb will print a suggested "debuginfo-install" command. Quit gdb and run then. After installing debuginfo, run the gdb command above again, and execute the following gdb command: t a a bt and paste the complete output into this bug report.
Created attachment 854112 [details] gdb output The original coredump isn't available (abrt quota) but I can reproduce this reliably. Attaching gdb output after debuginfos were installed.
Happened again but this time I had added -vga std to the command line. Apparently the code/backtrace was different enough that abrt didn't think it a dupe, so it created bug 1056911. Overall pattern is the same though, every second run fails.
I can get it to crash on every invocation if I add: -soundhw hda -snapshot to the command line: qemu-kvm -cpu host -smp 1,cores=2 -m 3000 -hda disk_images/win8.1.img -net nic -net user -rtc base=localtime -sdl -vga std -soundhw hda -snapshot Attaching the core_backtrace in a moment.
Created attachment 858763 [details] core_backtrace with "-soundhw hda -snapshot" added to command line
*** This bug has been marked as a duplicate of bug 1066084 ***