Date: Tue, 28 Mar 2017 12:44:05 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 203874] MSI/MSI-X interrupts don't work in VMware virtual machines Message-ID: <bug-203874-8-yTxbxs5pKD@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-203874-8@https.bugs.freebsd.org/bugzilla/> References: <bug-203874-8@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 igor@hybrid-lab.co.uk changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |igor@hybrid-lab.co.uk --- Comment #6 from igor@hybrid-lab.co.uk --- (In reply to bhavesh from comment #5) Is there still a good idea on to keep this blacklisting for ESXi, other than exposing bugs in fall-back code in drivers (https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D218113)? It's been nearly a year and a half since the last comment? I've removed the blacklisting for 11-RELEASE on my box inside ESXi 6.5 and there doesn't seem to be any previously reported signs of "badness" with LSI SAS emulation and igb(4) passthrough so far. --=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-8-yTxbxs5pKD>