astorrs wrote: For server virtualization of Windows Server 2003 on ESX/ESXi 3.5 I've found using 3-5 VMs per core with 2-4GB of physical RAM per core is pretty accurate for 95% of installations. So in other words a dual quad core Xeon (8 pCPUs) with 32GB of RAM should allow for somewhere between 24 and 40 virtual machines (this is assuming each VM is 1 vCPU). While these numbers are a good starting point the only way to know for sure would be to use a tool like PlateSpin PowerRecon (or similar) to gauge the current resource utilization of your physical servers.
royal wrote: But anyways, Hyper-V > ESX. Let the drama begin!
bwcarty wrote: and let DRS distribute the load fairly aggressively.
HeroPsycho wrote: royal wrote: But anyways, Hyper-V > ESX. Let the drama begin!
astorrs wrote: bwcarty wrote: and let DRS distribute the load fairly aggressively. How aggressive do you like to be? 1, 2, 3, 4, or only 5 star recommendations? I usually stick to 3.
Sunshine_54 wrote: Lol, I don't know how anyone can say Hyper V > ESX. VI3 has far more features and has far better performance. But anyways, don't want to get into a flamewar My 2 cents.
undomiel wrote: It's probably better to say HyperV > ESXi.
HeroPsycho wrote: undomiel wrote: It's probably better to say HyperV > ESXi. How so? ESXi can still do more with the same hardware, has memory sharing optimizations, and an easier transition to full Virtual Infrastructure in the future. And it's free. I'd do ESXi over HyperV, too.
royal wrote: Virtual PC > ESX imo.