From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
qemu-devel <qemu-devel@nongnu.org>,
ronnie sahlberg <ronniesahlberg@gmail.com>
Subject: Re: [Qemu-devel] virtio-scsi vs. virtio-blk
Date: Fri, 10 Aug 2012 14:43:32 +0200 [thread overview]
Message-ID: <502501F4.1000803@profihost.ag> (raw)
In-Reply-To: <50250114.9010704@redhat.com>
Hi Paolo,
Am 10.08.2012 14:39, schrieb Paolo Bonzini:
> Il 10/08/2012 14:35, Stefan Priebe - Profihost AG ha scritto:
>>>
>>> One way to activate passthough is via scsi-generic:
>>> Example:
>>> -device lsi -device scsi-generic,drive=MyISCSI \
>>> -drive file=iscsi://10.1.1.125/iqn.ronnie.test/1,if=none,id=MyI
>>
>> When i do this the guest system always uses the sym53c8xx kernel module.
>> This results in 70 iops instead of 30000 iops. Is this really correct
>> that it uses the very old sym53c8xx kernel module for this device?
>>
>> used start command:
>> http://pastebin.com/raw.php?i=23fkaQgc
>
> Just replace lsi with virtio-scsi-pci again. Also, using scsi-block
> instead of scsi-generic should have better performance, but I'm not sure
> Ronnie tested it with libiscsi.
I tried this earlier but this results in:
kvm: -device scsi-block,drive=drive-scsi0: scsi-block: INQUIRY failed
kvm: -device scsi-block,drive=drive-scsi0: Device 'scsi-block' could not
be initialized
Greets,
Stefan
next prev parent reply other threads:[~2012-08-10 12:43 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-08 15:21 [Qemu-devel] virtio-scsi vs. virtio-blk Stefan Priebe
2012-08-08 16:17 ` Paolo Bonzini
2012-08-08 17:12 ` Stefan Priebe
2012-08-08 17:37 ` Paolo Bonzini
2012-08-09 6:13 ` Stefan Priebe
2012-08-09 7:01 ` Paolo Bonzini
2012-08-09 7:07 ` Stefan Priebe
2012-08-09 7:19 ` Paolo Bonzini
2012-08-09 7:41 ` Stefan Priebe
2012-08-09 7:53 ` Paolo Bonzini
2012-08-09 8:00 ` Stefan Priebe
2012-08-09 8:03 ` Paolo Bonzini
2012-08-09 9:18 ` Stefan Hajnoczi
2012-08-09 10:17 ` Stefan Priebe - Profihost AG
2012-08-09 11:04 ` Stefan Hajnoczi
2012-08-09 11:10 ` Paolo Bonzini
2012-08-09 11:24 ` Stefan Priebe - Profihost AG
2012-08-09 12:08 ` Stefan Priebe - Profihost AG
2012-08-09 12:19 ` Paolo Bonzini
2012-08-09 12:31 ` Stefan Priebe - Profihost AG
2012-08-09 12:44 ` Paolo Bonzini
2012-08-09 15:41 ` Stefan Priebe - Profihost AG
2012-08-09 12:52 ` ronnie sahlberg
2012-08-09 13:15 ` Paolo Bonzini
2012-08-09 13:39 ` Stefan Priebe - Profihost AG
2012-08-09 13:42 ` Paolo Bonzini
2012-08-09 13:52 ` Stefan Priebe - Profihost AG
2012-08-09 14:35 ` Paolo Bonzini
2012-08-09 14:25 ` Stefan Priebe - Profihost AG
2012-08-10 9:22 ` Stefan Priebe - Profihost AG
2012-08-10 10:20 ` Paolo Bonzini
2012-08-10 10:28 ` Stefan Priebe - Profihost AG
2012-08-10 10:30 ` Paolo Bonzini
2012-08-10 11:12 ` ronnie sahlberg
2012-08-10 11:57 ` Stefan Priebe - Profihost AG
2012-08-10 12:04 ` ronnie sahlberg
2012-08-10 12:14 ` Stefan Priebe - Profihost AG
2012-08-10 12:24 ` ronnie sahlberg
2012-08-10 12:35 ` Stefan Priebe - Profihost AG
2012-08-10 12:39 ` Paolo Bonzini
2012-08-10 12:43 ` Stefan Priebe - Profihost AG [this message]
2012-08-10 11:20 ` ronnie sahlberg
2012-08-10 11:54 ` Stefan Priebe - Profihost AG
2012-08-10 11:58 ` ronnie sahlberg
2012-08-10 12:38 ` Stefan Priebe - Profihost AG
2012-08-10 11:49 ` Stefan Priebe - Profihost AG
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=502501F4.1000803@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=ronniesahlberg@gmail.com \
--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 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.