All of lore.kernel.org
 help / color / mirror / Atom feed
From: dow-f+vMXmRrMFEJlE21x6VTiUEOCMrvLtNR@public.gmane.org
To: dev-VfR2kkLFssw@public.gmane.org
Subject: Re: CPU does not support x86-64 instruction set
Date: Thu, 06 Jun 2013 23:02:19 +0000	[thread overview]
Message-ID: <W591581093126431370559739@atl4webmail11> (raw)

[-- Attachment #1: Type: text/plain, Size: 2279 bytes --]

>On Thu, Jun 6, 2013 at 5:27 PM, jinho hwang <hwang.jinho at gmail.com> wrote:>>> Hi,>>>> I am having trouble to compile the dpdk in a virtual machine. I am using>> KVM as a hypervisor, and guest os is ubuntu 12.10, kernel 3.5.0, x86_64. I>> have been using dpdk for a week and run the examples in a native platform.>> But when I try to move it to virtual machine, it gives me the following>> error:>>>> /home/guest/dpdk-1.2.3r1/lib/librte_eal/linuxapp/eal/eal.c:1:0: error: CPU>> you selected does not support x86-64 instruction set>>>> I am sure that I have installed 64 bit version as it shows in "uname -a".> Also, /proc/cpuinfo shows "model name: QEMU Virtual CPU version> >(cpu64-rhe16)".>>>> Do you have any idea?>>>> Thank you,>>>> Jinho>>>>I figured out just now. It was because gcc version. I used to use 4.4, but>in the guest virtual machine, I used 4.7 which may have additional>functions to check strictly. - Jinho>-------------- next part -------------->An HTML attachment was scrubbed...>URL: <http://dpdk.org/ml/archives/dev/attachments/20130606/0a77b188/attachment.html>


This error can also be cause by the VM's CPU definition not being defined. The following xml snippet of code is from my DPDK VM's definition.
<!-- /* Style Definitions */p.MsoNormal, li.MsoNormal, div.MsoNormal	{mso-style-unhide:no;	mso-style-qformat:yes;	mso-style-parent:"";	margin:0in;	margin-bottom:.0001pt;	mso-pagination:widow-orphan;	font-size:12.0pt;	font-family:"Times New Roman";	mso-fareast-font-family:"Times New Roman";}.MsoChpDefault	{mso-style-type:export-only;	mso-default-props:yes;}@page WordSection1	{size:8.5in 11.0in;	margin:1.0in 1.25in 1.0in 1.25in;	mso-header-margin:.5in;	mso-footer-margin:.5in;	mso-paper-source:0;}div.WordSection1</style></pre><p class="MsoNormal"><span style="font-size:10.0pt;font-family:Courier"><span style="mso-spacerun:yes"> </span><cpu mode='host-passthrough'></span></p><p class="MsoNormal"><span style="font-size:10.0pt;font-family:Courier"><span style="mso-spacerun:yes"> </span><topology sockets='1' cores='6'threads='2'/></span></p><p class="MsoNormal"><span style="font-size:10.0pt;font-family:Courier"><span style="mso-spacerun:yes"> </span></cpu></span></p><pre><br><br></pre><div><font face="Verdana" size="2"></font></div>

[-- Attachment #2: Type: text/html, Size: 2975 bytes --]

             reply	other threads:[~2013-06-06 23:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-06 23:02 dow-f+vMXmRrMFEJlE21x6VTiUEOCMrvLtNR [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-06-23 12:42 CPU does not support x86-64 instruction set Alex Markuze
     [not found] ` <CAKfHP0Vp+HVcNyh9kfrxGeLByXhcCu_Ymwc6u5-k4GCHYkjHXQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-06-23 14:42   ` Thomas Monjalon
2013-06-06 21:27 jinho hwang
2013-06-06 22:22 ` jinho hwang

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=W591581093126431370559739@atl4webmail11 \
    --to=dow-f+vmxmrrmfejle21x6vtiueocmrvltnr@public.gmane.org \
    --cc=dev-VfR2kkLFssw@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.