Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 13 May 2020 09:07:07 +0200
From:      Michael Schuster <>
To:        Christoph Kukulies <>
Cc:        freeBSD Mailing List <>
Subject:   Re: kldload vboxvfs.ko panics
Message-ID:  <>
In-Reply-To: <>
References:  <>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
>From the way you write it, I conclude you didn't set up a dedicated boot
environment ... (hint: it's not hard - 'man bectl' [or 'beadm' - they're
almost the same]).

If I were you and the workaround suggested by Pete doesn't help, I'd try to
boot from a USB stick, mount the installation and fix it up that way ...
(no idea how, though, sorry ... )


On Tue, May 12, 2020 at 5:02 PM Christoph Kukulies <>

> I hosed my kernel boot start by putting vboxvfs_load=3D"YES=E2=80=9C into
> loader.conf. Better not had done it.
> I noticed that FreeBSD 12.1 panicked whil I manually loaded vboxvfs.ko
> while VirtualBox was running.
> Well, not a good idea and the panic comes from the fact that Vbox was
> already running. So I wanted to try
> to load all required vbox modules right away on boot.
> So I cut off myself. How can I repair this? Boot into the Forth loader?
> How from then on?
> Of course the question why the kernel crashes on the vbox modules gotta b=
> solved in the first place.
> =E2=80=94
> Christoph
> _______________________________________________
> mailing list
> To unsubscribe, send any mail to "

Michael Schuster
recursion, n: see 'recursion'

Want to link to this message? Use this URL: <>