Date: Mon, 07 Feb 2022 15:08:56 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 261746] hn(4): Communication stops when enabling SR-IOV secondary mlx5en(4) interface (640FLR-SFP28) on Windows Server 2022 Message-ID: <bug-261746-7501-7mJT5uoIE0@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-261746-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-261746-7501@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D261746 --- Comment #5 from Michael <michael.adm@gmail.com> --- Firstly, I did a little investigation to find out what kind of commit cuts the connection when using the SR-IOV technology and mlx5en VF. This is comm= it e059c120b4223fd5ec3af9def21c0519f439fe57. With the GENERIC kernel and the previous commit a8e715d21b963251e449187c98292fff77dc7576, everything works as it should - SR-IOV VF works for both ConnectX-3 mlx4en and ConnectX-4 mlx5en. root@frw05v5:/usr/src # git checkout e059c120b4223fd5ec3af9def21c0519f439fe= 57 Previous HEAD position was a8e715d21b9 mlx5en: Add race protection for SQ r= emap HEAD is now at e059c120b42 mlx5en: Create and destroy all flow tables and r= ules when the network interface attaches and detaches. After the e059c120b42 checkout, the mlx5en VF network connection breaks. > How do you verify that the second interface stopped working? The working state is checked in an elementary way: Ping from the VM IP address outside the VM (in the same subnet, of course) and ping from outside the VM IP of the network interface of our VM we need. > If only the second SRIOV nic (Mellanox CX-4) causes problem, what happen = if=20 you just enable this nic, not enable the first one (Mellanox CX-3)? Does the second interface work in this case? I cited the use of the first network interface as an example to illustr= ate that the SR-IOV VF technology is operational on the hypervisor. And no, even with only one ConnectX-4 mlx5en network interface, this behavior is as described at the beginning. > How do you enable and disable the SRIOV interfaces? Hyper-V Manager -> right click on the VM -> Options -> Network adapter = -> Hardware acceleration -> "checkbox" Enable SR-IOV Secondly. FreeBSD-12.3-STABLE-amd64-20220203-r371543-disc1.iso - no changes were made (installing the system out of the box) - Everything is OK - SR-IOV VF works= for both ConnectX-3 mlx4en and ConnectX-4 mlx5en. FreeBSD-13.0-STABLE-amd64-20220203-40b816bd4f0-249223-disc1.iso - no changes were made (installing the system out of the box) - Everything is OK - SR-IO= V VF works for both ConnectX-3 mlx4en and ConnectX-4 mlx5en. --=20 You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-261746-7501-7mJT5uoIE0>