When importing a VM from KVM with thin provision disk the resulting disk in oVirt will effectively be pre-allocated, despite the thin option being selected during the import process. I believe this has a dependency on https://bugzilla.redhat.com/show_bug.cgi?id=1332019
can you please check that it's still the case, do we need any more work other than using el7.4?
(In reply to Alan Griffiths from comment #0) > I believe this has a dependency on > https://bugzilla.redhat.com/show_bug.cgi?id=1332019 I'm not entirely sure these two bugs are related. Can you confirm that your problem is only the situation where the source KVM stores the images as raw (as opposed to qcow2)? If yes, then the problem is that we cannot efficiently transfer sparse files between source and destination libvirt. This feature is tracked by bug 1282859.
(In reply to Michal Skrivanek from comment #1) > can you please check that it's still the case, do we need any more work > other than using el7.4? To answer this question: yes we will need to update kvm2ovirt to make use of the new libvirt feature.
My scenario was this: - I had a number of VMs which had been provisioned with pre-allocated raw disks. I converted the disks to thin prov qcow2 using virt-sparsify, verified they still booted correctly, then imported into oVirt. At the time it never occurred to me to check that they had actually been imported as thin-prov. It was only some time later when reviewing storage usage that I realised they were all pre-allocated.
If the source was qcow2 file than it's not related to the bug I mentioned in comment 2. Without further info I guess I'll close it as it works for me. What type of storage domain are you using in oVirt?
Block - Fibre channel.
this will not make 4.2, postponing
(In reply to Tomas Jelinek from comment #7) > this will not make 4.2, postponing oops, it just did. Fixed by bug 1628477 in 4.2.7