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 5C0BE1B4CF for ; Fri, 4 Jan 2019 21:06:50 +0100 (CET) Received: from mail.fortinet.com ([192.168.221.213]) by smtp.fortinet.com with ESMTP id x04K6nBp022961-x04K6nBr022961 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Fri, 4 Jan 2019 12:06:49 -0800 Received: from FGT-EXCH-MBX132.fortinet-us.com (192.168.221.132) by FGT-EXCH-CAS213.fortinet-us.com (192.168.221.213) with Microsoft SMTP Server (TLS) id 14.3.389.1; Fri, 4 Jan 2019 12:06:49 -0800 Received: from FGT-EXCH-MBX132.fortinet-us.com (192.168.221.132) by FGT-EXCH-MBX132.fortinet-us.com (192.168.221.132) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1531.3; Fri, 4 Jan 2019 12:06:48 -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; Fri, 4 Jan 2019 12:06:48 -0800 From: Liwu Liu To: "users@dpdk.org" Thread-Topic: Cannot run DPDK applications using Mellanox NIC under Hyper-V Thread-Index: AdSkaIlXmtS1/HLnTKOuGVPhM0hYtg== Date: Fri, 4 Jan 2019 20:06:48 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [96.45.36.15] 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:content-type:mime-version; bh=vHSQfPFebNOzBoDp14BPtwL2NMCxzjoA+KWMfsJtVLQ=; b=pOjoy5Pc+25TSq/EKVtWVwhIjIaaoFeAvxesiCA/zrI/UCGviSSven1io3YlMTlePoKdtsUH4zbO 3BllXBMy7Z/agFyt9+wEr3BKM29Yt9qnuu0xJjljzJTG50y/yTQ9dZBLq8nBX23BRR9X7v5UMbNH VFG7AYWH6181n1tr766gimFNZDj3+I+YH4z+pK/mEd2OOYlPssW7dLz8JUNz8h5XVen1ltDzudQx r5c4zfJTUw/9dhUEPzYwfvu1CAunePTiC4tDVlchksaGNxgzws6+/8o1Wqx/SPiHqlx+h6Fyglj1 eEt5Q6QWTQqhl4nAYTpv/GfzO6PO6lcNGTG41w== Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: [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: Fri, 04 Jan 2019 20:06:50 -0000 Hi Team, We used to have similar problem for Ubuntu 18.04 hypervisor and resol= ved by set log_num_mgm_entry_size=3D-1. (Refer to https://mails.dpdk.org/= archives/users/2018-November/003647.html ) Somehow for Windows Servers with MLNX VPI, I do not know where to set s= uch and DPDK over MLX4 on linux vm has same failure of attaching flow. [ 374.568992] __mlx4_ib_create_flow: mcg table is full. Fa= il 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= PF 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 confid= ential and proprietary material and information and are intended only for= the use of the intended recipient(s). If you are not the intended recipi= ent, you are hereby notified that any review, use, disclosure, disseminat= ion, distribution or copying of this message and any attachments is stric= tly prohibited. If you have received this email in error, please immediat= ely notify the sender and destroy this e-mail and any attachments and all= copies, whether electronic or printed. Please also note that any views, = opinions, conclusions or commitments expressed in this message are those = of the individual sender and do not necessarily reflect the views of Fort= inet, Inc., its affiliates, and emails are not binding on Fortinet and on= ly a writing manually signed by Fortinet's General Counsel can be a bindi= ng commitment of Fortinet to Fortinet's customers or partners. Thank you.= ***