[dpdk-users] Issue in installing DPDK on VM

[Mitali Yadav]

Hi,

We are installing dpdk2.2.0 on a VM having linux kernel 3.13.0-77 and we
are getting the following error.
-------------------------------------------------------------------------------------------------------------------------------------------------------
In file included from
/home/vm1/dpdk-2.2.0/lib/librte_eal/linuxapp/eal/eal_pci.c:42:0:
/home/vm1/dpdk-2.2.0/x86_64-native-linuxapp-gcc/include/rte_memcpy.h:625:2:
error: incompatible type for argument 2 of ‘_mm_storeu_si128’
  MOVEUNALIGNED_LEFT47(dst, src, n, srcofs);
  ^
In file included from
/home/vm1/dpdk-2.2.0/x86_64-native-linuxapp-gcc/include/rte_common.h:289:0,
                 from
/home/vm1/dpdk-2.2.0/x86_64-native-linuxapp-gcc/include/rte_memory.h:55,
                 from
/home/vm1/dpdk-2.2.0/x86_64-native-linuxapp-gcc/include/rte_eal_memconfig.h:38,
                 from
/home/vm1/dpdk-2.2.0/lib/librte_eal/linuxapp/eal/eal_pci.c:39:
/usr/lib/gcc/x86_64-linux-gnu/4.8/include/emmintrin.h:700:1: note: expected
‘__m128i’ but argument is of type ‘int’
 _mm_storeu_si128 (__m128i *__P, __m128i __B)
 ^
In file included from
/home/vm1/dpdk-2.2.0/lib/librte_eal/linuxapp/eal/eal_pci.c:42:0:
/home/vm1/dpdk-2.2.0/x86_64-native-linuxapp-gcc/include/rte_memcpy.h:625:2:
error: incompatible type for argument 2 of ‘_mm_storeu_si128’
  MOVEUNALIGNED_LEFT47(dst, src, n, srcofs);
  ^
In file included from
/home/vm1/dpdk-2.2.0/x86_64-native-linuxapp-gcc/include/rte_common.h:289:0,
                 from
/home/vm1/dpdk-2.2.0/x86_64-native-linuxapp-gcc/include/rte_memory.h:55,
                 from
/home/vm1/dpdk-2.2.0/x86_64-native-linuxapp-gcc/include/rte_eal_memconfig.h:38,
                 from
/home/vm1/dpdk-2.2.0/lib/librte_eal/linuxapp/eal/eal_pci.c:39:
/usr/lib/gcc/x86_64-linux-gnu/4.8/include/emmintrin.h:700:1: note: expected
‘__m128i’ but argument is of type ‘int’
 _mm_storeu_si128 (__m128i *__P, __m128i __B)

------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

When we searched online, we got similar issue in
http://rumpkernel-users.narkive.com/qJxwkczX/rump-kernel-for-dpdk.
They mentioned setting the CPU flags ssse3, avx and aes to resolve this
issue. These flags are enabled on the physical machine but not on the VM
even though they both have the same kernel and OS (ubuntu14.04). We have
used virt-manager with kvm-qemu as the hypervisor to host the VM. How can
we enable these flags in the VM. Or are we missing out on some other
parameter that need to be set?

Thanks,
Mitali