TechNet
Table of contents
TOC
Collapse the table of content
Expand the table of content

Plan for Hyper-V scalability in Windows Server 2016

Kathy Davies [MSFT]|Last Updated: 9/22/2016
|
4 Contributors

Applies To: Windows Server 2016 Technical Preview

This is preliminary content and subject to change.

This article gives you details about the maximum configuration for components you can add and remove on a Hyper-V host or its virtual machines, such as virtual processors or checkpoints. As you plan your deployment, consider the maximums that apply to each virtual machine, as well as those that apply to the Hyper-V host. Maximums for memory and logical processors are the biggest increases from Windows Server 2012, in response to requests to support newer scenarios such as machine learning and data analytics. For a comparison of these numbers, see the blog post Windows Server scalability and more! Other numbers are similar to those that apply to Windows Server 2012. (Maximums for Windows Server 2012 R2 were the same as Windows Server 2012.)

Note

For information about System Center Virtual Machine Manager (VMM), see Virtual Machine Manager. VMM is a Microsoft product for managing a virtualized data center that is sold separately.

Maximums for virtual machines

These maximums apply to each virtual machine. Not all components are available in both generations of virtual machines. For a comparison of the generations, see Should I create a generation 1 or 2 virtual machine in Hyper-V?

ComponentMaximumNotes
Checkpoints50The actual number may be lower, depending on the available storage. Each checkpoint is stored as an .avhd file that uses physical storage.
Memory12 TB for generation 2;
1 TB for generation 1
Review the requirements for the specific operating system to determine the minimum and recommended amounts.
Serial (COM) ports2None.
Size of physical disks attached directly to a virtual machineVariesMaximum size is determined by the guest operating system.
Virtual Fibre Channel adapters4As a best practice, we recommended that you connect each virtual Fibre Channel Adapter to a different virtual SAN.
Virtual floppy devices1 virtual floppy driveNone.
Virtual hard disk capacity64 TB for VHDX format;
2040 GB for VHD format
Each virtual hard disk is stored on physical media as either a .vhdx or a .vhd file, depending on the format used by the virtual hard disk.
Virtual IDE disks4The startup disk (sometimes called the boot disk) must be attached to one of the IDE devices. The startup disk can be either a virtual hard disk or a physical disk attached directly to a virtual machine.
Virtual processors240 for generation 2;
64 for generation 1
The number of virtual processors supported by a guest operating system might be lower. For details, see the information published for the specific operating system.
Virtual SCSI controllers4Use of virtual SCSI devices requires integration services, which are available for supported guest operating systems. For details on which operating systems are supported, see Supported Linux and FreeBSD virtual machines and Supported Windows guest operating systems.
Virtual SCSI disks256Each SCSI controller supports up to 64 disks, which means that each virtual machine can be configured with as many as 256 virtual SCSI disks. (4 controllers x 64 disks per controller)
Virtual network adapters12 total:
- 8 Hyper-V specific network adapters
- 4 legacy network adapters
The Hyper-V specific network adapter provides better performance and requires a driver included in integration services. For more information, see Plan for Hyper-V networking in Windows Server 2016.

Maximums for Hyper-V hosts

These maximums apply to each Hyper-V host.

ComponentMaximumNotes
Logical processors512Both of these must be enabled in the firmware:

- Hardware-assisted virtualization
- Hardware-enforced Data Execution Prevention (DEP)
Memory24 TBNone.
Network adapter teams (NIC Teaming)No limits imposed by Hyper-V.For details, see NIC Teaming.
Physical network adaptersNo limits imposed by Hyper-V.None.
Running virtual machines per server1024None.
StorageLimited by what is supported by the host operating system. No limits imposed by Hyper-V.Note: Microsoft supports network-attached storage (NAS) when using SMB 3.0. NFS-based storage is not supported.
Virtual network switch ports per serverVaries; no limits imposed by Hyper-V.The practical limit depends on the available computing resources.
Virtual processors per logical processorNo ratio imposed by Hyper-V.None.
Virtual processors per server2048None.
Virtual storage area networks (SANs)No limits imposed by Hyper-V.None.
Virtual switchesVaries; no limits imposed by Hyper-V.The practical limit depends on the available computing resources.

Failover Clusters and Hyper-V

This table lists the maximums that apply when using Hyper-V and Failover Clustering. It's important to do capacity planning to ensure that there will be enough hardware resources to run all the virtual machines in a clustered environment.

To learn about updates to Failover Clustering, including new features for virtual machines, see What's New in Failover Clustering in Windows Server 2016.

ComponentMaximumNotes
Nodes per cluster64Consider the number of nodes you want to reserve for failover, as well as maintenance tasks such as applying updates. We recommend that you plan for enough resources to allow for 1 node to be reserved for failover, which means it remains idle until another node is failed over to it. (This is sometimes referred to as a passive node.) You can increase this number if you want to reserve additional nodes. There is no recommended ratio or multiplier of reserved nodes to active nodes; the only requirement is that the total number of nodes in a cluster can't exceed the maximum of 64.
Running virtual machines per cluster and per node8,000 per clusterSeveral factors can affect the real number of virtual machines you can run at the same time on one node, such as:
- Amount of physical memory being used by each virtual machine.
- Networking and storage bandwidth.
- Number of disk spindles, which affects disk I/O performance.
© 2016 Microsoft