12–Using Microsoft Virtualization with Hyper-V
Teamed Network Adapters
185
83840-546-00 N
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
QCC GUI; however, CO and LSO will not work. This is a limitation of
Hyper-V because 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 QLASP 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 QLASP 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.
Windows Server 2008 R2
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.
A QLASP virtual adapter configured for VLAN tagging can be bound to a
Hyper-V virtual network, and is a supported configuration. However, the
VLAN tagging capability of QLASP cannot be combined with the VLAN
capability of Hyper-V. To use the VLAN capability of Hyper-V, the QLASP
team must be untagged.
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.
