From: Stefan Hajnoczi <stefanha@gmail.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: Asias He <asias@redhat.com>, Badari <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: Thu, 23 May 2013 15:32:19 +0200 [thread overview]
Message-ID: <CAJSP0QWM_pev+aX4GLupuV=r6fOf2eG1cEBrHAiLYZTqhi8xDQ@mail.gmail.com> (raw)
In-Reply-To: <20130523094809.GM4725@redhat.com>
On Thu, May 23, 2013 at 11:48 AM, Gleb Natapov <gleb@redhat.com> wrote:
> On Thu, May 23, 2013 at 08:53:55AM +0800, Asias He wrote:
>> On Wed, May 22, 2013 at 05:36:08PM -0700, Badari wrote:
>> > Hi,
>> >
>> > While testing vhost-scsi in the current qemu git, ran into an earlier issue
>> > with seabios. I had to disable scsi support in seabios to get it working.
>> >
>> > I was hoping this issue got resolved when vhost-scsi support got
>> > merged into qemu. Is this still being worked on ?
>>
>> Hmm, can you try seabios.git? Not sure if seabios shipped by qemu picked
>> up the fixes for vhost-scsi.
>>
> Nothing in seabios should crash qemu.
Agreed. I'm pretty sure it's the scenario that I posted in my other
reply to this thread.
The common virtio-scsi code in QEMU should guard against this. In
virtio-blk data plane I hit a similar case and ended up starting the
data plane thread (equivalent to vhost here) *before* the status
register is set to DRIVER_OK.
Stefan
next prev parent reply other threads:[~2013-05-23 13:32 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 [this message]
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
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='CAJSP0QWM_pev+aX4GLupuV=r6fOf2eG1cEBrHAiLYZTqhi8xDQ@mail.gmail.com' \
--to=stefanha@gmail.com \
--cc=asias@redhat.com \
--cc=gleb@redhat.com \
--cc=nab@linux-iscsi.org \
--cc=pbadari@us.ibm.com \
--cc=qemu-devel@nongnu.org \
/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).