Yes, you can calculate/retrieve the CPU and memory usage on the ESXi nodes in a cluster, before you execute the New-VM cmdlet.
Something like the following for example, it will return the name of the ESXi node with the lowest load (at this moment).
Note that the weighing factors for CPU and memory are both set to 1. Which means CPU & memory are considered equally important in the decision process.
But there are many other selection criteria possible.
$clusterName = 'MyCluster'
$cpuWeight = 1
$memWeight = 1
$esx = Get-Cluster -Name $clusterName | Get-VMHost
Get-Stat -Entity $esx -Realtime -MaxSamples 1 -Stat cpu.usage.average,mem.usage.average -Instance "" |
Group-Object -Property {$_.Entity.Name} | %{
$cpu = ($_.Group | where{$_.MetricId -eq 'cpu.usage.average'} | Select -ExpandProperty Value) * $cpuWeight
$mem = ($_.Group | where{$_.MetricId -eq 'mem.usage.average'} | Select -ExpandProperty Value) * $memWeight
New-Object PSObject -Property @{
Name = $_.Name
Value = $cpu + $mem
}
} | Sort-Object -Property Value | Select -First 1 -ExpandProperty Name
The New-VM cmdlet will not accept a clsuter on the VMHost cmdlet I'm afraid.
