Description of problem:
E830 card: add dpdk port to ovs bridge failed

Version-Release number of selected component (if applicable):
[root@wsfd-advnetlab151 ~]# uname -r
5.14.0-522.el9.x86_64
[root@wsfd-advnetlab151 ~]# rpm -qa|grep openvs
openvswitch-selinux-extra-policy-1.0-36.el9fdp.noarch
openvswitch3.4-3.4.0-9.el9fdp.x86_64
penvswitch3.3-3.3.0-49.el9fdp.x86_64

How reproducible:
Steps to Reproduce:
[root@wsfd-advnetlab151 ~]# driverctl -v set-override 0000:32:00.1 vfio-pci
driverctl: setting driver override for 0000:32:00.1: vfio-pci
driverctl: loading driver vfio-pci
driverctl: unbinding previous driver ice
driverctl: reprobing driver for 0000:32:00.1
driverctl: saving driver override for 0000:32:00.1
[root@wsfd-advnetlab151 ~]# ovs-vsctl --no-wait set Open_vSwitch . other_config:dpdk-init=true
ovs-vsctl --no-wait set Open_vSwitch . other_config:dpdk-socket-mem=1024,1024
[root@wsfd-advnetlab151 ~]# ovs-vsctl set Open_vSwitch . other_config:pmd-cpu-mask=0x4000000000000040000000000000
[root@wsfd-advnetlab151 ~]# ovs-vsctl add-br ovsbr0 – set bridge ovsbr0 datapath_type=netdev
[root@wsfd-advnetlab151 ~]# ovs-vsctl add-port ovsbr0 dpdk0 – set Interface dpdk0 type=dpdk ofport_request=10 options:dpdk-devargs=0000:32:00.1
ovs-vsctl: Error detected while setting up 'dpdk0': Error attaching device '0000:32:00.1' to DPDK. See ovs-vswitchd log for details.
ovs-vsctl: The default log directory is "/var/log/openvswitch".

Actual results:
Add dpdk port to ovs bridge failed.
[root@wsfd-advnetlab151 ~]# tail -f /var/log/openvswitch/ovs-vswitchd.log
2024-10-24T02:06:16.742Z|00175|dpdk|ERR|EAL: Driver cannot attach the device (0000:32:00.1)
2024-10-24T02:06:16.742Z|00176|dpdk|ERR|EAL: Failed to attach device on primary process
2024-10-24T02:06:16.742Z|00177|netdev_dpdk|WARN|Error attaching device '0000:32:00.1' to DPDK
2024-10-24T02:06:16.742Z|00178|netdev|WARN|dpdk0: could not set configuration (Invalid argument)
2024-10-24T02:06:16.742Z|00179|dpdk|ERR|Invalid port_id=1024

Expected results:
Add dpdk port to ovs bridge successfully.
It has no this issue when running the same case on e810 card.

Additional info:
beaker job:
https://beaker.engineering.redhat.com/jobs/10065706
sos report:
http://netqe-bj.usersys.redhat.com/share/tli/sos_report/sosreport-wsfd-advnetlab151-2024-10-23-hijzcrn.tar.xz