Another service that can be enabled is cross-cloud vMotion
Here are a few points about HCX vMotion
- The vMotion migration option is designed for moving single virtual machine at a time.
- Virtual machine state is migrated. There is no service interruption during a VMware HCX vMotion migration.
- As HCX uses vSphere Replication in the background – COLD MIGRATION uses the same process as vMotion – so even if you turn a VM off it will use vMotion and as a result a powered off VM cannot be migrated using Bulk Migration.
- On-Premises deployments need the VMkernel Interface for vMotion located on a Distributed Switch – Standard Switches are not supported
So once you enabled the service on the Compute Profiles and Service Mesh, it should become online alongside the other ones configured
One additional change that is required in your Compute Profile is to specify the vMotion network. Here I got one flat network so the vMotion network is the same as my management network. Not best practice of course.
You can see here in the diagram that everything runs on VLAN 0 in my environment
Let’s do a vMotion based migration. So here instead of Bulk Migration I select vMotion
And then you get a slap in the face for missing the basics
You should be able to follow the vMotion process in vCenter as well as in HCX
Here I am looking at both, HCX, vCenter and ping
Once vMotion is completed, you can see the VM now in the other cluster and I haven’t even lost a ping
So personally I gotta say – quite impressive.
Then of course the same in reverse :
One thing to note and it might be confusing ! HCX creates a ‘phantom’ ESXi host to help with the migration – here you can see 172.16.0.30:
You will notice that the IP of said host is the IP of the HCX Interconnect appliance
Next I will potentially look at L2 Extension but my lab isn’t setup for this just yet 🙂