qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Asias He <asias@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
	Gleb Natapov <gleb@redhat.com>,
	Badari Pulavarty <pbadari@us.ibm.com>,
	qemu-devel <qemu-devel@nongnu.org>,
	"Nicholas A. Bellinger" <nab@linux-iscsi.org>
Subject: Re: [Qemu-devel] qemu seabios issue with vhost-scsi
Date: Fri, 24 May 2013 08:02:07 +0800	[thread overview]
Message-ID: <20130524000207.GA22269@hj.localdomain> (raw)
In-Reply-To: <691725107.6754511.1369330272368.JavaMail.root@redhat.com>

On Thu, May 23, 2013 at 01:31:12PM -0400, Paolo Bonzini wrote:
> 
> 
> ----- Messaggio originale -----
> > Da: "Stefan Hajnoczi" <stefanha@gmail.com>
> > A: "Paolo Bonzini" <pbonzini@redhat.com>
> > Cc: "Badari Pulavarty" <pbadari@us.ibm.com>, "Asias He" <asias@redhat.com>, "Nicholas A. Bellinger"
> > <nab@linux-iscsi.org>, "qemu-devel" <qemu-devel@nongnu.org>, "Gleb Natapov" <gleb@redhat.com>
> > Inviato: Giovedì, 23 maggio 2013 19:18:26
> > Oggetto: Re: qemu seabios issue with vhost-scsi
> > 
> > On Thu, May 23, 2013 at 6:47 PM, Paolo Bonzini <pbonzini@redhat.com> wrote:
> > > Il 23/05/2013 18:38, Badari Pulavarty ha scritto:
> > >>> If that is with the old SeaBIOS, then SIGABRT is intended. :)  The guest
> > >>> is buggy, the problem in QEMU only lies in _how_ it fails.
> > >>>
> > >>> Paolo
> > >>>
> > >>>
> > >>
> > >> I am confused now. Without above changes, seabios fix makes the
> > >> guest boot. But with the above changes, I run into this (even with
> > >> seabios fix)
> > >
> > > Ah, okay.  I understood it crashed only with the SeaBIOS fix.
> > >
> > > I'll work on a more proper fix then.
> > 
> > Maybe use the same approach as data plane - activate vhost when
> > userspace sees the first virtqueue kick.  That way it works with weird
> > guests and never aborts.
> 
> Good idea.

I remember you mentioned that you wanted to start vhost earlier when you
were debugging vhost-scsi a few days ago.

> Paolo

-- 
Asias

  reply	other threads:[~2013-05-24  0:02 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-23  0:36 [Qemu-devel] qemu seabios issue with vhost-scsi Badari
2013-05-23  0:53 ` Asias He
2013-05-23  9:48   ` Gleb Natapov
2013-05-23 13:32     ` Stefan Hajnoczi
2013-05-23 14:48       ` Badari Pulavarty
2013-05-23 14:58         ` Paolo Bonzini
2013-05-23 15:27           ` Asias He
2013-05-23 15:30             ` Paolo Bonzini
2013-05-23 16:11               ` Badari Pulavarty
2013-05-23 16:19                 ` Paolo Bonzini
2013-05-23 16:38                   ` Badari Pulavarty
2013-05-23 16:47                     ` Paolo Bonzini
2013-05-23 17:18                       ` Stefan Hajnoczi
2013-05-23 17:31                         ` Paolo Bonzini
2013-05-24  0:02                           ` Asias He [this message]
2013-05-23 16:08           ` Badari Pulavarty
2013-05-23 12:45 ` 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=20130524000207.GA22269@hj.localdomain \
    --to=asias@redhat.com \
    --cc=gleb@redhat.com \
    --cc=nab@linux-iscsi.org \
    --cc=pbadari@us.ibm.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.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;
as well as URLs for NNTP newsgroup(s).