Symptoms:
When a POD associated to multiple DPDK interfaces is instantiated it crashes several times with the following error signature:
{"version":"0.2.0","timestamp":"2023-06-21T10:15:18.935+02:00","severity":"info","service_id":"pod-up-data-plane","metadata":{"proc_id":"8"},"message":"[pio] USER1: Port 2 flags - multicast 0x1, promisc 0x0!"}
{"version":"0.2.0","timestamp":"2023-06-21T10:15:18.936+02:00","severity":"info","service_id":"pod-up-data-plane","metadata":{"proc_id":"8"},"message":"[pio] vmxnet3_dev_start(): Device activation: UNSUCCESSFUL"}
{"version":"0.2.0","timestamp":"2023-06-21T10:15:18.936+02:00","severity":"error","service_id":"pod-up-data-plane","metadata":{"proc_id":"8"},"message":"[pktio_libpio_init] pio_init() => ERROR_DPDK_DEV_START"}
Log snippet:
Further analysis of the logs at vmkernel.log indicate an issue performing memory reservation for the interface:
2023-06-27T02:11:46.482Z cpu68:33812799)VmMemCow: 1772: p2m update: cannot reserve - cur 0 0 rsvd 1029 req 257 avail 1279
2023-06-27T02:11:46.482Z cpu68:33812799)Vmxnet3: 11366: Failed to map the rx data ring for rq 0