DPDK usage discussions
 help / color / mirror / Atom feed
From: Rex Shang <rshang@gmail.com>
To: users@dpdk.org
Subject: [dpdk-users] Running DPDK on Google Cloud Compute Engine (GCE)
Date: Wed, 13 Sep 2017 15:53:23 -0700	[thread overview]
Message-ID: <3D8C6C5A-89DB-4965-8B71-53B3AC845988@gmail.com> (raw)

Hi all

Just wondering if anyone has successfully have DPDK running on VM inside Google Cloud.  I’ve tried similar set up on my Mac Book Pro with Virtual Box and had success.  Using similar recipe, I can’t have testpmd pass the initialization.  Before I spend too much time, just wondering if I am working on mission impossible.  ;)  Your input is greatly appreciated.

Here is my setup:
Google Cloud Compute Engine
4 vCore with 8 GB of memory
Ubuntu 16.04 LTS
3 NIC with 2 used for DPDK (driver: net_virtio); I am a bit doubtful about this NIC but so far the NIC is up with “igb_uio"

Rex

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

EAL: Detected 4 lcore(s)
EAL: No free hugepages reported in hugepages-1048576kB
EAL: Probing VFIO support...
EAL: VFIO support initialized
EAL: PCI device 0000:00:04.0 on NUMA socket -1
EAL:   Invalid NUMA socket, default to 0
EAL:   probe driver: 1af4:1000 net_virtio
EAL: PCI device 0000:00:05.0 on NUMA socket -1
EAL:   Invalid NUMA socket, default to 0
EAL:   probe driver: 1af4:1000 net_virtio
EAL: PCI device 0000:00:06.0 on NUMA socket -1
EAL:   Invalid NUMA socket, default to 0
EAL:   probe driver: 1af4:1000 net_virtio
Interactive-mode selected
USER1: create a new mbuf pool <mbuf_pool_socket_0>: n=163456, size=2176, socket=0
Configuring Port 0 (socket 0)
Fail to configure port 0
EAL: Error - exiting with code: 1
  Cause: Start ports failed

             reply	other threads:[~2017-09-13 22:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-13 22:53 Rex Shang [this message]
2017-09-16  2:03 ` Tan, Jianfeng
2017-09-16  7:00   ` Learner Study
2017-09-16  7:01     ` Learner Study
2017-09-17  0:59       ` Rex Shang
2017-09-17  2:08   ` Rex Shang

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=3D8C6C5A-89DB-4965-8B71-53B3AC845988@gmail.com \
    --to=rshang@gmail.com \
    --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).