Host OS kernel panic when running Redox 0.0.3 in VirtualBox

[msikma]

Reproduction:

• Start VirtualBox 5.0.26 for Mac OS X 10.12.1.
• Create a new virtual machine set to Unknown Linux 64-bit, with 1024 MB RAM; ​everything else default.
• Start the virtual machine with the ​Redox 0.0.3 iso as boot media.

Expected behavior:

Expect the ISO to boot into the Redox system.

Actual behavior:

​Host OS kernel panic, causing an immediate reboot.

Other information:

​Redox is a new OS in early stages of development. 0.0.3 is the first precompiled ISO release. Many others have managed to run it in VirtualBox just fine, so there might be something weird going on with my setup.

Unfortunately I can't seem to find a log file anywhere. Can't find it either in $HOME/Library/VirtualBox or in the VM directory itself.

I've linked my VM configuration and crash report above.

[Socratis]

I sorted your non-Apple, non-VirtualBox kexts:

com.bluestacks.kext.Hypervisor	4.3.26
com.parallels.kext.hypervisor	11.2.1 32626
com.parallels.kext.netbridge	11.2.1 32626
com.parallels.kext.usbconnect	11.2.1 32626
com.parallels.kext.vnic	11.2.1 32626
com.vmware.kext.vmci	90.8.1
com.vmware.kext.vmioplug.15.2.0	15.2.0
com.vmware.kext.vmnet	0463.52.24
com.vmware.kext.vmx86	0463.52.24
net.telestream.driver.TelestreamAudio	1.1.1
org.pqrs.driver.Karabiner 10.22.0

So, you have Bluestacks, Parallels, VMWare, Telestream and Karabiner, besides VirtualBox. I assumed you looked at VirtualBox because it was the process identified as the culprit.

But with VirtualBox, Karabiner has been known for sure to cause crashes (they state that it doesn't work with 10.12, they have a beta), same with Bluestacks. I'll give you the opportunity to search for the details. So, I would say that I'm a little hesitant to say that it is the Redox that's causing the crash.

I have it running just fine on OSX 10.9.5 with VirtualBox 5.1.10 here (wow, 11.4MB for a livecd?).

PS. It's better if you attach logs and other files locally.

[msikma]

I'd like to report that the latest release (0.0.8) fixed whatever bug it was. Can't tell you exactly what the problem was, but it now boots fine. ​See the (now closed) ticket here.