<!-- #请描述你对使用openEuler相关场景的诉求-->

【场景描述】(如下载场景/使用文档场景/安装及迁移场景/其他场景)

基于dpdk使用openvswitch，添加物理网卡到openvswitch中

【ISSUE描述】

1. 系统环境

```

[root@node32 ~]# rpm -qa|grep dpdk

openvswitch-dpdk-3.2.1-4.oe2403.x86_64

dpdk-23.11-18.oe2403.x86_64

[root@node32 ~]# uname -a

Linux node32 6.6.0-28.0.0.34.oe2403.x86_64 #1 SMP Mon May 27 22:22:46 CST 2024 x86_64 x86_64 x86_64 GNU/Linux

[root@node32 ~]# lscpu

Architecture: x86_64

CPU op-mode(s): 32-bit, 64-bit

Address sizes: 46 bits physical, 48 bits virtual

Byte Order: Little Endian

CPU(s): 20

On-line CPU(s) list: 0-19

Vendor ID: GenuineIntel

BIOS Vendor ID: Intel(R) Corporation

Model name: Intel(R) Xeon(R) Silver 4210 CPU @ 2.20GHz

BIOS Model name: Intel(R) Xeon(R) Silver 4210 CPU @ 2.20GHz CPU @ 2.2GHz

BIOS CPU family: 179

CPU family: 6

Model: 85

Thread(s) per core: 1

Core(s) per socket: 10

Socket(s): 2

Stepping: 7

Frequency boost: enabled

CPU(s) scaling MHz: 114%

CPU max MHz: 2201.0000

CPU min MHz: 1000.0000

BogoMIPS: 4400.00

Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtop

ology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand l

ahf_lm abm 3dnowprefetch cpuid_fault epb cat_l3 cdp_l3 intel_ppin ssbd mba ibrs ibpb stibp ibrs_enhanced tpr_shadow flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid cqm mpx

rdt_a avx512f avx512dq rdseed adx smap clflushopt clwb intel_pt avx512cd avx512bw avx512vl xsaveopt xsavec xgetbv1 xsaves cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local dtherm ida arat pln pts vnmi pku o

spke avx512_vnni md_clear flush_l1d arch_capabilities

Virtualization features:

Virtualization: VT-x

Caches (sum of all):

L1d: 640 KiB (20 instances)

L1i: 640 KiB (20 instances)

L2: 20 MiB (20 instances)

L3: 27.5 MiB (2 instances)

NUMA:

NUMA node(s): 2

NUMA node0 CPU(s): 0-9

NUMA node1 CPU(s): 10-19

Vulnerabilities:

Gather data sampling: Vulnerable: No microcode

Itlb multihit: KVM: Mitigation: VMX disabled

L1tf: Not affected

Mds: Not affected

Meltdown: Not affected

Mmio stale data: Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled

Reg file data sampling: Not affected

Retbleed: Mitigation; Enhanced IBRS

Spec rstack overflow: Not affected

Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl

Spectre v1: Mitigation; usercopy/swapgs barriers and __user pointer sanitization

Spectre v2: Vulnerable: eIBRS with unprivileged eBPF

Srbds: Not affected

Tsx async abort: Mitigation; TSX disabled

[root@node32 ~]# uname -a

Linux node32 6.6.0-28.0.0.34.oe2403.x86_64 #1 SMP Mon May 27 22:22:46 CST 2024 x86_64 x86_64 x86_64 GNU/Linux

```

2. 已经绑定网卡驱动为vfio-pci

```

[root@node32 ~]# dpdk-devbind --status

Network devices using DPDK-compatible driver

============================================

0000:60:00.1 'Ethernet Connection X722 for 1GbE 37d1' drv=vfio-pci unused=i40e

Network devices using kernel driver

===================================

0000:60:00.0 'Ethernet Connection X722 for 1GbE 37d1' if=eno1 drv=i40e unused=vfio-pci

0000:62:00.0 '82599ES 10-Gigabit SFI/SFP+ Network Connection 10fb' if=enp98s0f0 drv=ixgbe unused=vfio-pci

0000:62:00.1 '82599ES 10-Gigabit SFI/SFP+ Network Connection 10fb' if=enp98s0f1 drv=ixgbe unused=vfio-pci

```

3. dpdk参数已配置并完成初始化

```

[root@node32 ~]# ovs-vsctl get Open_vSwitch . other_config

{dpdk-init="true", dpdk-socket-mem="4096,4096"}

[root@node32 ~]# ovs-vsctl get Open_vSwitch . dpdk_initialized

true

```

4. 此时，创建br，并将物理网口添加到br时报错，无法添加成功，提示无法解析设备

```

[root@node32 ~]# ovs-vsctl add-br br0 -- set bridge br0 datapath_type=netdev

[root@node32 ~]# ovs-vsctl add-port br0 dpdk-p0 -- set Interface dpdk-p0 type=dpdk options:dpdk-devargs=0000:60:00.1

ovs-vsctl: Error detected while setting up 'dpdk-p0': Error attaching device '0000:60:00.1' to DPDK. See ovs-vswitchd log for details.

ovs-vsctl: The default log directory is "/var/log/openvswitch".

[root@node32 ~]# tail -10 /var/log/openvswitch/ovs-vswitchd.log

2025-07-01T07:37:46.897Z|00080|bridge|INFO|bridge br0: using datapath ID 00005e4b237c0d47

2025-07-01T07:37:46.897Z|00081|connmgr|INFO|br0: added service controller "punix:/var/run/openvswitch/br0.mgmt"

2025-07-01T07:37:56.899Z|00082|memory|INFO|peak resident set size grew 72% in last 10.0 seconds, from 60508 kB to 103868 kB

2025-07-01T07:37:56.900Z|00083|memory|INFO|handlers:10 idl-cells-Open_vSwitch:104 ports:1 revalidators:4 rules:5

2025-07-01T07:38:02.259Z|00084|dpdk|ERR|EAL: failed to parse device "0000:60:00.1"

2025-07-01T07:38:02.259Z|00085|dpdk|ERR|EAL: failed to parse device "0000:60:00.1"

2025-07-01T07:38:02.259Z|00086|dpdk|ERR|EAL: Failed to attach device on primary process

2025-07-01T07:38:02.259Z|00087|netdev_dpdk|WARN|Error attaching device '0000:60:00.1' to DPDK

2025-07-01T07:38:02.259Z|00088|netdev|WARN|dpdk-p0: could not set configuration (Invalid argument)

2025-07-01T07:38:02.259Z|00089|dpdk|ERR|Invalid port_id=32

[root@node32 ~]# ovs-vsctl show

e3691f93-532b-4f69-a408-e2e8aded3f4f

Manager "ptcp:6640:127.0.0.1"

Bridge br0

datapath_type: netdev

Port dpdk-p0

Interface dpdk-p0

type: dpdk

options: {dpdk-devargs="0000:60:00.1"}

error: "Error attaching device '0000:60:00.1' to DPDK"

Port br0

Interface br0

type: internal

ovs_version: "3.2.1"

```