Import ova Thin provisioned disk conversion to pre allocated disks fails
Hi All, During the ova import process, preallocated disk policy is selected and the VM is imported successfully. Unfortunately the disks remain as Thin Provisioned - is this a known bug and is there a workaround? Kind Regards Simon...
On Thu, Mar 10, 2022 at 1:13 PM <simon@justconnect.ie> wrote:
Hi All,
During the ova import process, preallocated disk policy is selected and the VM is imported successfully. Unfortunately the disks remain as Thin Provisioned - is this a known bug and is there a workaround?
This should be fixed in oVirt 4.5: https://bugzilla.redhat.com/show_bug.cgi?id=1986726
Kind Regards
Simon... _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@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/6ONULHQQQOTJKJ...
Thanks Arik, Is there a fix that can be applied to current versions as 4.5 release and subsequent testing/approval is some way off/
One workaround that comes to my mind is to power up the VM, write a large file and delete it and run fstrim -av.Another approach is to create an additional LV inside the guest, use dd to fill it in and then blkdiscard and delete the LV . It will force the fisk to be fully allocated Best Regards,Strahil Nikolov Thanks Arik, Is there a fix that can be applied to current versions as 4.5 release and subsequent testing/approval is some way off/ _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@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/HXTHUA5QFBBCLM...
Another one might be to import the OVA as a template and then provision a VM from that template with allocation-policy=clone and specifying that the VM disk(s) should be preallocated On Fri, Mar 11, 2022 at 7:56 AM Strahil Nikolov via Users <users@ovirt.org> wrote:
One workaround that comes to my mind is to power up the VM, write a large file and delete it and run fstrim -av. Another approach is to create an additional LV inside the guest, use dd to fill it in and then blkdiscard and delete the LV .
It will force the fisk to be fully allocated
Best Regards, Strahil Nikolov
Thanks Arik,
Is there a fix that can be applied to current versions as 4.5 release and subsequent testing/approval is some way off/
_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@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/HXTHUA5QFBBCLM...
_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@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/4WUBMHETRW6O3P...
participants (3)
-
Arik Hadas -
simon＠justconnect.ie -
Strahil Nikolov