DPDK usage discussions
 help / color / mirror / Atom feed
From: hou guanghua <houguanghua@hotmail.com>
To: Mitali Yadav <yadavmitali1991@gmail.com>,
	"users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] Issue in installing DPDK on VM
Date: Thu, 18 Feb 2016 11:18:47 +0000	[thread overview]
Message-ID: <PS1PR0601MB1370FE357C4C8DFF08915972BBAF0@PS1PR0601MB1370.apcprd06.prod.outlook.com> (raw)
In-Reply-To: <CAEyHL0Dnp5971DBDMZRoU8k0Da6_GfzKBvCUU-bh9PfGdguv1Q@mail.gmail.com>


I had met the same problem with your before. In the GUI dialog (after run virt-manager), you can set the attributes of cpu, such as sse4_1,sse4_2. 
BTW, KVM is used in my enviroment.

Regards,
Guanghua

________________________________________
发件人: users [users-bounces@dpdk.org] &#20195;&#34920; Mitali Yadav [yadavmitali1991@gmail.com]
发送时间: 2016年2月18日 9:52
收件人: users@dpdk.org
主题: [dpdk-users] Issue in installing DPDK on VM

Hi,

We are installing dpdk2.2.0 on a VM having linux kernel 3.13.0-77 and we
are getting the following error.
-------------------------------------------------------------------------------------------------------------------------------------------------------
In file included from
/home/vm1/dpdk-2.2.0/lib/librte_eal/linuxapp/eal/eal_pci.c:42:0:
/home/vm1/dpdk-2.2.0/x86_64-native-linuxapp-gcc/include/rte_memcpy.h:625:2:
error: incompatible type for argument 2 of ‘_mm_storeu_si128’
  MOVEUNALIGNED_LEFT47(dst, src, n, srcofs);
  ^
In file included from
/home/vm1/dpdk-2.2.0/x86_64-native-linuxapp-gcc/include/rte_common.h:289:0,
                 from
/home/vm1/dpdk-2.2.0/x86_64-native-linuxapp-gcc/include/rte_memory.h:55,
                 from
/home/vm1/dpdk-2.2.0/x86_64-native-linuxapp-gcc/include/rte_eal_memconfig.h:38,
                 from
/home/vm1/dpdk-2.2.0/lib/librte_eal/linuxapp/eal/eal_pci.c:39:
/usr/lib/gcc/x86_64-linux-gnu/4.8/include/emmintrin.h:700:1: note: expected
‘__m128i’ but argument is of type ‘int’
 _mm_storeu_si128 (__m128i *__P, __m128i __B)
 ^
In file included from
/home/vm1/dpdk-2.2.0/lib/librte_eal/linuxapp/eal/eal_pci.c:42:0:
/home/vm1/dpdk-2.2.0/x86_64-native-linuxapp-gcc/include/rte_memcpy.h:625:2:
error: incompatible type for argument 2 of ‘_mm_storeu_si128’
  MOVEUNALIGNED_LEFT47(dst, src, n, srcofs);
  ^
In file included from
/home/vm1/dpdk-2.2.0/x86_64-native-linuxapp-gcc/include/rte_common.h:289:0,
                 from
/home/vm1/dpdk-2.2.0/x86_64-native-linuxapp-gcc/include/rte_memory.h:55,
                 from
/home/vm1/dpdk-2.2.0/x86_64-native-linuxapp-gcc/include/rte_eal_memconfig.h:38,
                 from
/home/vm1/dpdk-2.2.0/lib/librte_eal/linuxapp/eal/eal_pci.c:39:
/usr/lib/gcc/x86_64-linux-gnu/4.8/include/emmintrin.h:700:1: note: expected
‘__m128i’ but argument is of type ‘int’
 _mm_storeu_si128 (__m128i *__P, __m128i __B)

------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

When we searched online, we got similar issue in
http://rumpkernel-users.narkive.com/qJxwkczX/rump-kernel-for-dpdk.
They mentioned setting the CPU flags ssse3, avx and aes to resolve this
issue. These flags are enabled on the physical machine but not on the VM
even though they both have the same kernel and OS (ubuntu14.04). We have
used virt-manager with kvm-qemu as the hypervisor to host the VM. How can
we enable these flags in the VM. Or are we missing out on some other
parameter that need to be set?

Thanks,
Mitali

      reply	other threads:[~2016-02-18 11:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-18  9:52 Mitali Yadav
2016-02-18 11:18 ` hou guanghua [this message]

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=PS1PR0601MB1370FE357C4C8DFF08915972BBAF0@PS1PR0601MB1370.apcprd06.prod.outlook.com \
    --to=houguanghua@hotmail.com \
    --cc=users@dpdk.org \
    --cc=yadavmitali1991@gmail.com \
    /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).