VME 8.0.8 - Migration from VMware

[ut03550]

Hi.

I'm testing the new tool to migrate VMware VM's to VME... my first try is with an Ubuntu VM... The migration ends wells, and without errors (of course, before, do a "apt update/upgrade" in the VMware VM. But when the new VM in VME try to boot I obtain that there is no bootable disk... I've tried everything, booting from a Ubuntu live CDROM and trying to mount the disk, but I'm not be able to do it, because Ubuntu linux says that the disk don't have any formatting, that it's a qcow disk.

Any ideas?

[ut03550]

I think could be a communication problem between vCenter/ESXi and de VME-Manager/HVE Hosts.... Is there some place with a communications table to do the migrations?

[Arnout_Verbeken]

Did you prepare the VM as described in https://www.hpe.com/psnow/doc/a00146594enw ?
Note that this paper is out of date (since the migration procedure has changed to use the new wizard now - paper is in the process of being updated), but the prerequisites and the process you need to prepare your VM are still the same.
In you case, I think it might be related to how the mount points are defined (by sdX or by-uuid).
It is highly recommended ot make sure by-uuid is used.

[ut03550 · Accepted solution]

Yes. I've prepared the Windows VM and Linux VM as said in documentation (not this one that you provided... it's not easy to access and find documentation), but this one "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00006560en_us&page=GUID-D3E08022-96A5-4BD8-9DDF-67D942A361C0.html". 

But, finally, it was a communicaitions problem, that I solved in my LAB permiting all traffic... but in a complex network as my company, those communications could be a very hard problem to solve, especially for communications to VM's (we have several networks and environments, all completely isolated). It would be a "must" to have a more simple communications to do migrations... 

Connection Protocol Port(s) Purpose VME Manager ↔ vCenter TCP 443 Used for API communication to orchestrate migration tasks.

VME Manager → Source Linux VM TCP 22 Used for SSH to install the VME agent and prepare the workload.

VME Manager → Source Windows VM TCP 5985, 5986 Used for WinRM to install the VME agent and prepare the workload.

VME Manager → Morpheus Node (destination) TCP 5000-5010 A range of ports used for data transfer during the migration.

Morpheus Node ↔ Source VM TCP 9000-9005 A range of ports used for disk image transfer during migration.

Thank you.

Best regards.