Date: Fri, 04 Jan 2019 19:42:39 +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-OobCdERK5w@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 #18 from igor@hybrid-lab.co.uk --- (In reply to John Baldwin from comment #17) In order to investigate anything that sporadically breaks, you need to know= how to break it. Like I said in comment #6 when I disabled the hack, nothing was breaking; so why would anyone spend $$$ investigating anything without even= a clue as to a path to break it? My interpretation of comment #3 is "Our implementation is in accordance with the spec. Do you have a specific scena= rio that takes our implementation outside of the spec?" To which nothing was produced. Similarly, as bug #218113 shows MSI-X was also "hacked" for KVM (I don't kn= ow if that's still the case), so it would seem that according to FreeBSD neith= er KVM nor ESXi implement the hardware side of MSI-X properly? C'mon! :-) --=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-OobCdERK5w>