Problem description in short:
While provisoning the pool all VMs are provioned on the same ESX host, instead of being balanced over the 6 ESX hosts.
What balancing mechanism is used bij VMware View or vCenter cluster, to balance the VMs across the ESX hosts?
The situation:
New vSphere 5.1 ( latest build ) vCenter
6 * vSphere 5.1 ( latest build ) ESX with Fusion-io
VMware View 5.2 with floating desktops.
We build a completely new environment separated from the production servers, they are running on a different vCenter.
We are using Fusion-io ( local storage ) for the replica and delta VMs.
We have one cluster with no HA and DRS.
The 6 ESX hosts are connected to the cluster.
We got one parent-VM wich is placed on a NFS target and is published to the 6 ESX hosts.
All desktops are bases on floating desktops, wich imediatly refresh after logoff.
The Case:
The Pool settings:
- Parent-VM ( NFS ) selected
- vCenter Cluster selected
- No resource pools
- 6x local datastore targets ( Fusion-io all datastores are empty )
After creating the pool the provisioning of the replica and the delta-VMs get started.
But now is the problem, all VMs are provisoned on the same ESX host!
Why does it not balance the VMs across the 6 ESX hosts?
What mechanism is used by VMware View to balance the VMs across a cluster? Or is VMware View simply delivering all VMs to the vCenter Cluster and de cluster must handle it?
In this case with no DRS and local datastores it won`t work...
VMware View is aware of the density ( VMs ) on the local datastores, is this perhaps related? If so, all 6 the datastores are empty...
In this case after a short while the ESX host has no resources to satisfy the vDesktops demand and provisioning fails.
I`m experiencing this scenario with multible customers.... What am i missing?
