From: Stefan Hajnoczi <stefanha@gmail.com>
To: wireshark-dev@wireshark.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
ronnie sahlberg <ronniesahlberg@gmail.com>,
Cong Meng <mengcong@cn.ibm.com>
Subject: [Qemu-devel] Wireshark SCSI dissectors for new transports
Date: Tue, 28 Feb 2012 09:59:08 +0000 [thread overview]
Message-ID: <CAJSP0QXoBbFX6rOWVMA08DuS8WFrLTvNR+3Yyc-k8GLBdALgTQ@mail.gmail.com> (raw)
Wireshark today supports SCSI dissectors for iSCSI.
In the QEMU system emulator we have an emulated SCSI target which
handles devices for SCSI Parallel Interface (SPI), USB Mass Storage
Device, and now supports the new virtio-scsi transport (for efficient
virtual machine SCSI I/O).
Cong and I would like to add pcap support to the emulated SCSI target
in QEMU, making it easy to use Wireshark for SCSI debugging and
analysis. I'm looking for advice on getting started because we are
not familiar with Wireshark/dissector internals.
I believe the SCSI dissector does not support raw CDB dissection - it
requires a SCSI transport dissector (currently iSCSI). A few options
come to mind:
1. Change the SCSI dissector to support top-level dissecting of raw
SCSI CDBs without transport information (initiator, target, and other
metadata).
2. Add virtio-scsi and perhaps SPI SCSI transport dissectors.
3. A simpler approach I'm missing? :)
Suggestions appreciated.
Stefan
next reply other threads:[~2012-02-28 9:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-28 9:59 Stefan Hajnoczi [this message]
2012-02-28 10:19 ` [Qemu-devel] Wireshark SCSI dissectors for new transports ronnie sahlberg
2012-02-28 10:55 ` 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=CAJSP0QXoBbFX6rOWVMA08DuS8WFrLTvNR+3Yyc-k8GLBdALgTQ@mail.gmail.com \
--to=stefanha@gmail.com \
--cc=mengcong@cn.ibm.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=ronniesahlberg@gmail.com \
--cc=wireshark-dev@wireshark.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).