Hi Yaniv,

I found out reason it didn't work was probably bug.

For reference probably https://bugzilla.redhat.com/show_bug.cgi?id=1446878
I updated oVirt to release candidate 3 4.1.3 and this fixed the issue.

I am now investigating to have an extra 3.6 Dc in my new Hostedengine with a Cluster setup as 3.6, so I can switch storage domain and do a roll back to old Hosted engine in case of any problems.

Thanks for you comments!



Op ma 26 jun. 2017 om 11:18 schreef Yaniv Kaul <ykaul@redhat.com>:
On Fri, Jun 23, 2017 at 1:13 AM, Paul Groeneweg | Pazion <paul@pazion.nl> wrote:
We are moving our VMs from an old 3.6 oVirt platform to a new oVirt 4.1 platform.

I am looking for an easy way to migrate the VMs. ( I know about export domain, but this takes 2 times a copy action ) I tested and just detaching the Data domain and attaching it, didn't work. 


It should work, and is the easiest way by far. Can you share more details on what did not work for you?
Y.
 
Then I found the VM import option:
 - Adding a ssh key gen and setting password on virsh 
- load a list of machines in the webinterface from VM import
- when I start an import the system complains:
The following VMs retrieved from external server qemu+ssh://root@xxx.xxx.xxx.xxx/system are not in down status: VM [VM-NAME].
- I tried to suspend the VM, but this didn;t work either ( same error )
- Problem is ,when VM is shutdown, it disappears from this system list.

Is there a way to directly import a VM from old oVirt platform to the new platform

Looking forward to find a solution to quickly migrate our VMs.

Best Regards,

Paul Groeneweg


_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users