From: Michael Tokarev <mjt@tls.msk.ru>
To: Ray Kohler <ataraxia937@gmail.com>, 768517@bugs.debian.org
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Bug#768517: qemu-system-x86: virtio-scsi unreliable - crashes and write failures
Date: Sat, 08 Nov 2014 07:40:59 +0300 [thread overview]
Message-ID: <545D9EDB.5010901@msgid.tls.msk.ru> (raw)
In-Reply-To: <545D9CF2.7070207@msgid.tls.msk.ru>
[I forgot to add one comment]
08.11.2014 07:32, Michael Tokarev wrote:
> Control: tag -1 + moreinfo confirmed
>
> [Adding qemu-devel@]
>
> 08.11.2014 04:28, Ray Kohler wrote:
>>
>> virtio-scsi is quite unreliable compared to the version in wheezy. I see
>> many crashes, with this output:
>>
>> qemu-system-x86_64: wrong size for virtio-scsi headers
So you're saying this is a regression compared with version 1.1.2.
But the thing is -- did virtio-scsi _ever_ worked in 1.1? I don't
think it was. At least I can't perform the same OpenBSD install
in 1.1 verison at all -- the installer can't write anything to
virtio-scsi, it fails for me right when writing a partition table,
with "Invalid argument/Illegal Request" SCSI error code.
So it looks like this is not a regression, quite the opposite...
Unless, ofcourse, I'm doing something incorrectly.
qemu-system-x86_64 -enable-kvm -m 1G \
-device virtio-scsi-pci,id=scsi \
-drive file=foo.img,if=none,cache=unsafe,id=d \
-device scsi-hd,drive=d \
-vga std -cpu host -cdrom cd56.iso -monitor stdio
(for both 2.1 and 1.1.)
Thanks,
/mjt
prev parent reply other threads:[~2014-11-08 4:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000001498d03e356-ad9138e5-43c7-491b-aeb0-56e5b60c06de-000000@email.amazonses.com>
2014-11-08 4:32 ` [Qemu-devel] Bug#768517: qemu-system-x86: virtio-scsi unreliable - crashes and write failures Michael Tokarev
2014-11-08 4:40 ` Michael Tokarev [this message]
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=545D9EDB.5010901@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=768517@bugs.debian.org \
--cc=ataraxia937@gmail.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).