From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp-4.sys.kth.se (smtp-4.sys.kth.se [130.237.48.193]) by dpdk.org (Postfix) with ESMTP id BAA5258FE for ; Sat, 29 Dec 2018 10:42:29 +0100 (CET) Received: from smtp-4.sys.kth.se (localhost.localdomain [127.0.0.1]) by smtp-4.sys.kth.se (Postfix) with ESMTP id 650581E60; Sat, 29 Dec 2018 10:42:29 +0100 (CET) X-Virus-Scanned: by amavisd-new at kth.se Received: from smtp-4.sys.kth.se ([127.0.0.1]) by smtp-4.sys.kth.se (smtp-4.sys.kth.se [127.0.0.1]) (amavisd-new, port 10024) with LMTP id FwRylU1Kt1sS; Sat, 29 Dec 2018 10:42:25 +0100 (CET) Received: from exdb02.ug.kth.se (unknown [192.168.32.112]) by smtp-4.sys.kth.se (Postfix) with ESMTPS id 97E83B6; Sat, 29 Dec 2018 10:42:25 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kth.se; s=default; t=1546076545; bh=n4Y+VyvxHY9YhQlooMQSWZtdagmGngOUl6og2GJbfk0=; h=From:To:CC:Subject:Date:References:In-Reply-To; b=OWQLkbgZNOTSLHxZHCBJuwLU/C1qLuM0OJQSvQ0OdpmcLWEnk/jaJBAAOEKf2sfwp 8WtRB9zDOow9dqtAZE3cCd1nFBSENfBcdL35aH+L0hMse5mPVDK6z0Q2WZCH4uRAwb QRm3AOXZ8vvMn9mF2Ilq6sWw/w6vJ/yk78VnV88I= Received: from exdb05.ug.kth.se (192.168.32.115) by exdb02.ug.kth.se (192.168.32.112) with Microsoft SMTP Server (TLS) id 15.0.1367.3; Sat, 29 Dec 2018 10:42:24 +0100 Received: from exdb05.ug.kth.se ([192.168.32.115]) by exdb05.ug.kth.se ([192.168.32.115]) with mapi id 15.00.1367.000; Sat, 29 Dec 2018 10:42:25 +0100 From: Tom Barbette To: Murali Krishna , wuzhouhui CC: "users@dpdk.org" Thread-Topic: [dpdk-users] DPDK build failed in virtual machine Thread-Index: AQHUnpo8oA8D4u30m0O2KNNUbxw9E6WVeBiy Date: Sat, 29 Dec 2018 09:42:25 +0000 Message-ID: <1546076544827.99621@kth.se> References: <1545906028733.17773@kth.se> <5854e0ee.32f4e.167f4238a89.Coremail.wuzhouhui14@mails.ucas.ac.cn>, In-Reply-To: Accept-Language: fr-FR, sv-SE, en-US Content-Language: fr-FR X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [78.129.118.20] MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-users] DPDK build failed in virtual machine X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Dec 2018 09:42:30 -0000 ?You can also double check by doing cat /proc/cpuinfo in the guest. But the= message is clear, your guest CPU is x86 (32 bit). Tom ________________________________ De : Murali Krishna Envoy=E9 : vendredi 28 d=E9cembre 2018 11:43 =C0 : wuzhouhui Cc : Tom Barbette; users@dpdk.org Objet : Re: [dpdk-users] DPDK build failed in virtual machine can you try compiling dpdk after setting 'Copy host CPU configuation' optio= n under CPU settings of that VM in virt-manager. Regards, Murali On Fri, Dec 28, 2018 at 2:57 PM wuzhouhui > wrote: > -----Original Messages----- > From: "Tom Barbette" > > Sent Time: 2018-12-27 18:20:30 (Thursday) > To: wuzhouhui >, "users@dpdk.org" > > Cc: > Subject: RE: [dpdk-users] DPDK build failed in virtual machine > > Hi, > > By default DPDK build for the current CPU. > > I guess in your virtual machine configuration you enabled emulation of a = CPU instead of CPU passthrough. This is the default of libvirt I think. The= default emulated CPU has no fancy insturctions by default, and is, it seem= s from your error log, set in 32bit mode. > What do you mean "set in 32bit mode"? The arch of virtual machine is x86_64= , so the cpu should be in 64 bit mode. Thanks. Wu > Tom > > ________________________________________ > De : users > de la = part de wuzhouhui > > Envoy=E9 : lundi 24 d=E9cembre 2018 03:51 > =C0 : users@dpdk.org > Objet : [dpdk-users] DPDK build failed in virtual machine > > Hi, > > A naive question, but I couldn't find any clue when searching Internet. > > When I build DPDK in a CentOS-6.3 virtual machine, I got some errors: > > [wzh@CentOS6-compiler dpdk-stable-18.05.1]$ make config T=3Dx86_64-native= -linuxapp-gcc > Configuration done using x86_64-native-linuxapp-gcc > [wzh@CentOS6-compiler dpdk-stable-18.05.1]$ make > cc1: error: CPU you selected does not support x86-64 instruction set > =3D=3D Build lib > cc1: error: CPU you selected does not support x86-64 instruction set > =3D=3D Build lib/librte_compat > cc1: error: CPU you selected does not support x86-64 instruction set > SYMLINK-FILE include/rte_compat.h > =3D=3D Build lib/librte_eal > cc1: error: CPU you selected does not support x86-64 instruction set > ^Cmake[2]: *** [librte_eal] Interrupt > make[1]: *** [lib] Interrupt > make: *** [all] Interrupt > > [wzh@CentOS6-compiler dpdk-stable-18.05.1]$ gcc --version > gcc (GCC) 4.4.7 20120313 (Red Hat 4.4.7-4) > Copyright (C) 2010 Free Software Foundation, Inc. > This is free software; see the source for copying conditions. There is N= O > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOS= E. > > But build in host (CentOS-6.3) seems fine. Does it means that DPDP cannot= be > build in virtual machine? > > Thanks.