From: "Ján Tomko" <jtomko@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-devel@nongnu.org, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH] qcow2: Change default for new images to compat=1.1
Date: Fri, 23 Aug 2013 13:05:48 +0200 [thread overview]
Message-ID: <5217420C.7060906@redhat.com> (raw)
In-Reply-To: <1376904333-30336-1-git-send-email-kwolf@redhat.com>
On 08/19/2013 11:25 AM, Kevin Wolf wrote:
> By the time that qemu 1.7 will be released, enough time will has passed
> since qemu 1.1, which is the first version to understand version 3
> images, that changing the default shouldn't hurt many people any more
> and the benefits of using the new format outweigh the pain.
>
> qemu-iotests already runs with compat=1.1 by default.
>
> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
> ---
> block/qcow2.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/block/qcow2.c b/block/qcow2.c
> index 3376901..42ea7ec 100644
> --- a/block/qcow2.c
> +++ b/block/qcow2.c
> @@ -1402,7 +1402,7 @@ static int qcow2_create(const char *filename, QEMUOptionParameter *options)
> int flags = 0;
> size_t cluster_size = DEFAULT_CLUSTER_SIZE;
> int prealloc = 0;
> - int version = 2;
> + int version = 3;
>
> /* Read out options */
> while (options && options->name) {
>
This does not affect qemu-img (or bdrv_img_create), as it gets overwritten
with 2 when BLOCK_OPT_COMPAT_LEVEL is present in options, but the value is NULL.
Should this go into qcow2_create_options[] as well?
Jan
next prev parent reply other threads:[~2013-08-23 11:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-19 9:25 [Qemu-devel] [PATCH] qcow2: Change default for new images to compat=1.1 Kevin Wolf
2013-08-19 13:08 ` Stefan Hajnoczi
2013-08-19 16:06 ` Eric Blake
2013-08-23 11:05 ` Ján Tomko [this message]
2013-08-27 8:00 ` Kevin Wolf
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=5217420C.7060906@redhat.com \
--to=jtomko@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.