Request to use Compat 1.1 on New QCOW2 image creation?

Any reason to keep on using Compat 0.10? Its easy enough to fix with this, but it seems like it shouldn't be necessary on what is by definition a new install. #!/bin/sh src_img=$1 qemu-img amend -p -f qcow2 -o compat=1.1 ${src_img} -bill

Hi Bill, I need to check, but I don't it is specified by Kimchi. I think Kimchi relies on libvirt on that. So probably, the default on libvirt is 0.10. But again, I need to check that to confirm. Regards, Aline Manera On 04/11/2017 07:16 PM, WK wrote:
Any reason to keep on using Compat 0.10?
Its easy enough to fix with this, but it seems like it shouldn't be necessary on what is by definition a new install.
#!/bin/sh
src_img=$1
qemu-img amend -p -f qcow2 -o compat=1.1 ${src_img}
-bill
_______________________________________________ Kimchi-devel mailing list Kimchi-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/kimchi-devel

ok, could be. This virt-install line (which we also use) produces a qcow2 with the 1.1 compat layer. (Though maybe IT is telling libvirt what to do) virt-install -n $domain -r $memory --os-type=linux --disk $disk,device=disk,bus=virtio,cache=none,io=native --graphics vnc --noautoconsole --import --noreboot On 4/17/2017 5:39 AM, Aline Manera wrote:
Hi Bill,
I need to check, but I don't it is specified by Kimchi. I think Kimchi relies on libvirt on that. So probably, the default on libvirt is 0.10.
But again, I need to check that to confirm.
Regards, Aline Manera
On 04/11/2017 07:16 PM, WK wrote:
Any reason to keep on using Compat 0.10?
Its easy enough to fix with this, but it seems like it shouldn't be necessary on what is by definition a new install.
#!/bin/sh
src_img=$1
qemu-img amend -p -f qcow2 -o compat=1.1 ${src_img}
-bill
_______________________________________________ Kimchi-devel mailing list Kimchi-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/kimchi-devel
participants (2)
-
Aline Manera
-
WK