qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Jorge Lucángeli Obes" <t4m5yn@gmail.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: kvm-devel@lists.sourceforge.net, qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [kvm-devel] Storing command line options in qcow2 images
Date: Mon, 6 Aug 2007 20:31:30 -0300	[thread overview]
Message-ID: <59abf66e0708061631v43a277d6g49e0c629b475c2d6@mail.gmail.com> (raw)
In-Reply-To: <46B780E6.8050305@codemonkey.ws>

On 8/6/07, Anthony Liguori <anthony@codemonkey.ws> wrote:
> I don't think adding annotations as snapshots is the right approach.  I
> think proper support should be added in the header.  I wouldn't be too
> concerned with breaking compatibility in qcow2.  That's why it's qcow2
> and not just an updated version of qcow, qcow2 is still, AFAIK, open for
> breakage.

I think I'm fine either way. Avi suggested the snapshot-based
implementation so Laurent and I started working in that direction. We
are now close to finishing the basic functionality. That's not to say
that our solution should be accepted because it's almost ready. I
would like to reach consensus for the way in which all this should be
implemented.

The advantage of the snapshot-based approach is, as it has already
been discussed, its backwards-compatibility. I also think that it
requires less changes to the source code. I am not very familiar with
QEMU development so I'm not able to tell whether or not qcow2 is open
for breakage. I guess we decided to play it safe.

The header-based implementation would be conceptually easier of
course. It would have the added benefit of not having to deal with the
possible use of an empty snapshot (i.e., one with command line
options) in loadvm. That's the only thing left to fix in our current
implementation.

As I said, I'm fine either way. I have a final tomorrow, but after
that I will post our patches for review.

Cheers,
Jorge

      parent reply	other threads:[~2007-08-06 23:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <59abf66e0707292040j11c8b981mf7f793258e874400@mail.gmail.com>
2007-07-30  8:36 ` [Qemu-devel] Re: [kvm-devel] Storing command line options in qcow2 images Avi Kivity
2007-07-31  2:35   ` Jorge Lucángeli Obes
2007-07-31  7:00     ` Laurent Vivier
     [not found] ` <46B780E6.8050305@codemonkey.ws>
2007-08-06 23:31   ` Jorge Lucángeli Obes [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=59abf66e0708061631v43a277d6g49e0c629b475c2d6@mail.gmail.com \
    --to=t4m5yn@gmail.com \
    --cc=anthony@codemonkey.ws \
    --cc=kvm-devel@lists.sourceforge.net \
    --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).