All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Priebe - Profihost AG <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: Wed, 01 Aug 2012 11:24:11 +0200	[thread overview]
Message-ID: <5018F5BB.9070500@profihost.ag> (raw)
In-Reply-To: <5018EC7D.9090702@redhat.com>

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).
>
>

  reply	other threads:[~2012-08-01  9:24 UTC|newest]

Thread overview: 35+ 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
2012-08-01  8:44     ` Avi Kivity
2012-08-01  9:24       ` Stefan Priebe - Profihost AG [this message]
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:12                             ` [Qemu-devel] " Avi Kivity
2012-08-06 12:37                             ` Avi Kivity
2012-08-06 12:37                               ` [Qemu-devel] " Avi Kivity
2012-08-06 12:37                               ` Avi Kivity
2012-08-06 12:48                               ` Avi Kivity
2012-08-06 12:48                                 ` [Qemu-devel] " Avi Kivity
2012-08-06 12:48                                 ` Avi Kivity
2012-08-06 13:11                               ` Stefan Priebe - Profihost AG
2012-08-06 13:11                                 ` [Qemu-devel] " Stefan Priebe - Profihost AG
2012-08-08  5:51                               ` Stefan Priebe
2012-08-08  5:51                                 ` [Qemu-devel] " Stefan Priebe
2012-08-08  8:06                                 ` Stefan Hajnoczi
2012-08-08  8:06                                   ` [Qemu-devel] " Stefan Hajnoczi
2012-08-08  8:29                                   ` Stefan Priebe
2012-08-08  8:29                                     ` [Qemu-devel] " Stefan Priebe
2012-08-10 15:14                                     ` Stefan Hajnoczi
2012-08-10 15:14                                       ` [Qemu-devel] " 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=5018F5BB.9070500@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.