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:
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
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
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
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
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:
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
Hi Dominique,
Thanks for the logs
Does this issue also reproduce with new Windows VM's that you create?
If it's reproducing, can you please provide a scenario to reproduce this
issue with the VM configuration details? So can we try to reproduce it
Thanks,
Saif
On Tue, Aug 31, 2021 at 5:50 PM
Hi Saif,
Here the error in engine.log
2021-08-31 10:22:26,536-04 INFO
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default
task-8) [82b7a8d4-15d1-4553-94e5-34506d174ac4] EVENT_ID:
ANSIBLE_RUNNER_EVENT_NOTIFICATION(559), Query OVA info. Run query script.
Hi Dominique,
Hope you are doing well
In order to investigate this, we need to check the log files
Can you please try to do import again and provide the following log
files after the import:
- engine.log, from location:
/var/log/ovirt-engine/engine.log
- ansible log file (depending on the time
ssunto: [ovirt-users] Re: Import OVA
On Fri, Dec 14, 2018 at 5:45 PM < supo...@logicworks.pt > wrote:
Hi,
I have created a export domain using Glusterfs.
When I go to Storage-Domains, click on the export domain, on VM Import the
Import button is greyed out.
Did you first
On Fri, Dec 14, 2018 at 5:45 PM wrote:
> Hi,
>
> I have created a export domain using Glusterfs.
> When I go to Storage-Domains, click on the export domain, on VM Import the
> Import button is greyed out.
>
Did you first select the image you need to import?
> My test environment is running a
Hi,
The log you attached doesn't seem to contain any helpful information.
Please attach timely errors you see in vdsm.log and
/var/log/vdsm/import/import-[id].log
cc'ing Arik who may be able to help.
Best wishes,
Greg
On Thu, Jun 28, 2018 at 9:27 PM du_hon...@yeah.net
wrote:
> Hi
> my
13 matches
Mail list logo
