From: Stefan Hajnoczi <stefanha@gmail.com>
To: अनुज <anuj01@gmail.com>
Cc: rusty@rustcorp.com.au, qemu-devel@nongnu.org,
kvm@vger.kernel.org, virtualization@lists.linux-foundation.org
Subject: Re: [Qemu-devel] SCSI Command support over VirtIO Block device
Date: Mon, 13 Dec 2010 07:42:15 +0000 [thread overview]
Message-ID: <AANLkTi=MVouwpAu5Zfxexx-yOZa3p0SpQ4OrO+_ax-Ew@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1691 bytes --]
On Dec 13, 2010 5:14 AM, "अनुज" <anuj01@gmail.com> wrote:
>
> Hi
>
> I am trying to implement VirtIO support for a proprietary OS. And It
> would be great if I am able to process SCSI commands over VirtIO Block
> device.
>
> I tried to execute INQUIRY command but the status returned is UNSUPPORTED.
> If anyone provide example VirtIO SCSI Command request structure for
> INQUIRY command as per VirtIO spec Appendix D would be a great help.
>
> And also, the paragraph from VirtIO spec - 0.8.9 is confusing for me :
>
> "Historically, devices assumed that the fields type, ioprio and
> sector reside in
> a single, separate read-only buffer; the fields errors, data_len,
sense_len and
> residual reside in a single, separate write-only buffer; the sense
> eld in a separate
> write-only buffer of size 96 bytes, by itself; the fields errors,
> data_len, sense_len
> and residual in a single write-only buffer; and the status field is a
> separate readonly
> buffer of size 1 byte, by itself."
>
> Here 'status field of buffer size 1 byte' is whether readonly or
writeonly?
Writeonly
>
> I want to know from which version of Qemu-kvm supports processing of
> scsi commands over VirtIO block device as a backend.
> Although I checked the Host Feature fields in which VIRTIO_BLK_F_SCSI
> bit is set. I am using qemu-kvm version 0.12.3.
Make sure you have a scsi-generic block device in qemu-kvm, not just a
regular file or physical block device. Open /dev/sg.
Look at hw/virtio-blk.c in qemu-kvm for host implementation details.
>
> --
> Anuj Aggarwal
>
> .''`.
> : :Ⓐ : # apt-get install hakuna-matata
> `. `'`
> `-
>
[-- Attachment #2: Type: text/html, Size: 2089 bytes --]
next reply other threads:[~2010-12-13 7:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-13 7:42 Stefan Hajnoczi [this message]
2010-12-13 10:47 ` [Qemu-devel] SCSI Command support over VirtIO Block device अनुज
-- strict thread matches above, loose matches on Subject: below --
2010-12-13 5:14 अनुज
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='AANLkTi=MVouwpAu5Zfxexx-yOZa3p0SpQ4OrO+_ax-Ew@mail.gmail.com' \
--to=stefanha@gmail.com \
--cc=anuj01@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=rusty@rustcorp.com.au \
--cc=virtualization@lists.linux-foundation.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).