You problem is caused by compiling against 2 different kernel trees. The
version magic for the module must the same (see below). If you still have the
deploy machine (3.16.0.30) kernel tree accessible to your build machine you can
try setting the RTE_KERNELDIR=<path to 3.16.0.30 tree>. This can be set in your
environment or on the command line as shown below. Once the 2 version magic?s
match you should be good to go. You may also want to look at the CROSS
variable also if you need to use a different tool chain.
HTH ? Andy
# make install T=${RTE_TARGET} RTE_KERNELDIR=<path to 3.16.0.30 tree>
$ modinfo ${RTE_SDK}/${RTE_TARGET}/kmod/igb_uio.ko | grep vermagic
vermagic: 4.1.7-200.fc22.x86_64 SMP mod_unload
On 9/27/15, 8:27 PM, "dev on behalf of Nguyen Van Long" <dev-bounces at
dpdk.org on behalf of longnv at viosoft.com> wrote:
>Hi all,
>I am building DDPK and OVS as the instruction in
>https://software.intel.com/en-us/blogs/2015/06/09/building-vhost-user-for-ovs-today-using-dpdk-200
>
>My scenario is that I have 2 machines, one is called building machine (for
>build dpdk) and the another is called deploy machine.
>After finishing building DPDK in building machine, I copy all dpdk folders to
>deploy machine and try to setup DPDK devices in this machine as:
>RTE_SDK=?${HOME}/dpdk-2.0.0
>RTE_TARGET =?x86_64-ivshmem-linuxapp-gcc?
>
># Install and bind UIO interface eth0
>sudo modprobe uio
>sudo insmod ${RTE_SDK}/${RTE_TARGET}/kmod/igb_uio.ko
>
>
>Unfortunately, I got the error:
>insmod: ERROR: could not insert module
>../dpdk-2.0.0/x86_64-ivshmem-linuxapp-gcc/kmod/igb_uio.ko: Invalid module
>format
>
>I doubt that the different linux kernel causes the problem (linux kernel in
>building machine is 3.16.0.49 and in deploy machine is 3.16.0.30)
>but don't know how to fix that. Could you have any solution to build and
>deploy dpdk in machine with different kernel?
>
>Thank and best regard!
>
