From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.iitb.ac.in (smtp1.iitb.ac.in [103.21.127.13]) by dpdk.org (Postfix) with ESMTP id 413D92B9D for ; Thu, 2 Mar 2017 15:02:47 +0100 (CET) Received: from ldns1.iitb.ac.in (ldns1.iitb.ac.in [10.200.12.1]) by smtp1.iitb.ac.in (Postfix) with SMTP id 5F3BB10C for ; Thu, 2 Mar 2017 19:32:46 +0530 (IST) Received: (qmail 12843 invoked by uid 510); 2 Mar 2017 19:32:46 +0530 X-Qmail-Scanner-Diagnostics: from 10.200.1.25 by ldns1 (envelope-from , uid 501) with qmail-scanner-2.11 spamassassin: 3.4.1. mhr: 1.0. {clamdscan: 0.99.2/23153} Clear:RC:1(10.200.1.25):SA:0(0.0/5.6):. Processed in 2.853641 secs; 02 Mar 2017 19:32:46 +0530 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on ldns1.iitb.ac.in X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.6 tests=IITB_ORIG,PROPER_IITB_MSGID, T_RP_MATCHES_RCVD autolearn=disabled version=3.4.1 X-Spam-Pyzor: Reported 0 times. X-Envelope-From: mitaliyada@cse.iitb.ac.in X-Qmail-Scanner-Mime-Attachments: |gdb_error_call_stack.png|vm_gdb_error.png| X-Qmail-Scanner-Zip-Files: | Received: from unknown (HELO ldns1.iitb.ac.in) (10.200.1.25) by ldns1.iitb.ac.in with SMTP; 2 Mar 2017 19:32:43 +0530 Received: from jeeves.cse.iitb.ac.in (miller.cse.iitb.ac.in [10.129.3.1]) by ldns1.iitb.ac.in (Postfix) with ESMTP id 10562360044; Thu, 2 Mar 2017 19:32:43 +0530 (IST) Received: by jeeves.cse.iitb.ac.in (Postfix, from userid 51934) id EE3F38C239A; Thu, 2 Mar 2017 19:32:42 +0530 (IST) Received: from [10.129.2.155] (unknown [10.129.2.155]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by jeeves.cse.iitb.ac.in (Postfix) with ESMTPSA id D3FF08C2359; Thu, 2 Mar 2017 19:32:41 +0530 (IST) To: Yuanhan Liu References: <58AAC534.7000004@cse.iitb.ac.in> <20170222084323.GP18844@yliu-dev.sh.intel.com> <92b5577b-8c8a-e199-3b65-54323dbea48c@cse.iitb.ac.in> <20170223062714.GX18844@yliu-dev.sh.intel.com> <63560385-2261-7213-9e7c-6acef4d290c7@cse.iitb.ac.in> <20170302122342.GS18844@yliu-dev.sh.intel.com> <62e0d38c-f443-53f0-84c6-41a0ac47222d@cse.iitb.ac.in> <20170302125933.GU18844@yliu-dev.sh.intel.com> Cc: Priyanka , "users@dpdk.org" , "dev@dpdk.org" From: mitali Message-ID: Date: Thu, 2 Mar 2017 19:30:25 +0530 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 MIME-Version: 1.0 In-Reply-To: <20170302125933.GU18844@yliu-dev.sh.intel.com> X-Mailman-Approved-At: Thu, 02 Mar 2017 15:22:22 +0100 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="windows-1252"; Format="flowed" Subject: Re: [dpdk-users] [dpdk-dev] seg fault in InterVM communication using virtio X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Mar 2017 14:02:48 -0000 Hi, I rebuild dpdk with debug enabled and running the same dpdk application. Please go through the attached images showing the error as well as call = stack. Mitali On Thursday 02 March 2017 06:29 PM, Yuanhan Liu wrote: > On Thu, Mar 02, 2017 at 06:02:28PM +0530, mitali wrote: >> Hi, >> >> Ok. But with other PMDs like igb, when we are providing sriov vf to VM a= nd >> running our client/server dpdk application then there is no issue in >> communication between VMs. >> As soon as we use virtio setup for VMs and running same dpdk application= , it >> stops after sending 127 packet and seg fault comes while executing >> rte_eth_tx_burst(). We are still not clear why with virtio its creating = this >> issue but not with any other PMD. > No idea. You don't provide any further details. Please, would you just > enable the debug info, rebuild, run it with gdb and then dump the call > stack after crash? > > --yliu >> Mitali >> >> On Thursday 02 March 2017 05:53 PM, Yuanhan Liu wrote: >>> On Wed, Mar 01, 2017 at 07:20:37PM +0530, mitali wrote: >>>> Hi, >>>> >>>> We have some doubt regarding virtio front end. As we are running dpdk >>>> application inside VM with virtio setup, do we need to use virtio spec= ific >>>> functions like virtio_recv_pkts() and virtio_xmit_pkts() to receive and >>>> transmit packets, functions for port initialization like >>>> virtio_dev_queue_setup()? If yes, we are unable to find any application >>>> which uses these functions. Can you provide us some pointers on exampl= es >>>> which uses these functions. >>> If you are running DPDK inside guest (with virtio), then the virtio is >>> yet another PMD, meaning you should program it with the normal DPDK >>> ethdev APIs, something like rte_eth_dev_configure, rte_eth_rx/tx_queue_= setup, >>> etc. >>> >>> --yliu >>>> Thanks, >>>> Mitali >>>> >>>> On Thursday 23 February 2017 11:57 AM, Yuanhan Liu wrote: >>>>> 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 ima= ge which >>>>>> shows the vNIC setup for the VMs. >>>>>> >>>>>> We have written our own dpdk application to send and receive UDP pac= kets. 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 vNI= C using >>>>>> rte_eth_tx_burst() and rte_eth_rx_burst(). >>>>>> >>>>>> At the sender side after 127 packets the application stops and we ob= serve a seg >>>>>> fault in dmesg. Using the print statements we observed that it fault= s 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=3D'-g3 -O0' >>>>> >>>>> And run it with gdb then dump the call stack? >>>>> >>>>> --yliu -------------- next part -------------- A non-text attachment was scrubbed... Name: gdb_error_call_stack.png Type: image/png Size: 213966 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: vm_gdb_error.png Type: image/png Size: 304846 bytes Desc: not available URL: