DPDK usage discussions
 help / color / mirror / Atom feed
From: wuzhouhui <wuzhouhui14@mails.ucas.ac.cn>
To: "tom barbette" <barbette@kth.se>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] DPDK build failed in virtual machine
Date: Fri, 28 Dec 2018 17:27:09 +0800 (GMT+08:00)	[thread overview]
Message-ID: <5854e0ee.32f4e.167f4238a89.Coremail.wuzhouhui14@mails.ucas.ac.cn> (raw)
In-Reply-To: <1545906028733.17773@kth.se>


> -----Original Messages-----
> From: "Tom Barbette" <barbette@kth.se>
> Sent Time: 2018-12-27 18:20:30 (Thursday)
> To: wuzhouhui <wuzhouhui14@mails.ucas.ac.cn>, "users@dpdk.org" <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 seems 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 <users-bounces@dpdk.org> de la part de wuzhouhui <wuzhouhui14@mails.ucas.ac.cn>
> Envoyé : lundi 24 décembre 2018 03:51
> À : 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=x86_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
> == Build lib
> cc1: error: CPU you selected does not support x86-64 instruction set
> == Build lib/librte_compat
> cc1: error: CPU you selected does not support x86-64 instruction set
>   SYMLINK-FILE include/rte_compat.h
> == 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 NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
> 
> But build in host (CentOS-6.3) seems fine. Does it means that DPDP cannot be
> build in virtual machine?
> 
> Thanks.

  reply	other threads:[~2018-12-28  9:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-27 10:20 Tom Barbette
2018-12-28  9:27 ` wuzhouhui [this message]
2018-12-28 10:43   ` Murali Krishna
2018-12-29  9:42     ` Tom Barbette
  -- strict thread matches above, loose matches on Subject: below --
2018-12-24  2:51 wuzhouhui

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5854e0ee.32f4e.167f4238a89.Coremail.wuzhouhui14@mails.ucas.ac.cn \
    --to=wuzhouhui14@mails.ucas.ac.cn \
    --cc=barbette@kth.se \
    --cc=users@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).