Date: Tue, 20 Oct 2015 21:53:36 +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-WcxYMcq8bq@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=203874 Marius Strobl <marius@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |marius@FreeBSD.org --- Comment #2 from Marius Strobl <marius@FreeBSD.org> --- Removing the ESXi MSI-X quirk altogether simply is way too gross as the intention is to provide a setup which at least works out of the box, also on older versions of the the VMM and even if that doesn't yield the optimal configuration. As you apparently work for VMware, could you please get the revision ID in the PCI header of 0x079015ad and 0x07a015ad bridges bumped for the implementations that have MSI-X allocation fixed - if that hasn't already be done, yet -, so we can distinguish the good from the bad ones in the PCI code? My logs indicate that at least the bridges reporting revision 0x1 were affected. -- 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-WcxYMcq8bq>