There are no BAR resources for this device:
83:00.7 Ethernet controller [0200]: Chelsio Communications Inc Device
[1425:0000]
Subsystem: Chelsio Communications Inc Device [1425:0000]
Physical Slot: 818
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr+
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- >SERR- <PERR- INTx-
NUMA node: 1
Note the lack of any regions here.
Capabilities: [40] Power Management version 3
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D3 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [48] MSI: Enable- Count=1/32 Maskable+ 64bit+
Address: 0000000000000000 Data: 0000
Masking: 00000000 Pending: 00000000
Capabilities: [60] MSI-X: Enable- Count=32 Masked-
Vector table: BAR=4 offset=00000000
PBA: BAR=4 offset=00001000
There is no BAR4 for either the vector table or the PBA, the device is
broken. Maybe check dmesg for resource allocation errors. Note that a
device ID of 0000 is also reported for this device. Does this device
provide any useful function in the host outside of vfio?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1894869
Title:
Chelsio T4 has old MSIX PBA offset bug
Status in QEMU:
New
Status in Debian:
Unknown
Bug description:
There exists a bug with Chelsio NICs T4 that causes the following
error:
kvm: -device vfio-
pci,host=0000:83:00.7,id=hostpci1.7,bus=pci.0,addr=0x11.7: vfio
0000:83:00.7: hardware reports invalid configuration, MSIX PBA outside
of specified BAR
I discovered this bug on a Proxmox system, and I was working with a
downstream Proxmox developer to try to fix this issue. They provided
me with the following change to make from line 1484 of hw/vfio/pci.c:
static void vfio_msix_early_setup(VFIOPCIDevice *vdev, Error **errp)
* is 0x1000, so we hard code that here.
*/
if (vdev->vendor_id == PCI_VENDOR_ID_CHELSIO &&
- (vdev->device_id & 0xff00) == 0x5800) {
+ ((vdev->device_id & 0xff00) == 0x5800 ||
+ (vdev->device_id & 0xff00) == 0x1425)) {
msix->pba_offset = 0x1000;
} else if (vdev->msix_relo == OFF_AUTOPCIBAR_OFF) {
error_setg(errp, "hardware reports invalid configuration, "
However, I found that this did not fix the issue, so the bug appears
to work differently than the one that was present on the T5 NICs which
has already been patched. I have attached the output of my lspci
-nnkvv
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1894869/+subscriptions
