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 AC0304287F; Fri, 31 Mar 2023 09:40:54 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 54F5042B71; Fri, 31 Mar 2023 09:40:54 +0200 (CEST) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by mails.dpdk.org (Postfix) with ESMTP id 24665427F2 for ; Fri, 31 Mar 2023 09:40:51 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1680248451; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=ALHaI3QU+a0NcsMzHUruyibiyfApMiqKTnzJfK/ITuk=; b=YIWCkNB2t+5yGUHEkXUiR7uZo3rCU+bQfYoYJjWEl+LjOHwkjXOSMhnA5w1bsg/DyRUaba uFkR/y7xFVmP/68EFggpfxpdNIJsjfCG53bCZrndZZtiC+t3siR9be8tS4pvNb7GookOGs mpv46IEqJg2mEYY+8om84zelXWwalNw= Received: from mail-pf1-f197.google.com (mail-pf1-f197.google.com [209.85.210.197]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-185-qT7_jYM0PMyDToG2JgtNhg-1; Fri, 31 Mar 2023 03:40:50 -0400 X-MC-Unique: qT7_jYM0PMyDToG2JgtNhg-1 Received: by mail-pf1-f197.google.com with SMTP id x3-20020a62fb03000000b00622df3f5d0cso10082469pfm.10 for ; Fri, 31 Mar 2023 00:40:50 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1680248449; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=ALHaI3QU+a0NcsMzHUruyibiyfApMiqKTnzJfK/ITuk=; b=1ooGNi9z/CYXOXe4IAbyJvVFRDYPnctKM6kmJ9iJ7QgBDWJjfsF4i40iKXP1o6oO8L WXMO4GwKxzBOU2tllIp+LuF7+5Z0cJ8/EMdCG8EhFj2YNZ+KxCjPrc/JwxK4UBX40vPc BGLLBHE3LXXT/M3ccZA3CPrG521tGbcbjXl9DNtSJQ1il0DPygcknr+SxY+eVn/S20II tkRw+YMz0e7JPQ/va7z3MJAErlM8tOmtXspjzjlcC+skZEZzj4MLVpnku2jNSbLA5Xyg d1OSgiCUQT+/gi58bSr6CXyl7CSUQeQ/Tlzqx/igIn26xDLoRe+VVmiHJCnesIV88OPd AZYQ== X-Gm-Message-State: AAQBX9fisrm+Hpb1IcMb+ZVe+fzVA1/NxhkqW63bwJoV5WhagZoZGEm+ q4Rfwag7LRsA2izyugnU+cfMMLgamZetkL46jafDYfUBQOjAFOByECJOmYy//XwQUSnF8AZuahC /uIOrTs36tnmseZe8Fz0= X-Received: by 2002:a17:90a:600c:b0:240:9d66:cd54 with SMTP id y12-20020a17090a600c00b002409d66cd54mr4121863pji.8.1680248449222; Fri, 31 Mar 2023 00:40:49 -0700 (PDT) X-Google-Smtp-Source: AKy350YuGTf629A8U9/bqRPTfmx8m+QjY3nQ+hGtCA7Ad3t78PBy8hcDHV4AU4kstW6KMIS8fm9k3e5T7EsWIQucPio= X-Received: by 2002:a17:90a:600c:b0:240:9d66:cd54 with SMTP id y12-20020a17090a600c00b002409d66cd54mr4121857pji.8.1680248448912; Fri, 31 Mar 2023 00:40:48 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: David Marchand Date: Fri, 31 Mar 2023 09:40:37 +0200 Message-ID: Subject: Re: [Bug 1209] vmxnet3 interface not receiving any packets with dpdk-22.11.1 To: Jochen Behrens Cc: dev@dpdk.org, pagupta@vmware.com, amohakud@paloaltonetworks.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Hello Jochen, On Fri, Mar 31, 2023 at 9:07=E2=80=AFAM wrote: > > Bug ID 1209 > Summary vmxnet3 interface not receiving any packets with dpdk-22.11.1 > Product DPDK > Version 22.11 > Hardware x86 > OS All > Status UNCONFIRMED > Severity critical > Priority Normal > Component ethdev > Assignee dev@dpdk.org > Reporter amohakud@paloaltonetworks.com > Target Milestone --- > > Hi, > I recently upgraded our DPDK to 22.11.1 and observed that the guest vmxne= t3 > interface is not receiving any unicast packets. It's able to receive the > broadcast packets though. We enable promiscuous and all-multicast on the = port. > > rte_eth_promiscuous_enable(port); > rte_eth_allmulticast_enable(port); > > This happens when the vswitch has only 2 ports attached. > > On further triaging, > - I could find out that on the same setup, dpdk-20.11 works fine. > - Upon comparing the working scenario and non-working scenario on esx ho= st, I > could notice that there is some difference in port configuration of vswit= ch. > > Below is the snapshot of working case, where the ethFRP:frame routing { > requested:filter flags is 0x1d. > > port { > port index:365 > vnic index:0x00000003 > portCfg:build_1_15_2_vm-v3--p1e3-u2e3 > dvPortId: > clientName:sjc-cms-esx15-csm02-pan1 > clientType: 5 -> VMM Virtual NIC > clientSubType: 9 -> Vmxnet3 Client > world leader:2120158 > flags: 0x40013 -> IN_USE ENABLED WORLD_ASSOC CONNECTED > Impl customized blocked flags:0x00000000 > Passthru status: 0x8 -> DISABLED_BY_HOST > fixed Hw Id:00:50:56:b8:20:aa: > ethFRP:frame routing { > requested:filter { > flags:0x0000001d > unicastAddr:00:50:56:b8:20:aa: > numMulticastAddresses:0 > multicastAddresses: > LADRF:[0]: 0x0 > [1]: 0x0 > } > accepted:filter { > flags:0x0000001d > unicastAddr:00:50:56:b8:20:aa: > numMulticastAddresses:0 > multicastAddresses: > LADRF:[0]: 0x0 > [1]: 0x0 > } > } > > > For the non-working case the flag is set to 0x09. > > port { > port index:365 > vnic index:0x00000003 > portCfg:build_1_15_2_vm-v3--p1e3-u2e3 > dvPortId: > clientName:sjc-cms-esx15-csm02-pan1 > clientType: 5 -> VMM Virtual NIC > clientSubType: 9 -> Vmxnet3 Client > world leader:2120158 > flags: 0x40013 -> IN_USE ENABLED WORLD_ASSOC CONNECTED > Impl customized blocked flags:0x00000000 > Passthru status: 0x8 -> DISABLED_BY_HOST > fixed Hw Id:00:50:56:b8:20:aa: > ethFRP:frame routing { > requested:filter { > flags:0x00000009 > unicastAddr:00:50:56:b8:20:aa: > numMulticastAddresses:0 > multicastAddresses: > LADRF:[0]: 0x0 > [1]: 0x0 > } > accepted:filter { > flags:0x00000009 > unicastAddr:00:50:56:b8:20:aa: > numMulticastAddresses:0 > multicastAddresses: > LADRF:[0]: 0x0 > [1]: 0x0 > } > } > filter supported features: 0 -> NONE > filter properties: 0 -> NONE > rx mode: 0 -> INLINE > tune mode: 0 -> default > fastpath switch ID:0xffffffff > fastpath port ID:0xffffffff > } > > I think these are some of the flags set by vmxnet3 device and in dpdk-22.= 11, > its not updating the flags. As a maintainer of the net/vmxnet3 driver, could you please register to bugzilla? And please have a look. Thanks! --=20 David marchand