[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: pci passthrough issue introduced between 4.14.1 and 4.15.0

  • To: AL13N <alien@xxxxxxxx>
  • From: Jan Beulich <jbeulich@xxxxxxxx>
  • Date: Tue, 1 Jun 2021 16:33:43 +0200
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=suse.com; dmarc=pass action=none header.from=suse.com; dkim=pass header.d=suse.com; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=WPcPwxps5kyMy7X8TpWBhD/PnI8UMa6lr20ghPnD918=; b=Wf3wq6h2uGFgTB7YBHCtDcBRrkbIGxs9Bef1eH7JVaHwYUVsSa9IL7++2t8nt710nLmXj5HODL63oLrPV1QUMioAhEGAFh48lTTzmXGK+Ugi1apzQC3DTmRP6IwNCgznHnlc0xSizfFZEw5JhaqHORkCad1gRHLfBLkdb9qyuOcWJ5j4Qt6rAvkuYBV4ZzhqQ4G3FaUOUiDDcX/CJXAhY/fy/HTLxoFmrZFSWQpso0Rj5poGIE/OuB2umfGIkA/fuZfGrADGf3EsRezoYNURQQXzAq22GvP4aU29cPJiN4TeDbuhxcdAJa+totp/Z4+BFIUURnjopKCBytWiu+3i7Q==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=I02Qou4eiuomiTz+N8vP9AQcCrXJme7566hUmkDcxlxgxI6I4YAyHqAFFM7EmX5xUYRPli4csDaVu+BxTcDLZT3dsf1N7UsT2XFvxBgkZWHP4ilA8ExiIoPxtU3o4Nbu6Vg+ep4w6XtXJftEFwiTk4koNm2Kk1eOrtefGi4+blUxd9etuOBlZzdEWD3Wr0F32tsJlhLtVkdok2okPvqJR2XyMBE68TTdWQMAYNrOmJexRB9ooUIdA+Kt+9cvHzIP6t7cjSx/VlaifEkEPFT8PcnIRfI5PS1JSa+ZWWGVkKAH9XyU0lfnchVgehETa1+FwBwJzbi0kej5NYlRuH856w==
  • Authentication-results: lists.xen.org; dkim=none (message not signed) header.d=none;lists.xen.org; dmarc=none action=none header.from=suse.com;
  • Cc: Xen-devel <xen-devel@xxxxxxxxxxxxx>
  • Delivery-date: Tue, 01 Jun 2021 14:33:57 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>

On 01.06.2021 16:06, AL13N wrote:
> Jan Beulich schreef op 2021-06-01 12:08:
>> On 01.06.2021 09:36, AL13N wrote:
>>> Not 100% it's a bug or something i did wrong, but,
>>> with xl create i start a PV with 3 pci passthroughs
>>> after wards, xl pci-list shows all 3 nicely
>>> looking at the domU boot logs, pcifront is only creating one pci 
>>> device
>>> and lspci in the guest shows only 1 pci entry
>>> in at least 4.14.1 it still works.
>> This reminds me of my report at
>> https://lists.xen.org/archives/html/xen-devel/2021-03/msg00956.html
>> Meanwhile the proposed pciback change has gone in upstream:
>> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/xen/xen-pciback?id=c81d3d24602540f65256f98831d0a25599ea6b87
>> I wasn't, however, aware that this may have been an issue going
>> from 4.14.1 to 4.15.0, i.e. something that was presumably (as
>> George also has just said) a regression in the tools. Or else I
>> probably wouldn't have suggested taking care of this in Linux.
>> Nevertheless you may want to give that change a try.
> Well, both tests have only different tools en hypervisor, no kernel was 
> changed between both tests, neither in dom0 or domU , so, it might not 
> be pciback?

Well, if the problem was introduced in the tools and this having been
the reason for me running into the same or a similar issue, the patch
may still address the issue, even if - in case it's a regression in
the tools - it would have been better to also address the issue there.
As said, when analyzing the issue I didn't have indications of changed
tool stack behavior, i.e. I assumed the problem would have always been




Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.