Error encountered using virtual function of 82599 about moongen

[emmericp]

Some of MoonGens defaults are probably incompatible with the VF.

Better support for VFs is on my todo list.

[emmericp]

Can you use PFs instead of VFs?

VFs also come with other problems: for example, hardware timestamping is not supported by 82599 VFs.

[haris00]

No, because in my case it has to be multiple VMs each containing instance of MoonGen for stress testing purposes. I only have two physical functions where as many virtual functions. So physical function would limit the number of MoonGen instances i can spawn.
I am not much concerned with hardware timestamping. All i need is that i am able to send packets to a address and receive those packets back, thats it

[emmericp]

Okay, I just tested this: the problem is the number of TX queues (3) that this script tries to use, this is too much for the vf.

But it looks like you aren't going to need that many tx queues, so you should be fine.

However, MoonGen currently supports neither rate control nor device-based statistics for VFs. The former can be emulated with software like other packet generators do (just sleep), the latter can easily be fixed with manual counters.

I suggest to look at benchmark/upd-throughput.lua. This script works fine with VFs except that the transmit stats tracking doesn't work. But that can be fixed by replacing the device-based tx counter with a "manu"l tx counter. See quality-of-service-test.lua for an example of a manual tx counter.

You probably want to write your own script for this anyways, so this shouldn't be a problem.