Date: Fri, 04 Jan 2019 19:32:09 +0000 From: bugzilla-noreply@freebsd.org To: virtualization@FreeBSD.org Subject: [Bug 203874] [patch] MSI/MSI-X interrupts don't work in VMware virtual machines Message-ID: <bug-203874-27103-N8oJB9DDbW@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-203874-27103@https.bugs.freebsd.org/bugzilla/> References: <bug-203874-27103@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D203874 --- Comment #17 from John Baldwin <jhb@FreeBSD.org> --- I don't think the commenter in #3 understood what "broken" might mean in the context of MSI or MSI-X, so I attempted to give more detail on how a partic= ular type of breakage might boot Linux ok but not FreeBSD (as was the case for X= en). However, if VMWare 6.0 is known to work we could alter the quirk to instead use the version of VMWare (e.g. via SMBIOS strings or what not) instead of = PCI device IDs to know when to apply the quirk. In terms of what VMware would investigate, I gave very specific details (do= you implement an MSI-X shadow table, etc.) that someone familiar with the implementation would be able to investigate. This is not "not caring", thi= s is "the best suggestions I can give of what to look for given what I know of h= ow FreeBSD's use of MSI-X differs from Linux assuming I don't get to look at t= he sources myself". --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-203874-27103-N8oJB9DDbW>