qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Cc: uri Lublin <ulublin@redhat.com>
Subject: Re: [Qemu-devel] [6907] Introducing qcow2 extensions (Uri Lublin)
Date: Sun, 29 Mar 2009 14:44:26 -0500	[thread overview]
Message-ID: <49CFCF9A.9020903@codemonkey.ws> (raw)
In-Reply-To: <49CF0AE7.4010500@redhat.com>

Avi Kivity wrote:
> Anthony Liguori wrote:
>>> We should introduce a notion of compatible vs. incompatible extensions.
>>>
>>> A compatible extension my be ignored by the qcow2 code if it does 
>>> not understand the magic number.  An incompatible extension causes 
>>> an abort.  This allows both more flexibility in how we can change 
>>> the file format.  I believe ext* does the same thing.
>>
>> I was assuming that all extensions would be compatible.  I don't like 
>> the idea of having qcow2 files floating around that require specific 
>> version of QEMU.
>>
>> For that, we should just bump to qcow3 (that's what versioning is 
>> for, right? :-).
>
> The problem is that you would need to bump the version each time you 
> made an incompatible change.  We'd end up with qcow4351 very quickly.
>
> One option is to declare qcow3 as qcow2 + all incompatible extensions 
> just before 0.11.  Another is to require explicit user action to 
> enable an incompatible option.  If you did that, you could expect only 
> to upgrade qemu, not degrade, but that's a reasonable assumption in 
> many scenarios.

Well what sort of incompatible extensions are we talking about?  Are 
there things being kicked around?

Regards,

Anthony Liguori

      reply	other threads:[~2009-03-29 19:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-28 17:55 [Qemu-devel] [6907] Introducing qcow2 extensions (Uri Lublin) Anthony Liguori
2009-03-28 18:58 ` Avi Kivity
2009-03-29  1:13   ` Anthony Liguori
2009-03-29  5:45     ` Avi Kivity
2009-03-29 19:44       ` Anthony Liguori [this message]

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=49CFCF9A.9020903@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=qemu-devel@nongnu.org \
    --cc=ulublin@redhat.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).