VC4.0 usable vmotion between esx 3.5 and esx 4.0?

Similar Questions

• vMotion between ESX 3.5 5.1 ESXi MAchines?

  Hi guys I need to know if possible to a Vmotion between ESX 3.5 s machines to ESXi 5.1?

  I hace 2 servers with ESX 2.5 I want to do the update to 4.1 and then to 5.1 hot, for that, I have 4 new esxi 5.1.

  Accoeding to http://partnerweb.vmware.com/comp_guide2/sim/interop_matrix.php? It is not possible because you cannot manage the ESX 3.5 with vCenter 5.1 - I advise to use VMware Converter to V2V virtual machines to the new environment of 6.1.

• vMotion between hosts 4 ESXi and ESXi 5

  I have a group of ESXi 4.x hosts connected to a vCenter Server 4.1.  I have an another 5.1 vCenter Server Management 5.1 hosts.  I want to move my hosts ESXi 4.1 in my 5.1 vCenter Server and upgrade to 5.1.

  Since vCenter 5.1 can manage ESXi 4.x and 5.1 hosts in the same cluster (KB VMware: upgrading vCenter Server 5.1 recommended)

  Could I add my 4.x hosts to vCenter 5.1 and put them in maintenance mode one by one and then upgrade?  I'd be able to vmotion the VMs between my 4.x and ESXi hosts 5.1?

  The goal is to reduce or hopefully elimate downtime for virtual machines.

  Thank you!

  You can get the upgrade with no interruption of service, if you can:

  (a) connect the storage 4.1 hosts FC 5.1 guests, so it is shared by all hosts

  or

  (b) your license allows you to storage vMotion the VMS to storage of 5.1 hosts

  The normal steps would be:

  -Disconnect the 4.1 hosts the vCenter 4.1

  -Connect the 5.1 vCenter

  -connect storage 4.1 for the 5.1 hosts or Storage vMotion the VMs on

  -vMotion the VMs to 5.1 hosts

  -upgrade the 4.1 hosts

  Concerning

• VMotion between ESX 4.1 & ESXi 4.1 down on identical hardware

  I did turn ESX 4.1 a few months on 6 Dell R710 servers and have no problem of vmotion, but now I added 2 extra (identical) Dell R710 servers with ESXi 4.1 on them.

  The problem I have is that I can't vmotion running servers to the ESXi servers.

  Can I vmotion stop server on ESXi servers without problem and running (on ESXi) between these 2 ESXi R710s of vmotion.

  Also, I can't vmotion (on ESXi) servers to ESX servers.

  I get the same error message, re cpu is different! Although they are not.

  Thank you for taking the time to answer this.

  J

  This error message occurs generally if guests have different BIOS settings or even different BIOS versions.

  See http://kb.vmware.com/kb/1029785

  André

• vMotion between ESX 4.0 and ESX 3.5 hosts

  We are planning our ESX 3.5 to ESX 4.0 infrastructure upgrade.  I understand you can vmotion VM guests from 3.5 to 4.0 hosts, however you can migrate 4.0 3.5 guest hosts.  Before you try I know that we have to vCenter Server 4.0.

  Yes, vmotion is allowed between the two versions.

  Just don't upgrade the comment tools and virtual hardware until you get all of your ESX hosts on 4.0

  Good luck!

• CAN I VMotion between ESX server with they are in different version?

  Hi all

  I want to upgrade my 2.5u1 to 2.5u3 vCenter, then upgrade my all the ESX Servers 3.5u1 to 3.5u3. VMFS on storage shared SAN and VMotion already activated. My question is if I upgrade the first server ESX 3.5u1 to 3.5u3, can I use VMotion to migrade the 3.5u1 virtual machine remains in the new 3.5u3 updated? Thank you!

  -david

  PS. I had been looking, but too many results or not exactly my scenario. So hard to find one suitable.

  Yes and you can even go to 3.0.2 3.5.3 without a problem. Usually, it is the target CPU model that causes pain when he is not the same.

  http://blog.laspina.ca/

• Cannot Storage Vmotion between EMC Celerra NFS and NFS VNX

  Recently we have improved our infrastructure VMware 3.5 to 5.0. Managed to migrate all virtual machines to the Esxi5.0 without any problems. More recently, we bought new storage EMC VNX 5300, set up and configured the NFS storage for the early. All the warehouses of new data related to blades and all storage pools, old and new can be found under vCenter.

  Problem we have is that we can not Storage vMotion virtual machines of the old Celerra NFS for new NFS VNX stores. It comes back with the error "cannot access file VM VNX {datastore} filename '. We got a similar message appears when you try to create a new virtual machine or import an OVF on VNX new data warehouses.

  We have the license of the company, with Dell M600 blades with EMC storage as mentioned above.

  Pointers would be appreciated

  Kem

  Thanks for your contributions, but I solved it. A bit of a 'schoolboy error', but although I had added to the VMKernel IP in the host root and read-write in the NFS export properties, I also need to add the IP address of the hosts/blades. Storage vMotion successfully in new stores VNX. THX Kem

• You can VMotion between host ESXi 4 and ESXi 4 Update 1?

  I have a node 2 VMotion, HA cluster. Identical machines running ESXi 4. I want to use the patch to update 1 update. If I VMotion then update all my virtual machines on a host, the other on its own will I be able to VMotion virtual machines on the host being updated from the host not yet updated? Then update the second host.

  Thank you.

  There is no problem doing exactly what you describe - it is supported.

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

• 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.

• Problem with vmotion between two esx 4.1

  Hello

  I have set up an environment with a vcenter 4.1 and two Vsphere 4.1

  I've already implemented the vmotion between servers.

  However, when I try to migrate a virtual machine from one machine to the other, the process crashes with the following error:

  Migration to host < < unknown > > failed with the error Timeout (195887137).

  vMotion migration impossible to empty the buffer of the stream: Timeout

  vMotion migration expired 20000 ms waiting to transmit data

  Vmkernel, I see:

  4 August 19:35:19 edelvivesvir01 vmkernel: 0:02:16:28.511 cpu7:4288) MigrateNet: vm 4288:1422: dataSocket 0x4100a212f0c0 receive buffer is size 563724

  4 August 19:35:19 edelvivesvir01 vmkernel: 0:02:16:28.511 cpu7:4288) VMotion: 2825:1280943313439515 added D: 1 flow connection.

  4 August 19:35:19 edelvivesvir01 vmkernel: 0:02:16:28.696 cpu6:4612) VMotionDiskOp: 769: 1280943313439515 D: DiskOps successful trading.

  4 August 19:35:39 edelvivesvir01 vmkernel: 0:02:16:48.697 cpu11:4609) WARNING: VMotionUtil: 1147:1280943313439515 D: could not read header: Timeout

  4 August 19:35:39 edelvivesvir01 vmkernel: 0:02:16:48.697 cpu11:4609) WARNING: migrate: 296: 1280943313439515 D: Failed: timeout (0xbad0021) @0 x 0

  4 August 19:35:39 edelvivesvir01 vmkernel: 0:02:16:48.698 cpu11:4610) WARNING: VMotionUtil: 1147:1280943313439515 D: could not read header: Timeout

  4 August 19:35:39 edelvivesvir01 vmkernel: 0:02:16:48.709 cpu3:4605) WARNING: migrate: 4249: 1280943313439515 D: Migration considered a failure by the VMX.  It is probably a timeout, but check the VMX log for the actual error.

  4 August 19:35:39 edelvivesvir01 vmkernel: 0:02:16:48.720 cpu15:4613) FS3: 2988: Req mode: 1 audit delay of [type offset 10 c 00001 26828800 v 24, offset hb 3633152]

  [4 August 19:35:39 edelvivesvir01 vmkernel: gen 9, mode 3, owner 00000000-00000000-0000-000000000000 mtime 3228] on flight "SERVIDORES.

  4 August 19:35:43 edelvivesvir01 vmkernel: 0:02:16:52.735 cpu6:4605) Sched: vm 4606:1246: name = "vmm0:vCenter_Upgrade".

  I can do vmkping of each server to the other.

  The date is synchronized on both servers.

  Can someone help me understand this problem?

  Regards and thanks in advance.

  Hi again,

  Looks like you can't have jumbo frames enabled on the network adapters used by vMotion.

  I'm glad it works!

  VCP3/VCP4/VTSP/VSP/MCTS: Virtualization

• 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.

• 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.

• 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 different processors

  On my last job, I had two clusters vmware, using four hosts with HP DL580 servers and the other with two hosts in a HP BLADE system, I don't remember the model.

  So when I tried to move an active VM for clusters to each other, I got an error, so I'm looking here on community and I got the awnser is the reason the hosts had different processors and I can only move this virtual machine, if they are closed. If I can only move cold VM between my cluster.

  OK im on a new company name and they had M$ Hyper-V and now we are migrating to VMWARE (cool ) we have two DELL Poweredge servers, one with two Quad-Core Xeon X 5470 and the other with two Xeon Quad - Core E5320.

  So I guess I'm having a problem of fact a vmotion hot between it because the servers have different processors.

  So im buying new processors, but I find only Xeon Quad-Core X 5365, I think that it corresponds to that of the X 5470 but with cache and diferrent clock.

  My ask is, can I do a hot Vmotion with some VM of a Xeon X 5470 server on a Xeon X 5365 server.

  Stability of Slackware, safety and simplicity are the best choice!

  Yes,

  the vmotion VMs between different generations of cpu is only posible to put these hosts using Enhanced VMotion (CVS).

  Improved compatibility for VMotion (EVC) simplifies VMotion compatibility issues

  through the generations of CPU. EVC automatically configures the server with Intel CPU

  FlexMigration or AMD - V extended Migration technologies

  compatible with the old servers. After EVC is enabled for a cluster in the

  VirtualCenter inventory, all hosts in this cluster are configured to

  present identical CPU features and compatibility for VMotion CPU. The

  features introduced by each host are determined by selecting a predefined EVC

  base line. VirtualCenter does not allow the addition of hosts that cannot be

  automatically configured to be compatible with EVC baseline.

  To use CVS, you must run ESX Server 3.5 Update 2 or

  highest with Virtual Center 2.5 Update 2 or higher and have only compatible CPUs

  are listed in one of the following tables.

  CVS does not allow for migration with VMotion between Intel and AMD processors.*

  VCA makes it much

  easier to add servers with the new generation of processors in existing clusters

  containing a material more former generation. Entering an EVC cluster servers are

  automatically configured to be compatible with the hosts already in the

  clusters. Since this process is automatic, EVC is very simple to use and

  requires no expertise on CPU features and masks.

  Suresh

• 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.