Hyper-V 2008 R2 vs. vSphere virtual machine maximums

Tonight, I was researching some Hyper-V stuff and I ran across Microsoft’s maximums as they relate to virtual machines hosted on Hyper-V R2. It was an interesting read and, although I’ve looked at vSphere maximums in the past, I decided to put together a down and dirty comparison table outlining the most significant virtual machine maximums – processors, RAM, disks and network adapters. You’ll note that, with the exception of the number of drives supported and, to a lesser extent, network adapters, vSphere for surpasses Hyper-V when it comes to raw virtual machine capability. This positions vSphere as the better choice for particularly resource-intensive workloads that need more than 64 GB of RAM and more than 4 processing cores.

Component

Hyper-V R2

vSphere 4

Virtual processors supported inside a guest

4

8

Memory

64 GB

255 GB

Virtual IDE disks

4
(see note 1)

4

Virtual SCSI controllers

4

4

Virtual SCSI disks

256

60

Virtual hard disk capacity

2040 GB

2 TB – 512 bytes

Virtual network adapters

12
(see note 2)

10

Note 1 (Hyper-V): 8 NICs can be of the “network adapter” type, which provides better performance and requires a virtual machine driver that is included in the integration services packages. 4 NICs can be of the “legacy network adapter” type which emulates a specific physical network adapter and supports the Pre-execution Boot Environment (PXE).

Note 2 (Hyper-V): The startup disk must be an IDE device.

Source information:

vSphere: http://www.vmware.com/pdf/vsphere4/r40/vsp_40_config_max.pdf

Hyper-V: http://technet.microsoft.com/en-us/library/ee405267(WS.10).aspx

Leave a Comment

Your email address will not be published. Required fields are marked *

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Scroll to Top