[Bug 1894869] Re: Chelsio T4 has old MSIX PBA offset bug

2020-10-22 Thread Bug Watch Updater
** Changed in: debian Status: In Progress => 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

[Bug 1894869] Re: Chelsio T4 has old MSIX PBA offset bug

2020-09-15 Thread Alex Williamson
The device ID on function 7 is 0x 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

[Bug 1894869] Re: Chelsio T4 has old MSIX PBA offset bug

2020-09-15 Thread Nick Bauer
I was able to boot a VM with just the functions of the device with the ethernet controller function ID added as PCI devices. Something I noticed while adding in those devices though is that all of the others have a description associated with them in Proxmox, but the one that's causing the boot to

[Bug 1894869] Re: Chelsio T4 has old MSIX PBA offset bug

2020-09-15 Thread Alex Williamson
I don't understand the purpose of function 7 on these cards, the class code indicates an Ethernet device, but without any BARs, I very much doubt that the functions provide any useful service. Config space is invalid for the function as QEMU identifies, the referenced BAR resource for the MSI-X

[Bug 1894869] Re: Chelsio T4 has old MSIX PBA offset bug

2020-09-15 Thread Nick Bauer
Yeah, I figured out that the logic behind that patch was failed and corrected it to get the same error again already. Just to clarify, it is two of the same card giving the same error. I ran dmesg --level=err, but got no output. In the full output of dmesg, though, I noticed that there are some

[Bug 1894869] Re: Chelsio T4 has old MSIX PBA offset bug

2020-09-14 Thread Bug Watch Updater
Launchpad has imported 14 comments from the remote bug at https://bugzilla.proxmox.com/show_bug.cgi?id=2969. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at

[Bug 1894869] Re: Chelsio T4 has old MSIX PBA offset bug

2020-09-14 Thread Alex Williamson
PS, this can never be true: + (vdev->device_id & 0xff00) == 0x1425)) The lower byte would always be 00. It's the wrong fix anyway, BAR4 is still missing. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU.

[Bug 1894869] Re: Chelsio T4 has old MSIX PBA offset bug

2020-09-14 Thread Alex Williamson
There are no BAR resources for this device: 83:00.7 Ethernet controller [0200]: Chelsio Communications Inc Device [1425:] Subsystem: Chelsio Communications Inc Device [1425:] Physical Slot: 818 Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr+

[Bug 1894869] Re: Chelsio T4 has old MSIX PBA offset bug

2020-09-14 Thread Nick Bauer
** Bug watch added: bugzilla.proxmox.com/ #2969 https://bugzilla.proxmox.com/show_bug.cgi?id=2969 ** Also affects: debian via https://bugzilla.proxmox.com/show_bug.cgi?id=2969 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of

[Bug 1894869] Re: Chelsio T4 has old MSIX PBA offset bug

2020-09-09 Thread Nick Bauer
** Description changed: There exists a bug with Chelsio NICs T4 that causes the following error: kvm: -device vfio- pci,host=:83:00.7,id=hostpci1.7,bus=pci.0,addr=0x11.7: vfio :83:00.7: hardware reports invalid configuration, MSIX PBA outside of specified BAR - I was