qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: ronnie sahlberg <ronniesahlberg@gmail.com>
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: kwolf@redhat.com, qemu-devel@nongnu.org, nab@linux-iscsi.org,
	hare@suse.de
Subject: Re: [Qemu-devel] [PATCH 1/1] iscsi: add iSCSI block device support
Date: Mon, 22 Nov 2010 10:39:06 +1100	[thread overview]
Message-ID: <AANLkTimYND1+w2YWOH7P5LM3pL6yFTo87ajhY2SnCfTG@mail.gmail.com> (raw)
In-Reply-To: <20101122080230F.fujita.tomonori@lab.ntt.co.jp>

On Mon, Nov 22, 2010 at 10:13 AM, FUJITA Tomonori
<fujita.tomonori@lab.ntt.co.jp> wrote:
> On Mon, 22 Nov 2010 09:17:50 +1100
> ronnie sahlberg <ronniesahlberg@gmail.com> wrote:
>
>> This patch adds support for attaching directorly to iSCSI resources,
>> both DISK/SBC and CDROM/MMC, without the need to make the devices
>> visible to the host.
>
> This adds the iscsi initiator feature to qemu (as you did to dbench),
> right?

Yes.

>
>
>> The syntax to specify a iscsi resource is
>>    iscsi://<host>[:port]/<target-iqn-name>/<lun>
>>
>> Example :
>>    -drive file=iscsi://127.0.0.1:3260/iqn.ronnie.test/1
>>
>>   -cdrom iscsi://127.0.0.1:3260/iqn.ronnie.test/2
>
> Specifying lun looks odd (from the perspective of SCSI initiator)?
>

Ok.
I can easily to change this.
How would you prefer the iscsi:// url look like ?


> btw, how do we specify initiator's configuration (iscsi params, chap,
> initiator iqn, etc)?
>

You cant yet. :-(

Right now they are hardcoded to reasonable defaults I think will work
for most targets.
I want to add more of these features and make them settable from the
command line,
but that will take a lot of time.

Hopefully having a basic/non-flexible implementation as a first step
may even encourage others to
contribute to improve it until it is full featured.


regards
ronnie sahlberg

  reply	other threads:[~2010-11-21 23:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-21 22:17 [Qemu-devel] [PATCH 1/1] iscsi: add iSCSI block device support ronnie sahlberg
2010-11-21 23:13 ` FUJITA Tomonori
2010-11-21 23:39   ` ronnie sahlberg [this message]
2010-11-22  9:27 ` [Qemu-devel] " Kevin Wolf
2010-11-24 17:04 ` [Qemu-devel] " Christoph Hellwig
2010-11-24 19:14   ` Stefan Hajnoczi
2010-11-25  4:32     ` Nicholas A. Bellinger
2010-11-25  5:22       ` ronnie sahlberg
2010-11-25  9:30         ` Kevin Wolf

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=AANLkTimYND1+w2YWOH7P5LM3pL6yFTo87ajhY2SnCfTG@mail.gmail.com \
    --to=ronniesahlberg@gmail.com \
    --cc=fujita.tomonori@lab.ntt.co.jp \
    --cc=hare@suse.de \
    --cc=kwolf@redhat.com \
    --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 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).