Users Guide
19–Troubleshooting
Microsoft Virtualization with Hyper-V
288 BC0054508-00 J
In an IPv6 network, a team that supports CO 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 issue is a limitation of
Hyper-V, which 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.
To change or remove a team, use the Hyper-V Manager as follows:
1. Remove the team’s binding from all guest OSs that use any of the
VNICs in the team
2. Change the configuration.
3. Rebind the team’s VNICs to the guest OS.
Windows Server 2008 R2
When configuring a team of BCM57xx and BCM57xxx 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. In order to use the VLAN capability of Hyper-V, the
QLASP team must be untagged.
To change or remove a team, use the Hyper-V Manager as follows:
1. Remove the team’s binding from all guest OSs that use any of the
VNICs in the team
2. Change the configuration.
3. Rebind the team’s VNICs to the guest OS.
Configuring VMQ with SLB Teaming
When a Hyper-V server is installed on a system configured to use Smart Load
Balance and Failover (SLB) type teaming, you can enable virtual machine queue
(VMQ) to improve overall network performance. VMQ enables delivering packets
from an external virtual network directly to virtual machines defined in the SLB
team, eliminating the need to route these packets and, thereby, reducing
overhead.