From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 916B4A0547 for ; Mon, 19 Apr 2021 08:28:54 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 129E840683; Mon, 19 Apr 2021 08:28:54 +0200 (CEST) Received: from mail-il1-f178.google.com (mail-il1-f178.google.com [209.85.166.178]) by mails.dpdk.org (Postfix) with ESMTP id 0527240040 for ; Mon, 19 Apr 2021 08:28:52 +0200 (CEST) Received: by mail-il1-f178.google.com with SMTP id i22so23490113ila.11 for ; Sun, 18 Apr 2021 23:28:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=7h/Xo/iZT3mnOrPkz4QoDsftaZzkCYK86xZtmduOy/E=; b=MbpWWiwNeXoHbHAq7lEpQ50hurokulzmpIqOBZ9pboChROctjx2tkesas4O9Gn8QMT N6viZzIrnd3k7Bslwh2D8Ovz8wVQ1thLGLWNGJNQh5Ej0DWCYzIcchRXH4zHki54Pg4n dNp/jCvFax/K3UGuGSMf29MCKj6zRSd1hdxqA05EfD9jfSYPRrTOC4GVXJWcZpfIWBJ4 VjwMraHgxA+FqMZe68joFZSCNjizWE+GwkuAAysCmdusD94rjoSsLz06m0ySf0UK6+WZ fQZG4+95DWIjlQr/5CjXTbAqVUaIFN112glEPGbso8pfwKFNbVnrAmJK9vUAOs7s2bNB NlaQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=7h/Xo/iZT3mnOrPkz4QoDsftaZzkCYK86xZtmduOy/E=; b=Z5KBikEZ3n3uubDt7yKC8ueXMvdVczeSRZ0T5cQmntMXHIvi4Z30PLdqZH/7f7sGNx fAcVcN5epJkg1KV5TSBQAzsp/8VH+EMeeh+J2C7SXytQ5umFYzYTdFXPAuNltdhu81XJ 8sCvRo3m501sTg0dRpU3Yp1g2qpwz+LE+zEMavqlnQjN0qIGiHlVF+Bnf6DK9IPbDEc5 T76vmstkpMnKbANUo2R37yJCk0BUVSnvJCrPehE7lgVJGAI26pduMlTKvCnzgeeDdhfK ot33zQwamajKA8CVWlYp1T9VyJ1mP8++bmEqr6FqZzwL9qBQMC7CeevnCjhlcHqRDx2X LwOw== X-Gm-Message-State: AOAM531llU1daIqEmXm3tErgAy8X13qCvFeSwQmQ+45kdIr3yXtGsBEQ vWVy8hwfpsGY/RNXfBJaYWUCuNZZIRfCNIS/bApRJHUiHqQ= X-Google-Smtp-Source: ABdhPJzKeE9L+fXbOhg9+/BV6WVl1EIvlSlyx7+4bE4CaQI3KqzAb/7qIrpcLa5Rcs2TqPIXOy5gZlrWe44EnyFUUPM= X-Received: by 2002:a92:d811:: with SMTP id y17mr16323870ilm.221.1618813732298; Sun, 18 Apr 2021 23:28:52 -0700 (PDT) MIME-Version: 1.0 References: <20210418083753.308083bc@hermes.local> In-Reply-To: <20210418083753.308083bc@hermes.local> From: madhukar mythri Date: Mon, 19 Apr 2021 11:58:22 +0530 Message-ID: To: stephen@networkplumber.org Cc: users@dpdk.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 Subject: Re: [dpdk-users] Failed to bring-up DPDK ports on Azure VM X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org Sender: "users" Hi Stephen, Thanks for quick response. Yes this error is from a TAP driver from DPDK, but why this error/issue occurs only when configured with -2queues only ? Whereas with single or 4 queues it works Rx/Tx traffic works well. And also, this issue occurs only on single port-0, whereas on other ports this error/issue is not seen. On Sun, Apr 18, 2021 at 9:08 PM Stephen Hemminger < stephen@networkplumber.org> wrote: > On Sun, 18 Apr 2021 17:51:09 +0530 > madhukar mythri wrote: > > > Hi, > > > > When we tried to launch a DPDK app on Azure VM with 2-queues, > > seeing following errors and thus we are not able to receive any traffic > > on these NIC ports(MLX5). > > On Azure VM, using "net_failsafe" PMD. > > > > ======================= > > PORT 0 Max supports 16 rx queues and 16 tx queues (driver_name = > > net_failsafe, driver_type = 16) > > PORT 0 is polling for link-change, interrupts disabled > > *rss_add_actions(): Failed to load BPF section l3_l4 (11): Resource > > temporarily unavailable* > > net_failsafe: Failed to create flow on sub_device 1 > > add_flow(): create() fails for port 0; Reason: action not supported > > =================== > > > > This issue is seen with 2-queues only, whereas with 4-queues we are not > > seeing this issue. > > > > Does anybody faced similar issue and if any solution/work-around please > let > > me know. > > > > DPDK version: 20.11 > > With RHEL: 7.9 version. > > > > Thanks, > > Madhukar. > > > If you are using failsafe, make sure that you have the Mellanox drivers > enabled > in your DPDK build, also TAP device. You need to build with rdma-core > version 23 or > later, and you need to have the kernel modules for flower, multiq, and TAP. > > Turn on full DPDK logging and check the kernel log (dmesg). >