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
Struggling with bugs and issues on OVA export/import (my clear favorite
otherwise, especially when moving VMs between different types of hypervisors),
I've tried pretty much everything else, too.
Export domains are deprecated and require quite a bit of manual handling.
Unfortunately the
Thanks for diving into that mess first, because it allowed me to understand
what I had done as well...
In my case the issue was a VM moved from 4.3 to 4.4 seemed to be silently
upgraded from "default" (whatever was default on 4.3) to "Q35", which seems to
be the new default of 4.4.
But that
Interesting I’ve not hit that issue myself. I’d think it must somehow be
related to getting the event status. Is it happening to the same vms every
time? Is there anything different about the vm names or anything that would
set them apart from the others that work?
On Sun, Aug 30, 2020 at 11:56
OK,
I ve run the backup three times .
I still have two machines, where it still fails on TASK [Wait for export]
I think the Problem is not the timeout, in oVirt engine the export has already
finished : "
Exporting VM VMName as an OVA to /home/backup/in_progress/VMName.ova on Host
kvm360"
But
While I am trying to prepare a migration from 4.3 to 4.4 with the base OS
switch, I am exploring all variants of moving VMs.
OVA export/import and export domains have issues and failures so now I am
trying backup domains and fail to understand how they are to be used and the
sparse
yes you are right,
I ve already found. But this was not realy my problem. It causes from the
HostedEngine. Long time ago I ve decreased the memory. It seems that this was
the problem. now it is seems to be working pretty well.
___
Users mailing list
Also if you look at the blog post linked on github page it has info about
increasing the ansible timeout on ovirt engine machine. This will be
necessary when dealing with large vms that take over 2 hours to export
On Sun, Aug 30, 2020 at 8:52 AM Jayme wrote:
> You should be able to fix by
You should be able to fix by increasing the timeout variable in main.yml. I
think the default is pretty low around @ 600 seconds (10 minutes). I have
mine set for a few hours since I’m dealing with large vms. I’d also
increase poll interval as well so it’s not checking for completion every 10
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
On Sun, Aug 30, 2020 at 11:49 AM Arik Hadas wrote:
>
>
>
> On Sun, Aug 30, 2020 at 10:26 AM Yedidyah Bar David wrote:
>>
>> Hi,
>>
>> On Sun, Aug 30, 2020 at 9:55 AM Kyre wrote:
>> >
>> > Hello, I am using ovirt 4.3.8. I want to use the virsh command to boot the
>> > shutdown virtual machine,
Checking the timestamp (diff between now and timestamp) of the exportfile could
also an option to verify if the export is still ongoing instead of using the
ovirt_event_info.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to
On Sun, Aug 30, 2020 at 10:26 AM Yedidyah Bar David wrote:
> Hi,
>
> On Sun, Aug 30, 2020 at 9:55 AM Kyre wrote:
> >
> > Hello, I am using ovirt 4.3.8. I want to use the virsh command to boot
> the shutdown virtual machine, but when using virsh list --all and virsh
> list --state-shutoff, the
Hi,
On Sun, Aug 30, 2020 at 9:55 AM Kyre wrote:
>
> Hello, I am using ovirt 4.3.8. I want to use the virsh command to boot the
> shutdown virtual machine, but when using virsh list --all and virsh list
> --state-shutoff, the shutdown virtual machine did not display in the list.
> What is the
Hello, I am using ovirt 4.3.8. I want to use the virsh command to boot the
shutdown virtual machine, but when using virsh list --all and virsh list
--state-shutoff, the shutdown virtual machine did not display in the list. What
is the cause of this, and how can I display the shutdown virtual
Hello,
>https://github.com/silverorange/ovirt_ansible_backup
I am also still using 4.3.
In my opinion this is by far the best and easiest solution for disaster
recovery. No need to install an appliance, and if there is a need to recover,
you can import the ova in every hypervisor - no
17 matches
Mail list logo
