[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [BUG] problems with NICs pass through to OpenBSD guest
- To: Adam Szewczyk <szewcson@xxxxxxxxx>
- From: Roger Pau Monné <roger.pau@xxxxxxxxxx>
- Date: Fri, 16 Sep 2022 15:35:20 +0200
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=citrix.com; dmarc=pass action=none header.from=citrix.com; dkim=pass header.d=citrix.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-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=99otT8we/7e0MOONlXF3h3V+jEf7LpLhX8cdYTMlN+Q=; b=W+79rIF2jWNXdh/5oB+21adj7qrQ3+/Gs/+erwhSLdMuN44B1ybY0sQxy4BAHopSbFCBqk3+yhd9A5LdgCmvhDSpMgLoXinzWQ4bl/Yv6901QN6YTcxWbVUuFjN4W5JMVSf7tmNRaK7udUXSSZDVIKPtKqFTJzdWnCIZ3GN657huydIU9Z/noADdREpMSypO/2nJOBGwq9oapsZ18tPearoGzfAs2/APuWj407ll6xPvuF/GHb3XY0cXOCFFI3Zz4XuAFmNqiIzCYKIFHENdlR4mpV/V/SBj939/l8eXUe8NwpXjF8Y4DgA+bOKA3rLDs+Wb8mALJUsJQfhCcOPDZA==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=nio5yoITYK5YRzYhcQK6+obUtqjv7NxWS0BSf92lhYLVzr3X/KUk2puiVZOqOBaKKRMxQsyB2QIe68o176zrymcHGmy+VtVDw71WDrwcuEq802/nvO1aCdMrQ13W/Q0E471rtLhGTJrmItqxG4kL7s/TPKBMssnESeenfCXGHAhsoonw4LgLBywDkZqlGfkVBEe+F0Lv8MnnpuW71dPARnKDwAk9jdYp0mbdBm3BQ+0Qo7Ld2oTDNhvCgFSXFdLdvPgMU7rXanu/uBGyEO49kN13tG9FNNXDcdmr1CLZlzSw7bsdRslb1r56Dg3mfkqciEFAOSMhr2e16LZiAYdP5w==
- Authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=citrix.com;
- Cc: xen-devel@xxxxxxxxxxxxx
- Delivery-date: Fri, 16 Sep 2022 13:35:48 +0000
- Ironport-data: A9a23:CsOaYKMXJAYKGJjvrR2llsFynXyQoLVcMsEvi/4bfWQNrUoh3zRSm 2NJC22HaPnfazf3f4ogPY+3pBkB6MeDn95gTAto+SlhQUwRpJueD7x1DKtR0wB+jCHnZBg6h ynLQoCYdKjYdleF+lH3dOCJQUBUjcmgXqD7BPPPJhd/TAplTDZJoR94kqsyj5UAbeKRWmthg vuv5ZyEULOZ82QsaDhMuvvd8EoHUMna41v0gHRvPZing3eG/5UlJMp3Db28KXL+Xr5VEoaSL woU5Ojklo9x105F5uKNyt4XQGVTKlLhFVHmZk5tc7qjmnB/Shkaic7XAha+hXB/0F1ll/gpo DlEWAfZpQ0BZsUgk8xFO/VU/r0X0QSrN9YrLFDm2fF/wXEqfFO9zeVpS0IfE7ZE3dhYO1gJy aQSJD0CO0Xra+KemNpXS8FKr+F6dYzBGtNavXttizbEEfwhXJbPBb3Q4sNV1ysxgcYIGuvCY 80eanxkaxGojx9nYw9LTs5h2rr4wCChI1W0q3rMzUYzy3LUwwFrlqDkLfLee8CQRNUTlUGdz o7D1zSiWElHa4XDodaD2k+jmOvGjSfnYagDBZK/26VOkg2c+XNGXXX6UnP++5FVkHWWQMBSN EcP/SwGoq079UjtRd74NzWorXjBshMCVt54F+wh9BrL2qfSpQGDCQA5oiVpbdUnsIo8Q2ws3 1rQxtfxX2Ux4PuSVG6X8aqSoXWqIy8JIGQeZCgCCwwY/93kp4J1hRXKJjp+LJOIYhTOMWmY6 1i3QOIW3N3/UeZjO32HwG36
- Ironport-hdrordr: A9a23:8OIbeaAVKauSb0vlHehJsceALOsnbusQ8zAXPh9KJCC9I/bzqy nxpp8mPH/P5wr5lktQ/OxoHJPwOE80kqQFmbX5XI3SOjUO3VHFEGgM1+vfKlHbak7DH6tmpN xdmstFeaHN5DpB/KHHCWCDer5PoeVvmJrY+Ns2pE0dKT2CBZsQjTuQXW2gYzdLrUR9dO0EPa vZwvACiyureHwRYMj+Ln4ZX9Lbr9mOsJ79exYJCzMu9QHL1FqTmffHOind+i1bfyJEwL8k/2 SAuwvl5p+7u/X+7hPHzWfc47lfhdOk4NpeA86njNQTN1zX+3CVTbUkf4fHkCE+oemp5lpvuN 7Qoy04N8A20H/VdnHdm2qe5yDQlBIVr1Pyw16RhnXu5ebjQighNsZHjYVFNjPE9ksJprhHoe 929lPck6ASIQLLnSz76dSNfQptjFCIrX0rlvNWp2BDULEZdKRaoeUkjQlo+a87bW3HAb0cYa dT5Jm23ocWTbraVQGTgoBX+q3hYpxpdS32AnTruaSuoktrdT5CvgglLfck7wY9HaIGOuZ5Dt v/Q9pVfZF1P7orhPFGdZM8aPryLFDxajTxF0/XCWjbNcg8SgLwQtjMkf0I2N0=
- List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
Again, please keep xen-devel on Cc and don't top-post.
On Fri, Sep 16, 2022 at 03:19:30PM +0200, Adam Szewczyk wrote:
> I executed it in dom0 terminal and it prints lots of stuff, but when I run
> jus xl dmesg it prints almost the same logs. So I'm not sure if I have
> right output or what I shuld search for to paste it here.
Hm, you should see something like:
(XEN) [ 8729.266567] MSI information:
[...]
(XEN) [ 8709.154958] IRQ information:
[...]
In the output of `xl dmesg`
You can paste the full output of `xl dmesg`, that should be fine.
> Regards Adam.
>
> pt., 16 wrz 2022, 15:09 użytkownik Roger Pau Monné <roger.pau@xxxxxxxxxx>
> napisał:
>
> > Please keep xen-devel in Cc and avoid top-posting.
> >
> > On Fri, Sep 16, 2022 at 02:35:17PM +0200, Adam Szewczyk wrote:
> > > > 0:7:0: Intel AC 9560
> > > > 0x0000: Vendor ID: 8086, Product ID: a370
> > > > 0x0004: Command: 0006, Status: 0010
> > > > 0x0008: Class: 02 Network, Subclass: 80 Miscellaneous,
> > > > Interface: 00, Revision: 10
> > > > 0x000c: BIST: 00, Header Type: 80, Latency Timer: 00,
> > > > Cache Line Size: 00
> > > > 0x0010: BAR mem 64bit addr: 0x00000000f2014000/0x00004000
> > > > 0x0018: BAR empty (00000000)
> > > > 0x001c: BAR empty (00000000)
> > > > 0x0020: BAR empty (00000000)
> > > > 0x0024: BAR empty (00000000)
> > > > 0x0028: Cardbus CIS: 00000000
> > > > 0x002c: Subsystem Vendor ID: 8086 Product ID: 0034
> > > > 0x0030: Expansion ROM Base Address: 00000000
> > > > 0x0038: 00000000
> >
> > None of the BARs are at 0x404000 which seems to be where OpenBSD is
> > trying to load the firmware?
> >
> > I would have to look at the code to figure out exactly what it is
> > trying to do here (and why it fails).
> >
> > Can you also paste the output from `lspci -v`?
You seem to have missed this bit.
Regards, Roger.
|
