On Thu, Mar 10, 2022 at 1:13 PM 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
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-le...@ovirt.org
Privacy Statement: https:
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 Regard
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
wrote:
> One workaround that comes to my mind is to pow
Hi Arik,
I don’t see an option to select ‘allocation-policy=clone and specifying that
the VM disk(s) should be preallocated’ when creating a VM from the template.
Regard
Simon
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to u
On Sat, Mar 12, 2022 at 9:06 AM Simon Scott wrote:
> Hi Arik,
>
> I don’t see an option to select ‘allocation-policy=clone and specifying
> that the VM disk(s) should be preallocated’ when creating a VM from the
> template.
>
>From the API you need to specify clone=True as in [1] and the volume
I tried '2' but the disk is still Thin provisioned.
___
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/
7 matches
Mail list logo
