When I try to run multiple instances on a single server (modifying the configuration according to the manual), reports DPDK's error.

517 views
Skip to first unread message

Rhonin

unread,
Nov 29, 2021, 2:57:21 AM11/29/21
to TRex Traffic Generator
Hi all,

As the title suggests, I'm having some problems trying to configure multiple entities with a modified configuration. I tried to modify it on the basis of the manual( https://trex-tgn.cisco.com/trex/doc/trex_faq.html#_can_i_run_multiple_trex_servers_on_the_same_machine ) and the self-contained use case(./trex/cfg/ins1\2\3.yaml) and it still reports errors. Since I don't know much about DPDK and the manual doesn't have this error, I'm posting the log here and hope to get an answer.

My scenario is a TRex with multiple servers sharing a single traffice server, perhaps you can drop by and give the best solution you know of (e.g. virtualization / single instance+ multi-client, or something else I don't know)? Thanks a lot.

---------------------------------------------------------
The error LOG is as follows:

(1)

Starting Scapy server..... Scapy server is started

The ports are bound/configured.

Starting  TRex v2.86 please wait  ...

EAL: Requested device 0000:82:02.0 cannot be used

EAL: Requested device 0000:82:02.1 cannot be used

ERROR in DPDK map

Could not find requested interface 82:02.0

Killing Scapy server... Scapy server is killed

--------------------------------

(2)

tarting Scapy server.... Scapy server is started

The ports are bound/configured.

Starting TRex v2.86 please wait ...

PANIC in rte_eth_dev_shared_data_prepare():

Cannot allocate ethdev shared data

12: [./_t-rex-64(+0x131451) [0x55ca0f3d5451]]

11: [/lib64/libc.so.6(__libc_start_main+0xf5) [0x7f7280e9b555]]

10: [./_t-rex-64(_Z9main_testiPPc+0x1f4) [0x55ca0f3ba7cc]]

9: [./_t-rex-64(rte_eal_init+0x131f) [0x55ca0f712a3f]]

8: [./_t-rex-64(rte_bus_probe+0x4e) [0x55ca0f6f612e]]

7: [./_t-rex-64(rte_pci_probe+0x60) [0x55ca0f652a60]]

6: [./_t-rex-64(+0x3ae928) [0x55ca0f652928]]

5: [./_t-rex-64(+0x5071a5) [0x55ca0f7ab1a5]]

4: [./_t-rex-64(rte_eth_dev_allocate+0x2f) [0x55ca0f721e4f]]

3: [./_t-rex-64(+0x47c930) [0x55ca0f720930]]

2: [./_t-rex-64(__rte_panic+0xba) [0x55ca0f3bbfa3]]

1: [./_t-rex-64(rte_dump_stack+0x18) [0x55ca0f713488]]

./t-rex-64: line 100: 21343 Aborted (core dumped) ./_$(basename $0) $INPUT_ARGS $EXTRA_INPUT_ARGS

Killing Scapy server... Scapy server is killed

-------------------------------------------------------

Rhonin

unread,
Nov 29, 2021, 3:16:26 AM11/29/21
to TRex Traffic Generator
- port_limit: 2 version: 2 interfaces: ['86:00.2', '86:00.1'] <--- different ports prefix: instance2 <--- unique prefix zmq_pub_port: 4600 <--- unique ZMQ publisher port zmq_rpc_port: 4601 <--- unique ZMQ RPC port limit_memory: 1024 <--- limit used memory ... platform: <--- this section should use unique cores master_thread_id: 0 latency_thread_id: 1 dual_if: - socket: 0 threads: [2,3,4] ...

--------------------------------------------------
To add, for the above two logs,

the first, I was in the previous normal configuration file, only add prefix info;(As far as I know this is a parameter required by DPDK, is a process tag? Two identical tags are not supported under the same system?)
the second, I added all the above information, the port/ address/ core and thread changed to their own, in the case of memory enough to try a different limit memory(8096 ~ 1024) (the result is the same---Cannot allocate ethdev shared data)
Reply all
Reply to author
Forward
0 new messages