In regular KVM thin disks can be made fully preallocated when you 'expand' them to the predefined maximum size. Usually I create a large file and then I delete it. Something like this: 'dd if=/dev/zero of=/path/to/mounted/qcow2/disk/largefile bs=4M status=progress ; rm -f /path/to/mounted/qcow2/disk/largefile
I doubt it's different in oVirt as backend is the same (KVM/qemu/raw or qcow2). Best Regards, Strahil Nikolov На 9 август 2020 г. 10:15:26 GMT+03:00, Eyal Shenitzky <eshen...@redhat.com> написа: >Hi Jorge, > >Currently, there is no mechanism for doing this operation on the disk, >but >there is workaround such as: > >- Export the VM as OVA or to an export domain and import it back with >the >needed allocation method. > >On Thu, 6 Aug 2020 at 17:36, Jorge Visentini <jorgevisent...@gmail.com> >wrote: > >> Hi oVirt land. >> >> Can I convert the disks of Thin Provision to Preallocated? >> >> Best Regards. >> -- >> Att, >> Jorge Visentini >> +55 55 98432-9868 >> _______________________________________________ >> Users mailing list -- users@ovirt.org >> To unsubscribe send an email to users-le...@ovirt.org >> Privacy Statement: https://www.ovirt.org/privacy-policy.html >> oVirt Code of Conduct: >> https://www.ovirt.org/community/about/community-guidelines/ >> List Archives: >> >https://lists.ovirt.org/archives/list/users@ovirt.org/message/M5DGZFUB5KVW6LWQKRC5NFDUMOUN7RKD/ >> _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/56AYNQOQ245BT3GRTE3NWIIT3XADLCHN/
