Open norg opened 1 year ago
I tried v3.03 today again on that system and it turns out this option was the issue:
port_bandwidth_gb: 40
Once I remove this I don't h ave any errors anymore, also the complaint about hugepages is gone. Once I add this option in again the hugepages error shows up again:
ERROR there is not enough huge-pages memory in your system
EAL: Error - exiting with code: 1
Cause: Cannot init nodes mbuf pool nodes-0
In the docs it's still optional and explained as
The bandwidth of each interface in Gbs. In this example we have 10Gbs interfaces. For VM, put 1. Used to tune the amount of memory allocated by TRex.
The last sentence got me, is it not really used anymore and thus buggy?
Hi,
I'm currently trying to upgrade an environment with t-rex running. I used v2.81 for quite some time without issues, but I wanted to test the initial support for E810 NICs, so I upgraded to v3.00 but even my old NICs and configs didn't start. So I checked which version was the last known working one and which the first non working. So v2.83 is working for me and v2.84 is the first not working. I didn't find a major change that might be related.
So this is the new error I run into:
This worked like a charm with v2.83.
The trex config is:
DPDK setup output:
So a rather basic setup. The OS is Debian Buster with kernel 4.19. (I tried the kernel update to 5.10 but I ran into another issue where all hugepages were consumed and in the end T-rex (while starting) ran out of memory. I might create a dedicated issue for that as well.)
Based on the 2.84 release notes I can't see what causes this error. I tried also some versions in between like 2.85, 2.90, 2.99 and 3.00 but all stop with the PANIC.
Does anyone have an idea what might cause this?