FreeBSD (FreeNAS) VMs encounter "Critical Error" when Attempting to Boot

[n.t.grimm]

I've been experimenting with a couple of FreeNAS VMs before installing and configuring a home NAS. After taking a break for a couple weeks, I went to boot and update my FreeNAS VM this morning and found that I was encountering a critical error that stopped the boot/install.

The same issue occurred when trying to install a new FreeNAS VM on both my existing host, and an alternate host.

I've attached the log files from my primary host (compressed to meet size restrictions). Any help the community can provide would be greatly appreciated.

My primary host (Mac Pro) has the following configuration: Mac OS Sierra (10.12.3), 2.8 GHz Quad-core Intel Xeon, 24 GB RAM.

My secondary host (Macbook Pro) has the following configuration: Mac OS Sierra (10.12.3), 2.2 GHz Intel Core i7, 16 GB RAM.

[socratis]

First order of business, moving from "OSX Hosts" to "Other guests". The problem does not appear to be with your host.

[frank]

It's the typical problem with older Mac OS X hosts, see also ticket 16569. Some instruction not implemented. This is a known regression of VBox 5.1.x where we switched to a new instruction interpreter on Mac OS X. The interpreter is used under certain conditions so it may happen that such a Guru is never triggered.

This Guru is not triggered on more recent Mac OS X hosts. A fix is in the queue but no ETA.

[socratis]

Man... It turns out it was a host problem after all. I wanted to take a look at the logs later on, but Frank got there first. Moving back to "OSX Hosts". Last move, I promise...

For those of you interested in the why and what, here are the crucial parts of the log:

00:00:01.666107 DMI Product Name: MacPro5,1
00:00:23.938755 !! VCPU0: Guru Meditation -5300 (VERR_IEM_INSTR_NOT_IMPLEMENTED)
00:00:23.939021 CPUM: 0020:ffffffff80dc0850 0f ae 3f        clflush byte [rdi]

The "MacPro5,1" is either a mid-2010 or a mid-2012 computer which uses the Nehalem or Westemere CPUs. The also funny part is that it's one of the few (if not the only) Apple models that has the same product code.

@n.t.grimm
Can you identify your MacPro model more accurately, better than the VBox.log? And the MacBookPro as well? They don't look that old to me, but that's just me...

[n.t.grimm]

The Mac Pro in question is a mid-2010 model. From Every Mac, here are some of the associated identifiers:

Family: Mid-2010 (Nehalem)
ID: MacPro5,1
Model: A1289 (EMC 2314-2*)

The MacBook Pro in question is a Late 2011 model. From Every Mac, here are some of the associated identifiers:

Family: Late 2011 15"
ID: MacBookPro8,2
Model: A1286 (EMC 2563*)

Both machines have seen significant hardware upgrades over the years (optical drives, hard drives, RAM).

[socratis]

MacBookPro8,2

OK, that's not good, not good at all!!! Not for you, for me. Yours is the 15" early 2011, mine is MacBookPro8,3 the 17" early 2011 model. I really have to try the FreeNAS thing. From the log I see "FreeNAS-9.10.2-U1.iso", can you please verify that this is the one you were using?

It's the processor that I'm worried about, not the upgrades.

[n.t.grimm]

That is correct. The issue occurred with both FreeNAS-9.10.2-U1.iso as well as the new FreeNAS-Corral-Release.iso.

It's worth noting that when I downgraded VirtualBox using the installer that I downloaded in earlier January (VirtualBox-5.0.30-112061-OSX.dmg), I was successfully able to create my new image and begin booting it.

[socratis]

when I downgraded VirtualBox using the installer that I downloaded in earlier January (VirtualBox-5.0.30-112061-OSX.dmg), I was successfully able to create my new image and begin booting it.

That would actually be in line with what Frank said previously about this being a regression. And thank you for trying that one, because I'm watching those VERR_IEM_INSTR_NOT_IMPLEMENTED guru meditations, not only as a user, but as a Mac owner, which are the ones mainly affected. You are the first one that reported success with downgrading to the 5.0.x series, so that's great news (almost) for a workaround until this is resolved.

This is a known regression of VBox 5.1.x where we switched to a new instruction interpreter on Mac OS X. The interpreter is used under certain conditions so it may happen that such a Guru is never triggered.

I'm going to try the FreeNAS, now. I'm going to be Cc: myself to every VERR_IEM_INSTR_NOT_IMPLEMENTED bug and watch its progress...

[socratis]

BTW, while trying to compile a list of VERR_IEM_INSTR_NOT_IMPLEMENTED bugs, I discovered a more appropriate bug compared to the #16569 that Frank mentioned, one that was closed as a duplicate of 16569: #15790. It even has the FreeNAS part in the description...

[socratis]

OK, as I was afraid I'm getting a Guru Meditation as well with "FreeNAS-Corral-RELEASE.iso".
Reverting back to 5.0.36 allows me to boot and install the FreeNAS VM.