Date: Tue, 7 Aug 2018 11:14:45 -0400 From: AN <a.n.us@ieee.org> To: freebsd-current@freebsd.org Cc: vbox@freebsd.org Subject: Re: Vbox causing host crash/reboot on 12-current Message-ID: <CA%2B2zecw1Lv6A5FhDTU-qupHVVpTFvgNySD5HWO4oeCc=HzXKfg@mail.gmail.com> In-Reply-To: <CA%2B2zecyfmBrriuYOGLmbHVMV2b3R-rZKW9vetuJwXgKpUUqzmQ@mail.gmail.com> References: <CA%2B2zecyfmBrriuYOGLmbHVMV2b3R-rZKW9vetuJwXgKpUUqzmQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Update: I found the revision: https://svnweb.freebsd.org/base?view=revision&revision=336876 Use SMAP on amd64. Could this possibly cause VBox to crash and reboot the system? Is there a sysctl to disable? Thanks On Tue, Aug 7, 2018 at 10:46 AM, AN <a.n.us@ieee.org> wrote: > I recently started having severe instability on a workstation with > VirtualBox. I'm not sure if it was caused by the recent large ports > update, or a recent commit that affected SMAP. I can't seem to find > that revision, would someone please post it and also the workaround to > disable it, I would like to try it after work and see if disabling it > allows VBox to work. Is anyone else seeing this effect with Vbox? > > What I'm seeing is that as soon as a VM is started it reboots the > host, totally reproducible every time. I tried to rebuild VBox and > kmod, and also some qt5 ports but still not working. Any help is > appreciated, thanks for reading. > > Regards
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2B2zecw1Lv6A5FhDTU-qupHVVpTFvgNySD5HWO4oeCc=HzXKfg>