Windows Server-Hyper-V 3 virtual network card bandwidth application restrictions

In the Hyper-V 3 of Windows Server 2012, a series of new features is called, such as the network card traffic throttling feature.

Infrastructure-aware issues

During the hosting server planning process, administrators mainly consider the CPU, memory, disk space, and other necessary factors in the server infrastructure, but the network adapter (NIC) is usually a neglected link, mainly because the Gigabit Ethernet card is already very cheap, and most servers have at least two gigabit NICs built in. For a virtual environment, the bandwidth provided by the network card is very important, and this factor will directly affect the selected host server schema mode.

In practice, a host server may deploy more than 10 virtual machines, and only two physical gigabit adapters are configured. In addition to managing the network card, another physical network card is shared by all virtual machines, and client access will cause significant latency when multiple virtual machines are applied concurrently. If you are connecting to an iSCSI storage device, you need a separate network card and iSCSI storage device connectivity to form a dedicated storage network to increase the concurrency efficiency of disk IO. It is therefore recommended that each host server be configured with at least 3 network adapters, and the more the number the better.

At present, Gigabit Ethernet cards have been widely used. It is recommended that you configure the network card according to the following principles:

1. Use more than 2 network adapters on each host server.

2, a network card can be used exclusively as host management.

3, another one or more network card can be dedicated to the virtual machine (to obtain the highest integration rate, you can consider using a million Gigabit network card).

4. iSCSI storage devices are connected using a dedicated network card.

Bandwidth limit

In Hyper-V 3.0 environments, you can set bandwidth limits for virtual machine adapters based on the priority or application status of the virtual machine. With this feature enabled, even if there is a large amount of concurrent data traffic between multiple virtual machines, the maximum value for each virtual machine will not exceed the set peak.

Open the Hyper-V 3.0 manager, select the target virtual machine, open the Properties window, select the Network adapters option, select the Enable Bandwidth management option, and the bandwidth management feature is turned off by default, as shown in Figure 1.

Figure 1

Set "Minimum Bandwidth" and "Maximum bandwidth", as shown in Figure 2. It is recommended that you set the maximum threshold according to the virtual machine application status.

Figure 2