From: Kevin Wolf <kwolf@redhat.com>
To: MORITA Kazutaka <morita.kazutaka@lab.ntt.co.jp>
Cc: aliguori@us.ibm.com, sheepdog@lists.wpkg.org,
kvm@vger.kernel.org, qemu-devel@nongnu.org, avi@redhat.com,
Christoph Hellwig <hch@lst.de>
Subject: Re: [Qemu-devel] [RFC PATCH 0/2] Sheepdog: distributed storage system for QEMU
Date: Fri, 14 May 2010 12:05:51 +0200 [thread overview]
Message-ID: <4BED207F.1000201@redhat.com> (raw)
In-Reply-To: <87mxw2olkc.wl%morita.kazutaka@lab.ntt.co.jp>
Am 14.05.2010 11:54, schrieb MORITA Kazutaka:
>>> There is another problem to make the sheepdog driver be a protocol;
>>> how to deal with protocol specific create_options?
>>>
>>> For example, sheepdog supports cloning images as a format driver:
>>>
>>> $ qemu-img create -f sheepdog dst -b sheepdog:src
>>>
>>> But if the sheepdog driver is a protocol, error will occur.
>>>
>>> $ qemu-img create sheepdog:dst -b sheepdog:src
>>> Unknown option 'backing_file'
>>> qemu-img: Backing file not supported for file format 'raw'
>>>
>>> It is because the raw format doesn't support a backing_file option.
>>> To support the protocol specific create_options, if the format driver
>>> cannot parse some of the arguments, the protocol driver need to parse
>>> them.
>>
>> That's actually a good point. Yes, I think it makes a lot of sense to
>> allow parameters to be passed to the protocol driver.
>>
>
> Okay. But it seemed to require many changes to the qemu-img parser, so I didn't
> do it in the patchset I sent just now.
Yes, it probably requires a bit more than just five lines. We should
have it in the final version of the patch series, but we seem to agree
there and image creation is separate enough, so we can ignore it for the
discussion of the other parts.
Kevin
next prev parent reply other threads:[~2010-05-14 10:06 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-12 10:46 [Qemu-devel] [RFC PATCH 0/2] Sheepdog: distributed storage system for QEMU MORITA Kazutaka
2010-05-12 10:46 ` [Qemu-devel] [RFC PATCH 1/2] close all the block drivers before the qemu process exits MORITA Kazutaka
2010-05-12 14:01 ` Christoph Hellwig
2010-05-12 19:50 ` MORITA Kazutaka
2010-05-12 14:28 ` [Qemu-devel] " Avi Kivity
2010-05-12 20:16 ` MORITA Kazutaka
2010-05-13 2:34 ` MORITA Kazutaka
2010-05-12 10:46 ` [Qemu-devel] [RFC PATCH 2/2] block: add sheepdog driver for distributed storage support MORITA Kazutaka
2010-05-12 11:38 ` [Qemu-devel] [RFC PATCH 0/2] Sheepdog: distributed storage system for QEMU Kevin Wolf
2010-05-12 19:46 ` MORITA Kazutaka
2010-05-13 14:03 ` MORITA Kazutaka
2010-05-14 8:32 ` Kevin Wolf
2010-05-14 9:54 ` MORITA Kazutaka
2010-05-14 10:05 ` Kevin Wolf [this message]
2010-05-14 9:51 ` [Qemu-devel] [RFC PATCH v2 0/3] " MORITA Kazutaka
2010-05-17 10:19 ` [Qemu-devel] [RFC PATCH v3 " MORITA Kazutaka
2010-05-17 10:19 ` [Qemu-devel] [RFC PATCH v3 1/3] close all the block drivers before the qemu process exits MORITA Kazutaka
2010-05-17 10:19 ` [Qemu-devel] [RFC PATCH v3 2/3] block: call the snapshot handlers of the protocol drivers MORITA Kazutaka
2010-05-17 11:08 ` Kevin Wolf
2010-05-17 12:19 ` [Qemu-devel] " MORITA Kazutaka
2010-05-17 12:20 ` Kevin Wolf
2010-05-17 13:03 ` MORITA Kazutaka
2010-05-17 10:19 ` [Qemu-devel] [RFC PATCH v3 3/3] block: add sheepdog driver for distributed storage support MORITA Kazutaka
2010-05-14 9:51 ` [Qemu-devel] [RFC PATCH v2 1/3] close all the block drivers before the qemu process exits MORITA Kazutaka
2010-05-14 9:51 ` [Qemu-devel] [RFC PATCH v2 2/3] block: call the snapshot handlers of the protocol drivers MORITA Kazutaka
2010-05-14 12:55 ` [Qemu-devel] " Kevin Wolf
2010-05-14 9:51 ` [Qemu-devel] [RFC PATCH v2 3/3] block: add sheepdog driver for distributed storage support MORITA Kazutaka
2010-05-14 11:08 ` [Qemu-devel] " Kevin Wolf
2010-05-17 10:34 ` MORITA Kazutaka
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=4BED207F.1000201@redhat.com \
--to=kwolf@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=avi@redhat.com \
--cc=hch@lst.de \
--cc=kvm@vger.kernel.org \
--cc=morita.kazutaka@lab.ntt.co.jp \
--cc=qemu-devel@nongnu.org \
--cc=sheepdog@lists.wpkg.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).