|
How do I Configure VLANs on Intel® Ethernet Adapters in Hyper-V*?
Use Hyper-V Manager to configure VLANs on Intel Ethernet Adapters. Intel® PROSet and Advanced Network Services (ANS) driver are not required to configure VLANs. If you have installed Advanced Network Services (ANS) do not configure VLANs using the VLANs tab in Windows Device Manager. Only configure VLANs using Hyper-V Manager settings for the virtual machine (VM).
Which versions of Hyper-V* support VMDq and SR-IOV?
| Operating System |
VMDq
Supported? |
SR-IOV
Supported? |
| Windows Server 2008 with Hyper-V* |
No |
No |
| Windows Server 2008 R2 with Hyper-V* |
Yes |
No | |
How do I configure Virtual Machine Device Queues (VMDq) to work with the VLANs in Hyper-V?
Enable Virtual Machine Queues in the Advanced properties tab for your Intel Ethernet Adapter in Windows Device Manager. No additional configuration is needed. Hyper-V will automatically configure the virtual queue and VLAN filters for the adapter's driver.
| Note |
Intel® PROSet for Windows Device Manager must be installed before enabling VMDq on your Intel® Ethernet adapter. Intel® PROSet is required to enable operating system Virtual Machine Queue (VMQ) switch support. |
| Note |
The Virtual Machine Queues configuration option will automatically be displayed if your Intel Ethernet Adapter and operating system support VMDq. |
| Note |
If your adapter is part of a team, the Virtual Machine Queues configuration option may be grayed out and unavailable. Upgrade to Intel® Network Connections software version 15.0 or later or remove the adapter from the team to make this feature available. |
| Note |
Virtual Machine Queues are only available under Windows* Server 2008 R2. VMQ is not available under Windows* Server 2008. | |
What are the steps for configuring VLANs for a virtual machine?
- If you have not already done so, create a virtual network using the Hyper-V* Virtual Network Manager. You can access the Virtual Network Manager from the Actions pane in Hyper-V* Manager.
- Enter a name for the virtual network.
- Select external for the connection type and choose an available physical adapter from the list.
- Optionally, you can enable use of the virtual adapter for the management (host) operating system and configure a VLAN for the host OS.
- In the Network Adapter settings for the Virtual Machine (VM) select the Network to be used by the VM. In the example below V1 Network is selected. See steps 1 through 3 for creating, naming, and configuring a virtual network.
- Select Enable virtual LAN identification and enter a VLAN ID. In the example below 12 was entered as the VLAN ID.
Which Intel® Ethernet adapters support VMDq?
|
Description |
Virtual Machine
Queues per Port |
Intel® Ethernet Server Adapter X520 Series (SFP+)
Intel® Ethernet Server Adapter X520-T2 |
64 |
Intel® 10 Gigabit AF DA Dual Port Server Adapter
Intel® 10 Gigabit AT2 Server Adapter
Intel® 10 Gigabit AT Server Adapter
Intel® 10 Gigabit CX4 Dual Port Server Adapter
Intel® 10 Gigabit XF LR Server Adapter
Intel® 10 Gigabit XF SR Server Adapter
Intel® 10 Gigabit XF SR Dual Port Server Adapter |
16 |
Intel® Ethernet Server Adapter I340
Intel® Gigabit ET Quad Port Server Adapter
Intel® Gigabit ET Dual Port Server Adapter
Intel® Gigabit EF Dual Port Server Adapter |
8 | |
Can I use Intel Advanced Network Services (ANS) teaming with VMDq in Hyper-V*?
Yes, You must use Intel PROSet version 15.0 or later. Teaming was not compatible with VMDq and Hyper-V* in versions of Intel PROSet prior to version 15.0.
Use Virtual Machine Load Balancing (VMLB) teaming mode instead of Adapter Fault Tolerance (AFT), Adaptive Load Balancing (ALB), and Receive Load Balancing (RLB) teaming modes. VMLB teaming mode is selectable only when Microsoft Hyper-V* is available.
| Note |
If you use Intel PROSet versions prior to version 14.7 to configure teams or VLANs with Virtual Machine Queues enabled, system instability may occur including a potential Windows* bug check (popularly known as Blue Screen of Death or BSOD). |
| Note |
To recover from a Windows* bug check (BSOD) caused by configuring ANS teams or VLANS, unplug the Ethernet cables. After starting Windows remove the ANS configured teams and VLANs or disable Virtual Machine Queues. | |
Related Topics
Intel VMDq Explanation (YouTube*)
Intel VMDq Demonstration (YouTube*)
Virtual Machine Device Queues (VMDq)
Intel® Virtualization Technology (Intel® VT) for Connectivity (Intel® VT-c)
This applies to:
| 
