15–Microsoft Virtualization with Hyper-V
Teamed Network Adapters
264
83840-546-00 D
Windows Server 2008
When configuring a team of 8400/3400 Series network adapters on a Hyper-V
system, be aware of the following:
Create the team prior to binding the team to the Hyper-V virtual network.
Create a team only with an adapter that is not already assigned to a Hyper-V
virtual network.
In an IPv6 network, a team that supports CO and/or LSO and is bound to a
Hyper-V virtual network will report CO and LSO as an offload capability in
QCS; however, CO and LSO will not work. This is a limitation of Hyper-V.
Hyper-V does not support CO and LSO in an IPv6 network.
To successfully perform VLAN tagging for both the host (parent partition)
and the guest (child partition) with the ASP teaming software, you must
configure the team for tagging. Unlike VLAN tagging with a single adapter,
tagging cannot be managed by Hyper-V when using ASP software.
When making changes to a team or removing a team, remove the team’s
binding from all guest OSs that use any of the VNICs in the team, change
the configuration, and then rebind the team’s VNICs to the guest OS. This
can be done in the Hyper-V Manager.
Hyper-V virtual
switch over a teamed
adapter
Yes
Yes
Yes
–
Hyper-V virtual
switch over a VLAN
Yes
Yes
Yes
–
iSCSI boot
No
No*
No*
*Remote boot to SAN is sup-
ported.
Virtual Machine
Queue (VMQ)
No
Yes
Yes
RSC
No
No
Yes
Table 15-2. Configurable Teamed Network Adapter Hyper-V Features
(Continued)
Feature
Supported in Windows
Server Version
Comments/Limitation
2008
2008
R2
2012
Summary of Contents for 8400 Series
Page 390: ......
