Bug ID 1408437: TMM fails to start due to fragmented memory.

Last Modified: Jun 19, 2025

Affected Product(s):
BIG_IP_NEXT(SPK) SPK(all modules)

Known Affected Versions:
1.7, 1.7.1, 1.7.2, 1.7.3, 1.7.4, 1.7.5, 1.7.6, 1.7.7, 1.7.8, 1.7.9, 1.7.10, 1.8, 1.8.0, 1.8.2, 1.9, 1.9.0, 1.9.1, 1.9.2

Opened: Nov 30, 2023

Severity: 3-Major

Symptoms

TMM fails to start with error logs, as shown below: dpdk: Error: rte_pktmbuf_pool_create_by_ops() failed with rte error Cannot allocate memory. dpdk: Error: **** Fatal xnet DPDK Driver Configuration Error **** Allocating mbuf pool failed. dpdk: Error: **** Fatal xnet DPDK Driver Configuration Error **** Failed to initialize DPDK run-time environment (xnet error 1). xnet_lib [pci:0000:d8:02.6]: Error: Failed to initialize driver

Impact

TMM pod will end up in a Crashloop.

Conditions

This can happen when host assigns hugepages to the TMM container that are not physically contiguous.

Workaround

None.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips