Hyper-V has been much “souped” up in terms of the amount of resources it could work with. Here’s a table that gives you more information. Do bear in mind that over time, Microsoft will increase the amount of resources a VM can work with. In the past year that Hyper-V got release, Microsoft has increase twice the amount of processor support.
| Functionality | Microsoft Hyper-V Server R2 | Windows Server 2008 R2 Standard Edition | Windows Server 2008 R2 Enterprise Edition | Windows Server 2008 R2 Datacenter Edition |
| Logical Processor Support | 32 LP | 32 LP | 32 LP | 32 LP |
| Physical Memory Support | Up to 1 TB | Up to 32 GB | Up to 1 TB | Up to 1 TB |
| Cluster support: Live Migration | Yes | No | Yes | Yes |
| Max # of VMs | 8 V-Procs per LP (i.e. 256 uni-proc VMs) | 8 V-Procs per LP (i.e. 256 uni-proc VMs) | 8 V-Procs per LP (i.e. 256 uni-proc VMs) | 8 V-Procs per LP (i.e. 256 uni-proc VMs) |
| VM Licensing | None included | 1 Free Per License | 4 Free Per License | Unlimited |
There is a figure here that my require a little more explanation.
Under the row; “Max # of VMs” – 8 V Procs per Logical processor.
If you have VMs that are configured with only 1 CPU, then you can have a max of 256 VMs. 8 V Procs x 32 logical processors
if you have VMs that are configured with 4 CPUs, then you can have a max of 128 VMs. 8 V Procs x 32 logical processors / 4.
Logical processor
If you have 1 Dual Core CPU, that’s 2 logical processors
If you have 4 Dual Core CPU, that’s 8 logical processors
If you have 2 Quad Core CPU, that’s 8 logical processors
Note:
VMWare suffers the same problem has Hyper-V. 4 V Procs per VM. :-)
/Dennis
