Users Guide

19–Troubleshooting
Microsoft Virtualization with Hyper-V
Doc No. BC0054508-00 Rev. R
January 21, 2021 Page 286 Copyright © 2021 Marvell
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 2012, 2012 R2, 2016, 2019, and Azure Stack HCI
When configuring a 57xx and 57xxx 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.
 The locally administered address (LAA) set by Hyper-V takes precedence
over the address set in the adapter’s advanced properties.
 The LSO and CO features in the guest OS are independent of the network
adapter properties.
 To allow jumbo frame functionality from the guest OS, both the network
adapter and the virtual adapter must have jumbo frames enabled. Set the
Jumbo MTU property for the network adapter to allow traffic of large MTU
from within the guest OS. Set the jumbo packet of the virtual adapter to
segment the sent and received packets.
Jumbo frames Yes * OS limitation.
RSS Yes * OS limitation.
RSC Yes * OS limitation.
SR-IOV 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
Version 2012 and
Later
Comments and
Limitations