Date: Mon, 18 Oct 2021 02:20:23 +0000 From: bugzilla-noreply@freebsd.org To: virtualization@FreeBSD.org Subject: [Bug 255078] Kernel panic on starting VirtualBox with virtualbox-ose-kmod builded without VIMAGE option Message-ID: <bug-255078-27103-gCOooXsRQ9@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-255078-27103@https.bugs.freebsd.org/bugzilla/> References: <bug-255078-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=3D255078 russo@bogodyn.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |russo@bogodyn.org --- Comment #4 from russo@bogodyn.org --- For what it's worth, I just got bitten by this same issue. FreeBSD bogodyn.org 12.2-STABLE FreeBSD 12.2-STABLE stable/12-n233832-ebb3327d09c GENERIC amd64 virtualbox-ose-kmod-6.1.26 I had previously had the 5.x (-legacy) version installed and "upgraded" to 6.1.26. I had apparently tried to install this before when VIMAGE was default "off"= and the ports system had that config stored. As a result, my system crashed ha= rd the second I started virtualbox (I had not even started a VM --- it crashed= on launching the gui). Rebuilding the kmod with VIMAGE on fixed the problem. It runs fine so long= as VIMAGE is on. If VIMAGE must be on, it should no longer be an option in the port. At the very least there should alarm bells going off if the user tries to build without VIMAGE on. VIMAGE does default on now, but this doesn't help you if you have old confi= gs and aren't prompted to change them. --=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-255078-27103-gCOooXsRQ9>