VM doesn't start on Mountain Lion

[Scotter_10]

I had windows 7 running on my Mac just fine until yesterday when I updated. I can no longer start my virtual machine. I had the same sort of error the the last post had.

[rpmurray]

When you folks updated to 10.8.2 was the new EFI firmware update installed also?

[_Thomas_]

When you folks updated to 10.8.2 was the new EFI firmware update installed also?

No EFI update made.

[mandianme]

Same issue here. Update to 10.8.2 bricked VB 4.2

My MBPr system details:
Model Name: MacBook Pro Retina
Model Identifier: MacBookPro10,1
Processor Name: Intel Core i7
Processor Speed: 2.3 GHz
Number of Processors: 1
Total Number of Cores: 4
L2 Cache (per Core): 256 KB
L3 Cache: 6 MB
Memory: 8 GB
Boot ROM Version: MBP101.00EE.B02
SMC Version (system): 2.3f32
System Version: OS X 10.8.2 (12C54)
Kernel Version: Darwin 12.2.0
Boot Volume: Macintosh HD
Boot Mode: Normal
Secure Virtual Memory: Enabled

[houen]

Bump

[arajkov]

Any news or test builds fixing this problem?! I cant work with my developer machine until this is fixed ... or do I have to switch to parallels? Which is not my favorite option.....

[Dyre]

Same problem - MBPr, 10.8.2, VB 4.2 - nothing works anymore.

NS_ERROR_FAILURE (0x80004005)

Please please please fix this

[Roger Wang]

same problem on os x 10.8.2, vb 4.1.22 r80657

[Ammasuddet]

i also have the problem. i use a Macbook Pro Retina with OS 10.8.2

This is the Error message i get

Failed to open a session in the virtual machine NewTinyDebian.

VT-x is being used by another hypervisor.
(VERR_VMX_IN_VMX_ROOT_MODE).

VirtualBox can't operate in VMX root mode. Please close all other virtualization programs.
(VERR_VMX_IN_VMX_ROOT_MODE).

Details:
Resultscode: NS_ERROR_FAILURE (0x80004005)
Component: Console
Interface: IConsole {1968b7d3-e3bf-4ceb-99e0-cb7c913317bb}

[agnoeo]

I also have this issue with OS X 10.8.2 + EFI + VirtualBox 4.2 Update.

[inka]

same problem for me Retina + OS X 10.8.2 + VirtualBox 4.2. 10.8.1 worked without problems.

[mag]

Based on this https://discussions.apple.com/message/19657148#19657148 it seems to be as I expected and Apple is to blame for the root cause...

[michaln]

The issue has nothing to do with the EFI update, only with the OS X update. It turns out that the problem is also only indirectly related to VT-x.

The root cause is that the semantics of some IOKit memory management APIs subtly changed between 10.8.1 and 10.8.2, but only on systems with an IOMMU (aka VT-d).

[isaacsu]

Same problem as you guys. MBP Retina, upgraded EFI and OS X 10.8.2. Bricked VirtualBox 4.2 because of the VT-x issue.

I downgraded to OS X 10.8, and VirtualBox is working again.

To downgrade to 10.8,

1. Grab a copy of the OS X 10.8 InstallESD.dmg,
2. Use Disk Utility to restore to a USB drive (minimum 8gb).
3. Boot from USB (Hold down Option key when booting).
4. Make sure you're disconnected from the Internet (prevents the installer from auto updating).
5. Select "Reinstall Mac OS X"

This overwrites the OS with 10.8, and keeps all user data/applications intact.

Hope this helps someone.

[michaln]

Any news or test builds fixing this problem?! I cant work with my developer machine until this is fixed ... or do I have to switch to parallels? Which is not my favorite option.....

FYI, we're still waiting for the first official support request... So far it appears that all those poor folks who had to shell out their last buck for a shiny new Apple laptop were so cash-strapped that they couldn't afford the $50 for a VirtualBox license (or didn't think it was worth as much). Which naturally doesn't stop them from wanting this fixed yesterday. That is obviously not a very encouraging attitude from our perspective.

That said, please check https://www.virtualbox.org/ticket/10965#comment:21 for test builds of VirtualBox 4.1 and 4.2 which should fix this problem. Please note that only folks who have a problem with OS X 10.8.2 should install those. And please provide feedback (positive or negative) either on the ticket or here.