I read all the issues and docs regarding this topic, but can't figure out if and how this works with nff-go.
We can make our nff-go application work with Mellanox-Driver in a real-world and a virtual setup. But then we don't see all network-traffic in the virtual setup. For example ARP-Replies never reach the nff-go application.
According to this you should use the failsafe-mode for this:
DPDK applications must run over the failsafe PMD that is exposed in Azure. If the application runs directly over the VF PMD, it doesn't receive all packets that are destined to the VM, since some packets show up over the synthetic interface.
https://docs.microsoft.com/en-us/azure/virtual-network/setup-dpdk#failsafe-pmd
Adding --vdev="net_vdev_netvsc0,iface=eth1" to the DPDKArgs in flow.Config results in an init-error since nff-go doesn't link the needed drivers. The given testpmd example works as expected.
So my question is how you should/can use nff-go in an HyperV-VM with SR-IOV?
I read all the issues and docs regarding this topic, but can't figure out if and how this works with nff-go.
We can make our nff-go application work with Mellanox-Driver in a real-world and a virtual setup. But then we don't see all network-traffic in the virtual setup. For example ARP-Replies never reach the nff-go application.
According to this you should use the failsafe-mode for this:
https://docs.microsoft.com/en-us/azure/virtual-network/setup-dpdk#failsafe-pmd
Adding --vdev="net_vdev_netvsc0,iface=eth1" to the DPDKArgs in flow.Config results in an init-error since nff-go doesn't link the needed drivers. The given testpmd example works as expected.
So my question is how you should/can use nff-go in an HyperV-VM with SR-IOV?