From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <longnv@viosoft.com>
Received: from mail1.viosoft.com (173-164-244-81-SFBA.hfc.comcastbusiness.net
 [173.164.244.81]) by dpdk.org (Postfix) with ESMTP id 1D4A5567A
 for <dev@dpdk.org>; Mon, 28 Sep 2015 04:42:49 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1])
 by mail1.viosoft.com (Postfix) with ESMTP id 948832A421E4
 for <dev@dpdk.org>; Mon, 28 Sep 2015 03:27:24 +0000 (UTC)
Received: from mail1.viosoft.com ([127.0.0.1])
 by localhost (mail1.viosoft.com [127.0.0.1]) (amavisd-new, port 10032)
 with ESMTP id 4dqG0jaYVIj8 for <dev@dpdk.org>;
 Mon, 28 Sep 2015 03:27:23 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by mail1.viosoft.com (Postfix) with ESMTP id B25E22A4236B
 for <dev@dpdk.org>; Mon, 28 Sep 2015 03:27:23 +0000 (UTC)
X-Virus-Scanned: amavisd-new at mail1.viosoft.com
Received: from mail1.viosoft.com ([127.0.0.1])
 by localhost (mail1.viosoft.com [127.0.0.1]) (amavisd-new, port 10026)
 with ESMTP id 4GGL97MaHtAK for <dev@dpdk.org>;
 Mon, 28 Sep 2015 03:27:23 +0000 (UTC)
Received: from mail1.viosoft.com (mail1.viosoft.com [10.0.3.138])
 by mail1.viosoft.com (Postfix) with ESMTP id 7AF782A421E4
 for <dev@dpdk.org>; Mon, 28 Sep 2015 03:27:23 +0000 (UTC)
Date: Mon, 28 Sep 2015 03:27:23 +0000 (UTC)
From: Nguyen Van Long <longnv@viosoft.com>
To: dev@dpdk.org
Message-ID: <1522256370.1182490.1443410843370.JavaMail.zimbra@viosoft.com>
MIME-Version: 1.0
X-Originating-IP: [10.0.3.138]
X-Mailer: Zimbra 8.6.0_GA_1153 (ZimbraWebClient - FF35 (Linux)/8.6.0_GA_1153)
Thread-Topic: ERROR: Invalid module format
Thread-Index: HmFNPu10QogSfnVpmJ/gsWZO2o3xmg==
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: [dpdk-dev] ERROR: Invalid module format
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Sep 2015 02:42:49 -0000

Hi all,=20
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=20
My scenario is that I have 2 machines, one is called building machine (for =
build dpdk) and the another is called deploy machine.=20
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:=20
RTE_SDK=3D=E2=80=9D${HOME}/dpdk-2.0.0
RTE_TARGET =3D=E2=80=9Dx86_64-ivshmem-linuxapp-gcc=E2=80=9D

# Install and bind UIO interface eth0
sudo modprobe uio
sudo insmod ${RTE_SDK}/${RTE_TARGET}/kmod/igb_uio.ko=20


Unfortunately, I got the  error:=20
insmod: ERROR: could not insert module ../dpdk-2.0.0/x86_64-ivshmem-linuxap=
p-gcc/kmod/igb_uio.ko: Invalid module format=20

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)=20
but don't know how to fix that. Could you have any solution to build and de=
ploy dpdk in machine with different kernel?=20

Thank and best regard!=20