大网数据广告活动
Hyper-V与虚拟化

Plan for Hyper-V networking in Windows Server

· 52CE 我爱测

Describes what's needed for basic networking in Windows Server Hyper-V and gives links to instructions.

This article covers what you need for basic networking in Hyper-V, including considerations for live migration and other server features.

Hyper-V networking basics

Hyper-V networking uses a virtual switch and a virtual network adapter. The virtual switch connects to an Ethernet-based network, and the virtual network adapter connects to a port on the virtual switch, enabling a virtual machine to use the network. When you create a virtual machine and connect the virtual machine to a virtual switch, a virtual network adapter is automatically added. All virtual switches are part of the Hyper-V host, but each virtual network adapter belongs to only one virtual machine. For instructions, see Create a virtual switch for Hyper-V virtual machines.

The virtual switch is a software-based layer-2 Ethernet network switch. The virtual switch provides built-in features for monitoring, controlling, and segmenting traffic, as well as security, and diagnostics. You can add to the set of built-in features by installing plug-ins, also called extensions. Extensions are available from independent software vendors. For more information about the switch and extensions, see Hyper-V Virtual Switch.

Switch and network adapter choices

Hyper-V offers three types of virtual switches and two types of virtual network adapters. You choose the type when you create the switch or adapter. You can use Hyper-V Manager or the Hyper-V module for Windows PowerShell to create and manage virtual switches and virtual network adapters. Some advanced networking capabilities, such as extended port access control lists (ACLs), can only be managed by using cmdlets in the Hyper-V module.

You can change an existing virtual switch to a different type after creation, but changing the virtual switch type affects the networking capabilities of all connected virtual machines. You can connect a virtual network adapter to a different virtual switch, but you can't change a virtual network adapter from one type to another; instead, add another virtual network adapter and choose the appropriate type.

Virtual switch types are:

  • External virtual switch - Connects to a wired, physical network by binding to a physical network adapter.

  • Internal virtual switch - Connects to a network that can be used only by the virtual machines running on the host that has the virtual switch, and between the host and the virtual machines.

  • Private virtual switch - Connects to a network that can be used only by the virtual machines running on the host that has the virtual switch, but doesn't provide networking between the host and the virtual machines.

Virtual switch options:

Setting name Description
Allow management operating system to share this network adapter Allow the Hyper-V host to share the use of the virtual switch and NIC or NIC team with the virtual machine. With this enabled, the host can use any of the settings that you configure for the virtual switch, such as Quality of Service (QoS) settings, security settings, or other features of the Hyper-V virtual switch.
Enable single-root I/O virtualization (SR-IOV) Allow virtual machine traffic to bypass the virtual machine switch and go directly to the physical NIC. SR-IOV is only available for virtual machines running a supported Windows Server guest. For more information, see Single-Root I/O Virtualization.

Virtual network adapter types:

Adapter type Key constraints and when to use
Network adapter (Hyper-V specific network adapter) Available for generation 1 and generation 2 VMs. Requires a driver included in Hyper-V integration services, provided only for supported guest operating systems. Faster performance; recommended unless you need network boot or are running an unsupported guest OS.
Legacy network adapter Generation 1 VMs only; not available for generation 2 VMs. Emulates an Intel 21140-based PCI Fast Ethernet Adapter. Use when you need to boot to a network to install an operating system (for example, via Windows Deployment Services).

Hyper-V networking and related technologies

Some features rely on specific networking configurations or perform better under certain configurations.

Failover clustering - It's a best practice to isolate cluster traffic and use Hyper-V Quality of Service (QoS) on the virtual switch.

Live migration - Use performance options to reduce network and CPU usage and the time it takes to complete a live migration. For instructions, see Set up hosts for live migration without Failover Clustering.

Storage Spaces Direct - Storage Spaces Direct relies on the SMB3.0 network protocol and RDMA. For details, see Storage Spaces Direct overview.

Source: Microsoft Learn / Windows Server documentation by Microsoft and contributors (upstream author metadata: robinharwood). Documentation licensed CC BY 4.0. Code samples are covered by the MIT License. Converted from Markdown, with links normalized and embedded media omitted.

资料来源与适用范围

资料来源
Microsoft Learn / Windows Server documentation
适用范围
Windows Server · Source date 01/21/2026
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY 4.0 (documentation), MIT (code samples)

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。