On 2019-09-06 10:38 a.m., Michal Nowak wrote:
On 09/04/19 08:06 PM, Geoff Nordli wrote:
On 2019-09-04 10:40 a.m., Alan Coopersmith wrote:
On 9/4/19 10:20 AM, Geoff Nordli wrote:
Hi.
I posted this a couple of days on the omnios list, but haven't
gotten much feedback. I am hoping someone here might have some
clues as OI and Omnios share the same vbox code. Posted below is
some crash dump information.
I have several machines running vbox without issue. The only thing
I can think of here is that this machine has a "newer" Intel Xeon
Silver 4110 Processor.
Any other thoughts?
That looks like the crashes we see on Solaris when SMAP is enabled
on a CPU
new enough to support it. The VirtualBox drivers try to access
memory that
SMAP blocks access to from kernel space.
https://wiki.openindiana.org/oi/7.2+VirtualBox suggests "Workaround
is to put:
set disable_smap=1 in /etc/system and reboot, before starting
VirtualBox"
Hi Alan.
I tried the smap disable, doesn't seem to make a difference.
As well, I was told from the omnios list you don't need to disable
smap when using the vbox builds from omnios/OI. They now work
without having to disable it.
thanks,
Geoff
If the system was ever "tainted" by the upstream binary VirtualBox
packages, it might be actually easier to reinstall the system anew and
see if the problem persists - as others were suggesting, it should not.
Michal
Hi.
I have a core dump if someone is able to look at it and give me some clues.
https://www.dropbox.com/s/cq99x55uj7gspka/vmdump.0.OI.20190925?dl=1
All am doing is default install (text installer), fully update, install
virtualbox.
Create basic vm: /usr/bin/VBoxManage createvm --name test --ostype
Ubuntu_64 --register
Run it: VBoxHeadless -s test
then it core dumps.
thanks,
Geoff
_______________________________________________
openindiana-discuss mailing list
[email protected]
https://openindiana.org/mailman/listinfo/openindiana-discuss
