From nobody Mon Feb 07 15:08:56 2022 X-Original-To: net@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id BF8ED19AF278 for ; Mon, 7 Feb 2022 15:30:25 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from delivery.e-purifier.com (delivery.e-purifier.com [41.168.2.24]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4JsqpS3FbRz4YvG for ; Mon, 7 Feb 2022 15:30:24 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from [192.168.202.39] (helo=SEC-NGP-AG09) by delivery.e-purifier.com with smtp (Exim 4.94) (envelope-from ) id 1nH5y2-0003ON-UB for net@freebsd.org; Mon, 07 Feb 2022 17:30:14 +0200 Received: from mail pickup service by SEC-NGP-AG09.neotel.e-purifier.co.za with Microsoft SMTPSVC; Mon, 7 Feb 2022 17:30:12 +0200 Received: from sec-ngp-spt03.e-purifier.com ([192.168.201.1]) by SEC-NGP-AG09.neotel.e-purifier.co.za with Microsoft SMTPSVC(7.5.7601.17514); Mon, 7 Feb 2022 17:10:03 +0200 Received: from localhost (localhost [127.0.0.1]) by sec-ngp-spt03.e-purifier.com (Postfix) with ESMTP id 620234F9AC0 for ; Mon, 7 Feb 2022 17:10:04 +0200 (SAST) X-Virus-Scanned: by SpamTitan at e-purifier.com X-Spam-Flag: NO X-Spam-Score: -1.262 X-Spam-Level: X-Spam-Status: No, score=-1.262 tagged_above=-999 required=3.8 tests=[BAYES_00=-0.25, MAILING_LIST_MULTI=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, ST_P0F_Unix=-1, ST_RCVD_IN_HOSTKARMA_W=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no Received: from sec-ngp-spt03.e-purifier.com (localhost [127.0.0.1]) by sec-ngp-spt03.e-purifier.com (Postfix) with ESMTP id 100BF4FBBF6 for ; Mon, 7 Feb 2022 17:09:56 +0200 (SAST) Received-SPF: pass (freebsd.org ... _spf.freebsd.org: 96.47.72.81 is authorized to use 'freebsd-net+bounces-1259-ho=nanoteq.com@FreeBSD.org' in 'mfrom' identity (mechanism 'ip4:96.47.72.81' matched)) receiver=sec-ngp-spt03.e-purifier.com; identity=mailfrom; envelope-from="freebsd-net+bounces-1259-ho=nanoteq.com@FreeBSD.org"; helo=mx2.freebsd.org; client-ip=96.47.72.81 Received: from mx2.freebsd.org (mx2.freebsd.org [96.47.72.81]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by sec-ngp-spt03.e-purifier.com (Postfix) with ESMTPS id 2A8344FBBF4 for ; Mon, 7 Feb 2022 17:09:50 +0200 (SAST) Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits)) (Client CN "mx1.freebsd.org", Issuer "R3" (verified OK)) by mx2.freebsd.org (Postfix) with ESMTPS id 51FDA94D90 for ; Mon, 7 Feb 2022 15:09:46 +0000 (UTC) (envelope-from freebsd-net+bounces-1259-ho=nanoteq.com@FreeBSD.org) Received: from mlmmj.nyi.freebsd.org (mlmmj.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:24]) by mx1.freebsd.org (Postfix) with ESMTP id 4JsqLf09B3z3wBq for ; Mon, 7 Feb 2022 15:09:46 +0000 (UTC) (envelope-from freebsd-net+bounces-1259-ho=nanoteq.com@FreeBSD.org) Received: from mlmmj.nyi.freebsd.org (unknown [127.0.1.24]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id EC4C819A2B5F for ; Mon, 7 Feb 2022 15:09:45 +0000 (UTC) (envelope-from freebsd-net+bounces-1259-ho=nanoteq.com@FreeBSD.org) X-Original-To: net@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 001F919A1A4F for ; Mon, 7 Feb 2022 15:08:57 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4JsqKh1yDxz3vMW for ; Mon, 7 Feb 2022 15:08:56 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 006EA279A5 for ; Mon, 7 Feb 2022 15:08:55 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 217F8tgc092588 for ; Mon, 7 Feb 2022 15:08:55 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 217F8tGl092587 for net@FreeBSD.org; Mon, 7 Feb 2022 15:08:55 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f 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 Date: Mon, 07 Feb 2022 15:08:56 +0000 X-Bugzilla-Reason: CC AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: needs-qa X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: michael.adm@gmail.com X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: net@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Networking and TCP/IP with FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-net List-Help: List-Post: List-Subscribe: List-Unsubscribe: List-Id: Networking and TCP/IP with FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-net List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-net@freebsd.org MIME-Version: 1.0 ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1644246536; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=aRQtdn2Y4yYNlJRc3sohya4odLwTtaoQGSF3Cs6zl7k=; b=ukvwnu4EnT5yNelw+iAh025L37NkVj4FfH/vxTI9wTcPvgjZJTIagtHeyWMVlH8t/np+oy 08b+whw+WS4Y/arwsdc+npLjYUcyXC3J7Oauyk4lDvUtPe79d1/VGKF82nz42hGtRDADvu 2J6Rc7X40W/OLmdvaLHnhxvPRxzuSJeQVHePaOJ02ZCqlkvBrDSCLdubpeYbNtEeltVZON zuP3fuVfuiCJ+Ua3qgNtyezaRPoCrjcm389d6m1NLHjluyKAEykuxtgSq55iRqY36/AOW4 8Uqwa3STCy3RWnza49zAeWpI0AWfBdpIqRDB5c9mPJ2phOwh/2oYscNmnMb7FA== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1644246536; a=rsa-sha256; cv=none; b=H1dzTicXFNgSk85HPFUbjPnIDDdRO13pVM5BKe4qwFfahLaoE8vj4/lKDlBI5m2T54ming nNLVsEhUpnrd3mJgkxZnIhrctS5uEG7puZNAGa7JoG+jDQU89IRMmkNzmCzehxgJIyYDNQ Hu8ISgWLfLnrtQCoMgW/6MrewpJetsBwo6Hz+26etmgzFHZLr+MZNkIXIhtdfxbpsFgUSS 40Z32tFerGUQ49AwcjsLbHiwX86Kjxc04edtZrzlIa8oxdunvnnvoj/g7pgrIqSMqsULY0 MODO/4SGjZGRwgVzED7xqSzhutEe3HKOCGWJBz0GeIRmgH7w8JXAJ5SPWxlKcQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N X-OriginalArrivalTime: 07 Feb 2022 15:10:03.0635 (UTC) FILETIME=[C8927C30:01D81C34] x-archived: yes x-dbused: RGF0YSBTb3VyY2U9MTkyLjE2OC4yMDEuMjc= X-Rspamd-Queue-Id: 4JsqpS3FbRz4YvG X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=none; arc=pass ("freebsd.org:s=dkim:i=1"); dmarc=none; spf=softfail (mx1.freebsd.org: 41.168.2.24 is neither permitted nor denied by domain of bugzilla-noreply@freebsd.org) smtp.mailfrom=bugzilla-noreply@freebsd.org X-Spamd-Result: default: False [-3.26 / 15.00]; RCVD_TLS_LAST(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FREEFALL_USER(0.00)[bugzilla-noreply]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; HAS_XAW(0.00)[]; RCVD_COUNT_TWELVE(0.00)[14]; R_SPF_SOFTFAIL(0.00)[~all:c]; HAS_LIST_UNSUB(-0.01)[]; RCPT_COUNT_ONE(0.00)[1]; XAW_SERVICE_ACCT(1.00)[]; TO_DN_NONE(0.00)[]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FROM_NO_DN(0.00)[]; MAILLIST(-0.15)[generic]; MLMMJ_DEST(0.00)[net]; DMARC_NA(0.00)[freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; R_DKIM_NA(0.00)[]; ASN(0.00)[asn:36937, ipnet:41.168.0.0/17, country:ZA]; ARC_ALLOW(-1.00)[freebsd.org:s=dkim:i=1]; TO_DOM_EQ_FROM_DOM(0.00)[] X-ThisMailContainsUnwantedMimeParts: N https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D261746 --- Comment #5 from Michael --- 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.=