The Engine logs should be found in the machine where your engine runs under
- /var/log/ovirt-engine/engine.log
The host/VDSM logs should be found in the host/VDSM machine under -
/var/log/vdsm/vdsm.log
On Wed, Jun 5, 2019 at 1:11 PM Andrei Verovski <andreil1(a)starlett.lv> wrote:
On 5 Jun 2019, at 12:51, Eyal Shenitzky <eshenitz(a)redhat.com> wrote:
On Wed, Jun 5, 2019 at 12:40 PM Andrei Verovski <andreil1(a)starlett.lv>
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
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 <eshenitz(a)redhat.com> wrote:
>
> Is your disk is based on a file storage domain?
>
> On Wed, Jun 5, 2019 at 12:19 PM Andrei Verovski <andreil1(a)starlett.lv>
> 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 -- users(a)ovirt.org
>> To unsubscribe send an email to users-leave(a)ovirt.org
>> 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/users@ovirt.org/message/PML643EOXCT...
>>
>
>
> --
> Regards,
> Eyal Shenitzky
>
>
> _______________________________________________
> Users mailing list -- users(a)ovirt.org
> To unsubscribe send an email to users-leave(a)ovirt.org
> 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/users@ovirt.org/message/COZNUX35NFM...
>
--
Regards,
Eyal Shenitzky
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)ovirt.org
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/users@ovirt.org/message/GU3AVTEHJKZ...