From: Paolo Bonzini <pbonzini@redhat.com>
To: ronnie sahlberg <ronniesahlberg@gmail.com>
Cc: Kevin Wolf <kwolf@redhat.com>, qemu-devel <qemu-devel@nongnu.org>,
Alexandre DERUMIER <aderumier@odiso.com>
Subject: Re: [Qemu-devel] qemu-img convert with block driver without .bdrv_create (like iscsi)
Date: Thu, 25 Oct 2012 15:58:48 +0200 [thread overview]
Message-ID: <50894598.8030401@redhat.com> (raw)
In-Reply-To: <CAN05THSfMxqB2dcCKmzLNmTqUQ=cMnmLfjv_=-+a2vbLQ464FQ@mail.gmail.com>
Il 25/10/2012 15:41, ronnie sahlberg ha scritto:
> On Thu, Oct 25, 2012 at 1:02 AM, Kevin Wolf <kwolf@redhat.com> wrote:
>> Am 25.10.2012 09:52, schrieb Paolo Bonzini:
>>> Il 25/10/2012 09:46, Kevin Wolf ha scritto:
>>>>>> 1)add a .bdrv_create in block/iscsi.c ?
>>>>>>
>>>>>> (like host_device block driver, only open/close the device and check if size if big enough)
>>>> Yes, this is the right way.
>>>
>>> Could it be a default implementation of .bdrv_create (i.e. something
>>> you'd do in bdrv_create if the protocol doesn't have it)?
>>
>> No, there are block drivers that really can't create images. They should
>> keep failing.
>
> Technically, you can not create new LUNs via the iscsi protocol
> itself, you can only access pre-existing luns
> that have been created by some out-of-band method.
>
> So basically, with iscsi you can only ever access already preexisting luns.
>
> In that case I think requiring a .bdrv_create feels wrong. We are not
> creating a new LUN here but just opening an already existing LUN.
The problem is that bdrv_create is overloaded to mean both "create the
backing storage" and "format the image". Only the latter applies to
iSCSI and, in general, as far as protocols are concerned bdrv_create is
usually a no-op.
However, Kevin said he prefers to have an explicit override of
bdrv_create for iSCSI. Can you implement that? (I'll then do the same
for NBD).
Paolo
>
> What about changing bdrv_create() so that IF there is no .bdrv_create
> method, then assume it might be a pre-existing file in which case we
> fallback to use .bdrv_open instead.
>
> regards
> ronnie sahlberg
>
next prev parent reply other threads:[~2012-10-25 13:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <37f26e36-0239-4598-bfc3-477e7dcf3787@mailpro>
2012-10-25 7:25 ` [Qemu-devel] qemu-img convert with block driver without .bdrv_create (like iscsi) Alexandre DERUMIER
2012-10-25 7:42 ` Paolo Bonzini
2012-10-25 7:46 ` Kevin Wolf
2012-10-25 7:52 ` Paolo Bonzini
2012-10-25 8:02 ` Kevin Wolf
2012-10-25 13:41 ` ronnie sahlberg
2012-10-25 13:54 ` Kevin Wolf
2012-10-25 13:58 ` Paolo Bonzini [this message]
2012-10-25 14:00 ` ronnie sahlberg
2012-10-26 5:37 ` Alexandre DERUMIER
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=50894598.8030401@redhat.com \
--to=pbonzini@redhat.com \
--cc=aderumier@odiso.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=ronniesahlberg@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.