Date: Tue, 19 Jun 2018 14:57:04 +0000 From: bugzilla-noreply@freebsd.org To: virtualization@FreeBSD.org Subject: [Bug 220453] [Hyper-V] need to update Mellanox ConnectX-3 VF driver to support Live Migration Message-ID: <bug-220453-27103-NsNUZoFzDF@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-220453-27103@https.bugs.freebsd.org/bugzilla/> References: <bug-220453-27103@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220453 --- Comment #13 from Dexuan Cui <decui@microsoft.com> --- (In reply to pete from comment #12) Yes, it's expected that you saw a hn interface. Hyper-V is a little different from other hypervisors with respect to SR-IOV support for NIC. Hyper-V provides a pair of NICs to the VM: one is the Para-Virtualized NIC (hn), and the other is the hardware VF NIC, and both the NICs share the same MAC address, and usually almost all of the network traffic goes through the VF NIC so that we can take advantage of the benefits of the hardware VF NIC (i.e. lower latency and CPU utilization, and higher throughput) , but if necessary the network traffic can dynamically switch to the PV NIC, which facilitates things like live migration of the VM. To enable SR-IOV in FreeBSD on Hyper-V, in 2016 we updated the PV NIC driver (i.e. the netvsc driver) a little, and we added a pci front-end driver (i.e. the pcib driver) to discover the VF device, and in Aug 2017 sephe implemented an automatic “bond mode”, with which we don’t need to manually use the lagg driver any more, and the configuration work is done automatically for the PV NIC (we don't and shouldn't directly touch the VF interface). -- You are receiving this mail because: You are the assignee for the bug.help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-220453-27103-NsNUZoFzDF>