Date: Mon, 23 Oct 2023 20:29:01 +0000 From: bugzilla-noreply@freebsd.org To: virtualization@FreeBSD.org Subject: [Bug 274389] bhyve in 15-CURRENT unable to boot OpenBSD anymore Message-ID: <bug-274389-27103-MOveIz9oJM@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-274389-27103@https.bugs.freebsd.org/bugzilla/> References: <bug-274389-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=3D274389 Mark Johnston <markj@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |corvink@FreeBSD.org --- Comment #7 from Mark Johnston <markj@FreeBSD.org> --- I still don't fully understand the problem yet. What's happening is: - virtio-blk0 has an I/O bar, initially at 0x2000. - something maps it at 0xc000 early during boot, I speculate it's edk2. Th= is happens before any I/O is done. - OpenBSD's boot loader loads the kernel, kernel boots. - OpenBSD enumerates devices, tries to enable virtio-blk0. It sees that the BAR has address 0xc000, and because this apparently conflicts with an exist= ing resource, it disables the BAR by setting its address to 0, but that conflic= ts with an I/O port owned by atkbd That triggers the assertion failure. I spent quite some time trying to understand what it's conflicting with, the boot logs don't make it clear. I did notice that edk2-bhyve was upgraded recently; I tried downgrading to edk2-bhyve-g202202_10 and the problem went away. Corvin, do you have any i= dea what's going on here? --=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-274389-27103-MOveIz9oJM>