Similar Questions

• Add hosts with existing virtual machines for 'Greenfield' active DRS Cluster

  I'm currently involved in a project for the hypervisor 5.5 and vCenter. Existing are 2 physical servers with redundant everything and 8 SAS hot swap hard drive bays. Initially, 8 bays only 4 have been populated with hard drives. Hard disks have been removed, ESXi 5.0 has been loaded, 4 virtual machines created on each server and all lived happily ever after.

  Now, I would like to upgrade these servers to 5.5... as follows:

  I filled the remaining 4 bays on each server with some hard disks and created a second strip of sufficient capacity (twice the capacity of the 4 original disks). I'm stop servers, past the stripe for starting a new band of readers and installed ESXi 5.5 on the new band. The old Strip also remains in tact, so that I can start to ESXi 5.0, if I set to boot from the original soundtrack or boot to ESXi 5.5 if I boot to the new band (two operating systems starts very well, are properly networked, configured vCenter, etc.).

  When booting in 5.5, he sees his own, new band and is also the soundtrack which is listed as a second data store attached (I think actually I want to make possible migration of the simple VM from the old to the new data store), both are disk space of LSI, Non - SSD, Type VFMS5.

  Panic sets in when I start both computers in 5.5 and the time comes to add 5.5 hosts in a cluster (I also want to test the vStorage DRS and HA) and I've reached the setting of the, "choose Resource Pool." I'm scared to death that choose the first option, "all of the virtual machines in this updated host in the cluster resource pool root. Pools of resources currently present on the host computer will be deleted. "will mean not only a reformatting of the new band which I would like to add to the cluster, but also the still attached old band that includes the data that I want to keep. I don't want to lose data or virtual machines on the soundtrack, but to migrate them in a cluster of 2 servers ESXi 5.5. I was really hoping to migrate data to new tapes on new hosts and then re - purpose boards 2 original (on both computers) as a third table vStorage.

  Issues related to the:

  1. If I choose the option "put all the virtual machines from the host in the pool of resources of the root cluster. Pools of resources currently present on the host computer will be deleted. "with all the drives connected, all my data will be lost?

  2. If I pull the 4 original disks (5.0) and use the option 'put all virtual machines from the host in the pool of resources of the root cluster. Pools of resources currently present on the host computer will be deleted. "that with the new arrays connected (5.5) and then reconnect the old paintings after that the hosts are added to the cluster, will be only the re added still get sucked into the tables and data deleted?

  3. choose the second option, "create a new resource pool for virtual machines from the host and resource pools. This preserves hierarchy to pool resources in. the host' a safe option? If this option works, no matter if I have my original array attached when you add hosts to the cluster?

  Last point: by reading all the documents I found it seems strongly suggested to set up guests who have not a deployed virtual machines, that's why I'm going to great efforts to try to keep the new hosts as empty as possible and with 1 port base networking while waiting to complete the configuration. Does it matter if I migrate virtual machines or add them as guests to the ESXi 5.5 before or after I have add hosts to the cluster?

  Any ideas or help would be greatly appreciated.

  I'd go with option C.

  VSAN I would agree has some stupid requirements, but that they were aiming for is almost class company SAN at a decent price by using the SSD as caching tables, but as you said if you don't need not good I would continue to go with a NAS NFS solution.

• VCA serious question in a cluster after adding servers active DRS blades M630 Dell

  Hi guys,.

  I hope that you will be able to help me with this strange question that I feel right now.

  A couple of details first on our environment:

  • vCenter 5.0 U3
  • ESXi 5.0.0 - 2509828
  • 6 guests active DRS cluster
  • 4 hosts are Dell M620, E5-26XX v2 processor blades
  • 2 hosts are blades M630 Dell with processors of E5-26XX v2
  • VCA mode is currently set at "Westmere".
  • All ESXi hosts are fully patched using AUVS

  Before adding the new M630 blades to the cluster it any of the issues with the DRS or VCA, outside the constraints of resources, and the 4 blades M620 we are able to correctly migrate the virtual machines back.

  I could add the M630 blades to the cluster without problem and without errors or warnings have been issued. A week or so later, I noticed more deviations of DRS desired on the cluster. More inspection I noticed that quite a large number of virtual machines showed N/A beside VCA mode and I was not able to migrate them to any host on the cluster.

  Thinking it could be a bug of sorts, I turned off all the virtual machines in the cluster and run a script that resets the CPUID at default. In addition, as a measure of precaution, I restarted the vCenter server and ensures that the database has been effective. The hosts are synchronized time with an NTP source and fits perfectly on both hosts.

  After feeding all the VMS, I rebooted the M630 servers and inspected the BIOS settings to ensure that virtualization and NX/XD is enabled. With all virtual machines powered off, I was able to change the levels of the VCA to any available without warnings setting.

  When everything has been turned back on I noticed a strange behavior in the cluster.

  Virtual machines that are running on M620 blades show the right level of CVS and I am able to migrate them to all servers in the cluster. Once that they migrate to the blades M630, VCA state change s/o and I am unable to migrate anywhere, not even the other M630 blade in the cluster.

  The error that I am shown during the verification step is:

  The operation is not allowed in the current state of the connection to the host. Host CPU is not compatible with the requirements of the virtual machine to cpuid level 0 x 1 host bit ' ecx' register: 0000:0010:1001:1000:0010:0010:0000:0011 required: x 110: x01x:11 x 1: 1xx0:xx11:xx1x:xxxx:xx11 inconsistency detected for these characteristics: * General incompatibilities; see section 1993 of possible solutions.

  Dig deeper in my investigation, I came across this KB: 1034926[1]

  I checked the M620 user guides and the M630 and parameters mentioned in the KB should be enabled by default. Unfortunately, I have no way to check the BIOS settings because I can not all M630 blades enter into maintenance mode without turning off the virtual machines running on them and another maintenance window one day after previous, we're going to be deprecated. In addition, the error is not the same as that of the KB and my goal is to collect as much information before entering another window of maintenance requiring downtime.

  I hope that you will be able to provide any new perspectives or opening my eyes to things that I may have missed.

  Thanks in advance.

  The processor in this system is a v3 E5-2660, not an E5-26xx v2.  ESXi 5.0 doesn't know how to use the features of this processor FlexMigration.  I think that the first version of ESXi to support this processor is ESXi 5.1U2.

  Unfortunately, I do not see a workaround for ESXi 5.0 solution.

• Add or remove a host NOT in a DRS Cluster maintenance mode

  Is there a reason why add a host in an active DRS cluster that has say 20 virtual machines running on it would cause problems?  I understand a host must be in maintenance mode when adding or remvoing in a DRS cluster, but this can be done by disconnect/remove/add the host to the cluster.  Is there a technical reason why we should not do?  It disrupts DRS or HA?

  You'll be fine.  Best practice dictates in and out of a cluster in maintenance mode, but...

• ESXi hosts are divided into DRS cluster

  Hi all

  I'm going as well as I can explain it... In the case that I'm not being very clear, please not hesitate to ask me more questions.  Here is the scenerio:

  (1) I have a Blade IBM H chassis has 7 in there (host ESXi) servers

  (2) I have implemented a DRS cluster with these 7 Hosts

  (3) I have active VMotion and HA

  (4) the question is that 2,3 and 6 blades can only ping between them on the VMotion network and therefore can migrate to eachother

  (5) blades 1,4,5 and 7 only can ping each other and can therefore only VMotion for eachother.

  (6) this problem started to happen over the weekend, one day, and when we came back to work on Monday, we realized that the 3 hosts were not communicating on the network correctly.

  (7) one thing I noticed is when I unplugged all the DRS cluster hosts and then I connected to them again I realized that all guests were able to successfully connect to the Cluster but the hosts 2, 3 and 6 failed on the AP.  When I then reactivated the AP, he worked on these 3 guests.

  (8) due to this problem, I had remove the feature of DRS cluster because the system could not migrate the machines for guests.

  (9) one last thing I noticed was that when I VMotion, the machine I have VMotion loses network connectivity.  I must go to the publishing settings and disable the NETWORK adapter and re-enable the NETWORK card

  I hope someone can help with this problem

  Thank you all,.

  Antonio.

  Basically, the spanning tree Protocol is used to avoid loops in a bridged network. Please take a look at for example http://en.wikipedia.org/wiki/Spanning_tree_protocol for details on how it works.

  However, the individual switch ports that serve as uplinks for ESXi must be configured for Spanning-tree portfast.

  André

• VSAN error: host is in an active VSAN cluster but has no active VSAN service

  Guys,

  When I try to configure the vSAN cluster, I get the below error message:

  VSAN error: host is in an active VSAN cluster but has no active VSAN service

  Help, please.

  Thank you

  John

  Please follow lla: http://www.vmwarearena.com/2014/03/vsan-error-host-is-in-a-vsan-enabled-cluster-but-does-not-have-vsan-service-enabled.html

• Move-vm can migrate a powered off the virtual computer to a DRS cluster?

  When I try to move-vm has propelled off VM to a destination of DRS cluster, he says that he cannot migrate a powered off the virtual computer to a DRS cluster.   I can explicitly name the destination of the host and it works, but that defeats the purpose of using the DRS and forces me to script on the destination hosts.

  I do something wrong or I would be able to migrate a powered off the virtual computer to a DRS cluster?

  Thank you

  -MattG

  Hello, MattG-

  I get the same behavior as you when you try to move a VM PoweredOff to a DRS cluster, specifying the cluster as the value for the parameter - Destination to Move-VM (using PowerCLI v5.1 Rel 2 v5.5 Rel 1).  Not quite what I expected.

  To work around the problem, and without having to appoint a particular host as destination, you could use some Get-Random, do something like:

  Move-VM myVM0 -Destination (Get-Cluster myDestDRSCluster | Get-VMHost | ?{$_.State -eq "Connected"} | Get-Random) -RunAsync
  

  Who should receive the machine said cluster and on a host that is in the connected state.  A subsequent operation to the market (whenever do you eventually) should then see DRS power on the virtual machine on a suitable host in the cluster.

  Maybe the dev team can comment if this behavior is the expected or desired.

  Anyway, how does do for you?

• minimum size of DRS cluster

  What is the minimum recommended DRS cluster size. Is it true that the 2 would be a technical minimum? But y at - it a minimum size which is more effective?

  Is it true that the 2 would be a technical minimum?

  Yes, you can start using DRS with two nodes.

  But y at - it a minimum size which is more effective?

  It is certainly desirable to have several hosts, DRS actually works the same way with two hosts because it works with 32 hosts. The responsibility of the DRS is not not in a cluster to load balance, but to migrate workloads if necessary.

  André

• Best practices for a domain controller in a DRS cluster

  Hi all

  We have our virtualized 2 domain controllers.  We're in a DRS cluster, the other is on a 3rd stand alone ESX host.

  On the cluster, which is the best way to ensure that the domain controller starts first?  We lost our AC for awhile last night (again), and when turned on the cluster hosts, apparently the domain controller did not come entirely everything first, leading to a lot of problems with the other virtual machines.

  On the host of the 3rd, the second domain controller is configured to start first, with all the other virtual machines on a delay of 45 seconds.

  If you use HA, you can set the priority of restarting to 'high '. To find it by changing the settings of your cluster and "the VM options.

• DRS cluster: You can mix 4.1 ESX and ESXi 4.1?

  Not very complext, but we have a DRS cluster of 8 hosts x 3850 of IBM on ESX 4.1 and we will upgrade them both to ESXi 4.1 update 1.  There will be questions mixing a cluster of ESX and ESXi servers?

  Yes, 100% supported!  both are the same hypervisor, so you should have no problem running in the same cluster.  After all it is the best way to do a upgrade spread, and how we made our move between ESX and ESXi.

• Keep VM on a specific host in a DRS cluster?

  I have a DRS cluster with a handful of machines, but only one is a newer server, so it has a higher class of processor.

  I have a virtual machine that needs as much CPU as it can get, when she needs it.  However, I don't want to put it on manual or anything like that, because if the host is in maintenance mode, or something, I would like to migrate off VM.  But as soon as the host comes back online, I would that this VM to go as soon as possible.

  Is it possible to implement this type of "affinity" with a particular host?

  This ordinary handling DRS rules don't really work, because the virtual machine is somehow a user UC 'bursts '.  Normally, it does not use a lot of CPU, but when that happens, it does.

  I'm just curious to know if this is possible or not.  Thanks in advance!

  Russ

  No, you can not install this type of affinity.

  ---

  MCP, MCTS, VCP, VMware vExpert 2009

  http://blog.vadmin.ru

• DRS cluster resource allocation and CPU

  Hi all

  I have a question about the allocation of CPU resources to the guests in an environment of DRS. I was under the impression that all physical CPU resources are completely abstract the guest virtual computer. However, I see the following behaviors...

  -J' have a cluster DRS with two ESX hosts ~ 59GHz of the total available CPU resources. Physical ESX host computers have several multicore 2.9 GHz (I don't have practical details right now but that is irrelevant)

  -J' have a linux comments running RHEL 3.0 which seems high on slightly less than 2.9 GHz.

  Now there are a lot of resources of cpu without reserve available to the cluster, but this particular virtual machine can't enter any allocation of processor more than a little less than 2.9 GHz.

  So my question is this: are VMs limited CPU resources to the maximum of available resources to a single physical processor on the host, or must it be able to recover more of the DRS cluster resources? (Assuming a single vCPU guest), I can't seem to find any material that provides black and white if that's the case?

  If an SSN processing power is limited to the total amount of CPU resources of a single physical processor in the host, which is recommended for a machine that requires more CPU resources? Adding an another vCPU (and running vSMP)? I was under the impression that vSMP should be avoided unless a particular SMV workload could truly take advantage of SMP?

  See you soon,.

  Ben

  Well, Yes, each vCPU is limited to the resources of a single processor - there is no aggregate CPU by VM resources.  In the end, son of vCPU of a VM are given for a single CPU.  The only way to improve the performance of the virtual machine, it is just as you wrote - add vCPUs if the guest operating system and applications can use.  The cost is that all threads of vCPU for a virtual computer must be taken together, so if the virtual machine is unable to make their use, the waiting time for this and other virtual machines could increase, degrade their performance of the processor.

  A little more info...  An ESX host has one or more contexts of material performance (SESC).  Each core is a HEC.  Each instance of a CPU hyperthreading is also a HEC.  Thus, for a host with two processors Quad-heart and without hyperthreading, the total number of sesc on the host is eight.  Another example; for a host with two single core processors and each processor supports hyperthreading, the total number of sesc is four.

  Each vCPU uses a HEC.  A virtual machine with two vCPUs will use two sesc.  According to VMware, ESX will try to prioritize different sockets for use of the VM before two hearts on the same socket and before hyperthreading sesc on the same socket.

• Home put in service of a DRS cluster active mode NOT to trigger and automatic Vmotion

  I'm under 5.5 U2

  I have a cluster with active and defined DRS fully automated, but when I select the host for the maintenance mode of the VM NOT vmotion to another host in the cluster automatically. I have to vmotion manually each virtual machine to a host selected manually. There are a few VM with DRS off on them because they ONLY work on the host, they are assigned to (replication of virtual computer), but all the other VMS are defined 'by default (automated)'. Would it because I only have two of the host in the cluster?

  

  Try this.

  Hope it will solve your problem.

  http://www.vmwareminds.com/troubleshooting-maintenance-mode-process-get-stuck-at-2/

• service.msc overrides msconfig active service?

  My msconfig contains a list of SERVICES with check marks on each element.  The State could be running or stopped, but no date is given in the column Date disabled.  In other words, that all are enabled, no?

  My services.msc is also a list but with automatic manual, different Types of starts, disabled, etc.  I read do not change status in msconfig, but it is normal to make changes in the services.msc.

  This means, if I change the Startup Type to disabled, this will replace the State enabled in msconfig?  I'm just trying to reduce the startup time.

  Answering your question: Yes, disabling a service in services.msc removes Msconfig list service so we can say it replaces the msconfig settings
  I would like to disable Msconfig
  Disabling services in msconfig is safer than services.msc because when you enable them again he will restore it with the same settings (as if it was the manual in the first place he goes back to the manual on activation)
  However I do recommend NOT turning off Microsoft services
  
  

• Disabled - HA and DRS cluster hosts do not appear in vCOPS

  Have a cluster HA and DRS disabled so that each of the 10 hosts act as autonomous.  In vCOPS 5.8 UI, the hosts appear in the accounts for the cluster but cannot explore them or access it from the search box.  Any ideas?  Thank you

  Found - http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2068303 problem solved.