Feb 02 2015

vSphere 6.0 blog – vMotion

There are a ton of new features and improved features in the release of vSphere 6.0 and my intention is not to go through all of them and make yet another release note copy. VMware has put together a vSphere 6.0 documentation page that includes all the information you require in terms of release notes, installation documents, upgrade documents, component documentation and so on. You can find the page here.

I’m going to do a blog series including three blog post of three awesome improvements and/or new features in the new vSphere 6.0 release which a know a lot of you out there including many of my my customers will benefit a lot from.

The first one includes the new features of the well known feature VMware vMotion. Still remember when i first saw the feature and i that was one of the coolest things i have seen during my years in the IT industry.
Second, the support of multi vCPUs per virtual machine (VM) support in vSphere Fault Tolerance. Blog post available here.
Last thing is the Multi-Site Content Library. Blog post available here.

Three major improvements has been made to the vMotion feature. All of them adds goodness for especially disaster avoidance (DA) but also for the traditional vMotion process for both the automatic (Distributed Resource Schedular) process and the manual process used by vSphere administrators in their day-2-day job. So here they are.

  • Long distance vMotion – The process actually supports a Round Trip Time (RTT) of 100ms now instead of the old 5 ms limitation which has been around for a while now.
  • vMotion across virtual switches – How many times haven’t you been stuck or at least being forced to make some changes/workarounds to your or your customers environment during specific project or during day-2-day operation before you could complete the vMotion process based on incorrect vSphere network configuration.
  • vMotion across vCenter Servers – The vCenter Server is actually no longer the boundary for the vMotion process. You can actually move a VM from one vCenter Server to another and this also includes to the new vCenter Server’s Datacenter object and Folder object. I just can’t wait to see what different software vendors will say about this. Read, software vendors that requires you to license all the physical hardware where a VM might run. I would say in this case they have to claim all physical ESXi servers everywhere 🙂

The vMotion interface now has its own TCP/IP stack and by that can cross L3 network boundaries.

Features and requirements

As with any functionality they come with some features and some requirements.


  • MAC addresses preserved across vCenter Servers
    • Always unique within a vCenter Server
    • Not requested when VM leaves vCenter Server
  • Data prevention
    • Alarms, Events, Tasks History
    • DRS/HA
      • Host Isolation Response
      • Start up priority
      • Automation level
      • Affinity/Anti-Affinity Rules
    • MAC Addresses of virtual NIC
    • VM Resource Settings
      • Limits
      • Reservations
      • Shares
  • VM UUID is maintained across vCenter Servers


  • vCenter Server 6.0 or higher
  • SSO Domain
    • If using vSphere Web Client it has to be the same
    • If using API it is possible to use different
  • L2 network connectivity on VM port groups
    • IP addresses are not updated. Then you have to use e.g. Site Recovery Manager.
  • 250 Mbps network bandwidth per vMotion operation

vSphere 6.0 configuration maximums can be found here.


Skip to comment form

  1. Stayfans

    thx for the résumé.

  2. Nick Korte

    Thanks for the post. Some great information.

  3. Paulo Reis

    With new vMotion features we can increase HA. If one site is down, it can be moved to another site.

  4. ScoZel

    In my opinion, this is the best feature to come with vSphere 6!

  5. Yuri

    definatelly vMotion is one of the coolest features that got so many enhancements. Its a mayor step for VMware and the industry of Virtualization.

  6. Raffaello

    vMotion is the hottest renewed feature of vSphere 6! It opens a wide world of opportunities

  7. magander3

    Yes agree, closely followed by vSphere HA and FT:)

  8. Mike Medrano

    Another nice article!

    ~ Mike

  9. Looneyduk

    I have been waiting for these “barriers” to drop since the first release of vMotion. Good job VMWare, and another great post. Keep up the good work

  10. CoquiPR81

    Great read Magnus, Always appreciate the time and effort that you put into your blogs to keep the communities informed of new technologies. Keep up the great work!


  11. magander3

    thanks man.

  12. Zsolt Pamuki

    Long distance vMotion is a game changer. I can’t wait to see it in real life.

  13. Jay Wright

    Great info. This is a truly awesome feature. It will be nice to vMotion between sites

  14. Syed Fayyaz Hussain Rizvi

    Thanks for the post, great information in your Blogs.

  15. Timothy Matthews

    Thanks for the sum up.

    I wonder how the inter-vCenter vMotion will deal with MAC collisions, considering that they are kept within a vMotion.

  16. magander3

    Good question, don’t know actually.


  17. Cris Rodriguez

    Great feature, now to get the network team on board with layer 2 across data centers.

    Thanks again for the post.

  18. Andres Rojas

    Great post thx for the summary, but I question:
    When you mentioned the vMotion between vSwitches, you mean vDS, right?

  19. Mohamed Ibrahem

    Great article, many thanks for all your efforts

  20. Alessandro

    This is the best improvement for me in 6.0

  21. Geoff Neish

    With Long distance vMotion is there a limit on how big the VM is?
    We have a VM that is about 15TB in size, I just wonder how many years it would talk to vMotion something like that

  22. magander3

    guess it depends on your network speed. Haven’t seen a maximum VM size


  23. Amit Gumber

    Very Informative.

  24. MaxxABillion

    Agreed, informative

  25. Thomas True

    Very helpful to move VMs across vCenters with vMotion.

  26. vervoort jurgen

    do you realy need 250Mbps as Wan connection between the sites?

  27. Rahim

    Great feature with the cross migration. long awaited for a feature like thic

  28. Andres Rojas

    thx for the post

  29. Mohammed Sadiq

    Good Feature of Vsphere 6

  30. Shawn

    Wow! I am glad I came across this!

    The vMotion interface now has its own TCP/IP stack and by that can cross L3 network boundaries.

    This is awesome news! I don’t know how I missed that.

  31. Francisco Amadi

    Maybe 250 Mbps for a site-to-site communication are a little bit too much, expecially in other coutries than Korea, Japan or Singapore 🙂 Great insight though, thanks!

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code class="" title="" data-url=""> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong> <pre class="" title="" data-url=""> <span class="" title="" data-url="">