Part 13 – The VMware Exit: Migrating VMs to HPE VM Essentials

We have finally reached the part you have been waiting for- the VMware exit. In this blog, we will move this VM from our vSphere estate to HPE VM Essentials.

The source side is a small vSphere estate, and the target is the 3-node HVM cluster

Add vCenter as a Cloud

In VME, go to Infrastructure → Clouds → + Add → VMware vCenter:

Choose vCenter

Fill in only these fields and leave everything else at its default:

  • Name lon-vc
  • Enabled : ticked
  • Automatically Power On VMs – unticked

Fill in only these fields and leave everything else at its default:

  • API URL https://vcenter.lab.internal/sdk
  • Username administrator@vsphere.local, plus its password
  • Version 7.0, Datacenter DC-Lab, Cluster CL-esx
  • Inventory Existing Instances: On
  • Group: lab

In next screen, choose our Lab Group

Click Complete

Wait a few minutes for discovery

Create and run the migration plan

Go to Tools → Migrations

Click Add

Under the migration plan, provide all these details

  • Source: London-vCenter
  • Target: London HVM cluster
  • Resource pool – HVM Cluster01

Choose the target Network and Datastore on the HVM

Review and Click Complete.

  • Linux username: ubuntu
  • Linux password: password.
  • Install guest tools: No.
  • Preserve network config: Choose Network and Storage
  • Skip prechecks: unticked.
  • Skip Guest tools: unticked.

Click Run to Start Migration

Precheck → prepare → create → transfer

the source VM is shut down at this point.

  • Then use Actions → Convert to Managed to install the agent.

Finally, it completes

It’s on our hvm host, and once everything is okay, hit the Actions menu and set it to managed.

Run a ping check

The migration logs can be viewed from the vme cli so login as admin/password

sudo tail -f /var/log/morpheus/morpheus-ui/current | grep -iE --line-buffered 'migrat.*(warn|error|fail)|exception'

Migration done, finally so the tool does the job: one VM moved from vSphere to HVM with its IP intact and the source kept as a rollback.

(Visited 2 times, 1 visits today)

By Ash Thomas

Ash Thomas is a seasoned IT professional with extensive experience as a technical expert, complemented by a keen interest in blockchain technology.