From: Eric Blake <eblake@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>,
QEMU Developers <qemu-devel@nongnu.org>
Cc: Kevin Wolf <kwolf@redhat.com>, Qemu-block <qemu-block@nongnu.org>,
Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] using "qemu-img convert -O qcow2" to convert qcow v1 to v2 creates a qcow v3 file?
Date: Mon, 13 Nov 2017 11:55:13 -0600 [thread overview]
Message-ID: <a0d53b78-d9aa-7aa9-9fa5-8b29d53c1a9b@redhat.com> (raw)
In-Reply-To: <CAFEAcA_bXripv8_O8aRuDbdYQ3oWeVzdb8GO=o9j2oddYrg-0A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1247 bytes --]
On 11/13/2017 11:14 AM, Peter Maydell wrote:> I have a qcow v1 file
which I created by mistake (forgetting that
> you need to tell qemu-img create 'qcow2' and not just 'qcow'),
> which I want to convert to a v2 file so I can put snapshots into
> it. But when I try to do this with qemu-img convert it creates a
> v3 file instead:
>
> $ file hda-old.qcow
> hda-old.qcow: QEMU QCOW Image (v1), 5368709120 bytes
> $ build/x86/qemu-img convert -O qcow2 hda-old.qcow hda.qcow2
> $ file hda.qcow2
> hda.qcow2: QEMU QCOW Image (v3), 5368709120 bytes
>
> and if you then try to use that in QEMU it complains:
>
> qemu-system-aarch64: -drive if=none,file=hda.qcow2,format=qcow,id=hd:
> Unsupported qcow version 3
>
> What am I missing here?
qcow2 has two versions; v2 (aka compat=0.10), and v3 (aka compat=1.1).
We changed qemu-img to create v3 by default several years ago, but there
are older qemu binaries (hello, CentOS 6) that still don't understand
v3. Your qemu-system-aarch64 appears to be one of these older binaries.
Try:
qemu-img convert -O qcow2 -o compat=0.10 hda-old.qcow hda.qcow2
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 619 bytes --]
prev parent reply other threads:[~2017-11-13 17:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-13 17:14 [Qemu-devel] using "qemu-img convert -O qcow2" to convert qcow v1 to v2 creates a qcow v3 file? Peter Maydell
2017-11-13 17:29 ` Peter Maydell
2017-11-13 17:58 ` Eric Blake
2017-11-13 18:08 ` Eric Blake
2017-11-14 13:32 ` Max Reitz
2017-11-14 18:45 ` Thomas Huth
2017-11-14 18:46 ` Max Reitz
2017-11-14 20:30 ` John Snow
2017-11-14 20:35 ` Max Reitz
2017-11-14 20:38 ` John Snow
2017-11-14 20:44 ` Max Reitz
2017-11-13 17:55 ` Eric Blake [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=a0d53b78-d9aa-7aa9-9fa5-8b29d53c1a9b@redhat.com \
--to=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-block@nongnu.org \
--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).