Thank you Rob for the advice, actually I have made symlink as in the thread introduced, however I still got the error "not viable"...
________________________________ From: Rob Kossler <[email protected]> Sent: 06 April 2021 18:23:05 To: Chang, Kaixin Cc: [email protected] Subject: Re: [USRP-users] dpdk, VFIO group is not viable Hi Kasim, There are some previous posts to the user's list around Feb 2-3, 2021 regarding some DPDK troubles I was having. In particular, Aaron Rossetto mentioned putting just a few symlinks in a new folder and using the dpdk_driver variable from uhd.conf to point to this folder. This may be helpful for your case. Rob On Tue, Apr 6, 2021 at 9:37 AM Chang, Kaixin <[email protected]<mailto:[email protected]>> wrote: Dear Ettus team, I followed the instruction of https://kb.ettus.com/Getting_Started_with_DPDK_and_UHD to enable dpdk for my X310, however I have an error when I execute benchmark_rate as sudo su [INFO] [UHD] linux; GNU C++ version 9.3.0; Boost_107100; UHD_4.0.0.0-93-g3b9ced8f EAL: Detected 4 lcore(s) EAL: Detected 1 NUMA nodes EAL: Multi-process socket /var/run/dpdk/rte/mp_socket EAL: No free hugepages reported in hugepages-1048576kB EAL: Probing VFIO support... EAL: VFIO support initialized EAL: PCI device 0000:00:1f.6 on NUMA socket -1 EAL: Invalid NUMA socket, default to 0 EAL: probe driver: 8086:15d7 net_e1000_em EAL: PCI device 0000:0e:00.0 on NUMA socket -1 EAL: Invalid NUMA socket, default to 0 EAL: probe driver: 8086:10fb net_ixgbe EAL: 0000:0e:00.0 VFIO group is not viable! EAL: Requested device 0000:0e:00.0 cannot be used EAL: PCI device 0000:0e:00.1 on NUMA socket -1 EAL: Invalid NUMA socket, default to 0 EAL: probe driver: 8086:10fb net_ixgbe EAL: 0000:0e:00.1 VFIO group is not viable! EAL: Requested device 0000:0e:00.1 cannot be used [ERROR] [DPDK] No available DPDK devices (ports) found! [ERROR] [UHD] Device discovery error: RuntimeError: No available DPDK devices (ports) found! EAL: FATAL: already called initialization. EAL: already called initialization. [ERROR] [DPDK] Error with EAL initialization [ERROR] [X300] X300 Network discovery error RuntimeError: Error with EAL initialization [00:00:00.000506] Creating the usrp device with: addr=192.168.30.2,second_addr=192.168.40.2,use_dpdk=1... EAL: FATAL: already called initialization. EAL: already called initialization. [ERROR] [DPDK] Error with EAL initialization [ERROR] [UHD] Device discovery error: RuntimeError: Error with EAL initialization EAL: FATAL: already called initialization. EAL: already called initialization. [ERROR] [DPDK] Error with EAL initialization [ERROR] [X300] X300 Network discovery error RuntimeError: Error with EAL initialization Error: LookupError: KeyError: No devices found for -----> Device Address: addr: 192.168.30.2 second_addr: 192.168.40.2 use_dpdk: 1 Why is 0000:0e:00.1 VFIO group is not viable!? I have checked dpdk-devbind --status-dev net and get Network devices using DPDK-compatible driver ============================================ 0000:0e:00.0 '82599ES 10-Gigabit SFI/SFP+ Network Connection 10fb' drv=vfio-pci unused=ixgbe 0000:0e:00.1 '82599ES 10-Gigabit SFI/SFP+ Network Connection 10fb' drv=vfio-pci unused=ixgbe Network devices using kernel driver =================================== 0000:00:1f.6 'Ethernet Connection (4) I219-LM 15d7' if=enp0s31f6 drv=e1000e unused=vfio-pci 0000:02:00.0 'Wireless 8265 / 8275 24fd' if=wlp2s0 drv=iwlwifi unused=vfio-pci which seems to be fine. thank you for your help sincerely Kasim _______________________________________________ USRP-users mailing list -- [email protected]<mailto:[email protected]> To unsubscribe send an email to [email protected]<mailto:[email protected]>
_______________________________________________ USRP-users mailing list -- [email protected] To unsubscribe send an email to [email protected]
