[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: port-i386/53064: i386 kernel fault under VirtualBox
The following reply was made to PR port-i386/53064; it has been noted by GNATS.
From: Valery Ushakov <uwe%stderr.spb.ru@localhost>
Subject: Re: port-i386/53064: i386 kernel fault under VirtualBox
Date: Sat, 3 Mar 2018 14:23:53 +0300
On Fri, Mar 02, 2018 at 17:34:26 +0000, bch wrote:
> On Fri, Mar 2, 2018 at 7:10 AM Valery Ushakov <uwe%stderr.spb.ru@localhost> wrote:
> > I think you mean VT-x (make sure it's enabled in the BIOS).
> I can check
You can see it in the VM's log. E.g.:
00:00:05.135897 VM: fHMEnabled=true (configured) fRecompileUser=false fRecompileSupervisor=false
00:00:05.135900 VM: fRawRing1Enabled=false CSAM=true PATM=true
00:00:05.156239 HM: HMR3Init: VT-x w/ nested paging and unrestricted guest execution hw support
> though I'm not sure I'll have access to adjust this machine.
> As a datapoint, FreeBSD 11.1 runs fine, fwiw.
VirtualBox recompiler cannot cope with some of the code in NetBSD
locore (iirc, it's confused because netbsd only does indirect jumps to
the cli instruction in spllower).
If you are stuck without VT-x, you can tell vbox to not use "raw
mode" for the kernel with --recompile-supervisor command line
option (it's not exposed in the GUI). That will be slow, but will
If you can compile custom kernels you can probably also use my very
old patches from
Ignore TSS part (it was a proof of concept hack), you only need spl.S
Main Index |
Thread Index |