From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp.fortinet.com (smtp.fortinet.com [208.91.113.81]) by dpdk.org (Postfix) with ESMTP id E984F1B523 for ; Mon, 7 Jan 2019 18:46:05 +0100 (CET) Received: from mail.fortinet.com ([192.168.221.213]) by smtp.fortinet.com with ESMTP id x07Hk5VF015807-x07Hk5VH015807 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 7 Jan 2019 09:46:05 -0800 Received: from FGT-EXCH-MBX131.fortinet-us.com (192.168.221.131) by FGT-EXCH-CAS213.fortinet-us.com (192.168.221.213) with Microsoft SMTP Server (TLS) id 14.3.389.1; Mon, 7 Jan 2019 09:46:04 -0800 Received: from FGT-EXCH-MBX132.fortinet-us.com (192.168.221.132) by FGT-EXCH-MBX131.fortinet-us.com (192.168.221.131) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1531.3; Mon, 7 Jan 2019 09:46:03 -0800 Received: from FGT-EXCH-MBX132.fortinet-us.com ([fe80::78b9:5f97:8cec:b419]) by FGT-EXCH-MBX132.fortinet-us.com ([fe80::78b9:5f97:8cec:b419%11]) with mapi id 15.01.1531.003; Mon, 7 Jan 2019 09:46:03 -0800 From: Liwu Liu To: Olga Shern , "users@dpdk.org" Thread-Topic: [dpdk-users] Cannot run DPDK applications using Mellanox NIC under Hyper-V Thread-Index: AQHUpNt0FFW17uWOhEeMllnKoYY4mKWkF1rw Date: Mon, 7 Jan 2019 17:46:03 +0000 Message-ID: <6215b52b0e73479ba3a19faa0dbbf2dc@fortinet.com> References: <0309079c2f954a509bf9f42dd43cef99@fortinet.com> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [96.45.36.15] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; d=fortinet.com; s=dkim; c=relaxed/relaxed; h=from:to:subject:date:message-id:references:content-type:mime-version; bh=wHrmSUMhI66+WfgZNdSsYgNpKHiCU3ZMMb/KNTvy5ow=; b=rGMKar62/3a3MRT4JeoLvFvsuhWMEZr0cOHgZg7GsRIr3cif03guvm6oZQ3NeDAtBJ81It9kWpOA 1Vw5GxHKjtrBn58C2cT5BvPdRu4E3v06la159w8StqI8FM9pceEBeQIS9QGVWcP2ESVEXrx7PmYf 0aEZKz88eAtxps6l6rDs4CpDxS26zo7WQyAuS0KwyqXskrO+D7cwEWMwe/V7zQ8CU7psGzorNB80 F7U4RP/IusSowyHLjIM+M29FyKVLBx1wglkdR2PFzmPrQ5L1nNfpiqZ8vrU9MAUYLkXKkdvH9M8a 54ORcsz10DPVLBl36aGEINrRa+cPn6sqxX0oVw== Subject: Re: [dpdk-users] Cannot run DPDK applications using Mellanox NIC under Hyper-V X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Jan 2019 17:46:06 -0000 Hi Olga, We target at Azure though we use a local Windows Server for better debug= ging purpose. I tested on Ubuntu 18@Azure with SRIOV. It seems to be the case doing "e= thtool -U" to attach flow also fails due to same reasone (error 12 out of m= emory). Many thanks, Liwu -----Original Message----- From: Olga Shern =20 Sent: Saturday, January 5, 2019 1:46 AM To: Liwu Liu ; users@dpdk.org Subject: RE: [dpdk-users] Cannot run DPDK applications using Mellanox NIC u= nder Hyper-V HI Liwu,=20 Are you running your application on Azure VMs? Thanks, Olga -----Original Message----- From: users [mailto:users-bounces@dpdk.org] On Behalf Of Liwu Liu Sent: Saturday, January 5, 2019 12:29 AM To: users@dpdk.org Subject: [dpdk-users] Cannot run DPDK applications using Mellanox NIC under= Hyper-V Hi Team, We used to have similar problem for Ubuntu 18.04 hypervisor and resolve= d by set log_num_mgm_entry_size=3D-1. (Refer to https://emea01.safelinks.pr= otection.outlook.com/?url=3Dhttps%3A%2F%2Fmails.dpdk.org%2Farchives%2Fusers= %2F2018-November%2F003647.html&data=3D02%7C01%7Colgas%40mellanox.com%7C= 0f967c6706714e2e992008d67294013a%7Ca652971c7d2e4d9ba6a4d149256f461b%7C0%7C1= %7C636822377359958550&sdata=3DAsxbxqWhKsGgMAMulz92p6SXzfPR%2FCxebrJ88fM= O%2B5k%3D&reserved=3D0 ) Somehow for Windows Servers with MLNX VPI, I do not know where to set suc= h and DPDK over MLX4 on linux vm has same failure of attaching flow. [ 374.568992] __mlx4_ib_create_flow: mcg table is full. Fail= to register network rule. size =3D 64 (out of memory error code) Would like to get your help on this. It seems to be the case that the P= F interface is not configured to trust VF interfaces to be able to add new = flow rules. Many thanks for help, Liwu *** Please note that this message and any attachments may contain confiden= tial and proprietary material and information and are intended only for the= use of the intended recipient(s). If you are not the intended recipient, y= ou are hereby notified that any review, use, disclosure, dissemination, dis= tribution or copying of this message and any attachments is strictly prohib= ited. If you have received this email in error, please immediately notify t= he sender and destroy this e-mail and any attachments and all copies, wheth= er electronic or printed. Please also note that any views, opinions, conclu= sions or commitments expressed in this message are those of the individual = sender and do not necessarily reflect the views of Fortinet, Inc., its affi= liates, and emails are not binding on Fortinet and only a writing manually = signed by Fortinet's General Counsel can be a binding commitment of Fortine= t to Fortinet's customers or partners. Thank you. ***=20