qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Dong Xu Wang <wdongxu@linux.vnet.ibm.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH V14 1/6] docs: document for add-cow file format
Date: Fri, 26 Oct 2012 10:34:27 +0200	[thread overview]
Message-ID: <508A4B13.2040103@redhat.com> (raw)
In-Reply-To: <CAGrFBsgMk5wh_VM87C9PN0j6Z5hfZvgqBWDHgGeWkXw_Kzh87g@mail.gmail.com>

Am 26.10.2012 04:54, schrieb Dong Xu Wang:
> On Thu, Oct 25, 2012 at 10:56 PM, Eric Blake <eblake@redhat.com> wrote:
>> On 10/25/2012 07:36 AM, Dong Xu Wang wrote:
>>> +
>>> +            64 - 79:    image file format
>>> +                        Format of image file. It must be non-empty. It is coded
>>> +                        in free-form ASCII, and is not NUL-terminated. Zero
>>> +                        padded on the right.
>>
>> [1]...here you claim that backing and image file format are mandatory
>> (must not be empty).  Shouldn't you allow the file format to be empty,
>> in which case qemu will probe?  And why do you even need image file
>> format - isn't the whole point of add-cow to wrap a raw image file, or
>> are you planning on also being able to wrap non-raw files?  Are there
>> other non-raw file formats that lack backing file support, where add-cow
>> can be used to give it a backing file?
>>
> 
> Kevin or Stefan, can you give me some opinion? Thanks.

Yes, there are plenty of other block drivers that don't support backing
files, either because their image format/protocol can't provide such
information or just because it's not implemented in qemu today.

Kevin

  reply	other threads:[~2012-10-26  8:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-25 13:36 [Qemu-devel] [PATCH V14 0/6] add-cow file format Dong Xu Wang
2012-10-25 13:36 ` [Qemu-devel] [PATCH V14 1/6] docs: document for " Dong Xu Wang
2012-10-25 14:56   ` Eric Blake
2012-10-26  2:54     ` Dong Xu Wang
2012-10-26  8:34       ` Kevin Wolf [this message]
2012-10-25 13:36 ` [Qemu-devel] [PATCH V14 2/6] make path_has_protocol non static Dong Xu Wang
2012-10-25 13:36 ` [Qemu-devel] [PATCH V14 3/6] qed_read_string to bdrv_read_string Dong Xu Wang
2012-10-25 13:36 ` [Qemu-devel] [PATCH V14 4/6] rename qcow2-cache.c to block-cache.c Dong Xu Wang
2012-10-25 13:36 ` [Qemu-devel] [PATCH V14 5/6] add-cow file format core code Dong Xu Wang
2012-10-25 13:36 ` [Qemu-devel] [PATCH V14 6/6] qemu-iotests: add add-cow iotests support Dong Xu Wang

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=508A4B13.2040103@redhat.com \
    --to=kwolf@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=wdongxu@linux.vnet.ibm.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 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).