You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There a couple of problems that keep dpdk-ans form working on Azure.
First the current CPU on bigger machine types is reported as core-avx2 by install-deps.sh.
Even if I just link in the haswell binaries, it still doesn't start because.
Second, the network interface on Azure is using failsafe PMD and MLX as a hidden device.
Even if you get the portmask right, it fails when I start it as:
There a couple of problems that keep dpdk-ans form working on Azure.
First the current CPU on bigger machine types is reported as core-avx2 by install-deps.sh.
Even if I just link in the haswell binaries, it still doesn't start because.
Second, the network interface on Azure is using failsafe PMD and MLX as a hidden device.
Even if you get the portmask right, it fails when I start it as:
ans -w a8f0:00:02.0 -l 4,5 -n 4 -- -p 0xf --config='(1,4,5)'
USER1: rte_ip_frag_table_create: allocated 25165952 bytes at socket 0
add veth1 device, kni id 0
USER8: LCORE[4] Interface veth1 if_capabilities: 0x800e
USER8: LCORE[4] Interface (veth1) isnt' added
Of course since this is all in your non open source code :-( No outside party can fix it.
The text was updated successfully, but these errors were encountered: