VMotion between several hosts

Similar Questions

• VMotion between 2 Hosts with different processors

  Hallo,

  I have a server in my homelab I use for studies of VMsphere and I want to get a second machine to test advanced features such as HA, Vmotion etc.

  My first server has a map of X9SCM-9 with processor Xeon E3-1230V2 (Ivy Bridge). I am currently running ESX 5.0 U2 on it.

  I was counting on obtaining of material quality for the second host consumers because I don't want to spend a lot on it, so I thought that I need any CPU generation Ivy Bridge.

  I tested today with a second machine with a Pentium G2020 Ivy Bridge, but when I try to Vmotion he says "the virtual machine requires physical features that are not available or disabled on the host... ».

  So I figure there must be a difference in architecture regardless of the CPU beeing an Ivy Bridge CPU.

  When I try to activate CVS it just me are going to the 'Nehalem' Version so my virtual machines running on host 1 would not be able to use all the features of the CPU since the Xeon.

  So the question boils down to: what is the processor less which offer compatibility VCA L5?

  Or is there something else to consider in VMotion between two hosts with different processors?

  I got a shared storage, etc. of the same network configuration.

  Thank you

  Benjamin

  Hi Benjamin,

  For compatibility VCA L5 want to look at one of the following models, Intel CPU:

  • Ivy Bridge: Series E3-1200-v2
  • HASWELL

  I would recommend mental health that before rushing and a CPU purchase, check if a cheaper option would be, as Jon mentions in suppresss some fo the CPU compatibility checks so obviously, this is not desirable in a production environment, and must be applied in your study of VMware Lab to the home address.

  Hope this helps,

  Simon

  TechHead

  http://techhead.co

• vMotion between two hosts with different version?

  
  Hello

  Can I vMotion VM between two hosts with different version? For example, a virtual machine of esxi 6.0 5.5 esxi and esxi esxi 6.0 5.5 vMotion.

  Thank you.

  Yes, it will avoid you to move.

• can I vmotion between different host bus adapters

  Hello

  Just a quick question.

  I have 2 ESX servers.

  an ESX has a Qlogic and the other HBA, Emulex.

  can I make a storage between these servers ESX vmotion?

  Thank you.

  Don't forget virtualization virtualizes the physical storage - so as long as the HBAs connect to storage even as others have said there should be no vMotioning quick question.

• Having a problem with vmotion between two hosts with processors Intel E5640

  Hi all.

  We organize a group of 14 guests, each with ESX 4.0, build 261974 installed.

  They are managed through vCenter 4.0.0 and construction 258672, vSphere client 4.0.0 builf 258672.

  The hosts are blades from IBM, in a BladecenterH.

  Some of the blades are older model HS21 (type 7995) with processors Intel Xeon E5440.

  The rest of the blades are more recent model HS22V (type 7871) with processors Intel Xeon E5640.

  We are currently replacing old HS21 blades with more the HS22 blades, so we just bought 7 HS22s, all with the same Intel E5640 processors located in the blades currently in service. One of the things that this transition will happen for us is allowing us to have the same processor type in all of our blades and remove vMotion compatibility problems we had in the past. We were unable to turn on CVS, because we would have had to shut down a cluster of virtual machines on the latest hosts and could not take this kind of failure. We will turn VCA after that.

  Here's the question:

  We just installed the first new knives, and when turn on us and try to vMotion VMs to it, it fails. He gives us the error standard vMotion on CPU register incompatibilities, and that we should read kb1993. The thing is, they all have the same processor. Same identifier type, same everything, yet for some reason vCenter is convinced they are incompatible. We checked things in BIOS, and they are all the same.

  We are ideas, other than the new knives have a later rev BIOS than the old ones.

  Any thoughts?

  Thank you!

  -Tim

  According to the missing pieces, http://www-947.ibm.com/support/entry/portal/docdisplay?lndocid=MIGR-5086963 should help you solve the problem.

  André

• VMotion between 2 remote hosts on the same site

  Hey everybody. I am new to a company that owns 2 Server vCenter, one in each data center, and we have a few servers standa-only (no not a cluster) in some places.

  All hosts are registered with several Enterprise. Let me draw the locations, you will have an idea:

  VCenter1

  -Datacenter1 (remote domain controller 01)

  * Host1

  ...

  * Host15

  2 VCenter
  

  -Datacenter2 (remote domain controller 01)

  * Host16

  ...

  * Host30

  -Data Center 3 (LAN)

  * HostLocal1

  * HostLocal2

  That make sense, as I have 15 guests on data center 1 and 2. We use 2 VCenter to manage the HostLocal1 and HostLocal2, but we don't group them together and we do not have vMotion among them, because all vMotion traffic must go to vCenter, then on the second host, is this right? Is there a way to prevent this?

  Let me rephrase: VMotion traffic would be like this:

  HostLocal1-> VCenter 2-> HostLocal2

  Or:

  HostLocal1-> HostLocal2.

  Wrote this question down make realize me that my hypothesis is incorrect, vMotion traffic has nothing to do with VCenter, activities stems from these 2 servers. Can anyone confirm?

  Thank you very much for your time.

  We use 2 VCenter to manage the HostLocal1 and HostLocal2, but we don't group them together and we do not have vMotion among them, because all vMotion traffic must go to vCenter, then on the second host, is this right? Is there a way to prevent this?

  Let me rephrase: VMotion traffic would be like this:

  HostLocal1--> VCenter 2---> HostLocal2

  Or:

  HostLocal1--> HostLocal2.

  vMotion traffic runs only between the source and the destination host ESX (i). The assumption that the traffic flows via vCenter's vMotion is downright bad. vCenter is simply required to initiate/control the vMotion between the hosts, but it is completely left out the data transferred between the host to move the virtual machine.

  The assumption that you need a cluster for vMotion object or clustering automatically implies vMotion won't as well.

• Storage shared between cluster hosts

  Hello

  I have a number of hosts managed under a VC server clusters. I want to downgrade the ESX 3.5 cluster and spend all my virtual machines to my vSphere cluster. I intend to move the storage currently used by ESX 3.5 clusters as well.

  Is this OK (or supported) or even possible for me to do the following?

  1. attach the storage used by the cluster cluster vSphere ESX 3.5 (so it is folded in TWO clusters).

  2. the servers from ESX3.5 to vSphere vMotion cluster cluster.

  3. turn off the cluster of ESX 3.5.

  I guess it boils down to two questions.

  1. can you be shared between host cluster storage two?

  2. If you can, is it possible to vMotion between cluster hosts, assuming that all the vMotion compatibility checks are successful?

  If the above is not possible, I'm guessing that a V2V of VMS ESX 3.5 would be the way to go, and I have to find new storage for the cluster of vSphere.

  Thank you

  G

  Hello

  If you have a SAN vSphere-taking in charge, so there is no problem.

  According to the CRA on your 3.5/vSphere ESX CPU hosts, you might have problems with storage vmotion/vmotion. One way would be to enable CVS, however requiring all virtual machines to be powered off.

  But present the LUN 3.5 4.x guests and make a svmotion is not a problem if you have taken care of storage. (www.vmware.com/go/hcl).

  Then you can just vmotion (if you do not have CPU incompatibility) virtual machines to new hosts, or stop and move.

  VCP3/VCP4/VSP/VTSP/MCTS: Virtualization

• vMotion (without shared storage) between two hosts with different vSwitches standard s VM

  I can VM vMotion (without shared storage) between two hosts with different vSwitches standard? The vSwitches on these two hosts have different names and number of NIC, but have the same name of portgroup.

  
  Thank you.

  Yes, you can in a Storage VMotion to one Esxi to another with no shared storage...

  It is important the portgroup bears the same name... This is the reference for the VM...

• As part of the SAR cert is to have a NW separated between ESXi host required for VMotion or is it OK to use IP for VMotion management, in the execution of Certification tests.

  As part of the SAR cert is "have a NW/dedicated separate between hosts ESXi (on which we GOS) mandatory for VMotion or is - OK to use IP for VMotion management in the execution of Certification tests.»

  Note that the verification passed Test when you use management IP for Vmotion and without a dedicated connection to NW between ESXi hosts.

  Separate dedicated network interface cards preferred. No problem with the test after this change case.

• Can we do vmotion between hosts with load balancing in network cards grouping different strategy.

  Hello

  We are implementin new host in our Infra and do some vmotions between different groups. A group a host with balancing 'route based on IP hash. " Can we do Vmotion to another cluster where the hosts have different load balancing policies. In addition, if we change the policy on new hosts in furture of load balancing is loss of downtime or a package?

  Kind regards

  Vikram Kumar

  First of all, no problem from VMs one ESX to another, they use different political Multipathing.

  Second, if you use IP hash, it means you are using etherchannel (or LACP) on the physical layer - configuration/cancellation of the configuration that almost always require that the uplinks are not used by any VMs, so you have time to synchronize the physical and virtual configuration. It is not a time out, but you need to plan accordingly - all depends on your physical network capacity.

• Storage vMotion issue License - license of moving between ESX Hosts 4.1?

  I have a question about Storage vMotion with ESX 4.1 license.

  One of my environments ESX 3.5 existing consists of 10 ESX 3.5 hosts - 8 ESX 3.5 servers Standard and 2 ESX 3.5 Enterprise servers.  I use a centralized license server (I think that's the correct term).

  I found that I can "move" the vMotion (and vMotion) Storage capacity of two of my 10 servers that only two of them are enabled for vMotion, both.  I do this by topic under VI Client-> select the host ESX-> Configuration-> network-> properties-> VMkernel-> Edit-> toggle the box "VMotion" activated-> OK.   I guess that by doing this, that I'm actually just spend my licenses 'ESX Enterprise' between the hosts.

  Be able to run Storage vMotion on one or two guests at a time is a lot for a few times a year I need to reconfigure my back-end storage.

  Two Questions:

  1. this use is technically legal in a perspective of VMware licenses?

  2. now, I'm looking to upgrade to ESX 4.1 and wonder if I'll be able to keep doing this?  I have read that ESX 4.x got rid of the centralized server license model, so not sure if I could 'move' licenses around like that... In fact since vMotion is now included in Standard Edition, I guess I could 'pull out' through a license only one ESX Enterprise server in order to obtain the license of storage vMotion.

  I let my support/subscription lapse for as long it is cheaper to purchase new licenses rather than paying for support costs with retroactive effect on my existing licenses.   The price difference between Standard and Enterprise is large (3 times the cost) that I don't think I can swing is business licenses for all of my guests past the bean counters, where the reason for this post.

  Reflections and comments?

  Each host has a license key number. You can apply a new license key to a host, and it is immediately activated. I guess you would be technically violate licensing for seconds as a license number was recorded at two hosts. There is a place in the vSphere client to "assign a new license key to this host. When a license key has been assigned, it remains as a choice, then you can simply choose the functionality licensed one and below the other.

• vMotion between a Quad Core computer host and a hexacore

  Is it possible to vmotion between a double x 5570 and double a 5670 x server?

  Thank you!

  Hello.

  Yes, you need to activate the VCA mode as described in KB 1003212 for the 5570 and 5670 to work together.  Regardless of the number of cores.

  Good luck!

• Cannot migrate between identical hosts in the same cluster - CPUID level 0 x 1 'ecx' inconsistency

  I have problems of migration of virtual machines between hosts that are identical. They are the new BL 6 490 HP servers with a pair of processors x 5570 @ 2.93 Ghz and I activated the "Intel Xeon 45nm Core 2" EVC mode, there is also two other cluster hosts (HP BL480 G1 with a pair of processors E5430 @ 2 .66GHz).

  I ESX4, vCenter4 and all the latest firmware on all devices.

  When I try to migrate an identical to another or to other hosts host machines, I get the following error;

  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:0000:0000:0000:0010:0010:0000:0001

  Required: 1000:0000:0000:000 x: xxx0:0x1x:xxx0:x 001

  Inconsistency detected for these features:

  • General incompatibilities; see section 1993 of possible solutions.

  I have consulted the Article KB http://kb.vmware.com/kb/1993 and the document referred to Sub http://kb.vmware.com/kb/1008315

  All affected machines are hardware VM 7, the last VMTools are installed, have not RDM or nonstandard hardware, there is no floppy disk or CD drive mapped drive

  I tried to change such CPUID mask specified in the document 1008315, but this did not help. I also tried to change the mask of CPUID for ecx to be 0-

  ---

  -

  ---

  -

  ---

  -

  ---

  -

  ---

  -

  ---

  -

  ---

  and that did not help.

  I turned off a VM to ensure that he had picked up the CVS settings. I am able to vMotion, virtual machine when it is off, but this is not enough as we have several "stuck" on the same host machine and cannot be moved by the DRS or manually.

  Virtual machines are Windows 2003 (R2, SP2, x 32). worked well before vMotion on all hosts. Other identical machines from the same model are fast vMotioning very well, and when we were on ESX 3.5u2 wasn't a problem.

  Can someone advise me on how I can diagnose and fix this problem?

  I had the same problem after migrating from ESX 3.5 to V4.0 with almost the same HW-Configuration you have. (BL490c and BL480c). But in my environment, the article you mentioned has brought the solution:

  To manually remove the CPUID masks using the VI Client:

  1 power off the virtual machine.

  2 - Click on the VM, then click on change settings.

  3. click on the Options tab.

  4. Select CPUID mask under Advanced.

  5. click on advanced.

  6. click Reset all to default.

  7. click on OK.

  8. click on OK.

  9. start the virtual machine and migrate.

  Have you actually tried it? The default mask is OK, there is no problem with it in your environment, as I have said already, I have the same hardware as you.

  Paul

• VMotion fails with «Host CPU is incompatible...» »

  After setting our vCenter 4 / environment laboratory of ESX 4 with two hosts ESX 4, I added two of our ESX 3.5 hosts in vCenter 4 managed environment. These 3.5 hosts had 10 Windows 2003 EE 64-bit Server identical virtual machines, running on them. I then used storage vMotion (migration) to move all ten VMs over a LUN share by the ESX 4 hosts and migrate them while they are now running on the ESX 4 hosts.  They came over the fine. Activated fine. Ran very well. vMotioned back between the two ESX 4 hosts fine.

  I then put off 5 of the 10 computers virtual and enhanced their virtual hardware version 4 to version 7. I have them fed up.

  I have also built several new virtual machines on the host ESX 4 from scratch using the same process and the same image that I used to create virtual machines hosted on ESX 3.5 hosts. So far so good.  Can I vMotion between all 5 virtual machines that are still at version 4 guests two ESX 4 and I can vMotion new computers virtual 7 built on ESX4 host, but if I try to vMotion of 5 virtual machines have been upgraded to version 7, I get the message below.

  Host CPU is incomaptible with the requirements of the virtual machine to CPUID level 0 x 1 register 'cex '.
  Bits of the host: 0000:0000:0000:0000:0010:0000:0001
  Required: 1000:0000:0000:000 x: x 10 xx10:0: xxx0:x 001
  Inconsistency detected for these features:
  * General incompatibilities; see section 1993 of possible solutions.

  I read the KB article referenced, but this is to overcome the problems with fast vMotioning between levels or different processor types. These two hosts ESX 4 (10-esx-mp and mp-esx-11) are identical DL580 G5. It's only the improved VMs that fail to migrate.

  I stop each host ESX 4, restarted in the BIOS and set the option of VT processor on 'disable', of booted up the box, let it come completely up, then again, rebooted the box of ebb in BIOS and by setting the option VT back on 'enable '. It's not helping.

  Someone else has seen this?

  If you have identical CPU, then check the configuration of virtual machine (in the .vmx file) to see if there is an old CPUID mask value and simply remove them.

  Then again turn on the virtual machine.

  See also:

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

  André

• VMotion on two hosts

  We have two hosts and are currently using the same network/vswitch vmotion and vm management.

  I understand that it is best to separate the network for vmotion management.

  (1) may simply run a straight cable between two hosts?

  (2) should the vmotion switch be in a separate network?

  Based on the number of physical network interface cards in your host, instead of connecting the two hosts directly without switch, allows to isolate the vMotion traffic and management VLAN and given that you're going to use a VLAN different you will need a different subnet (network).