Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 15 Dec 2019 02:07:25 +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-IZwBe5MUt7@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

Mark Peek <mp@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mp@FreeBSD.org

--- Comment #29 from Mark Peek <mp@FreeBSD.org> ---
I looked into this issue a bit to better understand the lineage. There was a
report of issues for FreeBSD in ESXi 5.0 back in late 2011:
https://forums.freebsd.org/threads/freebsd-9-rc2-breaks-mpt-driver-when-use=
d-with-vmware-and-pcie-passthrough.27899/

And the blacklist quirk was added here in 2013-03:
https://svnweb.freebsd.org/base/head/sys/dev/pci/pci.c?revision=3D247632&vi=
ew=3Dmarkup

I could not find a bug report for the above FreeBSD issue within the VMware=
 bug
tracker. But it did show up as a Linux 4.3+ issue in 2016-01 reported again=
st
ESXi 6.0.

The issue and resolution was documented in this knowledge base article which
lists fixes in ESXi 5.5 patch 08 and 6.0 patch 03 which came out in 2016.
https://kb.vmware.com/s/article/2150585

I will note that Comment #19 indicates it is broken in ESXi 5.5 build 32485=
47
which appears to be in the patch 07 branch prior to this fix being availabl=
e.

Now, let=E2=80=99s look at EOL dates:
vSphere 5.0 and 5.1 EOL - August 24, 2016
vSphere 5.5 EOL =E2=80=93 September 19, 2018
vSphere 6.0 EOL =E2=80=93 March 2020

There have been patch releases made available in 2016 to address both 5.5 a=
nd
6.0, plus having 5.5 already EOL and 6.0 in a few months. Given that it is =
my
recommendation we 1) remove the blacklist for these devices and 2) not
investigate or add version checking (which likely would be error prone and
would not take into account patch releases).

I just proposed a patch to remove the quirk which I can commit with approva=
ls:
https://reviews.freebsd.org/D22819

--=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-IZwBe5MUt7>