VDI Vmotion between hosts with appvolumes

Similar Questions

• 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 hosts on different subnets

  Before you start, I'm a network engineer, not a server guru, please bare with me

  Is it possible to vMotion a virtual machine to a host on an IP network to another host, on a different IP network?

  Example:

  Data Center 1 - 10.1.1.1/24 with VM in the 10.1.2.0/24 ESX Server

  Same city, different site, binding fiber 10 GB between facilities 2ms latency

  Data Center 2 - 10.2.1.1/24 in the 10.2.2.0/24 with VM ESX Server

  Scenario:

  vMotion a computer virtual network 10.1.2.0/24 to the 10.2.2.0/24 network where virtual machine, on arrival on the ESX 2 data center server, now uses a IP address of 10.2.2.0/24.

  Any guidance towards a white paper or a guide would be greatly appreciated.

  Thank you all for your time.

  -Chris

  Network engineer

  Press Ganey Associates

  vMotion is possible between hosts on different subnets, but unless your discussions presented to the virtual machines are on the same subnet, you will eventually drop the virtual machine on a VLAN different and IP addressing will fail.

  There are ways around this, you could script the change of IP address / present several IP addresses of the virtual machine / or reservations DHCP to use, but you will need to ensure DNS etc. records are updated.

  If you have some kind of load balancer, you could in theory balance workloads on 2 IPs hosted on the same VM, to solve the network ip address issues, although in the end, you'll want a VLAN tended to port VM coverage groups.

  Good luck

• 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

• 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

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

• Stop reboot request when fast vMotioning to a host with a different processor

  I need help to find a better way to deal with a prompt to reboot my users get due to a vDesktop in model (Dell 710) host vMotioned to another (Dell 720). The difference between the two is the processor models. The 710 is a Xeon X 5670 and the 720 is a Xeon E5-2667. The two processors use the same .inf (cpu.inf) file and apparently the drivers. Simply, it triggers the installation process of the material causing the Plug and Play Manager to require a restart of the operating system after the installation. The result, I'm wanting just needs that this reboot window displays don't not weither would it by slaughtering the hardware installation process, hide the window of dialogue itself, or any other possible way to configure the system which does not show users. I've confirmed that you don't have to restart the machine remain operational. Here is some additional information on the operating system and all.

  Windows 7 32 bit

  1 vCPU

  2G of RAM

  vSphere 5.0.0 623860

  Discover Constable's 5.0.0 481677

  Any suggestions or thoughts are greatly appreciated.

  Tanner

  I encountered the same problem and the only solution I've found so far is to start the master on both hosts.  When he started on the two hosts, the message no longer appears when moving the virtual machine back to a host with a different model of CPU.  I have two clusters currently, so I have not tested vMotioning fast machine between hosts with different CPU while it is running.  When I had the chance to test, I'll post my results.

  -Chris

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

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

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

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

• Update / fixes ESXi single host with VCSA running on it.

  We have just updated since the free version of ESXi 5 by ordering the Kit of Essentials. In the process, of course, we were able to deploy vCenter Update Manager (which has been the main motivation, like patching manually the free version seemed to be quite a pain). We have a Windows host that has installed the Update Manager, and we have a VCSA running on the single instance of ESXi, we deployed to date. We were able to install the plugin on the viClient and scan the ESXi host for patches with success (a need a good number). But, we're stuck trying to install the patches... us when trying to restore the host, we get: "the operation is not supported on the selected inventory items. Check events for the objects selected for the operation.

  The host says:

  The 10.0.1.80 host has a virtual VMware vCenter machine

  Device server with VMware vSphere update

  Manager or VMware vCenter Server installed. The

  Virtual MACHINE needs to be moved to another host for the

  consolidation to proceed.

  error

  28/08/2014-16:21:32

  Clean up the entity

  10.0.1.80

  root

  Looking at this logic, for the host switch to maintenance mode, the VCSA should have been suspended (apparently, actually moved), which would avoid in turn patches / updates to the deployment. Am I correct in thinking, that we have a second host and networked storage? Made a Kit Essentials / license provide for the possibility of vMotion from one host to another? It wasn't really clear... Yes, the web site says "vMotion" is included in most Essentials, but find it me hard to imagine any point to a facility in ESXi stream without the ability to vMotion between one system and another guest...

  Welcome to the community,

  And since you have only an ESXi host and your vCSA is running on this host, you cannot patch this host with Update Manager for reason that already know you: the host should be the maintenance mode.

  Add about another host, with Kit Essentials without vMotion functionality, you can try using a data store of shared storage between two hosts, stop the vCSA on first host and switch the vCSA on the second host... and finally the first host patch.

• 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