Users Guide

19–Troubleshooting
Microsoft Virtualization with Hyper-V
285 BC0054508-00 J
Single Network Adapter
Configuration of the Microsoft virtualization with Hyper-V for a single network
adapter differs depending on the Windows Server version used.
Windows Server 2008
When configuring a BCM57xx and BCM57xxx network adapter on a Hyper-V
system, be aware of the following:
 An adapter that is to be bound to a virtual network must not be configured for
VLAN tagging through the driver’s advanced properties. Instead, Hyper-V
should manage VLAN tagging exclusively.
 Because Hyper-V does not support jumbo frames, QLogic recommends that
you do not use this feature. Connectivity issues may occur with the child
partition.
 The locally administered address (LAA) set by Hyper-V takes precedence
over the address set in the adapter’s advanced properties.
 In an IPv6 network, a team that supports CO or LSO, and that is bound to a
Hyper-V virtual network, reports 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.
IPv6 CO (parent and child partition) No* Yes Yes * When bound to a virtual net-
work, OS limitation.
Jumbo frames No* Yes Yes * OS limitation.
RSS No* No* Yes * OS limitation.
RSC No* No* Yes * OS limitation.
SR-IOV No* No* Yes * OS limitation.
NOTE
For full functionality, ensure that Integrated Services, which is a component
of Hyper-V, is installed in the guest operating system (child partition).
Table 19-1. Configurable Network Adapter Hyper-V Features (Continued)
Feature
Supported in Windows
Server
Comments and
Limitations
2008 2008 R2
2012
and
Later