From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by dpdk.org (Postfix) with ESMTP id 5CEE25B2C for ; Mon, 21 Jan 2019 14:39:12 +0100 (CET) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by fmsmga101.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 21 Jan 2019 05:39:11 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.56,503,1539673200"; d="scan'208";a="313542990" Received: from aburakov-mobl1.ger.corp.intel.com (HELO [10.237.220.84]) ([10.237.220.84]) by fmsmga005.fm.intel.com with ESMTP; 21 Jan 2019 05:39:09 -0800 To: "Hu, Xuekun" , Ravi Kerur , Thomas Monjalon Cc: "dev@dpdk.org" , "Ananyev, Konstantin" , "Lu, Wenzhuo" References: <4a54fe58-02d8-07ef-b706-f747383f4985@intel.com> <3b6d6cfc-7e2e-70ee-e059-aa31dc23c93b@intel.com> <1ab980ce-16a5-4bf4-e673-b706e3126474@intel.com> <88A92D351643BA4CB23E303155170626635418D0@SHSMSX103.ccr.corp.intel.com> <88A92D351643BA4CB23E30315517062663547499@SHSMSX103.ccr.corp.intel.com> From: "Burakov, Anatoly" Message-ID: Date: Mon, 21 Jan 2019 13:39:08 +0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0 MIME-Version: 1.0 In-Reply-To: <88A92D351643BA4CB23E30315517062663547499@SHSMSX103.ccr.corp.intel.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit Subject: Re: [dpdk-dev] IXGBE, IOMMU DMAR DRHD handling fault issue 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, 21 Jan 2019 13:39:12 -0000 On 21-Jan-19 1:18 PM, Hu, Xuekun wrote: > >> You might also want to look here: https://bugs.dpdk.org/show_bug.cgi?id=76 > >> There are apparently issues with some kernel versions that will manifest themselves as problems with using VF devices with IOMMU in a VM. > > Thanks, Anatoly. By updating host kernel to 4.18, the issue is gone. 😊 > @Thomas, does this look like something we should add to known issues? This question has been asked a few times already. -- Thanks, Anatoly