1. Any comments regarding dpdk version?
[A] I recommend to use latest - DPDK 2.2. i've used MLNX_DPDK 2.1 and DPDK 2.2 from upstream.
2. As for ivshmem - we currently using native. However, you didn't include it in your tutorial. Should I configure it manually or is it already enabled by default (as part of the DPDK package on mlx site?
[A] To be honest, i never used ivshmem. Mellanox do not change the default and therefore i don't think it is enabled. I do need to try it and then will have better answer (and tutorial)
3. Note that in on one of your tutorials you have mentioned that CONFIG_RTE_BUILD_COMBINE_LIBS should be configured to N while in your tuturial above you claim that it should be configured to Y.
[A] It is application specific. OVS needs DPDK to be built as combined lib, other application no. by default it combined lib is disabled. for the exampls application like testpmd you do not need it.
3. A more general question: We try to transmit data from two guests located in two different hosts (connected using mlx 40GB switch) and DPDK-OVS. We wanted to make sure that we do not miss anything: while dpdk is installed in both the host and guests OS, ovs installation is needed only in the hosts.
[A] Yes, OVS installed only on the host. DPDK on the guests is not a must btw (but DPDK does support virtio). the short tutorial above do not cover DPDK in the guests.
4. Have you tried configuring DPDK using virt-manager as well?
[A] No, only QEMU. i guess you can do it with manually edit the xmls but never did it myself. might be a good suggestion for the port, i will try to add it.