VMware

This Question is Possibly Answered

1 "correct" answer available (10 pts) 1 "helpful" answer available (6 pts)
5 Replies Last post: May 25, 2009 6:52 AM by Piet Kiekebos  

lab manager load balancing problem posted: May 21, 2009 12:27 PM

Click to view JasonBurrell's profile Enthusiast 93 posts since
Apr 21, 2008

I currently have 3 machines that are in my lab manager farm. One of the servers has two cpu's while the other two just have one cpu. Over the course of a month VM's are powered on my two cpu host more than the other two. It looks like this:

Host1(1cpu) - 15vms
Host2(1cpu) - 18vms
Host3(2cpu) - 60vms

All hosts have the same amount of ram. Does LM just look at aviable CPU when it places a VM? Does anyone else run into this. What I endup doing is disabling host3 so VMs are forced on to Host1&2. Its very manual and annoying. None of my machines can vmotion due to them being fenced. Is it possible to change a value to make LM favor Host1&2? Or have it based on memory rather than cpu?


Re: lab manager load balancing problem

1. May 21, 2009 3:29 PM in response to: JasonBurrell
Click to view skishi's profile Master VMware Employees 626 posts since
Oct 6, 2006
What version of LM are you using?
Are you using DRS or not?

Re: lab manager load balancing problem

3. May 22, 2009 9:07 AM in response to: JasonBurrell
Click to view skishi's profile Master VMware Employees 626 posts since
Oct 6, 2006
LM places VMs when DRS is not used.
When DRS is used, we have DRS recommend the host to place the VMs.
There's a couple things may want to try: turning DRS off on the cluster or waiting for the next version of LM which has cross-host-fencing.

When DRS is turned off, the LM placement routine:
First check hosts for validity (proper CPU for saved state, datastore connectivity, etc.).
Then places the VMs on the host with the smallest (MemoryReservation% + CPUReservation%). By default, we do not reserve CPU on LM VMs, so placement will largely be due to memory on the hosts if you haven't changed the CPU reservation settings on your VMs.

Steven

Re: lab manager load balancing problem

5. May 26, 2009 1:28 AM in response to: skishi
Click to view Piet Kiekebos's profile Novice 4 posts since
Dec 2, 2004
Steven,

I have the same problem. 4 ESX servers. With DRS on I see deployed machines are started loadbalanced with DRS, but are moved by labmanager (see the account doing this) to only one machine.

update: I have found the problem. Reconnect my other 3 servers to labmanger creates the failure: I was forgotten to reconnect the physical networks to the server nics. (tab resources-Networks).

After disable DRS on the cluster and decrease the VM running on server 4, there was a nice warning: no available networks on the other 3 server and no space to run the niew configuration on server 4. That was the trigger. Now with DRS enabled, the deployements are loadbalanced over the hosts.

Piet.

VMware Beta Programs

Want to be Considered for Future Beta Programs?

Learn More

VMware Developer

Download SDKs, APIs, videos,
training, and more in the Developer community.

Learn More

Developer
Sample Code

Increase your developer productivity with VMware API sample code.

Learn More

VMworld
Sessions & Labs

Online access to the latest VMworld Sessions & Labs and online services.

Learn more

Purchase PSO Credits Online

Purchase credits to redeem training and consulting services online.

Buy Now

Community Hardware Software

View reported configurations or report your own.

Learn More

Only VMware ... Delivers Nexus 1000V

Ensure consistent, policy-based network capabilities to virtual machines across your data center.

Learn More

Communities