VBox crash on Yosemite

[VBman]

Hi there,

I tried to run my VBox, which was built based on version 4.1.24, with a 32bit Linux guest vm on a 64bit Yosemite(10.10.1).
After launched, it crashed.

Here is the related info:
1. The system message console reported:
...
2/19/15 10:47:18.000 PM kernel[0]: VirtualBox (map: 0xffffff8046b195a0) triggered DYLD shared region unnest for map: 0xffffff8046b195a0, region 0x7fff8f600000->0x7fff8f800000. While not abnormal for debuggers, this increases system memory footprint until the target exits.

2/19/15 10:47:21.362 PM VirtualBox[1216]: conn now
2/19/15 10:47:21.388 PM VirtualBox[1216]: Could not connect with KEXT

2/19/15 10:47:28.114 PM com.apple.xpc.launchd[1]: (com.apple.ReportCrash[1311]) Endpoint has been activated through legacy launch(3) APIs. Please switch to XPC or bootstrap_check_in(): com.apple.ReportCrash
2/19/15 10:47:31.329 PM ReportCrash[1311]: Saved crash report for VirtualBox[1216] version 4.1.24 (4.1.24) to /Users/jm/Library/Logs/DiagnosticReports/VirtualBox_2015-02-20-135836_Supports-Mac-mini.crash

2/19/15 10:47:46.164 PM Problem Reporter[1362]: Failed to connect (_imageWell) outlet from (ProblemReportWindowController) to (NSImageView): missing setter or instance variable
...

2. VBox generated:
...
Crashed Thread: 11 EMT

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00000000000fed18

...

Thread 11 Crashed:: EMT
0 VBoxREM.dylib 0x0000000101d30530 ldl_kernel + 32
1 VBoxREM.dylib 0x0000000101d3b543 helper_ljmp_protected + 131
2 ??? 0x000000010f5cded0 0 + 4552711888
...

3. See the attached log files:

VBox-crash-on-Yosemite.zip

log info for the crashed vm.

(27.21 KiB) Downloaded 10 times

In my vm configuration file, I turned off the hardware virtualization by disabling VT-x/ADM-v and nested paging features.

My questions are:
1. How I can check if my VBox driver is correctly loaded and running?

2. In terms of the above info, the crash seems relate to x86 emulation of vbox for running my 32bit guest vm. There are two files VMM/VMMRZ/VMMRZ.cpp and recompiler/target-i386/op_helper.c may be for this emulation issue.

Can someone give me some suggestions of how to debug this issue? or point to somewhere I can start my debugging?

Thanks a lot in advance.

[loukingjr]

You may want to update to VirtualBox 4.3.22. VB 4.1.24 is almost three years old now. There have been two major releases and many maintenance releases since. If for no other reason than the many, many improvements.