Hey Edison, all,
https://github.com/apache/cloudstack/commit/05bec59c1498dbcfb8a1089c86855fd3b433ea58
breaks our internal build with
+ qemu-img convert -o compat=0.10 -f raw -c -O qcow2 raw.img \
systemvmtemplate-systemvm-persistent-config-4.5.0.124-kvm.qcow2
Unknown option 'compat'
qemu-img: Invalid options for file format 'qcow2'.
This is on CentOS release 6.6, which has qemu-img-0.15.0-1.el6.rfx.x86_64.
Based on
http://wiki.qemu.org/OlderNews
that seems like it is a really old qemu (august 2011).
I'm guessing you have a newer OS / newer qemu? Can you please let me know what
OS, OS version and qemu(-img) version you are using?
Also, does anyone know if there some minimum version of qemu-img that should be
used / cloudstack assumes? Is 0.15 still ok to do an acceptable image
conversion with? (we currently don't have any kvm use ourselves, but, I'd like
for our build infra to produce useful kvm images nonetheless).
According to
http://wiki.qemu.org/ChangeLog/1.1
the -o compat switch was introduced in 1.1.
According to
https://github.com/qemu/qemu/commit/9117b47717ad208b12786ce88eacb013f9b3dd1c
the default format was changed from 0.10 to 1.1 in qemu 1.7 and onwards.
The libvirt people
https://bugzilla.redhat.com/show_bug.cgi?id=997977
say they pass -o compat when qemu supports it (so when v >= 1.1 I imagine).
I think we should do the same in the build script and I'll make a patch.
But, should we publish newer-format images too? According to
http://wiki.qemu.org/Features/Qcow3
the new format is much better so I imagine qcow/kvm users will really
appreciate the newer formats.
Thoughts?
cheers,
Leo
