kldload vboxvfs.ko panics

Michael Schuster michaelsprivate at gmail.com
Wed May 13 07:07:21 UTC 2020


>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 ... )

HTH
Michael

On Tue, May 12, 2020 at 5:02 PM Christoph Kukulies <kuku at kukulies.org>
wrote:

> 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.
>
>
>> Christoph
>
> _______________________________________________
> freebsd-questions at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "
> freebsd-questions-unsubscribe at freebsd.org"
>


-- 
Michael Schuster
http://recursiveramblings.wordpress.com/
recursion, n: see 'recursion'


More information about the freebsd-questions mailing list