[Bug 255078] Kernel panic on starting VirtualBox with virtualbox-ose-kmod builded without VIMAGE option

From: <bugzilla-noreply_at_freebsd.org>
Date: Mon, 18 Oct 2021 02:20:23 UTC

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


I had previously had the 5.x (-legacy) version installed and "upgraded" to

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 hard
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 configs
and aren't prompted to change them.

You are receiving this mail because:
You are the assignee for the bug.