[dpdk-users] Cannot run DPDK applications using Mellanox NIC under Hyper-V

Olga Shern olgas at mellanox.com
Sat Jan 5 10:45:51 CET 2019

HI Liwu, 

Are you running your application on Azure VMs?


-----Original Message-----
From: users [mailto:users-bounces at dpdk.org] On Behalf Of Liwu Liu
Sent: Saturday, January 5, 2019 12:29 AM
To: users at 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 resolved by set log_num_mgm_entry_size=-1. (Refer to https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmails.dpdk.org%2Farchives%2Fusers%2F2018-November%2F003647.html&data=02%7C01%7Colgas%40mellanox.com%7C0f967c6706714e2e992008d67294013a%7Ca652971c7d2e4d9ba6a4d149256f461b%7C0%7C1%7C636822377359958550&sdata=AsxbxqWhKsGgMAMulz92p6SXzfPR%2FCxebrJ88fMO%2B5k%3D&reserved=0

  Somehow for Windows Servers with MLNX VPI, I do not know where to set such and DPDK over MLX4 on linux vm has same failure of attaching flow.

    [  374.568992] <mlx4_ib> __mlx4_ib_create_flow: mcg table is full. Fail to register network rule. size = 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,


***  Please note that this message and any attachments may contain confidential and proprietary material and information and are intended only for the use of the intended recipient(s). If you are not the intended recipient, you are hereby notified that any review, use, disclosure, dissemination, distribution or copying of this message and any attachments is strictly prohibited. If you have received this email in error, please immediately 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 Fortinet, Inc., its affiliates, and emails are not binding on Fortinet and only a writing manually signed by Fortinet's General Counsel can be a binding commitment of Fortinet to Fortinet's customers or partners. Thank you. *** 

More information about the users mailing list