Date: Fri, 22 May 2020 02:48:10 +0000 From: bugzilla-noreply@freebsd.org To: virtualization@FreeBSD.org Subject: [Bug 246647] Fix for #229852 still not MFCed in 12.1R-P5 Message-ID: <bug-246647-27103-tEb4wDZO3o@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-246647-27103@https.bugs.freebsd.org/bugzilla/> References: <bug-246647-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=3D246647 Anatoli <me@anatoli.ws> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Closed |Open Resolution|Not A Bug |--- --- Comment #3 from Anatoli <me@anatoli.ws> --- I'm reopening this bug report as suggested by Kubilay Kocak as I believe th= is bug (together with the #245392) is a show-stopper for production use of bhy= ve with pci passthru in some environments (this one on Intel CPUs, the other o= ne with OpenBSD/NetBSD guests). #245392 was blocking PCI passthru use with oth= er BSDs for years. In my particular case I'm deploying an infrastructure with 2 enterprise-gra= de servers as bhyve hosts serving dozens of OpenBSD guests and we can't use ST= ABLE 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 #2453= 92 gets closed. --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-246647-27103-tEb4wDZO3o>