Re: [Qemu-discuss] qcow2 import error

[Konstantinos Papadopoulos]

[root@overcloud-controller-0 aat]# file aat-1.1-amend.qcow2
aat-1.1-amend.qcow2: QEMU QCOW Image (v2), 42949672960 bytes
[root@overcloud-controller-0 aat]# file aat-1.1.qcow2
aat-1.1.qcow2: QEMU QCOW Image (v3), 42949672960 bytes
[root@overcloud-controller-0 aat]#

On Tue, Jun 11, 2019 at 4:20 PM Max Reitz <address@hidden> wrote:

> On 11.06.19 15:11, Konstantinos Papadopoulos wrote:
> > Well If I get the question correctly, you are asking about the output of
> > the amended command?
> > if so, please find the output below
> > [root@overcloud-compute-6 nova]# qemu-img amend -f qcow2 -o compat=0.10
> > aat-1.1-amend.qcow2 -p
> >     (100.00/100%)
> >
> > which by the way takes place spontaneously.
>
> No, I’m asking what the "file" tool thinks of the file.  It should be
> able to detect the qcow2 version. fpr example:
>
> $ qemu-img create -f qcow2 foo.qcow2 64M
> Formatting 'foo.qcow2', fmt=qcow2 size=67108864 cluster_size=65536
> lazy_refcounts=off refcount_bits=16
> $ file foo.qcow2
> foo.qcow2: QEMU QCOW2 Image (v3), 67108864 bytes
> $ qemu-img amend -f qcow2 -o compat=0.10 foo.qcow2
> $ file foo.qcow2
> foo.qcow2: QEMU QCOW2 Image (v2), 67108864 bytes
>
> Note the "(v3)" vs. "(v2)".
>
>
> I’m wondering whether the amend process is buggy or whether something
> else is going on.
>
> Max
>
>

-- 

Konstantinos G. Papadopoulos, Dr-Eng.
Software Development Engineer
Intracom Telecom S.A., IXG
Marinou Antipa 41, Pilaia,
Thessaloniki, Greece, GR 57001
tel   : +30-2310-497459 (int.: 3959)
e-mail: address@hidden
      : address@hidden
      : address@hidden
url   : www.intracom-telecom.com

<address@hidden>