Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 12 May 2020 09:59:10 -0700
From:      Pete Wright <pete@nomadlogic.org>
To:        Christoph Kukulies <kuku@kukulies.org>, freebsd-questions@freebsd.org
Subject:   Re: kldload vboxvfs.ko panics
Message-ID:  <5e116285-cfb1-c521-3b87-5b3574b61fc9@nomadlogic.org>
In-Reply-To: <FB40F98C-F937-485E-8B83-D2BE7B2765CA@kukulies.org>
References:  <FB40F98C-F937-485E-8B83-D2BE7B2765CA@kukulies.org>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help


On 5/12/20 8:02 AM, Christoph Kukulies 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.
>

I believe if you enter the loader prompt you can unset this via:

unset vboxbvfs_load
show vboxvfs_load

the second command should verify that you are not loading the module.  
more info is available in the loader(8) manpage.

-pete

-- 
Pete Wright
pete@nomadlogic.org
@nomadlogicLA




Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?5e116285-cfb1-c521-3b87-5b3574b61fc9>