4.3.6 VINF_EM_TRIPLE_FAULT on OSX Guru Meditation

[salep]

Hi,

I checked similar tickets (VINF_EM_TRIPLE_FAULT on OSX Guru Meditation), and they all say it works on 4.3.6 release.

In some tickets, it is reported that Nested Paging is the cause.

Hence I tried both nested paging on, and off (including disabling PAE/NX), but with no success.

[salep]

Virtual Box log with nested paging enabled

[salep]

Virtual Box log where nested paging and PAE/NX is disabled

[Frank Mehnert]

There are several reasons for this error code. The main problem was with AMD CPUs and this problem was definitely fixed in VBox 4.3.6. We also see reports for certain Intel hosts but this is a different problem. We are currently trying to find a reproduction scenario on Intel hosts.

[salep]

Replying to frank:

There are several reasons for this error code. The main problem was with AMD CPUs and this problem was definitely fixed in VBox 4.3.6. We also see reports for certain Intel hosts but this is a different problem. We are currently trying to find a reproduction scenario on Intel hosts.

Thanks for the fast reply. If there is anything you want me to test, please let me know.

[salep]

My cpu stats:

root@asus4:/home/bor# lscpu

Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 8 On-line CPU(s) list: 0-7 Thread(s) per core: 2 Core(s) per socket: 4 Socket(s): 1 NUMA node(s): 1 Vendor ID: GenuineIntel CPU family: 6 Model: 42 Stepping: 7 CPU MHz: 1600.000 BogoMIPS: 6784.54 Virtualization: VT-x L1d cache: 32K L1i cache: 32K L2 cache: 256K L3 cache: 8192K NUMA node0 CPU(s): 0-7

[bird]

First, I'm obliged to point out that OS X is only supported on Apple hardware...

Second, You've hacked your configuration quite a bit beyond the defaults. For instance I can see you're not using EFI as is default for OS X guest, but the PC compatible BIOS as firmware. That ain't gonna work.

Closing the report as invalid.

[salep]

Hi,

Thanks for the tips. Just know that this configuration works on 10.8 on the same machine.

Hence if you face a similar issue in the future, know that something might have changed from 10.8 to 10.9 that gives "VINF_EM_TRIPLE_FAULT" on the same machine with the same configurations.