VMware Cloud Community
g_rzegorz
Contributor
Contributor

PCI device not map correctly for using as passthrough on Z490 chipset

Hello,

I have a problem with the configuration of the TBS TV tuner after switching to a new server configuration.

So far I've been using the configuration for several years:

Esxi 6.7.0
Processor: i7-4770S CPU
motherboard: Asrcok Z87 Extreme3
tuner: TBS 6982

Everything works fine, the card is easily configured after passthru and added to the linux machine.
Everything has been working fine and stable for years.


However, it's time to change the server to a newer configuration:

Esxi 8.0.1
processor: i7-10700
Motherboard: MSI Z490 A PRO
tuner: tuner: TBS 6982

Unfortunately, after configuring the system, it turned out that there is a problem with configuring the tuner via passthru.
Unfortunately, it does not appear in the device list. Other cards, e.g. LSI controller, can be configured as passthru.
The problem is only with this card.
I checked the Esx versions 6.0 6.5 6.7 7.0 8.0 and all the same - so I assume it's rather a problem with the chipset and the motherboard.

I also managed to make a test on another board with a processor:

processor: i7-8700
Motherboard: Asrock Z370 PRO4
tuner: tuner: TBS 6982

and unfortunately the problem also occurs!!.

 

Below are screenshots of what it looks like on the "old" server and the "new" one

In the list of devices after inserting the card, the device 1c:0 and 1c:6 appear as in the picture:

This is "new" server z490 chipset:

z490-with_TBS.jpg

 

 

This is old "server" with Z87 chipset:

z87-with_TBS.jpg

 

From the console it looks like this:

 

This is "new" server z490 chipset:

 

 

 

[root@localhost:~] lspci
0000:00:00.0 Host bridge: Intel Corporation 10th Gen Core Processor Host Bridge/DRAM Registers
0000:00:01.0 PCI bridge: Intel Corporation 6th-10th Gen Core Processor PCIe Controller (x16)
0000:00:02.0 VGA compatible controller: Intel Corporation CometLake-S GT2 [UHD Graphics 630]
0000:00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model
0000:00:12.0 Signal processing controller: Intel Corporation Comet Lake PCH Thermal Controller
0000:00:14.0 USB controller: Intel Corporation Comet Lake USB 3.1 xHCI Host Controller
0000:00:14.2 RAM memory: Intel Corporation Comet Lake PCH Shared SRAM
0000:00:16.0 Communication controller: Intel Corporation Comet Lake HECI Controller
0000:00:17.0 SATA controller: Intel Corporation Comet Lake SATA AHCI Controller
0000:00:1b.0 PCI bridge: Intel Corporation Comet Lake PCI Express Root Port #17
0000:00:1b.4 PCI bridge: Intel Corporation Comet Lake PCI Express Root Port #21

0000:00:1c.0 PCI bridge: Intel Corporation Device 06b8
0000:00:1c.6 PCI bridge: Intel Corporation Device 06be

0000:00:1f.0 ISA bridge: Intel Corporation Z490 Chipset LPC/eSPI Controller
0000:00:1f.3 Audio device: Intel Corporation Comet Lake PCH cAVS
0000:00:1f.4 SMBus: Intel Corporation Comet Lake PCH SMBus Controller
0000:00:1f.5 Serial bus controller: Intel Corporation Comet Lake PCH SPI Controller
0000:01:00.0 RAID bus controller: Broadcom MegaRAID SAS Invader Controller
0000:03:00.0 Ethernet controller: Intel Corporation PRO/1000 PT Dual Port Server Adapter
0000:03:00.1 Ethernet controller: Intel Corporation PRO/1000 PT Dual Port Server Adapter

 

 

 

This is old "server" with Z87 chipset:

 

 

 

[root@localhost:~] lspci
0000:00:00.0 Bridge: Intel Corporation 4th Gen Core Processor DRAM Controller
0000:00:01.0 Bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller [PCIe RP[0000:00:01.0]]
0000:00:02.0 Display controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller
0000:00:03.0 Multimedia controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller
0000:00:14.0 Serial bus controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI [vmhba32]
0000:00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1
0000:00:19.0 Network controller: Intel Corporation Ethernet Connection I217-V [vmnic0]
0000:00:1a.0 Serial bus controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2
0000:00:1b.0 Multimedia controller: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller
0000:00:1c.0 Bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 [PCIe RP[0000:00:1c.0]]
0000:00:1c.2 Bridge: Intel Corporation 82801 PCI Bridge [PCIe RP[0000:00:1c.2]]
0000:00:1c.4 Bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #5 [PCIe RP[0000:00:1c.4]]
0000:00:1c.6 Bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #7 [PCIe RP[0000:00:1c.6]]
0000:00:1d.0 Serial bus controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1
0000:00:1f.0 Bridge: Intel Corporation Z87 Express LPC Controller
0000:00:1f.2 Mass storage controller: Intel Corporation Lynx Point AHCI Controller [vmhba0]
0000:00:1f.3 Serial bus controller: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller
0000:01:00.0 Bridge: Integrated Device Technology, Inc. [IDT] PES12N3A PCI Express Switch
0000:02:02.0 Bridge: Integrated Device Technology, Inc. [IDT] PES12N3A PCI Express Switch
0000:02:04.0 Bridge: Integrated Device Technology, Inc. [IDT] PES12N3A PCI Express Switch
0000:03:00.0 Network controller: Intel Corporation 82571EB Gigabit Ethernet Controller (Copper) [vmnic1]
0000:03:00.1 Network controller: Intel Corporation 82571EB Gigabit Ethernet Controller (Copper) [vmnic2]
0000:04:00.0 Network controller: Intel Corporation 82571EB Gigabit Ethernet Controller (Copper) [vmnic3]
0000:04:00.1 Network controller: Intel Corporation 82571EB Gigabit Ethernet Controller (Copper) [vmnic4]
0000:06:00.0 Bridge: ASMedia Technology Inc. ASM1083/1085 PCIe to PCI Bridge
0000:08:00.0 Mass storage controller: LSI Logic / Symbios Logic LSI2008 [vmhba1]

0000:09:00.0 Multimedia controller: Philips Semiconductors SAA7160

 

 

 

I looked in the dmesg logs and found the following entries for this device:

 

This is "new" server z490 chipset:

 

 

[root@localhost:~] dmesg | grep ':1c'
0:00:00:05.348 cpu0:1048576)VMKAcpi: 225:  pci bus (00) 00:1c, pin INTA, ioapicID=2, intIn=16, trigger=levl, polarity=lo
0:00:00:05.348 cpu0:1048576)VMKAcpi: 225:  pci bus (00) 00:1c, pin INTB, ioapicID=2, intIn=17, trigger=levl, polarity=lo
0:00:00:05.348 cpu0:1048576)VMKAcpi: 225:  pci bus (00) 00:1c, pin INTC, ioapicID=2, intIn=18, trigger=levl, polarity=lo
0:00:00:05.348 cpu0:1048576)VMKAcpi: 225:  pci bus (00) 00:1c, pin INTD, ioapicID=2, intIn=19, trigger=levl, polarity=lo
2023-05-27T21:03:50.012Z cpu0:1048576)PCIE: 685: 0000:00:1c.0: PCIe v2 PCI Express Root Complex Port
2023-05-27T21:03:50.012Z cpu0:1048576)PCI: 1320: Found a PCIe-to-PCIe bridge at 0000:00:1c.0
2023-05-27T21:03:50.012Z cpu0:1048576)PCIE: 685: 0000:00:1c.6: PCIe v2 PCI Express Root Complex Port
2023-05-27T21:03:50.012Z cpu0:1048576)PCI: 1320: Found a PCIe-to-PCIe bridge at 0000:00:1c.6
2023-05-27T21:03:50.012Z cpu0:1048576)PCI: 395: Found physical slot 0x4 (peer 0x0) from SMBIOS entry of 0000:00:1c.6 for 0000:00:1c.6
2023-05-27T21:03:50.012Z cpu0:1048576)PCI: 404: Found description "J8B4" from SMBIOS entry of 0000:00:1c.6 for 0000:00:1c.6
2023-05-27T21:03:50.012Z cpu0:1048576)PCI: 1045: 0000:00:1c.0: probing 8086:06b8 0000:0000 0604 00f0
2023-05-27T21:03:50.012Z cpu0:1048576)PCI: 532:   Adding bus 04 with parent 0000:00:1c.0
2023-05-27T21:03:50.012Z cpu0:1048576)PCI: 339: probe-scanning pcie bridge @ 0000:00:1c.0 (spawned-bus = 04)
2023-05-27T21:03:50.012Z cpu0:1048576)PCI: 1045: 0000:00:1c.6: probing 8086:06be 0000:0000 0604 00f0
2023-05-27T21:03:50.012Z cpu0:1048576)PCI: 532:   Adding bus 05 with parent 0000:00:1c.6
2023-05-27T21:03:50.012Z cpu0:1048576)PCI: 339: probe-scanning pcie bridge @ 0000:00:1c.6 (spawned-bus = 05)
2023-05-27T21:03:50.014Z cpu0:1048576)PCI: 1299: 0000:00:1c.0: registering 8086:06b8 0000:0000
2023-05-27T21:03:50.014Z cpu0:1048576)Device: 1550: Registered device: 0x4306a3801eb0 p0000:00:1c.0 808606b800000000060400 (parent=0x41ca4306a38019de)
2023-05-27T21:03:50.014Z cpu0:1048576)PCIE: 634: 0000:00:1c.0: claimed by PCIe port module.
2023-05-27T21:03:50.014Z cpu0:1048576)PCI: 308: skipping probe-scanning pcie bridge @ 0000:00:1c.0 (spawned-bus = 04)
2023-05-27T21:03:50.014Z cpu0:1048576)PCI: 339: register-scanning pcie bridge @ 0000:00:1c.0 (spawned-bus = 04)
2023-05-27T21:03:50.014Z cpu0:1048576)PCI: 1299: 0000:00:1c.6: registering 8086:06be 0000:0000
2023-05-27T21:03:50.014Z cpu0:1048576)Device: 1550: Registered device: 0x4306a3801eb0 p0000:00:1c.6 808606be00000000060400 (parent=0x41ca4306a38019de)
2023-05-27T21:03:50.014Z cpu0:1048576)PCIE: 634: 0000:00:1c.6: claimed by PCIe port module.
2023-05-27T21:03:50.014Z cpu0:1048576)PCI: 308: skipping probe-scanning pcie bridge @ 0000:00:1c.6 (spawned-bus = 05)
2023-05-27T21:03:50.014Z cpu0:1048576)PCI: 339: register-scanning pcie bridge @ 0000:00:1c.6 (spawned-bus = 05)
2023-05-27T21:04:50.781Z cpu8:1050360)PCIE: 203: 0000:00:1c.0: Bypassing non-ACS capable device in hierarchy
2023-05-27T21:04:50.781Z cpu8:1050360)PCIE: 187: 0000:00:1c.6: PCI Express Root Complex Port ACS settings (V, U) not configured for blocking P2P
2023-05-27T21:04:50.781Z cpu8:1050360)PCIE: 203: 0000:00:1c.6: Bypassing non-ACS capable device in hierarchy

 

 

 

This is old "server" with Z87 chipset:

 

 

 

[root@localhost:~] dmesg | grep '00:1c'
0:00:00:04.328 cpu0:2097152)VMKAcpi: 235:  pci bus (00) 00:1c, pin INTA, ioapicID=2, intIn=16, trigger=levl, polarity=lo
0:00:00:04.328 cpu0:2097152)VMKAcpi: 235:  pci bus (00) 00:1c, pin INTB, ioapicID=2, intIn=17, trigger=levl, polarity=lo
0:00:00:04.328 cpu0:2097152)VMKAcpi: 235:  pci bus (00) 00:1c, pin INTC, ioapicID=2, intIn=18, trigger=levl, polarity=lo
0:00:00:04.328 cpu0:2097152)VMKAcpi: 235:  pci bus (00) 00:1c, pin INTD, ioapicID=2, intIn=19, trigger=levl, polarity=lo
0:00:00:04.347 cpu0:2097152)PCI: 474: 0000:00:1c.0: PCIe v2 PCI Express Root Complex Port
0:00:00:04.347 cpu0:2097152)PCI: 1305: Found a PCIe-to-PCIe bridge at 0000:00:1c.0
0:00:00:04.347 cpu0:2097152)PCI: 409: 0000:00:1c.0: PCIe v2 PCI Express Root Complex Port
0:00:00:04.347 cpu0:2097152)PCI: 474: 0000:00:1c.2: PCIe v2 PCI Express Root Complex Port
0:00:00:04.347 cpu0:2097152)PCI: 1305: Found a PCIe-to-PCIe bridge at 0000:00:1c.2
0:00:00:04.347 cpu0:2097152)PCI: 409: 0000:00:1c.2: PCIe v2 PCI Express Root Complex Port
0:00:00:04.347 cpu0:2097152)PCI: 474: 0000:00:1c.4: PCIe v2 PCI Express Root Complex Port
0:00:00:04.347 cpu0:2097152)PCI: 1305: Found a PCIe-to-PCIe bridge at 0000:00:1c.4
0:00:00:04.347 cpu0:2097152)PCI: 409: 0000:00:1c.4: PCIe v2 PCI Express Root Complex Port
0:00:00:04.347 cpu0:2097152)PCI: 474: 0000:00:1c.6: PCIe v2 PCI Express Root Complex Port
0:00:00:04.347 cpu0:2097152)PCI: 1305: Found a PCIe-to-PCIe bridge at 0000:00:1c.6
0:00:00:04.347 cpu0:2097152)PCI: 409: 0000:00:1c.6: PCIe v2 PCI Express Root Complex Port
0:00:00:04.347 cpu0:2097152)PCI: 1042: 0000:00:1c.0: probing 8086:8c10 0000:0000
0:00:00:04.347 cpu0:2097152)PCI: 405: 0000:00:1c.0: Adding to resource tracker under parent Root.
0:00:00:04.347 cpu0:2097152)PCI: 354: probe-scanning pcie bridge @ seg‌‌slot 0000:00:1c (spawned-bus = 05)
0:00:00:04.347 cpu0:2097152)PCI: 1042: 0000:00:1c.2: probing 8086:244e 0000:0000
0:00:00:04.347 cpu0:2097152)PCI: 405: 0000:00:1c.2: Adding to resource tracker under parent Root.
0:00:00:04.347 cpu0:2097152)PCI: 354: probe-scanning pcie bridge @ seg‌‌slot 0000:00:1c (spawned-bus = 06)
0:00:00:04.348 cpu0:2097152)PCI: 405: 0000:06:00.0: Adding to resource tracker under parent 0000:00:1c.2.
0:00:00:04.348 cpu0:2097152)PCI: 1042: 0000:00:1c.4: probing 8086:8c18 0000:0000
0:00:00:04.348 cpu0:2097152)PCI: 405: 0000:00:1c.4: Adding to resource tracker under parent Root.
0:00:00:04.348 cpu0:2097152)PCI: 354: probe-scanning pcie bridge @ seg‌‌slot 0000:00:1c (spawned-bus = 08)
0:00:00:04.348 cpu0:2097152)PCI: 820: ARI-capable device 0000:08:00.0 under non-ARI-capable bridge 0000:00:1c.4
0:00:00:04.348 cpu0:2097152)PCI: 405: 0000:08:00.0: Adding to resource tracker under parent 0000:00:1c.4.
0:00:00:04.348 cpu0:2097152)PCI: 1042: 0000:00:1c.6: probing 8086:8c1c 0000:0000
0:00:00:04.348 cpu0:2097152)PCI: 405: 0000:00:1c.6: Adding to resource tracker under parent Root.
0:00:00:04.348 cpu0:2097152)PCI: 354: probe-scanning pcie bridge @ seg‌‌slot 0000:00:1c (spawned-bus = 09)
0:00:00:04.348 cpu0:2097152)PCI: 405: 0000:09:00.0: Adding to resource tracker under parent 0000:00:1c.6.
0:00:00:04.349 cpu0:2097152)PCI: 1257: 0000:00:1c.0: registering 8086:8c10 0000:0000
0:00:00:04.349 cpu0:2097152)Device: 1466: Registered device: 0x4304b2376790 p0000:00:1c.0 80868c1000000000060400 (parent=0x77f74304b237683f)
0:00:00:04.349 cpu0:2097152)PCI: 321: skipping probe-scanning pcie bridge @ seg‌‌slot 0000:00:1c (spawned-bus = 05)
0:00:00:04.349 cpu0:2097152)PCI: 354: register-scanning pcie bridge @ seg‌‌slot 0000:00:1c (spawned-bus = 05)
0:00:00:04.350 cpu0:2097152)PCI: 1257: 0000:00:1c.2: registering 8086:244e 0000:0000
0:00:00:04.350 cpu0:2097152)Device: 1466: Registered device: 0x4304b2376790 p0000:00:1c.2 8086244e00000000060401 (parent=0x77f74304b237683f)
0:00:00:04.350 cpu0:2097152)PCI: 321: skipping probe-scanning pcie bridge @ seg‌‌slot 0000:00:1c (spawned-bus = 06)
0:00:00:04.350 cpu0:2097152)PCI: 354: register-scanning pcie bridge @ seg‌‌slot 0000:00:1c (spawned-bus = 06)
0:00:00:04.350 cpu0:2097152)PCI: 1257: 0000:00:1c.4: registering 8086:8c18 0000:0000
0:00:00:04.350 cpu0:2097152)Device: 1466: Registered device: 0x4304b2376790 p0000:00:1c.4 80868c1800000000060400 (parent=0x77f74304b237683f)
0:00:00:04.350 cpu0:2097152)PCI: 321: skipping probe-scanning pcie bridge @ seg‌‌slot 0000:00:1c (spawned-bus = 08)
0:00:00:04.350 cpu0:2097152)PCI: 354: register-scanning pcie bridge @ seg‌‌slot 0000:00:1c (spawned-bus = 08)
0:00:00:04.350 cpu0:2097152)PCI: 1257: 0000:00:1c.6: registering 8086:8c1c 0000:0000
0:00:00:04.350 cpu0:2097152)Device: 1466: Registered device: 0x4304b2376790 p0000:00:1c.6 80868c1c00000000060400 (parent=0x77f74304b237683f)
0:00:00:04.350 cpu0:2097152)PCI: 321: skipping probe-scanning pcie bridge @ seg‌‌slot 0000:00:1c (spawned-bus = 09)
0:00:00:04.350 cpu0:2097152)PCI: 354: register-scanning pcie bridge @ seg‌‌slot 0000:00:1c (spawned-bus = 09)

 

 

[root@localhost:~] dmesg | grep '00:09'
0:00:00:04.328 cpu0:2097152)VMKAcpi: 235: legacy* bus (100) 00:09, pin INT , ioapicID=2, intIn=9, trigger=levl, polarity=hi
0:00:00:04.348 cpu0:2097152)PCI: 474: 0000:09:00.0: PCIe v1 PCI Express Endpoint
0:00:00:04.348 cpu0:2097152)PCI: 234: 0000:09:00.0: Found support for extended capability 0xb (Vendor Specific)
0:00:00:04.348 cpu0:2097152)PCI: 141: Found physical slot 0x12 from $PIR for 0000:09:00.0
0:00:00:04.348 cpu0:2097152)PCI: 409: 0000:09:00.0: PCIe v1 PCI Express Endpoint
0:00:00:04.348 cpu0:2097152)PCI: 1042: 0000:09:00.0: probing 1131:7160 6982:0002
0:00:00:04.348 cpu0:2097152)PCI: 405: 0000:09:00.0: Adding to resource tracker under parent 0000:00:1c.6.
0:00:00:04.350 cpu0:2097152)PCI: 1257: 0000:09:00.0: registering 1131:7160 6982:0002
2023-05-27T00:23:09.180Z cpu6:2097549)PCI: 814: 0000:09:00.0 to 3
2023-05-27T00:23:09.180Z cpu6:2097549)WARNING: PCI: 178: 0000:09:00.0: Bypassing non-ACS capable device in hierarchy
2023-05-27T00:23:10.844Z cpu7:2097561)WARNING: PCI: 178: 0000:09:00.0: Bypassing non-ACS capable device in hierarchy
2023-05-27T00:23:10.844Z cpu7:2097561)PCIPassthru: PCIPassthruAttachDev:221: Attached to PCI device at 0000:09:00.0
2023-05-27T00:23:10.844Z cpu7:2097561)PCIPassthru: PCIPassthruStartDev:362: Received start request for PCI device at 0000:09:00.0
2023-05-27T00:23:10.844Z cpu7:2097561)PCIPassthru: PCIPassthruScanDev:264: Received scan request for PCI device at 0000:09:00.0
2023-05-27T00:26:48.244Z cpu1:2099531)IOMMU: 2451: Device 0000:09:00.0 placed in new domain 0x43049e251820.
2023-05-27T00:26:56.518Z cpu7:2099539)IOMMU: 2451: Device 0000:09:00.0 placed in new domain 0x43049e251820.

 

Do you have any idea how to run the card so that it can be properly added via passthrough,
to the virtual machine as I have done so far? 🙂

 

Reply
0 Kudos
0 Replies