DPDK patches and discussions
 help / color / mirror / Atom feed
From: Nikos Anastopoulos <n.anastop@gmail.com>
To: dev@dpdk.org
Subject: [dpdk-dev] System hangs when using dpdk in a guest machine
Date: Thu, 15 May 2014 17:24:55 +0300	[thread overview]
Message-ID: <CABYgoL-SS7aUcLWi4WbeSzOsuAgCfwzn0R=yhTXD5zMSWJUH9w@mail.gmail.com> (raw)

Hi,

I am experiencing an irrecoverable system hang when trying to run the
'helloworld' dpdk example from within a CentOS 6.5 guest (4 VCPUS, 7GB
RAM), running on VirtualBox (Windows host).

Specifically, I have successfully built dpdk-1.6.0r2 for the
"x86_64-ivshmem-linuxapp-gcc" target.
I perform the following initialization actions without problem (all as root):
1. mkdir -p /dev/hugepages
2. mount -t hugetlbfs nodev /dev/hugepages
3. echo 0 > /proc/sys/kernel/randomize_va_space
4. modprobe uio
5. insmod $RTE_SDK/$RTE_TARGET/kmod/igb_uio.ko

Afterwards I launch the app as root as follows:
$ ./helloworld -c f -n 4

EAL: Detected lcore 0 as core 0 on socket 0
EAL: Detected lcore 1 as core 1 on socket 0
EAL: Detected lcore 2 as core 2 on socket 0
EAL: Detected lcore 3 as core 3 on socket 0
EAL: Skip lcore 4 (not detected)
EAL: Skip lcore 5 (not detected)
EAL: Skip lcore 6 (not detected)
EAL: Skip lcore 7 (not detected)
EAL: Skip lcore 8 (not detected)
...
EAL: Skip lcore 62 (not detected)
EAL: Skip lcore 63 (not detected)
EAL: Searching for IVSHMEM devices...
EAL: No IVSHMEM configuration found!
EAL: Setting up memory...

The app freezes at this point, and after a while the guest OS freezes
as well, forcing me to power it off from the host (Virtualbox). After
a guest reboot I cannot find anything in the kernel logs related with
the hang.

Note also that the above steps have been validated, and the app has
successfully run, on a native CentOS 6.5 machine.

Any idea of what could be the cause for this behaviour?

Thanks in advance,
Nikos

                 reply	other threads:[~2014-05-15 14:24 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CABYgoL-SS7aUcLWi4WbeSzOsuAgCfwzn0R=yhTXD5zMSWJUH9w@mail.gmail.com' \
    --to=n.anastop@gmail.com \
    --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).