Date: Wed, 30 Sep 2020 15:35:22 -0500 From: Jeremy <jeremy.m.cox@gmail.com> To: freebsd-stable@freebsd.org Subject: Re: Re:virtualbox crash Message-ID: <CAPH9q1pEQ06aYdS9T68-pSuwyo-Ne6hwiFDECwA_Wcjm-C8ixw@mail.gmail.com> In-Reply-To: <CAPH9q1pU-_EAyAgbpTPY6ceydV8oQg%2Bg-mMgt_xNJ9pMtaqnXA@mail.gmail.com> References: <CAPH9q1pU-_EAyAgbpTPY6ceydV8oQg%2Bg-mMgt_xNJ9pMtaqnXA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
So I rebuilt both virtualbox-ose and virtualbox-ose-kmod and the driver successfully loaded in my system updated to beta 3, but I haven't tested virtualbox yet to see if it actually works, although I have no reason to believe it won't. I suppose the issue really is if you forget to disable loading vboxdrv.ko like I did, it can result in a hard lockup. I know I had to lookup how to mount ZFS from a live cd to fix loader.conf, it's been a few years since the last time I've had to do it. On Tue, Sep 29, 2020, 16:14 Jeremy <jeremy.m.cox@gmail.com> wrote: > I am also experiencing this problem after updating to beta 3. It is a hard > lockup and no keys will respond. It requires the computer to be turned off > via the power button. But it definitely looks like an issue with the > virtualbox driver. Normally I disable the drivers from loading before I do > an update but this time I forgot to. >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPH9q1pEQ06aYdS9T68-pSuwyo-Ne6hwiFDECwA_Wcjm-C8ixw>