Tag Archives: virtualbox

VirtualBox CompareExchange128 Error


Today, I attempted to upgrade my Windows 8 machine to the yet-to-be-released Windows 8.1, and I got the following error:

You can't install Windows 8.1 because your processor doesn't support CompareExchange128.

error

I am running 64-bit Mac as my primary operating system, and have set up 64-bit Windows 8 on a VM using VirtualBox.

Cause

One of the additional system requirements for 64-bit Windows 8.1 installation is that the CPU must also support CMPXCHG16b, PrefetchW and LAHF/SAHF. And this setting is disabled in VirtualBox by default.

Please check out this link for the other system requirements for Windows 8.1.

Solution

Open up the command prompt of your choice – Terminal / iTerm, and execute the following command:

VBoxManage setextradata [VM_Name] VBoxInternal/CPUM/CMPXCHG16B 1

And, that’s it! You’re ready to install Windows 8.1!

Network connectivity on a new CentOS installation


I had recently set up a new CentOS VM (v6.2) on my VirtualBox, but had a tough time configuring it to use the internet connectivity from my host machine. Here is a snapshot of the VirtualBox network settings for the VM:

Screen Shot 2013-06-09 at 4.16.50 PM

After quite a bit of troubleshooting, finally it turned out to be a simple config change. By default, CentOS does not configure the network interfaces on a new installation. I just had to execute the following command to configure the ethernet network interface. It acquired a new IP address and the network connectivity issue got resolved.

$ dhclient -v eth0

VirtualBox error: Kernel driver not installed (rc=-1908)


I use VirtualBox to  run a Windows 8 VM on my Mac. Something strange happened today. My Mac ran out of battery while I was working on something important on the Windows VM. I recharged my Mac and tried to restart the VM, but the VM was not booting up at all. I kept getting the following error:

VirtualBox error: Kernel driver not installed (rc=-1908)

Since the machine had not shut down gracefully, the VM seemed to have got corrupted.

After spending quite a bit of time trying to troubleshoot this problem, I was finally able to resolve it. Reinstalling VirtualBox helped resolve the issue. Obviously, I did lose all the unsaved changes, but the good part was that the VM was still intact, and it booted up just fine!

Just penning it down so that it helps someone else facing the same issue…