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 3F7254287F; Fri, 31 Mar 2023 09:06:58 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id CCD83427F2; Fri, 31 Mar 2023 09:06:57 +0200 (CEST) Received: from inbox.dpdk.org (inbox.dpdk.org [95.142.172.178]) by mails.dpdk.org (Postfix) with ESMTP id 5FEE6427E9 for ; Fri, 31 Mar 2023 09:06:56 +0200 (CEST) Received: by inbox.dpdk.org (Postfix, from userid 33) id 4AA8842881; Fri, 31 Mar 2023 09:06:56 +0200 (CEST) From: bugzilla@dpdk.org To: dev@dpdk.org Subject: [Bug 1209] vmxnet3 interface not receiving any packets with dpdk-22.11.1 Date: Fri, 31 Mar 2023 07:06:56 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: DPDK X-Bugzilla-Component: ethdev X-Bugzilla-Version: 22.11 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: amohakud@paloaltonetworks.com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: dev@dpdk.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: multipart/alternative; boundary=16802464160.F6771d.3388724 Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All MIME-Version: 1.0 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 --16802464160.F6771d.3388724 Date: Fri, 31 Mar 2023 09:06:56 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All https://bugs.dpdk.org/show_bug.cgi?id=3D1209 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 vmxnet3 interface is not receiving any unicast packets. It's able to receive the broadcast packets though. We enable promiscuous and all-multicast on the po= rt. rte_eth_promiscuous_enable(port); rte_eth_allmulticast_enable(port); This happens when the vswitch has only 2 ports attached.=20 On further triaging, - I could find out that on the same setup, dpdk-20.11 works fine.=20 - Upon comparing the working scenario and non-working scenario on esx host= , I could notice that there is some difference in port configuration of vswitch. Below is the snapshot of working case, where the ethFRP:frame routing { requested:filter flags is 0x1d.=20 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=20 [1]: 0x0=20 } accepted:filter { flags:0x0000001d unicastAddr:00:50:56:b8:20:aa: numMulticastAddresses:0 multicastAddresses: LADRF:[0]: 0x0=20 [1]: 0x0=20 } } 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=20 [1]: 0x0=20 } accepted:filter { flags:0x00000009 unicastAddr:00:50:56:b8:20:aa: numMulticastAddresses:0 multicastAddresses: LADRF:[0]: 0x0=20 [1]: 0x0=20 } } 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. Could you please help on this?? I would try to create a simplest test setup with testpmd and update here. --=20 You are receiving this mail because: You are the assignee for the bug.= --16802464160.F6771d.3388724 Date: Fri, 31 Mar 2023 09:06:56 +0200 MIME-Version: 1.0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All
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 vmxnet3
interface is not receiving any unicast packets. It's able to receive the
broadcast packets though. We enable promiscuous and all-multicast on the po=
rt.

rte_eth_promiscuous_enable(port);
rte_eth_allmulticast_enable(port);

This happens when the vswitch has only 2 ports attached.=20

On further triaging,
-  I could find out that on the same setup, dpdk-20.11 works fine.=20
-  Upon comparing the working scenario and non-working scenario on esx host=
, I
could notice that there is some difference in port configuration of vswitch.

Below is the snapshot of working case, where the  ethFRP:frame routing {
requested:filter flags is 0x1d.=20

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=20
         [1]: 0x0=20
      }
      accepted:filter {
         flags:0x0000001d
         unicastAddr:00:50:56:b8:20:aa:
         numMulticastAddresses:0
         multicastAddresses:
         LADRF:[0]: 0x0=20
         [1]: 0x0=20
      }
   }


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=20
         [1]: 0x0=20
      }
      accepted:filter {
         flags:0x00000009
         unicastAddr:00:50:56:b8:20:aa:
         numMulticastAddresses:0
         multicastAddresses:
         LADRF:[0]: 0x0=20
         [1]: 0x0=20
      }
   }
   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.

Could you please help on this??


I would try to create a simplest test setup with testpmd and update here.

You are receiving this mail because:
  • You are the assignee for the bug.
=20=20=20=20=20=20=20=20=20=20
= --16802464160.F6771d.3388724--