What I have done to try to spread the load is to stagger the assignment of VMs. For example, if you have 5 ESXi hosts and 15 VMs: host1 - vm1, vm6, vm11 host2 - vm2, vm7, vm12 host3 - vm3, vm8, vm13 host4 - vm4, vm9, vm14 host5 - vm5, vm10, vm15
Also, vSphere 4.1 does not have limitations that impact most current hardware but you should be aware of the vSphere 5.0 licensing limitation of 32 GB of total RAM assigned to VMs per host. The good news is that VCL 2.3 will fully support KVM. :) -Andy On Thu, Dec 8, 2011 at 4:05 PM, Mike Haudenschild <m...@longsight.com> wrote: > Hello to all. I've been tasked with building out and managing a VCL > implementation that will utilize VMWare ESXi 4.1 hypervisors across 5 > separate servers. I have trolled the existing documentation and listserv > archive, but I have two burning questions: > > 1. I've read in another thread that VCL doesn't have load balancing > capabilities per se as part of the scheduler. How does VCL equalize the > load of virtual machines across several hypervisors? > > 2. I've found that the "free" VMWare hypervisor 4.1 license caps out at one > physical processor (with 6 cores). Are most folks running a non-free VMWare > license alongside VCL? > > I greatly appreciate any assistance that current VCL users and the dev team > can provide! > > Regards, > Mike > > -- > *Mike Haudenschild* > Education Systems Manager > Longsight Group > (740) 599-5005 x809 > m...@longsight.com > www.longsight.com
