Vbox causing host crash/reboot on 12-current

[Vladimir Kondratyev]

Hi

I am sure that crashes was caused by SMAP as I am faced with them too.
I have made following patch to fix panic (attached)
Apply it to portstree and rebuild emulators/virtualbox-ose-kmod

P.S. It is POC so no arch/SMAP autodetection

On 8/7/18 6:14 PM, AN wrote:
> 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 at 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
> _______________________________________________
> freebsd-current at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe at freebsd.org"


-------------- next part --------------
A non-text attachment was scrubbed...
Name: vbox-smap.patch
Type: text/x-patch
Size: 1825 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-current/attachments/20180808/f7a22693/attachment.bin>