Date: Wed, 13 May 2020 08:57:03 +0200 From: Christoph Kukulies <kuku@kukulies.org> To: Pete Wright <pete@nomadlogic.org> Cc: freebsd-questions@freebsd.org Subject: Re: kldload vboxvfs.ko panics Message-ID: <3491A0C3-35C1-4CA7-B35F-5166CB6CCB14@kukulies.org> In-Reply-To: <5e116285-cfb1-c521-3b87-5b3574b61fc9@nomadlogic.org> References: <FB40F98C-F937-485E-8B83-D2BE7B2765CA@kukulies.org> <5e116285-cfb1-c521-3b87-5b3574b61fc9@nomadlogic.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> Am 12.05.2020 um 18:59 schrieb Pete Wright <pete@nomadlogic.org>: >=20 >=20 >=20 > On 5/12/20 8:02 AM, Christoph Kukulies wrote: >> I hosed my kernel boot start by putting vboxvfs_load=3D"YES=E2=80=9C = into loader.conf. Better not had done it. >>=20 >> 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. >>=20 >> So I cut off myself. How can I repair this? Boot into the Forth = loader? How from then on? >>=20 >> Of course the question why the kernel crashes on the vbox modules = gotta be solved in the first place. >>=20 >=20 > I believe if you enter the loader prompt you can unset this via: >=20 > unset vboxbvfs_load > show vboxvfs_load OK unset vboxvfs_load no such file or directory
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3491A0C3-35C1-4CA7-B35F-5166CB6CCB14>