public inbox for linux-kernel@vger.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: Mon, 06 Aug 2012 10:46:36 +0200	[thread overview]
Message-ID: <501F846C.50903@profihost.ag> (raw)
In-Reply-To: <501F8226.9090500@redhat.com>

 >Am 06.08.2012 10:36, schrieb Avi Kivity:
> On 08/05/2012 10:00 PM, Stefan Priebe wrote:
>>>>>>>>> So here are 3 backtraces from booting the rescue system:
>>>>>>>>> http://pastebin.com/raw.php?i=xCy2pEcP
>>>>>>>>>
>>>>>>>>> To me they all look the same.
>>>>>>>>
>>>>>>>> They are.  What version of qemu are you using?
>>>>>>>
>>>>>>> latest stable-1.1 branch (1.1.1) - which works fine with latest RHEL6
>>>>>>> kernel.
>>>>>>
>>>>>> This could be due to a kernel bug, or due to a different code path
>>>>>> taken
>>>>>> in qemu because of differing features exposed to kvm.
>>>>>>
>>>>>> Please try qemu-kvm.git master and report.
>>
>> OK got it running it's just awfully slow and i was too impatient. It
>> crashes at the part as 1.1.1 stable.
>>
>
> Slow?  what does 'info kvm' say?

Will recheck right now i'm running 1.1.1 again.

> I got master running and it wasn't particularly slow.  I'll try 1.1.1 too.

But still i got the segfault and core dump - this is my main problem? I 
mean qemu-kvm master isn't declared as stable. So i don't care about the 
slowness here.

What can we do about the core dump and crash?

Stefan

  reply	other threads:[~2012-08-06  8:46 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
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 [this message]
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=501F846C.50903@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