Date: Wed, 13 May 2020 09:27:23 +0200 From: Christoph Kukulies <kuku@kukulies.org> To: Michael Schuster <michaelsprivate@gmail.com> Cc: freeBSD Mailing List <freebsd-questions@freebsd.org> Subject: Re: kldload vboxvfs.ko panics Message-ID: <B14299BE-ED16-46A9-ADD7-68B21026A08D@kukulies.org> In-Reply-To: <CADqw_gJA_tkPKvxaPO-kH0th5Fz8yShS-rsSNOen_OZSG5r8JQ@mail.gmail.com> References: <FB40F98C-F937-485E-8B83-D2BE7B2765CA@kukulies.org> <CADqw_gJA_tkPKvxaPO-kH0th5Fz8yShS-rsSNOen_OZSG5r8JQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> Am 13.05.2020 um 09:07 schrieb Michael Schuster <michaelsprivate@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 — Christoph > HTH > Michael > > On Tue, May 12, 2020 at 5:02 PM Christoph Kukulies <kuku@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 >>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?B14299BE-ED16-46A9-ADD7-68B21026A08D>