ryecoaaron I'm back to testing OMV6 after couple of weeks breaks and there seems to be a bug in the KVM restore function. A VM with a single qcow2 format disk backs up as qcow2, but restores as a raw format disk producing an error when the VM is started.
Code
root@omv6:/Opool/kvm_storage# qemu-img info test.qcow2
image: test.qcow2
file format: qcow2
virtual size: 10 GiB (10737418240 bytes)
disk size: 790 MiB
cluster_size: 65536
Format specific information:
compat: 1.1
compression type: zlib
lazy refcounts: true
refcount bits: 16
corrupt: false
extended l2: false
root@omv6:/Opool/backup/server/test/2022-05-07_13-25-13# qemu-img info test.qcow2_2022-05-07_13-25-13.bak
image: test.qcow2_2022-05-07_13-25-13.bak
file format: qcow2
virtual size: 10 GiB (10737418240 bytes)
disk size: 765 MiB
cluster_size: 65536
Format specific information:
compat: 1.1
compression type: zlib
lazy refcounts: false
refcount bits: 16
corrupt: false
extended l2: false
root@omv6:/Opool/backup/server/test/2022-05-07_13-25-13
root@omv6:/Opool/kvm_storage# qemu-img info test.qcow2
image: test.qcow2
file format: raw
virtual size: 10 GiB (10737418240 bytes)
disk size: 790 MiB
root@omv6:/Opool/kvm_storage#The culprit seems to be line 143 in /usr/sbin/omv-restore-vm
Code
qemu-img dd if="${bak}" of="${copyTo}" bs=1MWithout -f -o flags, "qemu-img dd" doesn't seem to preserve qcow2 format.