A bit off topic, but I'm *so* looking forward to VCL 2.3 with KVM, as at our
site we've hit limits with both ESXi 4.1 (6 cores per socket, giving us only 24
of 32 cores on a fancy new 4 socket box), and with the RAM limits of ESXi 5.0.
Anticipatingly,
Terry McGuire
On 9 Dec 2011, at 1333h, Andy
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 im
Mike,
Our approach to load balancing is to put all of our VMs inside a vCenter
cluster with dynamic resource scheduling enabled -- this allows vmware to move
VMs around to balance the load. We can then have an arbitrary number of
physical servers, but to the VCL it looks like a single vmhost. Th
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 do
