From mboxrd@z Thu Jan 1 00:00:00 1970 From: Yuanhan Liu Subject: Re: seg fault in InterVM communication using virtio Date: Thu, 23 Feb 2017 14:27:14 +0800 Message-ID: <20170223062714.GX18844@yliu-dev.sh.intel.com> References: <58AAC534.7000004@cse.iitb.ac.in> <20170222084323.GP18844@yliu-dev.sh.intel.com> <92b5577b-8c8a-e199-3b65-54323dbea48c@cse.iitb.ac.in> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Priyanka , "users@dpdk.org" , "dev@dpdk.org" To: mitali Return-path: Content-Disposition: inline In-Reply-To: <92b5577b-8c8a-e199-3b65-54323dbea48c@cse.iitb.ac.in> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 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