Aidan Finn, IT Pro

In Windows Server 2008 R2 it was:

• 4 vCPUs
• 64 GB RAM

In the Windows Server “8” Developer Preview it was:

• 32 vCPUs
• 512 GB RAM

In Windows Server “8” Beta people gasped when it jumped to:

• 32 vCPUs
• 1 TB RAM

And now I can finally say that VMware will shit their pants when they read that Windows Server 2012 Release Preview VMs will support:

• 64 vCPUs
• 1 TB RAM

VMware vSphere 5.0 supports a max of 32 vCPUs and 1TB RAM.  Throw in the 64 TB VHDX (compared to 2 TB VMDK) and MSFT has VMware beat on scalability.

Hyper-V Replica for free, Network Virtualisation, SR-IOV, SMB 3.0 transparent failover storage, Shared Nothing Live Migration, PowerShell, Storage Migration, …… How does VMware compete in a few months time when vSphere 5.0 becomes the product that is feature chasing and is way more expensive?

Anyone remember Novell?

Credit to Hans Vredevoort for finding the announcement.

Also read:

• VMware – I Hope You Have Your Depends On – Hyper-V Hosts Scale Out … Again
• And Max Running vCPUs Per Host Is Going Up Too

Copyright Warning

This blog post is the property of Aidan Finn (@joe_elway / http://www.aidanfinn.com) and may not be reused in any manner without prior consent of Aidan Finn. You may quote one paragraph from this blog post if you link to the original blog post.

Related posts:

1. What Gartner Says Of Windows Server 2012 Hyper-V Versus vSphere 5.1
2. Why Windows Server 2012 Hyper-V VHDX 4K Alignment Is So Important
3. Comparison of Windows Server 2012 Hyper-V Versus vSphere 5.1