From: Peter Lieven <pl@dlh.net>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: ext Kevin Wolf <kwolf@redhat.com>,
Bernhard Kohl <bernhard.kohl@nsn.com>,
qemu-devel@nongnu.org,
"Nicholas A. Bellinger" <nab@linux-iscsi.org>,
Hannes Reinecke <hare@suse.de>
Subject: Re: [Qemu-devel] [PATCH] lsi53c895a: add support for ABORT messages
Date: Wed, 27 Apr 2011 15:06:50 +0200 [thread overview]
Message-ID: <4DB814EA.2070809@dlh.net> (raw)
In-Reply-To: <4DB6FB25.5080505@msgid.tls.msk.ru>
On 26.04.2011 19:04, Michael Tokarev wrote:
> 26.04.2011 18:46, Peter Lieven wrote:
> []
>> i recently saw some qemu-kvm 0.12.5 guests with scsi and this patch
>> applies crashing when
>> we updated our backend iscsi storages. (short interrupt in traffic flow,
>> iscsi disconnect + reconnect)
>>
>> i always see:
>> lsi_scsi: error: ORDERED queue not implemented
>>
>> and then either the maschine just hangs or it even aborts due to this
>> assertion:
>> qemu-kvm-0.12.5: /usr/src/qemu-kvm-0.12.5/hw/lsi53c895a.c:596:
>> lsi_reselect: Assertion `s->current == ((void *)0)' failed.
> http://bugs.debian.org/613413 talks about this very issue too ;)
>
>> any ideas?
> Unfortunately, no, except that it looks like scsi support is
> not of production quality still.
Do you know a reliable way to reproduce the ORDERED queue not
implemented error?
I tried with 0.14.0, but I were not able to. I will now try with 0.12.5.
However in 0.14.0 I manage to freeze a VM when copying data from an SCSI
device and
then temporarely interrupt the connection to my iSCSI storage which is
used as backend
on the host. Strangely, I cannot reprocude this when I run qemu-kvm in
gdb. There I just
see some SIGPIPE errors, but when I continue everything is fine.
From what I read from the SCSI2 specs a target should either implement
all tagged queue
commands or none. If tagged queing is not supported it should send a
reject message, but
continue with the following command.
http://ldkelley.com/SCSI2/SCSI2/SCSI2-06.html#6.6.17
Can somebody who is more familiar with SCSI look into this? SCSI drive
support
seems to be serverly broken.
Peter
> /mjt
next prev parent reply other threads:[~2011-04-27 13:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-06 14:42 [Qemu-devel] [PATCH] lsi53c895a: add support for ABORT messages Bernhard Kohl
2010-10-07 11:27 ` [Qemu-devel] " Kevin Wolf
2011-03-08 23:04 ` Peter Lieven
2011-03-09 5:33 ` Stefan Hajnoczi
2011-03-09 8:47 ` Kevin Wolf
2011-03-09 9:25 ` Bernhard Kohl
2011-03-09 9:38 ` Peter Lieven
2011-04-26 14:46 ` [Qemu-devel] " Peter Lieven
2011-04-26 17:04 ` Michael Tokarev
2011-04-27 13:06 ` Peter Lieven [this message]
2011-04-01 20:16 ` [Qemu-devel] " Aurelien Jarno
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=4DB814EA.2070809@dlh.net \
--to=pl@dlh.net \
--cc=bernhard.kohl@nsn.com \
--cc=hare@suse.de \
--cc=kwolf@redhat.com \
--cc=mjt@tls.msk.ru \
--cc=nab@linux-iscsi.org \
--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 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.