Re: The two image formats called qcow

[Kevin Wolf <kwolf@suse.de>]

Keir Fraser schrieb:
> It's tricky where users' non-volatile storage is concerned though. Other
> than that I would say the bug should be fixed immediately. Is there an easy
> way to detect with reasonable reliability whether we have an old or new
> image? Failing that we may have to provide a tool to convert old images to
> new format.

Something like "that number looks too big, it be must little endian"
could easily turn into "that harddisk looks big, let's break the image",
I suspect.

However, I just noticed that the tapdisk qcow driver writes an extended
Xen-specific header to the image file. This should be reliable enough to
detect tapdisk images.

Is it an option to convert broken images to big endian when it is opened
for the first time in ioemu? In this case, the fix for older versions
could be in one place at least instead of being scattered over the whole
file. Then you wouldn't be able to open such a file with tapdisk again,
though.

Kevin