Bug ID 1977037: TMM Virtual Edition on Azure goes into crash loop due to missing kernel driver

Last Modified: Aug 08, 2025

Affected Product(s):
BIG-IP Install/Upgrade, LTM(all modules)

Known Affected Versions:
17.5.1

Opened: Jul 09, 2025

Severity: 3-Major

Symptoms

- TMM goes into crash loop - Repeated logs similar to the following can be seen from /var/log/tmm* notice dpdk[001dd800-2e3d-001d-d800-2e3d001dd800]: DPDK internal port_id 2 notice dpdk: Error: DMA mapping of application heap failed with rte_error Operation not supported notice dpdk: Error: app_heap_dma_map: app heap DMA mapping failed with rte_errno Operation not supported notice dpdk[001dd800-2e3d-001d-d800-2e3d001dd800]: Error: DMA mapping application heap notice dpdk: Error: Removing heap memory (0x40016a600000, 67108864 bytes): Device or resource busy notice xnet_lib [vmbus:eth2]: Error: Failed to initialize driver notice xnet[00:e2.0]: Error: Unable to attach to xnet dev notice xnet(1.2)[00:e2.0]: Error: Unable to initialize device notice xnet(1.2)[00:e2.0]: Waiting for tmm1 to reach state 4... notice ndal Error: Restarting TMM

Impact

TMM is unable to successfully start. Device is unable to process traffic.

Conditions

- BIG-IP Virtual Edition is running on Microsoft HyperV on Azure Cloud - Mellanox ConnectX-3 NIC is used - XNET driver is being used

Workaround

Configure BIG-IP Virtual Edition to use the sock driver by entering the following command: echo "device driver vendor_dev f5f5:f550 sock" >> /config/tmm_init.tcl Reboot the BIG-IP VE instance by entering the following command: reboot

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips