From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by dpdk.org (Postfix) with ESMTP id AB3C92BB9 for ; Mon, 19 Dec 2016 09:29:36 +0100 (CET) Received: from int-mx11.intmail.prod.int.phx2.redhat.com (int-mx11.intmail.prod.int.phx2.redhat.com [10.5.11.24]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 16CFDC057FA4; Mon, 19 Dec 2016 08:29:36 +0000 (UTC) Received: from [10.36.116.128] (ovpn-116-128.ams2.redhat.com [10.36.116.128]) by int-mx11.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id uBJ8TXiT017040 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 19 Dec 2016 03:29:35 -0500 To: Sreenaath Vasudevan , dev@dpdk.org References: From: Maxime Coquelin Message-ID: Date: Mon, 19 Dec 2016 09:29:32 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.68 on 10.5.11.24 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.32]); Mon, 19 Dec 2016 08:29:36 +0000 (UTC) Subject: Re: [dpdk-dev] Virtio driver lockup in KVM X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Dec 2016 08:29:36 -0000 Hi Sreenaath, On 12/19/2016 09:21 AM, Sreenaath Vasudevan wrote: > Hi > I am running a DPDK application with virtio driver and ran in to driver rx > lockup issue. Are you running vhost-user DPDK backend on host or Kernel backend? > The application seems to be running fine for couple of hours before it > stops receiving packets on the interface. Transmission of packets seems to > work fine on the same interface while reception of packets stop. > Has anyone run in to anything similar? Not that I am aware, I would suggest you recompile DPDK with debug, attach to the DPDK process when it happens and check what PMd threads are doing. > > Following is the environment > Application runnign dpdk-2.2 > VM running on KVM hypervisor using VIRTIO driver > Cheers, Maxime