Implementing SR-IOV Failover for Windows Guests During Migration
summary
A two‑network model is implemented: a new virtual IO protocol driver plus a COM notify object that atomically switches datapaths between passthrough VF and emulated vNIC during migration, packaged as separate miniport and protocol INF installs. Code is upstreamed and validated on 100 Gbps hardware with 9K MTU showing 100 Gbps tests show near‑zero throughput loss. Known gaps: VF statistics not propagated, some start‑order and PnP‑ID workarounds, and requires newer Windows and a two‑step certification.
AI-written summary · about
chapters (22)
- 0:00Intro
- 2:14How to Contribute
- 2:29Contributors
- 2:44NDIS (Network Driver Interface Specification) Architecture
- 4:34Virtio-net (NetKVM) Driver for Windows
- 4:59The Problem - Live Migration and SR-IOV
- 5:43Overview of SR-IOV Migration Solutions
- 6:00Previous Efforts
- 6:21Overview of Software Solutions
- 7:51Windows NIC Teaming
- 9:06Windows MUX Intermediate Driver
- 12:10Network Binding of NIC Teaming or MUX
- 12:49Hyper-V VM Network
- 13:58Hyper-V SR-IOV VF Failover
- 15:12Network Binding in Hyper-V
- 15:43Comparison Summary
- 17:55VirtlO SR-IOV VF Failover
- 19:54Protocol Driver in 2-netdev Model
- 22:21Known Issues
- 24:00Installation
- 24:24WHQL Certification
- 24:54Performance
related talks
29mEnable SRIOV on PowerNV Platform
19mBring RoCE (RDMA over Converged Ethernet) Capability to Virtio-net Device
23mBreaking Theoretical Limits: The Gap Between Virtual NICs and Physical Network Cards
36mShared Virtual Addressing for High Performance Arm Infrastructure Platforms
15mMigrOS: Transparent Live-Migration Support for Containerised RDMA Applications
32mTo InfiniBand and Beyond!
41mVirtIo-Net PCIe Function Using Linux PCI Endpoint Framework
21mVirtio Devices Emulation in SPDK Based on Vfio-User Protocol