From: Stefan Priebe <s.priebe@profihost.ag>
To: Avi Kivity <avi@redhat.com>
Cc: mtosatti@redhat.com, kvm@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: KVM segfaults with 3.5 while installing ubuntu 12.04
Date: Tue, 31 Jul 2012 19:37:13 +0200 [thread overview]
Message-ID: <501817C9.6090405@profihost.ag> (raw)
In-Reply-To: <5017F19E.4070308@redhat.com>
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)
at /root/src/pve-qemu-kvm/qemu-kvm/hw/virtio-blk.c:62
#4 0x00007f6ca54d630b in virtio_blk_handle_scsi (req=0x7f6ca6fe4440) at
/root/src/pve-qemu-kvm/qemu-kvm/hw/virtio-blk.c:263
#5 0x00007f6ca54d6961 in virtio_blk_handle_request (req=0x7f6ca6fe4440,
mrb=0x7fffc18a5330)
at /root/src/pve-qemu-kvm/qemu-kvm/hw/virtio-blk.c:385
#6 0x00007f6ca54d6b0f in virtio_blk_handle_output (vdev=0x7f6ca6fb3a70,
vq=0x7f6ca6fb3b40)
at /root/src/pve-qemu-kvm/qemu-kvm/hw/virtio-blk.c:418
#7 0x00007f6ca54e096e in virtio_queue_notify_vq (vq=0x7f6ca6fb3b40) at
/root/src/pve-qemu-kvm/qemu-kvm/hw/virtio.c:648
#8 0x00007f6ca533aa5f in virtio_pci_host_notifier_read
(opaque=0x7f6ca6fb3b40)
at /root/src/pve-qemu-kvm/qemu-kvm/hw/virtio-pci.c:197
#9 0x00007f6ca528950e in qemu_iohandler_poll (readfds=0x7f6ca5ca7a20,
writefds=0x7f6ca5ca7aa0, xfds=0x7f6ca5ca7b20, ret=1)
at iohandler.c:121
#10 0x00007f6ca534d706 in main_loop_wait (nonblocking=0) at main-loop.c:497
#11 0x00007f6ca534022c in main_loop () at
/root/src/pve-qemu-kvm/qemu-kvm/vl.c:1569
#12 0x00007f6ca53471ae in main (argc=39, argv=0x7fffc18a5ee8,
envp=0x7fffc18a6028) at /root/src/pve-qemu-kvm/qemu-kvm/vl.c:3745
Stefan
next prev parent reply other threads:[~2012-07-31 17:37 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-31 11:59 KVM segfaults with 3.5 while installing ubuntu 12.04 Stefan Priebe - Profihost AG
2012-07-31 14:54 ` Avi Kivity
2012-07-31 17:30 ` Stefan Priebe
2012-07-31 17:37 ` Stefan Priebe [this message]
2012-08-01 8:44 ` Avi Kivity
2012-08-01 9:24 ` Stefan Priebe - Profihost AG
2012-08-01 9:33 ` Avi Kivity
2012-08-01 9:42 ` Stefan Priebe - Profihost AG
2012-08-01 9:53 ` Avi Kivity
2012-08-01 11:29 ` Stefan Priebe - Profihost AG
2012-08-01 15:15 ` Avi Kivity
2012-08-05 10:08 ` Stefan Priebe
2012-08-05 10:29 ` Avi Kivity
2012-08-05 15:52 ` Stefan Priebe
2012-08-05 19:00 ` Stefan Priebe
2012-08-06 8:36 ` Avi Kivity
2012-08-06 8:46 ` Stefan Priebe - Profihost AG
2012-08-06 12:12 ` Avi Kivity
2012-08-06 12:37 ` Avi Kivity
2012-08-06 12:48 ` Avi Kivity
2012-08-06 13:11 ` Stefan Priebe - Profihost AG
2012-08-08 5:51 ` Stefan Priebe
2012-08-08 8:06 ` Stefan Hajnoczi
2012-08-08 8:29 ` Stefan Priebe
2012-08-10 15:14 ` Stefan Hajnoczi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=501817C9.6090405@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox