kldload vboxvfs.ko panics
kuku at kukulies.org
Wed May 13 07:27:27 UTC 2020
> Am 13.05.2020 um 09:07 schrieb Michael Schuster <michaelsprivate at gmail.com>:
> 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 ... )
Thanks. I solved it that way. Booted the FreeBSD 12.1 installation DVD, escaped into shell and edited /boot/loader.conf
> On Tue, May 12, 2020 at 5:02 PM Christoph Kukulies <kuku at kukulies.org>
>> I hosed my kernel boot start by putting vboxvfs_load="YES“ 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 be
>> solved in the first place.
More information about the freebsd-questions