Failing 64bit guest VM on Lion (MacBook Air)

[tomozo]

Hi there

64bit guest vm if everything was working fine until now, suddenly no longer work.

It was run
· Mac OS X Update, (firmware update, perhaps at the same time)
· VirtualBox Update 4.1.12> 4.1.14

so now
· MacBook Air 11-inch, Mid 2011
· Mac OS X Lion 10.7.4（11E53）
· Boot Rom MBA41.0077.B0F
· SMC 1.74f1
· VirtualBox Update 4.1.14

Message that appears when you start the Virtual Machine,

VT-x/AMD-V hardware acceleration has been enabled, but is not operational. Your 64-bit guest will fail to detect a 64-bit CPU and will not be able to boot.

Please ensure that you have enabled VT-x/AMD-V properly in the BIOS of your host computer.

MacBook Air doesn't have BIOS Setting.

Any idea what's wrong?

Thanks a lot

[mpack]

As far as I can tell, the log you posted shows a fully functional VT-x, and so can't be the log which goes with the error message you described - which incidentally is usually caused by having some other VM software installed and running.

[tomozo]

Thanks !!

it conflicts with "Intel Hardware Accelerated Execution Manager".
# Android-x86 Emulator

ref)
http://software.intel.com/en-us/forums/ ... p?t=103907

[jez]

Hi folks

Glad i found this post as having the same issue, i.e virtual box failing to launch any 64 bit guest on an osx lion host with the hardware acceleration error message. I can confirm, in my case at least, that the problem was the Intel Hardware Accelerated Execution Manager that i had recently installed using the Android SDK Manager.

However, i found that uninstalling the above software was not as simple as deselecting and removing the package via Android SDK Manager as it still seemed to be causing the same issue even though apparently not installed. In the end i followed the uninstall instructions (google 'uninstall intel execution manager' - i cannot at present post a link it seems)....which basically tell you to run:

Code: Select all

sudo /System/Library/Extensions/intelhaxm.kext/Contents/Resources/uninstall.sh

After that and a reboot VirtualBox is back in business