From: Yuanhan Liu <yuanhan.liu@linux.intel.com>
To: mitali <mitaliyada@cse.iitb.ac.in>
Cc: Priyanka <ppnaik@cse.iitb.ac.in>,
"users@dpdk.org" <users@dpdk.org>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: seg fault in InterVM communication using virtio
Date: Thu, 23 Feb 2017 14:27:14 +0800 [thread overview]
Message-ID: <20170223062714.GX18844@yliu-dev.sh.intel.com> (raw)
In-Reply-To: <92b5577b-8c8a-e199-3b65-54323dbea48c@cse.iitb.ac.in>
On Wed, Feb 22, 2017 at 02:25:29PM +0530, mitali wrote:
> Hi Yuanhan,
>
> We are using virt-manager to start the VMs. We are attaching the image which
> shows the vNIC setup for the VMs.
>
> We have written our own dpdk application to send and receive UDP packets. The
> command we are using is
>
> ./build/app/dpdkapi -c 1 -- -p 1 where dpdkapi is our application.
>
> Inside the application we are sending and receiving packets from vNIC using
> rte_eth_tx_burst() and rte_eth_rx_burst().
>
> At the sender side after 127 packets the application stops and we observe a seg
> fault in dmesg. Using the print statements we observed that it faults in
> rte_eth_tx_burst(). All the 127 were received at the receiving VM.
Would you recompile dpdk with debug info enaled, which could be done by:
make ... EXTRA_CFLAGS='-g3 -O0'
And run it with gdb then dump the call stack?
--yliu
next prev parent reply other threads:[~2017-02-23 6:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-20 10:30 seg fault in InterVM communication using virtio Priyanka
2017-02-22 8:43 ` Yuanhan Liu
2017-02-22 8:55 ` mitali
2017-02-23 6:27 ` Yuanhan Liu [this message]
2017-03-01 13:50 ` mitali
2017-03-02 12:23 ` Yuanhan Liu
2017-03-02 12:32 ` mitali
2017-03-02 12:59 ` Yuanhan Liu
2017-03-02 14:00 ` mitali
2017-03-02 11:13 ` ppnaik
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=20170223062714.GX18844@yliu-dev.sh.intel.com \
--to=yuanhan.liu@linux.intel.com \
--cc=dev@dpdk.org \
--cc=mitaliyada@cse.iitb.ac.in \
--cc=ppnaik@cse.iitb.ac.in \
--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 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.