From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Alex Markuze <alex@weka.io>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Fwd: CPU does not support x86-64 instruction set
Date: Tue, 24 Jun 2014 10:21:04 +0200 [thread overview]
Message-ID: <28645484.qtAJ9e2qr1@xps13> (raw)
In-Reply-To: <CAKfHP0WNnaYRirXX_P=yAfdRHD-UbHtPZZfPX86aa5yiGUhSUg@mail.gmail.com>
Welcome Alex.
Please, for future messages, try to answer below as explained here:
http://dpdk.org/ml
2014-06-24 11:12, Alex Markuze:
> Thomas Monjalon <thomas.monjalon@6wind.com> wrote:
> > 2014-06-23 15:42, Alex Markuze:
> > > Hi, I'm new to DPDK and Im trying to compile on a x86 Ubuntu 14.04
> > VM(KVM).
> > > And I'm getting this error:
> > >
> > > "error: CPU you selected does not support x86-64 instruction set"
> >
> > You should try "-cpu host" option of Qemu/KVM in order to have the full
> > instruction set of your host.
>
> I've resolved the issue in a similar way by modifying the VM xml config
> file with this line
> <cpu mode='host-passthrough’/>.
>
> I was wondering if a Makefile/.config solution exists w/o modifying an
> existing VM in cases where its not possible.
> I've tried to modify the .config file with 'CONFIG_RTE_MACHINE="native" ->
> CONFIG_RTE_MACHINE="x86-64"'
> But it didn't seem to matter (I didn't explore this much farther, I
> dint really try a clean build and didn't make sure that the .config file
> I've modified was read).
Not sure to understand what you want.
If you try to build DPDK for most of machines (including VM), you should set
CONFIG_RTE_MACHINE="default"
in your .config file.
--
Thomas
next prev parent reply other threads:[~2014-06-24 8:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-23 12:42 [dpdk-dev] " Alex Markuze
2014-06-23 14:42 ` Thomas Monjalon
[not found] ` <CAKfHP0XAfnXU1mC8b+=1d63rnj1J9GR-UM471HAyCQXkDEKDcg@mail.gmail.com>
2014-06-24 8:12 ` [dpdk-dev] Fwd: " Alex Markuze
2014-06-24 8:21 ` Thomas Monjalon [this message]
2014-06-24 9:14 ` Alex Markuze
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=28645484.qtAJ9e2qr1@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=alex@weka.io \
--cc=dev@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).