On Sun, Aug 30, 2020 at 11:46 PM wrote:
>
> BTW: This is the message I get on the import:
> VDSM nucvirt command HSMGetAllTasksStatusesVDS failed: value=low level Image
> copy failed: ("Command ['/usr/bin/qemu-img', 'convert', '-p', '-t', 'none',
> '-T', 'none', '-f', 'qcow2',
>
Hi Gianluca, we have read the massage from Jayme, but we have problem
with the INTERNAL ansible playbook.
Wen we run an export, ovirt internally run the playbook
/usr/share/ovirt-engine/playbooks/ovirt-ova-export.yml
but only export at time
Il 27/08/2020 11:15, Gianluca Cecchi ha
BTW: This is the message I get on the import:
VDSM nucvirt command HSMGetAllTasksStatusesVDS failed: value=low level Image
copy failed: ("Command ['/usr/bin/qemu-img', 'convert', '-p', '-t', 'none',
'-T', 'none', '-f', 'qcow2',
> On Fri, Aug 28, 2020 at 2:31 AM
> You should really try the attach/detach storage domain, this is the
> recommended way to move
> vms from one ovirt system to another.
>
> You could detach the entire domain with all vms from the old system,
> and connect it to the new
> system, without
On Fri, Aug 28, 2020 at 2:31 AM wrote:
>
> I am testing the migration from CentOS7/oVirt 4.3 to CentOS8/oVirt 4.4.
>
> Exporting all VMs to OVAs, and re-importing them on a new cluster built from
> scratch seems the safest and best method, because in the step-by-step
> migration, there is
I am testing the migration from CentOS7/oVirt 4.3 to CentOS8/oVirt 4.4.
Exporting all VMs to OVAs, and re-importing them on a new cluster built from
scratch seems the safest and best method, because in the step-by-step
migration, there is simply far too many things that can go wrong and no easy
On Tue, Aug 25, 2020 at 3:29 PM Tommaso - Shellrent
wrote:
> Hi Gianluca.
>
> We have a problem wit "export as ova" too.
>
> In our env we back up all the vm with a python script that run an export.
>
> If we run multiple export at the same time, also on different
> datacenter[but same engine],
Hi Gianluca.
We have a problem wit "export as ova" too.
In our env we back up all the vm with a python script that run an export.
If we run multiple export at the same time, also on different
datacenter[but same engine], the wait for each other and do not run in
async mode.
If only one of
On Fri, Jul 19, 2019 at 5:59 PM Gianluca Cecchi
wrote:
> On Fri, Jul 19, 2019 at 4:14 PM Gianluca Cecchi
> wrote:
>
>> On Fri, Jul 19, 2019 at 3:15 PM Gianluca Cecchi <
>> gianluca.cec...@gmail.com> wrote:
>>
>>>
>>>
>>> In engine.log the first error I see is 30 minutes after start
>>>
>>>
On Fri, Jul 19, 2019 at 4:14 PM Gianluca Cecchi
wrote:
> On Fri, Jul 19, 2019 at 3:15 PM Gianluca Cecchi
> wrote:
>
>>
>>
>> In engine.log the first error I see is 30 minutes after start
>>
>> 2019-07-19 12:25:31,563+02 ERROR
>> [org.ovirt.engine.core.common.utils.ansible.AnsibleExecutor]
>>
On Fri, Jul 19, 2019 at 3:15 PM Gianluca Cecchi
wrote:
>
>
> In engine.log the first error I see is 30 minutes after start
>
> 2019-07-19 12:25:31,563+02 ERROR
> [org.ovirt.engine.core.common.utils.ansible.AnsibleExecutor]
> (EE-ManagedThreadFactory-engineScheduled-Thread-64) [2001ddf4] Ansible
11 matches
Mail list logo
