Hide Forgot
Description of problem: KVM generated another different coredump with user network Version-Release number of selected component (if applicable): kvm-64-3.fc9.x86_64 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: Core was generated by `qemu-kvm -s -m 320 -smp 2 -net nic,model=pcnet -net user -redir tcp:2222::22 -s'. Program terminated with signal 11, Segmentation fault. [New process 32224] [New process 32233] [New process 32219] #0 0x0000000000407a49 in qemu_mod_timer (ts=0x2e94080, expire_time=3155428127584) at /usr/src/debug/kvm-64/qemu/vl.c:1072 1072 if ((alarm_timer->flags & ALARM_FLAG_EXPIRED) == 0 && Missing separate debuginfos, use: debuginfo-install SDL.x86_64 alsa-lib.x86_64 gnutls.x86_64 libX11.x86_64 libXau.x86_64 libXcursor.x86_64 libXdmcp.x86_64 libXext.x86_64 libXfixes.x86_64 libXrandr.x86_64 libXrender.x86_64 libgcrypt.x86_64 libgpg-error.x86_64 libtasn1.x86_64 libxcb.x86_64 zlib.x86_64 (gdb) bt #0 0x0000000000407a49 in qemu_mod_timer (ts=0x2e94080, expire_time=3155428127584) at /usr/src/debug/kvm-64/qemu/vl.c:1072 #1 0x0000000000425c10 in pcnet_ioport_writew (opaque=0x0, addr=2922132320, val=8101256) at /usr/src/debug/kvm-64/qemu/hw/pcnet.c:1617 #2 0x0000000000503521 in kvm_outw (opaque=<value optimized out>, addr=13152, data=40328) at /usr/src/debug/kvm-64/qemu/qemu-kvm.c:466 #3 0x000000000051fb70 in kvm_run (kvm=0x2dbd030, vcpu=1) at libkvm.c:724 #4 0x0000000000502e56 in kvm_cpu_exec (env=<value optimized out>) at /usr/src/debug/kvm-64/qemu/qemu-kvm.c:134 #5 0x00000000005039f5 in kvm_main_loop_cpu (env=0x2e85010) at /usr/src/debug/kvm-64/qemu/qemu-kvm.c:314 #6 0x0000000000503b70 in ap_main_loop (_env=<value optimized out>) at /usr/src/debug/kvm-64/qemu/qemu-kvm.c:346 #7 0x000000303c60740a in start_thread (arg=<value optimized out>) at pthread_create.c:297 #8 0x000000303bae678d in clone () from /lib64/libc.so.6
Can you see if kvm-65 helps? (http://koji.fedoraproject.org/koji/buildinfo?buildID=45620)
I will see, but I do not have a testcase, to easily check that bug will not happen again. BTW - I've already tested kvm-65 build by myself from git - and there was still present my other reported coredump with user network.
Happened to me again with kvm-65 (using very latest Linus git kernel tree) Using bridged networking warning: Can't read pathname for load map: Input/output error. Core was generated by `qemu-kvm -boot n -s -M pc -monitor stdio -m 260 -smp 2 -net nic,model=pcnet,mac'. Program terminated with signal 11, Segmentation fault. [New process 14733] [New process 14759] [New process 14734] [New process 14709] #0 0x00000000004079f9 in qemu_mod_timer (ts=0x2e5ea30, expire_time=228088830895) at /usr/src/debug/kvm-65/qemu/vl.c:1072 1072 if ((alarm_timer->flags & ALARM_FLAG_EXPIRED) == 0 && (gdb) bt #0 0x00000000004079f9 in qemu_mod_timer (ts=0x2e5ea30, expire_time=228088830895) at /usr/src/debug/kvm-65/qemu/vl.c:1072 #1 0x0000000000425c6d in pcnet_ioport_readw (opaque=0x0, addr=455564207) at /usr/src/debug/kvm-65/qemu/hw/pcnet.c:1641 #2 0x000000000050356e in kvm_inw (opaque=<value optimized out>, addr=23471, data=0x7b9d88) at /usr/src/debug/kvm-65/qemu/qemu-kvm.c:466 #3 0x000000000051fb68 in kvm_run (kvm=0x2dbb040, vcpu=0) at libkvm.c:704 #4 0x0000000000502f16 in kvm_cpu_exec (env=<value optimized out>) at /usr/src/debug/kvm-65/qemu/qemu-kvm.c:146 #5 0x0000000000503ba0 in ap_main_loop (_env=<value optimized out>) at /usr/src/debug/kvm-65/qemu/qemu-kvm.c:330 #6 0x0000003a6d80729a in ?? () #7 0x0000000040ccc950 in ?? () #8 0x0000000000000000 in ?? ()
I should add that this crash dump might not be related to the previous - as it happened during qemu exit. (gdb) print alarm_timer $1 = (struct qemu_alarm_timer *) 0x0 Thus it looks like access to most probably already destroyed structure. Assuming some wrong close order.
Changing version to '9' as part of upcoming Fedora 9 GA. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This message is a reminder that Fedora 9 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 9. 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 '9'. 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 9'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 9 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
This bugzilla is fixed in the F11 - and could be probably closed
Thanks Zdenek, sorry we let this one drop