qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@suse.de>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel][PATCH] Qemu image over raw devices
Date: Wed, 17 Dec 2008 13:57:06 +0100	[thread overview]
Message-ID: <4948F722.9090303@suse.de> (raw)
In-Reply-To: <4947A52B.50301@redhat.com>

Shahar Frank schrieb:
> Kevin, Daniel,
> 
> What do you think is the right thing to do here?
> 
> Option one:
> 
> 1. I can suggest a new extension mechanism for QCOW2 (it can be even
> backwards compatible) and store the backing file format there
> 2. I can add a flag to qemu-img create to force backing file format
> (that is stored in the above extension).
> 
> Or:
> 
> Option two:
> 
> I can register qcow2 as a protocol and allow users to explicitly force
> qcow2 image logic.
> It is true that the ":" notation is still used, but as this notation is
> still required even for the drive option (vvfat, for example) it won't
> be the first to introduce it to the system.
> 
> I have a feeling you both prefer option one ;-)

I think I'm not really decided on that one. For me, the most important
thing is that you don't force users to rely on guessing. So while I
slightly tend towards the first option, I also wouldn't be opposed to
the second one.

Kevin

  reply	other threads:[~2008-12-17 12:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <571317069.373331229413498662.JavaMail.root@zmail02.collab.prod.int.phx2.redhat.com>
2008-12-16  7:50 ` [Qemu-devel][PATCH] Qemu image over raw devices Shahar Frank
2008-12-16  9:40   ` Kevin Wolf
2008-12-16 10:21     ` Shahar Frank
2008-12-16 12:10       ` Kevin Wolf
2008-12-16 12:55         ` Shahar Frank
2008-12-17 12:57           ` Kevin Wolf [this message]
2008-12-18 17:20             ` Shahar Frank
2008-12-16 10:53     ` Daniel P. Berrange
2008-12-15 14:04 Shahar Frank
2008-12-15 18:17 ` Kevin Wolf
2008-12-16 11:15 ` Daniel P. Berrange

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=4948F722.9090303@suse.de \
    --to=kwolf@suse.de \
    --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).