Hi, ok i found a faster way to trigger this. Just boot the ubuntu rescue system. So here are 3 backtraces from booting the rescue system: http://pastebin.com/raw.php?i=xCy2pEcP To me they all look the same. Thanks! Stefan Am 01.08.2012 10:44, schrieb Avi Kivity:
On 07/31/2012 08:37 PM, Stefan Priebe wrote:Now i got it working - sorry used old gdb. This is the backtrace: Core was generated by `/usr/bin/qemu-system-x86_64 -id 103 -chardev socket,id=qmp,path=/var/run/qemu-s'. Program terminated with signal 11, Segmentation fault. #0 0x00007f6ca10faed8 in ?? () from /lib/libc.so.6 (gdb) where #0 0x00007f6ca10faed8 in ?? () from /lib/libc.so.6 #1 0x00007f6ca54e0098 in virtio_notify_vector (vdev=0x7f6ca10fae98, vector=32620) at /root/src/pve-qemu-kvm/qemu-kvm/hw/virtio.c:493 #2 0x00007f6ca54e0e25 in virtio_notify (vdev=0x7f6ca10fae98, vq=0x7f6ca10faf18) at /root/src/pve-qemu-kvm/qemu-kvm/hw/virtio.c:739 #3 0x00007f6ca54d5bb0 in virtio_blk_req_complete (req=0x7f6ca6fe4440, status=0)I notice the ip is different from the first trace. Please run this a few more times and see if it always fails in the same place, or in random places (and post the traces please).
-- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
