question of VMotion

Similar Questions

• question of vMotion iSCSI and jumbo frames

  Hello

  I have a cluster ESXi 4.1 using vCenter and a SAN MD3200i.  I'll do an upgrade to optimize the installation, which includes the installation of four NIC ports in hosts that will be used for iSCSI.  I struggle to enable frames or not, but if I do, I just want to do for the iSCSI, at least for now.  Currently, the maps iSCSI network on the hosts and the MD3200 iSCSI connections are connected to two switches separated, although I have seven other switches in the building connected to the PC, printers, etc.  What I only turn frames on two switches that iSCSI is connected, or do I have to enable frames on all my switches?  There is a Dell 2724 and eight 6224Ps of Dell.  ISCSI is connected to the 2724 and one from the 6224Ps.

  The two switches that are connected to the iSCSI ports are not dedicated iSCSI switches; they have other devices on them, but I can only enable the frames extended globally on the switch.  Would there be any problem allowing the frames extended on the switches, otherwise all connected devices are configured for them?

  Another question about vMotion: I will create four ports on each host for iSCSI vmkernel.  Currently, there is also a port configuration vmkernel for traffic management and vMotion.  Is it possible to set up each of the four iSCSI for vMotion vmkernel channels, or should I leave it configured on the port of vmkernel management?

  Thank you!

  Sure. If you're going to enable Jumbo frames, you need to have dedicated switches for that, or a switch that may have different units MTU on their ports.

• question of vMotion and storage vMotion

  I have everything set, UCS 5108, ESXi host, VMs, I don't have a SAN connection yet... My question is if I can enable vMotion? Let's say I have a cluster in vCenter, within this group, I have attached two ESXi host, win2008 VM in an ESXi and running, I can migrate (using vMotion) as win2008 VM to an another ESXi without connection SAN?

  How storage vMotion to an ESXi host hardrive to an another ESXi host hardrive? Is this possible?

  Note: I have not connection SAN in this configuration

  One of the requirements for vMotion is shared storage that would allow visibility between source and destination ESXi hosts. (SAN, iSCSI or NFS).

  http://www.VMware.com/PDF/vSphere4/R41/vsp_41_dc_admin_guide.PDF

  pages 210 to 215

  You can use OpenFiler as an iSCSI for lab tests SAN

  http://www.Openfiler.com/community/download/

  Thank you

  Zouheir

• Question about Vmotion

  Guys,

  I finally had time to raise a second cheap esxi host today.  I installed vShere 4.  The hosts are always 3.5.

  I tried vmotion as part of my test, but I couldn't make it work.  There are two questions:

  First issue - incompatible processor.  I followed KB 1993 and tried to hide "NX/XD.  A host has a celeron 1.6 and the second host has a core quad (q9550).  I'll probably have to replace the host with the celeron cpu.

  Second question - I get this error "currently connected NIC 'NIC 1' uses 'Mtrac' network, whi is not accessible."

  I am interested in getting this fixed.  Comes from the machine, I tried to move the "Mtrac" network adapter.

  TIA,

  TNT

  To answer your questions:

  1. Architecture of the Celereon and q955 chips you use is so dramatically different that I don't think you'll ever get to work for vMotion - VCA is really aim clients whoare purchase processors in the same family or relatively close to the generations.

  2. If networking on the ESX servers must be the same - in other words your VM has been connected to the virtual MAchine port group called Mtrac on the source host and on the other host there was no virtual machine port group with this name-

  If you find this or any other answer useful please consider awarding points marking the answer correct or useful

• questions of vMotion

  Problems making a vMotion, someone saw in the errors below?

  Migration [-1062724889:1456753412128804] unable to connect to the remote host < 10.0.0.17 > < 192.168.26.228 > host: timeout.

  vMotion migration [-1062724889:1456753412128804] vMotion migration [-1062724889:1456753412128804] thread flow cannot connect to the remote host < 10.0.0.17 >: host ESX The failed to connect on the VMotion network

  VMotion migration failed because the ESX hosts were not able to connect to the network for vMotion. Check network vMotion and physical network configuration settings.

  vMotion migration [-1062724889:1456753412128804] cannot read streams keepalive: Connection closed by remote host, probably due to timeout

  Failed to wait for data. Error 195887167. Connection closed by remote host, probably due to delay.

  Hello

  There is a bad vmk configuration in your cluster.

  Migration [-1062724889:1456753412128804] unable to connect to the remote host <10.0.0.17>host <192.168.26.228>: timeout.

  The cabability of vMotion is enabled on vmKernels in different subnets.

  One of the guests a vMotion enabled on the VMK with the following IP address: 10.0.0.17

  The second host a vMotion enabled on the VMK with an IP address from the 192.168.26.0 subnet.

  I think that your hosts have several VMKs. Please enable vMotion only on VMKs who are in the same subnet (10.0.0.0 or 192.168.26.0)

  Greetings

  Falk

• Basic question Storage VMotion

  Hello friends,

  I'm new to ESX and learning as well as my friend.

  We have a lab test... configuration in which we have 2 servers now., 1 HP 4 GB of RAM, an enormous amount of processor P3 HARD drive. We run more vCenter server as a virtual machine and some VM is running... Now we got a new server Dell with 8 GB of RAM, dual P4 Q-core... and we want to move those VMS to Dell.

  For this I'll have to install ESX on the new server and put it in VCenter.

  The two servers are not on a dedicated storage, I don't know if I'll be able to use SVMotion to transfer these VM to the new server.

  Is this Possible?

  Thanks for your quick responses of friends.

  Storage VMotion is a transparent in another data store migration while the virtual machine still works. I suppose you have no shared storage, so you can only do cold migration, but it would be very simple for you.

  Select the virtual machines you want to migrate, feed their stop and "migrate." Select "change host and data store.

  The only problem is to migrate vCenter. But there is one thing - hot-clone, you can rather than migration. Old vCenter power off and turn it on again.

  ---

  VCP MCSA, MCTS Hyper-V, VMware vExpert 2009, 3/4

  http://blog.vadmin.ru

• Problem with hard stop and guest OS - question of VMotion

  Hi all! I'm having a problem and I hope I can find help...

  Basically, we are in the middle of HA and VMotion test and we found that when we make a hard stop on one of our boxes of ESX 4 (simulating the loss of an ESX box), the guest operating system disconnects and stops on the ESX host that cut us off. He does VMotion off for another host ESX in our environment and then restarts the VM guest save... Anyone has any ideas of why it does this? It should be keep alive, no?

  I have install multiple ESX 3.5 environments and never had this problem and hoping maybe I am missing something in ESX 4.

  Thank you!

  Ed

  false, he did exactly as it was designed... the name chosen for HA is perhaps not the biggest.

  It should help you understanding between the HA and FT:

  http://www.VMware.com/products/VI/VC/HA.html

  www.VMware.com/PDF/vmware_ha_wp.pdf

  http://www.VMware.com/products/fault-tolerance/

  www.VMware.com/files/PDF/Resources/ft_virtualization_wp.pdf

  Essentially if you want continuous availability, without interruption, you need to implement VMware FT (Fault Tolerance) While HA, will try to minimize downtime as little as possible, but it's time to stop, as you saw.

  =========================================================================

  William Lam

  VMware vExpert 2009

  Scripts for VMware ESX/ESXi and resources at: http://engineering.ucsb.edu/~duonglt/vmware/

  repository scripts vGhetto

  VMware Code Central - Scripts/code samples for developers and administrators

  http://Twitter.com/lamw

  If you find this information useful, please give points to "correct" or "useful".

• Question about vMotion unable to migrate due to the incompatibility of SSE4.1

  Hi all

  We bought another HP BL480c G1 and he joined our cluster, running ESX Server 3.5 U3. First of all and then I realized that our supplier has sent a version with a Xeon E5440. Other guests also BL480c G1, uses slightly older Xeon E5345, which is apparently a difference family produced minor.

  This genereates following error message when you try to vMotion:

  "Impossible to migrate from esx1 to esx4. Host CPU is incomatible to the requirements of the virtual machine to CPUID level 0 x 1 'ecx' register .... Inconsistency detected for these characteristics: * SSE4.1. see the article 1993 for a possible solution.

  I tested a substitution of mask of vMotion (according to KB1993) on a test server and vMotion then works as expected. The substitution of masks is of course supported nor recommended because it can cause instability with vMotion.

  Someone at - he found a solution support around this issue? Or has anyone ever encountered problems with the substitution?

  I found nothing in the BIOS to disable SSE4.1.

  Please post your solutions, workarounds and experiences.

  Thank you

  Björn Johansson

  Hi Bjorn,

  It's good to know that the E5345 comes with FlexMigration, Intel you need to update their documentation.

  If I understand correctly FlexMotion is supported by VMware for 3.5 Update 2:

  _______________________________________

  Best compatibility - VMotion Simplifies VMotion compatibility through the generations of CPU issues. Improved compatibility VMotion (CVS) automatically configure the processors in the server with Intel FlexMigration or AMD - V extended Migration technologies to be compatible with the old servers. After that EVC is enabled for a cluster in the VirtualCenter inventory, all the hosts in this cluster are configured to ensure compatibility of the CPU for VMotion. VirtualCenter does not allow the addition of hosts that cannot be automatically configured to be compatible with those already in the EVC cluster.

  REF: http://www.vmware.com/support/vi3/doc/vi3_esx35u2_vc25u2_rel_notes.html#whatsnew

  _____________________________________________________

  recommended is another story, I think VMware are constantly updating their software to include a wider range of supported hardware, but in an ideal world, we should try and keep the material the same to ensure 100% compatibility.

  Ciaran

  If you found this information useful, please consider awarding points to 'Correct' or 'useful '. Thank you!

• Regarding vSphere VCA and vMotion

  Hi all

  I have several questions about vMotion and VCA, can anyone help?

  1. If I mix several types of CPU (from the same supplier of CPUS) in a vSphere without EVC cluster active, what will happen? can I vMotion VM on the host?

  2. I can vMotion VM Cluster with older CPU for the Cluster with more recent CPU? Assume that CVS is not activated on the two groups.

  3. can I vMotion VM Cluster with older CPU for the Cluster with more recent CPU? Assume that CVS is not enabled on the source cluster, but active on the destination Cluster.

  4. I can vMotion VM Cluster with older CPU for the Cluster with more recent CPU? Suppose that EVC is enabled on the source cluster, but not active on the destination Cluster.

  5 can I vMotion of virtual machine of a stand-alone ESXi host on an active EVC cluster? Assume that the CPU is the same.

  6 the KB "EVC and CPU compatibility FAQ" below, if we disable CVS on a cluster, the virtual machine can only be migrated to hosts with CPU even or more.

  Why virtual machines is only able to move to other ESX/ESXi hosts that are in the same generation of CPU or more? It's in front of my knowledge.

  VMware KB: EVC and CPU compatibility FAQ

  What is the impact on vSphere features of the Cluster when I turn off the CVS mode?

  To turn off the CVS on a cluster mode, it affects vSphere Cluster features in the following ways:

  • vSphere HA (High availability): vSphere HA is not affected because of the cyclic power failover virtual machines when you start on a new host. This allows the VM picking up the new ID CPU and it allows to start without problem
  • vSphere DRS (Distributed Resource Scheduler):
    • vMotion: virtual machines is only able to move to other ESX/ESXi hosts that are in the same generation of CPU or more. If the DRS is configured for fully automated, this can result in virtual machines, eventually migrating to hosts on the cluster with the generation of CPU more old where they cannot be moved via vMotion on different hosts with a newer processor generation.
    • Storage vMotion: virtual machines are able to be moved to Storage vMotion with EVC mode disabled in a cluster
  • Location of the pagefile: it is not affected.

  Thank you.

  1. If I mix several types of CPU (from the same supplier of CPUS) in a vSphere without EVC cluster active, what will happen? can I vMotion VM on the host?

  (a) you very well can vMotion virtual computers between the hosts with identical processors within the cluster.

  (b) for vMotions on different hosts, it depends on CPU instruction set parity and orientation, i.e. the older generation-> new generation or vice versa.

  Consider the following: when a VM is turned on at the start, it is presented in UC sets from the physical host, where it has been turned on. It must keep these settings until the virtual machine is turned off, any host it is migrated to in the meantime. Therefore, as long as a host provides these CPU instruction sets, it can be vMotioned it. Further instructions on new hosts games is irrelevant for this and just hidden-away of the guest. So old-> new should be fine, but new-> old most likely will not work because the virtual machine works with games of additional CPU instructions that only is simply not supported by the older physical processor.

  2. I can vMotion VM Cluster with older CPU for the Cluster with more recent CPU? Assume that CVS is not activated on the two groups.

  Yes, generally vMotion shall function in older generations of CPU to the most recent, the same common CPU instruction sets are supported by the destination CPU host and enabled in the BIOS.

  3. can I vMotion VM Cluster with older CPU for the Cluster with more recent CPU? Assume that CVS is not enabled on the source cluster, but active on the destination Cluster.

  4. I can vMotion VM Cluster with older CPU for the Cluster with more recent CPU? Suppose that EVC is enabled on the source cluster, but not active on the destination Cluster.

  Yes, the same general vMotion as explained above requirements. If CVS is enabled on any, both or a cluster does not matter (of course provided a configured VCA level is not reverse the physical hardware capabilities 'new' and 'old').

  5 can I vMotion of virtual machine of a stand-alone ESXi host on an active EVC cluster? Assume that the CPU is the same.

  Yes, the same general vMotion as explained above requirements. A stand-alone host is exactly the same thing treated as a non - active EVC cluster.

• Single network or Multi vMotion Nic card

  Here are our current design for our soon vSphere 5.1 deployment

  There has a been a good bit of internal discussions on whether to use a single 10 GB for vMotion network adapter or use two NICs 10 GB for vMotion

  Most of the debate has been around "isolate" the vMotion traffic and makes it as localized as possible

  We all have the vMotion traffic is a vlan separate, vlan127 you can see in our design

  The big question becomes exactly where will the vMotion traffic? What switches/links it really go?

  Is this correct?

  1. If we start with a vMotion nic, then once that Vmotion begins traffic will be generated from the host lose the virtual machine and the host wins the virtual machine. In this scenario, traffic will cross a BNT switch. This leads to two conclusions
     
     
     1. Traffic is never as far away as the nucleus of Juniper
        
     2. vlan127 (vMotion) didn't need to be part of the trunk, go to the heart of Juniper to the TNB
        
  2. If we go with two NICs of vMotion, then the two 10GB network adapters might be involved in vMotion. This means that vMotion traffic between two hosts ESXi could hit a switch BNT, browse the battery connections (two 10 GB between the BNTs connections) and go to another host via a network card. GB 10 it has also led to two conclusions:
     
     1. Traffic is never as far away as the nucleus of Juniper. He remains isolated on a single switch BNT or moves between BNT switches through the two stack 10 GB connections
        
     2. vlan127 (vMotion) didn't need to be part of the trunk, go to the heart of Juniper to the TNB
        

  

  vMotion traffic is just unicast IP traffic (well good, except for some bug) between ESXi configured for vMotion, vmkernel ports if all goes well insulated in a non-routed layer 2 broadcast domain (VLAN). Simple as that. Considering that the traffic will cross physically regardless of the physical NIC is configured for the respective vmkernel ports. The path between the two is obviously depends on the layer 2 switching/STP infrastructure, which in your case would be just the blade chassis switches.

  Multi-NIC vMotion essentially implements several independent streams between different IP addresses and MAC, belonging to the same host. Consider the following:

  Host A and B with vmk1, using physical vmnic1, connected to physical pSwitch1 and vmk2, using vmnic2, connected to pSwitch2. The two pSwitches directly the trunk the VLAN vMotion between them.

  If the two hosts have only vmk1 is enabled for vMotion, traffic will never pass by pSwitch1. If host B has only vmk2 enabled for vMotion or you switch uplink, it'll pass the two pSwitches.

  Now, if you enable the two interfaces for vMotion vmkernel, it is difficult to say how the hosts decide what vmk connects to that. You may find yourself going through the two pSwitches for the two water courses, or you're lucky and you end up with source and destination interfaces that reside on the same pSwitch. I don't know how ESXi decides the pairings, this article seems to suggest it's done deterministically for that in a similar configuration, the same key vmk would connect between them:

  http://www.yellow-bricks.com/2011/12/14/multi-NIC-VMotion-how-does-it-work/

  Whatever the case, unless you need to other hosts on different switches, connected through your hearts only, to be able to vMotion between hosts, there no need at all to mark the vMotion VLANS on your links between chassis and Core switches.

  You see, your question of vMotion Multi-NIC is completely unrelated to this.

  If we start with a vMotion nic, then once that Vmotion begins traffic will be generated from the host lose the virtual machine and the host wins the virtual machine. In this scenario, traffic will cross a BNT switch. This leads to two conclusions

  1. Traffic is never as far away as the nucleus of Juniper
  2. vlan127 (vMotion) didn't need to be part of the trunk, go to the heart of Juniper to the TNB

  1. Yes.

  2. Yes.

  Circulation * could * crosses both switches BNT, according to what I explained above.

  If we go with two NICs of vMotion, then the two 10GB network adapters might be involved in vMotion. This means that vMotion traffic between two hosts ESXi could hit a switch BNT, browse the battery connections (two 10 GB between the BNTs connections) and go to another host via a network card. GB 10 it has also led to two conclusions:

  1. Traffic is never as far away as the nucleus of Juniper. He remains isolated on a single switch BNT or moves between BNT switches through the two stack 10 GB connections
  2. vlan127 (vMotion) didn't need to be part of the trunk, go to the heart of Juniper to the TNB

  1.Yes.

  2.Yes.

  Personally, I'd go with Multi-NIC vMotion use NIOC with soft actions in your config file.

• vMotion between versions and licenses

  I have a question about vMotion in vSphere 4.1.  It is primarily on licenses, as I know technically what I'm asking, it's doable.

  With the inclusion of vMotion in Standard licenses, can run a mixed environment (eg. Enterprise and Standard licenses) and vMotion between hosts with different licenses?

  For simplicity, assume that the environment is running 4.1.  Although if you know, could you please indicate if it would work between versions (eg. between 3.5 and 4.1 or 4.0 and 4.1).

  Thank you.

  
  
  The answer you are looking for is + 5.23.2

  Yes.  As long as you have licenses vMotion on all host ESX (i), and you meet the requirements of vMotion (shared storage, CPU compatibility, network, etc.) whereas there should be no problem.  Remember that if a mixed environment of VI3 and vSphere4 hosting, do not upgrade the comment tools.

• vMotion - Compatible processor Updates - HP/Intel

  The last update I could find at HP was dated from 01/07/2008.

  We have a Xeon CPU E5440 DL380G5 running.

  My question is vMotion will work with this server and a DL380G6 with Xeon 5500 series processors?

  Thank you.

  vMotion and HA will be, once you have set the correct level of EVC. FT is not working properly. Compatibility info... more FT

  VMware VCP4

  Review the allocation of points for "useful" or "right" answers.

• VMotion Port on the host

  I have just a very quick question regarding vmotion on the host port.  I need to change the IP address on one of them and was curious to know if this is something that can be done on the fly.  If I put DRS on manual I am able to change the address of the port without disrupting things?  Any help is appreciated.  Thank you!

  Hello

  Yep, everything you need to do is value DRs manual then go to settings and change the default gateway and the ip address and vlan if need be the vmotion port

  If you have found this or other useful information, please consider awarding points to 'Correct' or 'useful '.

  Gregg Robertson, VCP3, 4, MCSE, MCSA, MCTS, MCITP

• VMotion using on OpenFiler iSCSI LUNS

  Does anyone know if it is possible to 'share' a logic unit number on an OpenFiler iSCSI target so I can use VMotion? So far, I can't my second ESX server to connect to the LUN.

  Should not be a problem,

  Follow this: http://www.petri.co.il/connect-vmware-esx-server-iscsi-san-openfiler.htm

  of http://superuser.com/questions/101662/vmotion-using-iscsi-lun-on-openfiler

  StarWind software developer

  www.starwindsoftware.com

• Make VMOTION on a different server with different, example HP and DELL

  A colleague asked me a strange question of VMOTION, you can go,

  You have HP DL380 G5 and a DELL Power edge 1620 (or anything) in a cluster as ESX host. Now if I want to use VMOTION between these two servers, should what precautions I take?

  Please let me know because I have never tried as we all HP inside the VC as ESX Server.

  Thank you

  Anky

  There is no vMotioning fast problem between different manufacturers of servers - Andre's notes it is critical CPU compatibility - so if Dell and HP servers have the same processor (or family) that vmotion will work

  If you find this or any other answer useful please consider awarding points marking the answer correct or useful