vMotion compatibility

Similar Questions

• The processors for vMotion compatibility

  We have just upgraded to vSphere Essentials 6, Plus so we can take advantage of vMotion. We have built an almost exact replica of our existing Dell PowerEdge T420 server, so that we can have a high availability for virtual machines, they move from one physical server to another, depending on the needs. Looking through the documentation of DRS cluster, it is said that the processors 'must come from the same class of supplier (Intel and AMD) with the same family of compatible processor for migration with vMotion. . "(vSphere 5.5 Documentation Centre()'

  Our current server has a processor of v2 Intel Xeon E5-2440 (8 cores, 20 MB of cache, 1.9 GHz). The seller we buy our new generation of server of door the same CPU model number (Intel Xeon E5-2440), but with 6 cores, 15 MB of cache, 2. 4 GHz. They have to special order the exact same processor, we currently have. We will encounter any problems if the rest of the hardware is the same, but the processors are slightly different? Same supplier, same family, same model number – only with fewer cores, less cache, more GHz. Is that what I should consider before moving?

  Thank you!

  Ben

  Your processors are of different generations, the E5-2440 is a Sandy Bridge and the E5-2440 v2 is an Ivy Bridge, take a look here: http://ark.intel.com/compare/64612, 75263

  And since they are from a different generation, you need to activate CVS in your cluster to the power of the machine virtual vMotion between these hosts, have a look here for more information on the CVS: KB VMware: best vMotion compatibility (EVC) processor support

• The host cannot be admitted to the current cluster Enhanced vMotion compatibility mode.

  Hello everyone

  Here's the situation...

  I have:

  vSphere 5.1 Cluster with two 5.1 ESXi hosts and configuration VSA.

  vCenter Server running on a virtual Windows Server 2012 machine.

  Task: Transfer virtual vCenter to a physical machine.

  I have install the physical machine with Windows server 2012.

  Installed vCenter 5.5 (hosts Newer then the ESXi 5.1)

  VSA installed Manager (VSA Cluster 5.5)

  When go to VSA Manager I am introduced to the following screen...

  

  Recover DOES NOT work!

  Full move operation DOES NOT work!

  It recognizes the Cluster AUV-> check availability (is online and OK)-> begins to create the Cluster VSA and it fails with the following error...

  Move the cluster host

  VSA HA Cluster

  The host cannot be admitted to the current cluster Enhanced vMotion compatibility mode. Under voltage or suspension of the virtual machines on the host can use the CPU features hidden by this mode.

  Could someone please help?

  Thanks to you all! This problem has been SOLVED as follows...

  • VCenter Server go to--> "C:\Program Files\VMware\Infrastructure\tomcat\webapps\VSAManager\WEB-INF\classes".
  • Open the file "dev.properties" with Notepad
  • Change the line that says "evc.config.baseline = lowest" to 'highest = evc.config.baseline' and save the file.
  • Perform the SERVICES. MSC and reboot 'VMware VirtualCenter Management Webservices'

  After that it of back in the VSA Manager and run it again 'Cluster of VSA recover'!

  Now, the wizard should be able to add hosts to the inventory, create the HA Cluster and add hosts to the HA cluster and configure Cluster HA.

  Done everything! :-)

• FT/HA/vMotion compatibility

  Hello

  I hope that the forum does not mind this strange issue. I tried to continue my learning of vSphere and ESXI installed on a white box with i7-2600 machine, on the Intel H67 chipset. Everything works

  I would now like to add a second esxi host, practice FT/HA/Vmotion. I intend to stick with the i7-2600 for the processor, but my question is, the motherboard chipset should it be the same? I have to stay with a motherboard that is H67?

  Thank you.

  -MN

  Hello

  Shorat response is "no, it doesn't have to be the same.

  Slightly longer answer is:

  For HA, it shouldn't make any difference if it's the same or not (mother or processor card). For FT, and vMotion processor count.

  Although FT and vMotion are apparently completely different one from the other, FT is possible with vMotion, so, the first thing to do is to understand the vMotion compatibility.

  The "only thing" vMotion to be is (apart from a shared storage, network connectivity, etc.) East of compatible processors between them. You can have a look on this

  http://KB.VMware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalID=1003212

  and this

  http://KB.VMware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalID=1991

  As you will see, processor questions and where you do not have the same processor, then you should play a little with VCA.

  This is a compatibility table for EVC and the mask, you need to use in case you want to use two different processors

  http://KB.VMware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalID=1003212

  And in case you want to learn a little more about all these (basic knowledge), you can take a look in this doc.

  http://www.VMware.com/files/PDF/vmotion_info_guide.PDF

  I hope this has helped you!

  Concerning

  SEB

• VCA and VMotion compatibility

  I am looking for a few new ESX boxes to expand our data center of VSphere 4 current U1.

  Ideally, I would buy Intel E7540 series servers because they can FT and adapt the specifications I need.

  I currently have a mix of X 5355 and E7330 ESX boxes.

  DELL sales tell me that E7540 processors are not compatible with the existing X 5355 vmotion and processors E7330 (even with active CVS).

  VCA and flexmigration enable me to vmotion (hot) between theses processors and processor E7540? I have the impression that the seller DELL is perhaps wrong as I thought VCA and flexmigration should mitigate the differences between these processors (obviously within reason)? Surely at least between the E7330 and the E7540?

  I had a look to many documents, including the KB Article: 1003212 but still trying to find a definitive answer?

  Forget DELL sales. They should be compatible under VCA VMotion (VCA's enhanced VMotion compatibility). But they are obviously not compatible FT.

  ---

  MCSA, MCTS, VCP, VMware vExpert 2009

  http://blog.vadmin.ru

• vMotion compatibility Intel CPU

  Hi all

  I'm making reference to this document: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US & cmd = displayKC & externalId = 1991

  Requirements of VMotion CPU compatibility for Intel processors

  We have four servers BL460c G1 (Xeon 54xx CPU). I want to buy two new servers to replace 2 we have in an offbeat upgrade. The new servers are BL460c G7 (Xeon 56xx CPU).

  In the above document, our current processor is part of Group C. Our new servers fit into Group E. There are instructions of compatibility vmotion for vMotioning fast between the groups C - D and D-e... but I need to know if I can vMotion the c.-e. group. Is this possible, or what I can not vmotion?

  Thanks for your help!

  The VMware Compatibility Guide for your research material and click on the CPU model. This will open a web page that shows all modes of EVC supported CPU.

  André

• VMotion compatibility between Opteron 6100 (Magny Cours) and Opteron 6200 (Interlagos)

  Anyone know if knew that Opteron 6200 (Interlagos) are compatible with Opteron 6100 (Magny Cours) VMotion?

  VMware used to maintain an up-to-date list of processors with a compatibility matrix, but I didn't see a current copy of this document within a certain time.  The last that I could dig up was 2008, so I ask my question here.

  Also, if anyone knows of a compatibility matrix was updated that they could tell me, that would be helpful.

  Thank you!

  Allen Beddingfield

  Systems engineer

  The University of Alabama

  Allen: I can confirm that VMotion works between Opteron 6100 and 6200 if you are using the CVS 'AMD Opteron Genesis 3 (no 3DNow!) '.

• VMotion compatibility guide

  Hi all

  Can someone help me find a compatibility guide for VMotion on HP servers. We run two HP DL380G6 servers with Intel® Xeon® X 5560 processors and you want to buy HP DL380 G7 servers with Intel® Xeon® X 5650 processors. I need to know if these different models will be able to vmotion.

  Thank you

  Kenny

  Hi Kenny,

  You can take a look at the following article.

  Good luck.

  Concerning

  Franck

• Intel's Nehalem VMotion compatibility - And current Xeon

  Hi all

  I was wondering if anyone can tell me if the processors Intel Nehalem will be compatible with the Xeon VMotion, I in my BL460c?  I am looking into the possibility of adding some BL490c to our ESX cluster, once they are released, but I am wary of any possible difference in CPU.

  If you enable CVS in your cluster, you should not have problems with compatibility.

  -KjB

• VMotion compatibility - different CPU

  Sorry to post a question, but I just haven't found the answer in the readme guides and admin I have for 4.1.  We use servers for our cluster, all HP DL380 G5 with the dual Xeon 5430 (quadcore).  We are looking to add a few boxes to the cluster, and we will most likely go with the HP DL380 G7 beings are current servers are almost two years now.  G7 will always have Xeon processors, but they will certainly have higher clock speeds to this processor will not match exactly.  In my view, that this used to be a problem in the past, when he came to VM vMotioning fast between the two different cpu.  My question is, is this even a question?  If I stay within the Intel Xeon family, I'm ok for vmotion between two different cpu?  The same of course, brand just diffenrent speeds and possibly different number of hearts.

  Thank you

  -scott

  You may need to activate CVS for vMotion work

  http://KB.VMware.com/kb/1003212

• Intel Xeon 54xx vmotion compatibility

  Hello.

  If I understand correctly - vmotion on same family CPU should work without problem.

  We got 3 nodes with Xeon 5410 and 1 node with Xeon 5430.

  VMotion of 5410-5430 work is good.

  But it works of 5430 to 5410 incompatibility NX/XD.

  Hide allows a flag NX/XD, but he isn't very good resolution for us.

  question 2:

  (1) is on same family vmotion CPU should work without any problem?

  (2) what do we lose if disable NX/XD indicator on each virtual machine?

  (3) the concealment of NX/XD is better or worse then VCA?

  NX/XD is only a function of the CPU, but there are others (like SSE).

  So the good solution is VCA at the level of the cluster or CPUID mask at the virtual machine level.

  I suggest that the VCA solution is very simple to implement.

  Create a new cluster empty, enable CVS, move each ESX in the new cluster (the ESX must be in maintenance mode).

  See also: http://kb.vmware.com/kb/1005764

  André

• Someone at - it a processors for VMotion compatibility table.

  I have a bunch of two nodes and try to consolidate this number up to 3 or 4 knots, but I need to try to understand what are coincident with what processors. VMware has a chart, but for the life of me I can't find. I have HP and IBM blades and standard server systems. with a slew of old and new processors. Looking for a way to determine if I can match processors even if they match 100%. For example

  HP ProLiant DL585 AMD Opteron Processor 848 G1, I can match with a

  HP ProLiant DL585 G1 AMD Opteron Processor 852

  Without masking of Vmotion and CPU still work.

  Thanks in advance!

  The HP ftp://ftp.compaq.com/pub/products/servers/vmware/vmotion.pdf

  Also check Opscheck.  http://www.vwire.com/free-tools/opscheck

  VMware http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1003212 link

• Sanity Check: Hardware compatibility: vMotion/CPU/VCA etc.

  Hi all

  We currently have a DRS cluster with 6 hosts Dell Poweredge R610 with Intel Xeon 5540 or 5530 processors which, according to article KB (http://kb.vmware.com/kb/1991) are in Group D for the vMotion compatibility. (Nehalem-EP)

  I want to add new hosts to the cluster and try again Dell R620s. These have Xeon CPU E5-2640. I can't find an article with the same level of detail for the new processors. The compatibility guide Vmware tells me that it is a Sandy bridge processor?

  
  

  If I add hosts with newer processors to the cluster, be they work? Or do I have to turn on some sort of CVS mode?

  
  

  If I read this article (KB VMware: best vMotion compatibility (EVC) processor support ) he gives to think that I would need to market the VCA Level2 (Nehalem). This would be 'disable' have the CPU features in the new host beyond what former processors... But what happens in 'x' time of years when all guests have disappeared - presumbaly I can then disable compatibility EVC mode so that all the features of the CPU are presented? This would have a negative impact on existing virtual machines?

  
  

  Please could someone health mental check me or point me in the direction of something to reassure me?

  
  

  Thanks in advance
  

  
  

  
  

  
  

  NB. Currently on vSphere 4.0, but the upgrade to 5/5.1 soon.

  
  

  
  

  I suppose that once the VCA mode is activated, it will always be equal to the level of the 'down' (older?) (In this case Nehalem) CPU level up to what the last host with Nehalem processors is removed from the cluster.

  Yes, that's correct.

• vMotion works between HP DL380 G7 and the Gen9

  Hi all

  VMotion I would like to know how working with HP DL380 G7 HP DL380 Gen9?

  Can someone help me?

  vMotion between this two servers:

  HP DL380 G7:

  Intel Xeon E5649

  Embedded NIC 4x1GbE

  + NC364T PCI Express Gigabit QuadPort

  HP DL380 Gen9:

  Intel Xeon E5-2650v3

  Embedded NIC 4x1GbE

  + 10 GB 2-port 10GBASE-T 533FLR-t HP FlexFabric

  Can someone help me?

  I would be very grateful
  

  Ralf
  

  The G7 has a CPU of generation Westmere, the Gen9 has a generation of Haswell CPU.

  vMotion requires that you have the same subset of games of CPU instructions and common on the source and destination of the CPU and active features in the server BIOS.

  This means that in your case:

  You will be able to vMotion virtual machine that has been powered on the host of the G7 (VM runs with Westmere instructions) for the Gen9 and so (but only if you don't re - power cycled the VM on the host G9).

  But you will not be able to vMotion virtual machine that has been powered - we on the Gen9 host (VM runs with Haswell instructions) to the host of the G7 most old car is missing these more recent CPU instruction sets.

  VCA comes here. By activating EVC on the common cluster with the generation of CPU down (in your case Westmere), all guests will present only these instruction sets to virtual machines when they are powered - on, which makes possible dynamic migration through the different physical CPU generations.

  See the following articles for more information about CVS:

  VMware KB: Enhanced vMotion compatibility (EVC) support processor

  VMware KB: EVC and CPU compatibility FAQ

  Alternatively you could manually hide CPU instructions by VM - with advanced options if you don't have a source host and destination in the same cluster, but it is a tedious task and I would not recommend it.

• Quick vMotioning problem between two servers HP BL460c Gen 9 when EVC enabled

  I have two HP BL460c Gen 9 blades configured exactly the same thing with 2 x Intel XEON E5-2660 v3 processors in each of them. Both running the same version ROM (I36 06/05/2015) and running the same version of ESXi (5.0.0 build 2509828). They are managed by a Server Build 2656067 vCenter 5.0.0.

  When I configure these two servers in a cluster with EVC disabled I am able to vMotion between them. However, if I activate the Intel EVC modes so I am unable to vMotion between these two identical servers.  Here is an example of the message that I get when I updated Westmere VCA mode

  Host CPU is not compatible with the requirements of the virtual machine to CPUID level 0 x 1 'ecx' register

  Bits of the host: 0000:0010:1001:1000:0010:0010:0000:0011

  Required: x 110: x01x:11 x 1: 1xx0:xx11:xx1x:xxxx:xx11

  Inconsistency detected for these features:

  * General incompatibilities

  If I disable CVS, then I can vMotion VMs between them.

  I wanted to add these hosts to an existing cluster configured with EVC Westmere mode so that I was able to vMotion between old and new guests, but was unable to vMotion VMs off the new hosts, even if I tried to vMotion to another new host.

  Configure a new cluster with only these two new hosts to so I could experiment. I can only vMotion between them if CVS is disabled. I cannot further increase the VCA mode on this new cluster, for example of Westmere to Sandy Bridge then I have virtual machines under tension within the cluster. For example: I put the VCA mode at Westmere, feeding on a virtual computer, when I go to change the CVS to Sandy Bridge mode I get the following message, I should be able to increase the VCA mode but may not lower it

  The cluster cannot be configured with the selected Enhanced vMotion

  Compatibility mode; The CPU features disabled by this mode may be currently in use

  by slot voltage or suspension of the virtual machines in the cluster.

  I get this message even if I try to set the VCA mode at the same level, that it is already.

  Anyone got any ideas on how to solve this problem?

  Hello

  Seems, your CPU supports 5.0 ESXi and vCenter 5.0, you must upgrade your vSphere vSphere 6.x for the VCA.

  See the links below and also compatibility VCA matrix attached:

  VMware KB: Enhanced vMotion compatibility (EVC) support processor

  Intel CPU VCA Matrix (Enhanced VMware vMotion compatibility) | Virten.NET