[Bug 203874] [patch] MSI/MSI-X interrupts don't work in VMware virtual machines

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203874

--- Comment #24 from Chris Collins <chrysalis at chrysalisnet.org> ---
I would be ok with a 5.x only blacklist, the problem is I think there is no way
to seemingly identify it as apparently the pci id's are the same.

So I think should be two changes.

1 - For "all" hardware, if its on a blacklist, add something to DMESG that
tells the end user something like "MSIX disabled due to blacklist, can disable
via this bootloader"
As I think silently blocking a function is the wrong way to go about things.
2 - The default behaviour should be to suit the current supported builds of
vmware so default to no blacklist, but keep an option so those using
unsupported versions can still use the OS.  But if a way could be found to
differentiate between new and old vmware then yeah keep a blacklist for old
vmware.

Also another point of concern, so we know at this point the kernel developer
that replied here has vanished.

The vmware developers have written a pvscsi driver for FreeBSD, that driver is
suffering the same issues as this bug report.

It has sat in review status for nearly a year.  Initially the vmware developer
who submitted it was available for responses but I expect has now given up so
this issue of things been left in limbo status is holding back FreeBSD
virtualization capability.

This bug report was submitted 4 years ago, there does seem to be some kind of
issue with approach to this kind of thing.

-- 
You are receiving this mail because:
You are the assignee for the bug.