From: "Richard W.M. Jones" <rjones@redhat.com>
To: qemu-devel@nongnu.org, qemu-block@nongnu.org, mreitz@redhat.com,
mlevitsk@redhat.com, sgarzare@redhat.com
Subject: Bug? qemu-img convert to preallocated image makes it sparse
Date: Thu, 16 Jan 2020 14:13:52 +0000 [thread overview]
Message-ID: <20200116141352.GA32053@redhat.com> (raw)
I'm not necessarily saying this is a bug, but a change in behaviour in
qemu has caused virt-v2v to fail. The reproducer is quite simple.
Create sparse and preallocated qcow2 files of the same size:
$ qemu-img create -f qcow2 sparse.qcow2 50M
Formatting 'sparse.qcow2', fmt=qcow2 size=52428800 cluster_size=65536 lazy_refcounts=off refcount_bits=16
$ qemu-img create -f qcow2 prealloc.qcow2 50M -o preallocation=falloc,compat=1.1
Formatting 'prealloc.qcow2', fmt=qcow2 size=52428800 compat=1.1 cluster_size=65536 preallocation=falloc lazy_refcounts=off refcount_bits=16
$ du -m sparse.qcow2 prealloc.qcow2
1 sparse.qcow2
51 prealloc.qcow2
Now copy the sparse file into the preallocated file using the -n
option so qemu-img doesn't create the target:
$ qemu-img convert -p -n -f qcow2 -O qcow2 sparse.qcow2 prealloc.qcow2
(100.00/100%)
In new qemu that makes the target file sparse:
$ du -m sparse.qcow2 prealloc.qcow2
1 sparse.qcow2
1 prealloc.qcow2 <-- should still be 51
In old qemu the target file remained preallocated, which is what
I and virt-v2v are expecting.
I bisected this to the following commit:
4d7c487eac1652dfe4498fe84f32900ad461d61b is the first bad commit
commit 4d7c487eac1652dfe4498fe84f32900ad461d61b
Author: Max Reitz <mreitz@redhat.com>
Date: Wed Jul 24 19:12:29 2019 +0200
qemu-img: Fix bdrv_has_zero_init() use in convert
bdrv_has_zero_init() only has meaning for newly created images or image
areas. If qemu-img convert did not create the image itself, it cannot
rely on bdrv_has_zero_init()'s result to carry any meaning.
Signed-off-by: Max Reitz <mreitz@redhat.com>
Message-id: 20190724171239.8764-2-mreitz@redhat.com
Reviewed-by: Maxim Levitsky <mlevitsk@redhat.com>
Reviewed-by: Stefano Garzarella <sgarzare@redhat.com>
Signed-off-by: Max Reitz <mreitz@redhat.com>
qemu-img.c | 11 ++++++++---
1 file changed, 8 insertions(+), 3 deletions(-)
Reverting this commit on the current master branch restores the
expected behaviour.
Thoughts?
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
libguestfs lets you edit virtual machines. Supports shell scripting,
bindings from many languages. http://libguestfs.org
next reply other threads:[~2020-01-16 14:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-16 14:13 Richard W.M. Jones [this message]
2020-01-16 14:37 ` Bug? qemu-img convert to preallocated image makes it sparse Max Reitz
2020-01-16 14:50 ` Kevin Wolf
2020-01-16 14:55 ` Max Reitz
2020-01-16 15:38 ` Maxim Levitsky
2020-01-16 15:56 ` Max Reitz
2020-01-16 16:00 ` Richard W.M. Jones
2020-01-16 16:02 ` Max Reitz
2020-01-17 10:28 ` David Edmondson
2020-01-16 14:47 ` Max Reitz
2020-01-16 14:53 ` Richard W.M. Jones
2020-01-16 14:57 ` Eric Blake
2020-01-16 15:03 ` Max Reitz
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=20200116141352.GA32053@redhat.com \
--to=rjones@redhat.com \
--cc=mlevitsk@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=sgarzare@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.