A fix for the bug #229852 (bhyve: IOMMU (Intel VTd) PCI passthrough attempt locks up some systems) was stated as MFCed 6 months ago (https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229852#c21 and https://svnweb.freebsd.org/base?view=revision&revision=355440) but it's still not included in 12.1R-P5.
This is a severe bug crashing the entire system (12.1R) when starting bhyve with pci passthru.
*** This bug has been marked as a duplicate of bug 229852 ***
Thank you for the report Anatoli
The commit in base r349184 was indeed merged (MFC'd) to stable/12 in base r355440 (see bug 229852)
Merges to *stable* branches are scheduled for inclusion in *future* minor releases.
Only Errata Notices (EN's) and Security Fixes (SA's) are pushed to
releng" branches, that is to say, included in "current" minor releases (*.*-pX releases)
If you would like to request that the resolution for bug 229852 be considered an EN (Errata Notice), please re-open that issue.
Having said that, given the date of the original fix/merge (over 6 months ago), and the schedule for future 12.x releases, an EN request is unlikely to be accepted (in my opinion, I may be wrong).
I'm reopening this bug report as suggested by Kubilay Kocak as I believe this bug (together with the #245392) is a show-stopper for production use of bhyve with pci passthru in some environments (this one on Intel CPUs, the other one with OpenBSD/NetBSD guests). #245392 was blocking PCI passthru use with other BSDs for years.
In my particular case I'm deploying an infrastructure with 2 enterprise-grade servers as bhyve hosts serving dozens of OpenBSD guests and we can't use STABLE nor can we wait for 6 months more for these fixes to be included in 12.2R (we already got a considerable delay because of these bugs).
Though maybe it makes sense to combine both bugs in a single EN, when #245392 gets closed.
I would like to second the request for this to be considered for an EN to 12.1-RELEASE. I spent almost half a day recently trying to figure out why passing through a NIC on one particular Xeon 12.1 host was crashing the host before I found this bug. I’d be surprised if the new Xeon systems I’ve recently ordered don’t also have the same issue. As this if for a production environment, I’d prefer not to have to run off of 12-STABLE.