vMotion in vSphere 5.5

Posted: September 17, 2015 in VMWare

VMware vSphere live migration (vMotion) allows us  to move an entire running virtual machine from one physical server to another, without downtime. The virtual machine retains its network identity and connections, ensuring a seamless migration process. We can also move VM to another storage.This article is sequel of my previous article

In this one we will configure vSphere for seemless VM migration from one ESXi host to another.

Creating vSphere cluster

To create vCenter cluster right click on Datacenter-New Cluster


While creating a cluster,we can enable high availability (HA)-detect failure and recover VMs


VMware DRS (Distributed Resource Scheduling), balance VMs over hosts to ensure even resource usage between all hosts

Admission control configures constraints on resource usage and any action that would violate these constraints is not permitted.When you enable VM Monitoring, the VM Monitoring service (using VMware Tools) checks if each virtual machine in the cluster is running by checking for regular heartbeats and I/O activity from the VMware Tools process running inside the guest.You can specify how many host failures cluster can endure.


Enhanced vMotion Compatibility (EVC) simplifies vMotion compatibility issues across CPU generations. EVC automatically configures VM processors based on ESXi’s CPU (AMD or Intel)

Virtual SAN (VSAN) is a software based distributed storage solution which is built directly in the hypervisor (ESXi layer)

Add hosts into cluster:



Creating SAN storage

A storage area network (SAN) is a network that provides access to consolidated, block level data storage

A SAN typically has its own network of storage devices,in this example we’ll be using ISCSi krenel network ( from previous lab.

On FreeNas server,i added two 10GB’s HDD,and created mirror volume (NAS),i already covered creating volumes in prevoius lab,so i won’t go through it again.

After creating volume,we need to share it,click Share-Unix-Add Unix share


Add descriptive name,network from which can be accessed to NFS,and choose Maproot user (root)

  -maproot=user The credential of the specified user is used for remote access by root.


And enable NFS service


Adding NFS storage to Cluster

Now,when we have NFS storage,add it to Cluster,Right click on Cluster and choose New Datastore



Enter the datastore Name,FreeNAS IP address and volume path


Give access to NFS share to both ESXi hosts


Now,when cluster is created,configure vSphere to uses datastores for heartbeating.One ESXi host is declared as master.The following algorithm is used for  selecting the master:

– The host with access to the greatest number of datastores wins.

– In a tie, the host with the lexically highest moid is chosen.

A Managed Object Reference ID also known just as MoRef ID is a unique value that is generated by the vCenter Server and is guaranteed to be unique for a given entity in a single vCenter instance,for more info visit http://www.doublecloud.org/2011/06/managedobjectreference-vs-managedobject/

The master/slave concept is used for monitoring vSphere HA clusters,and it uses an election process to determine which host is to be the master. This election process occurs any time the existing master fails, is shut down, or is placed into maintenance mode.When the master host in a vSphere HA cluster can not communicate with a slave host over the management network, the master host uses datastore heartbeating to determine whether the slave host has failed.If the slave host has stopped datastore heartbeating, it is considered to have failed and its virtual machines are restarted elsewhere Datastore heartbeating allows vSphere HA to determine the difference between a failed host and a host that has just been split off from the others for example.

vCenter uses dastastores to determine VM state

We’ll add two datastores for heartbeating:NFS we created in this post,and another one (iSCSI) created in previous one.

Click on New Cluster-Setings-Edit-DataStoreHeartbeating and select both datastores


VM migration

I created Linux Puppy VM on Datastore named Datastore and want to transfer it to moving machine disconnect it’s DVD drive from it

Right click on VM and choose migrate


Click change host host selection within the cluster


Select ESXi host to which you want to migrate VM



Machine is migrated to



Migating VM to another storage

Puppy VM is on Datastore named datastore and I want to migrate it to NFS datastore

Again right click on VM and choose migrate and this time select change datastore



  1. sheikvara says:

    Awesome my dear Friend.



Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s