The device ID on function 7 is 0x0000 which is typically not valid,
there's no entry for it in the PCI IDs database. Someone from Chelsio
would need to explain why it's even exposed, but there doesn't seem to
be any value in quirking it since it provides no useful function.
** Changed in: qemu
Status: New => Invalid
--
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:
Invalid
Status in Debian:
In Progress
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
