[dpdk-dev] compile error on ubuntu 14.4.4 kernel 4.2.0-27-generic in qemu

[Sharath]

Root cause: Default cpu config when the VM has be been started by qemu does
not support SSE.

I have resolved this issue. Here the resolution which I used. Might be
helpful for others

Method 1
After Configuring VM by GUI based Virtual Machine Manager, go to the CPU
config & make SSE as "Required"

Method 2
pass -cpu options to qemu-system-x86_64 with your cpu type [Nehalem] in my
case.
-cpu
Nehalem,+rdtscp,+x2apic,+dca,+pdcm,+xtpr,+tm2,+est,+vmx,+ds_cpl,+monitor,+dtes64,+pbe,+tm,+ht,+ss,+acpi,+ds,+vme

Thanks to *Masaru OKI & *
*Christian Ehrhardt for the info*

[dpdk-dev] compile error on ubuntu 14.4.4 kernel 4.2.0-27-generic in qemu

[Christian Ehrhardt]

It is hard for me to spot what exactly is missing, but while it was never
intended for trusty the version we have for xenial should get you going.

# all kind of dependencies
sudo apt-get install build-essential ubuntu-dev-tools debhelper dh-python
dh-systemd doxygen graphviz inkscape libcap-dev libpcap-dev libxen-dev
libxenstore3.0 python python-sphinx texlive-fonts-recommended
texlive-latex-extra
# get the version we currently package for xenial
pull-lp-source dpdk xenial
# run the packaged build which takes care of most enabling/disabling and
such
cd dpdk-2.2.0
./debian/rules build

Also as you need at least some SSE (level depends on your config) which
isn't in the guest by default.
Take a look at this - although I'm not 100% sure how mouch of it works back
on trusty.
https://help.ubuntu.com/16.04/serverguide/DPDK.html#dpdk-in-guest

>From there you can derive into whatever you need.
Or just take the build process as your starting point for your own.
On the other hand I encourage you to go to 16.04 and just use the packaged
version if that would suit your needs.


Christian Ehrhardt
Software Engineer, Ubuntu Server
Canonical Ltd

On Sun, Apr 17, 2016 at 8:41 PM, Masaru OKI  wrote:

> On 2016/04/18 3:27, Sharath wrote:
>
>> I am facing feew compile errors while compiling dpdk. The env is ubuntu
>> running as an VM, VM is started by qemu. How do I fix the compile errors?
>>
>
> Default qemu virtual cpu does not support SSE4.2.
> Try qemu -cpu help, and specify your reasonable cpu.
>

[dpdk-dev] compile error on ubuntu 14.4.4 kernel 4.2.0-27-generic in qemu

[Masaru OKI]

On 2016/04/18 3:27, Sharath wrote:
> I am facing feew compile errors while compiling dpdk. The env is ubuntu
> running as an VM, VM is started by qemu. How do I fix the compile errors?

Default qemu virtual cpu does not support SSE4.2.
Try qemu -cpu help, and specify your reasonable cpu.

[dpdk-dev] compile error on ubuntu 14.4.4 kernel 4.2.0-27-generic in qemu

[Sharath]

HI,

I am facing feew compile errors while compiling dpdk. The env is ubuntu
running as an VM, VM is started by qemu. How do I fix the compile errors?

In file included from
/home/vpptest/vpp/build-root/build-vpp-native/dpdk/dpdk-2.2.0/lib/librte_eal/linuxapp/eal/eal_pci.c:42:0:
/home/vpptest/vpp/build-root/install-vpp-native/dpdk/include/rte_memcpy.h:
In function ?rte_memcpy?:
/home/vpptest/vpp/build-root/install-vpp-native/dpdk/include/rte_memcpy.h:625:2:
error: implicit declaration of function ?_mm_alignr_epi8?
[-Werror=implicit-function-declaration]
  MOVEUNALIGNED_LEFT47(dst, src, n, srcofs);
  ^
/home/vpptest/vpp/build-root/install-vpp-native/dpdk/include/rte_memcpy.h:625:2:
error: nested extern declaration of ?_mm_alignr_epi8?
[-Werror=nested-externs]
/home/vpptest/vpp/build-root/install-vpp-native/dpdk/include/rte_memcpy.h:625:2:
error: incompatible type for argument 2 of ?_mm_storeu_si128?
In file included from
/home/vpptest/vpp/build-root/install-vpp-native/dpdk/include/rte_common.h:289:0,
 from
/home/vpptest/vpp/build-root/install-vpp-native/dpdk/include/rte_memory.h:55,
 from
/home/vpptest/vpp/build-root/install-vpp-native/dpdk/include/rte_eal_memconfig.h:38,
 from
/home/vpptest/vpp/build-root/build-vpp-native/dpdk/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?

Thanks
Sharath