> On 5 Jun 2019, at 12:51, Eyal Shenitzky <[email protected]> wrote: > > > > On Wed, Jun 5, 2019 at 12:40 PM Andrei Verovski <[email protected] > <mailto:[email protected]>> wrote: > Hi, > > It is located on NFS storage domain V4. > > Note that there is a bug that will prevent you from creating a VM from a > template as with preallocated disks - > https://bugzilla.redhat.com/show_bug.cgi?id=1403183 > <https://bugzilla.redhat.com/show_bug.cgi?id=1403183> > This was fixed only in version 4.3 > > Furthermore, it seems that fix missed the scenario you described. > > Can you please submit a bug and attach the VDSM and the engine logs?
Are all log files located on hosted engine ? Or something needs to be taken from node PC ? > > > > >> On 5 Jun 2019, at 12:28, Eyal Shenitzky <[email protected] >> <mailto:[email protected]>> wrote: >> >> Is your disk is based on a file storage domain? >> >> On Wed, Jun 5, 2019 at 12:19 PM Andrei Verovski <[email protected] >> <mailto:[email protected]>> wrote: >> Hi ! >> >> Followup to my previous post. >> Creating template from snapshot in 4.2.8 also suffers from the same bug - >> allocation policy selected to thin provision even if I select RAW from the >> popup menu. >> Verified twice. >> >> >> > Looks like there is some strange glitch creating new VM from template on >> > oVirt 4.2.8.2. >> > >> > Basically I’m need to convert disk image from QCOW2 thin allocated to raw >> > format in an existing VM. >> > These are steps performed: >> > 1) Create snapshot of an existing VM. >> > 2) Make template from snapshot. >> > 3) Create new VM using template, in Resource Allocation -> Storage >> > Allocation -> Clone -> Format -> Raw. >> > >> > Unfortunately, newly created VM still have QCOW2 thin allocated disk. >> > Did this operation twice to be sure, and both times things went wrong. >> > >> > What is done wrong, and how to solve this problem? >> > Thanks in advance. >> > >> _______________________________________________ >> Users mailing list -- [email protected] <mailto:[email protected]> >> To unsubscribe send an email to [email protected] >> <mailto:[email protected]> >> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ >> <https://www.ovirt.org/site/privacy-policy/> >> oVirt Code of Conduct: >> https://www.ovirt.org/community/about/community-guidelines/ >> <https://www.ovirt.org/community/about/community-guidelines/> >> List Archives: >> https://lists.ovirt.org/archives/list/[email protected]/message/PML643EOXCTC72MRAPP6UYLFSJNAPD7M/ >> >> <https://lists.ovirt.org/archives/list/[email protected]/message/PML643EOXCTC72MRAPP6UYLFSJNAPD7M/> >> >> >> -- >> Regards, >> Eyal Shenitzky > > _______________________________________________ > Users mailing list -- [email protected] <mailto:[email protected]> > To unsubscribe send an email to [email protected] > <mailto:[email protected]> > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > <https://www.ovirt.org/site/privacy-policy/> > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > <https://www.ovirt.org/community/about/community-guidelines/> > List Archives: > https://lists.ovirt.org/archives/list/[email protected]/message/COZNUX35NFM5C2PHUN2U3A3XJUMZPFIQ/ > > <https://lists.ovirt.org/archives/list/[email protected]/message/COZNUX35NFM5C2PHUN2U3A3XJUMZPFIQ/> > > > -- > Regards, > Eyal Shenitzky
_______________________________________________ Users mailing list -- [email protected] To unsubscribe send an email to [email protected] Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/[email protected]/message/GU3AVTEHJKZT5D5QHPI7GGC2PABQOUD5/
