Cannot install Ubuntu in VirtualBox due to “this kernel requires an x86-64 CPU, but only detects an i686 CPU, unable to boot” error


This kernel requires an x86-64 CPU, but only detected an i686 CPU.

Trying to install kali linux or ubuntu on Oracle VirtualBox or VMware ?

but when running the virtual machine you got this message " This kernel requires an x86-64 CPU, but only detected an i686 CPU. Unable to boot – please use a kernel appropriate for your CPU ".

as someone asked on my Youtube Video about

Installing Kali linux on VMware

1) There is many case you are receiving this message for but the most common one can be fixed from your bios settings on intel CPU you have to enable " Intel Virtualization Technology " and on AMD CPU you have to enable "AMD V" this will simply fix this error

how to enable Virtualization Technology

Power on your computer and open the BIOS by pressing the delete key or F1 key or F2 or Alt and F4 keys it depend on the system you have. Open the Processor submenu The processor settings menu may be in the Chipset, Advanced CPU...
0 0
0 0

VirtualBox is a software which allows the user to run variety of operating systems be it Windows, Mac or BSD or any other OS. Fortunately, VirtualBox is available for Ubuntu 16.04 and the installation is a fairly easy process. After you’ve installed the VirtualBox you will need the bootable ISO to configure the Virtual OS to run through Virtual Box.

In order to install VirtualBox follow the steps below.

Installing VirtualBox on Ubuntu 16.o4

Click the search your computer icon from the top left and type Terminal. Click Terminal to open it.

Download the deb file using the wget command from here. I recommend using the AMD64 bit version regardless of the CPU type you have because it contains the same set of instructions.

In terminal, type or copy/paste the following command


PRO TIP: If the issue is with your computer or a laptop/notebook...
0 0

If you’re getting an error that “Windows failed to start” while trying to install 64bit Windows 7 on a Virtualbox machine with an Ubuntu host, then you’ll appreciate the following fix.

Go ahead and open Virtualbox. Right-click the virtual machine that you intend use for the Windows 7 installation. Then click “settings”.

In the settings box that appears, click “System”.

Now, check the box that reads “Enable IO APIC” and then click “OK”. At this point, you should be able to boot up the virtual machine without seeing the error message.

However, you may get a new error… that windows cannot install to your disk. In that case, you’ll need to change the type of controller your virtual machine uses for the virtual disk.

So, select “Storage” from the options on the left and, if you see that your virtual disk is attached to an SATA controller, remove it.

Now select the IDE controller and attach the...

0 0

Hello everyone, the new version of Oracle Virtualbox 5.2 is now available for download. This new version comes with many improvements and features. In this new version, we can export VM to Oracle Cloud (OPC). Also it supports unattended guest installation. For more information about the changelog, please visit this official webpage. This tutorial is going to show you how to install Virtualbox 5.2 on Ubuntu 16.04 Xenial Xerus. Please don’t forget to check out our Linux Tutorial page for more great tutorials.

Steps to install Virtualbox 5.2 on Ubuntu 16.04

Step 1. Remove Previous Version of Virtualbox

In case you have previous Virtualbox 5.1 on your computer, you must remove it first prior to the installation. If not, you will get the following error when installing Virtualbox 5.2. But if this is your first Virtualbox installation, skip to step 2.

dhani@dhani-ThinkPad-T450:~/Downloads$ sudo gdebi virtualbox-5.2_5.2.0-118431_Ubuntu_xenial_amd64.deb

0 0

I am getting everytime this error, please please do help Failed to open a session for the virtual machine Windows10.

The virtual machine 'Windows10' has terminated unexpectedly during startup with exit code 1 (0x1). Result Code: NS_ERROR_FAILURE (0x80004005) Component: MachineWrap Interface: IMachine {f30138d4-e5ea-4b3a-8858-a059de4c93fd} Kernel driver not installed (rc=-1908) The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Please install virtualbox-dkms package and load the kernel module by executing 'modprobe vboxdrv' as root. If it is available in your distribution, you should install the DKMS package first. This package keeps track of Linux kernel changes and recompiles the vboxdrv kernel module if necessary. where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The support driver is not installed. On linux, open returned ENOENT.

The key part of the error message is this...

0 0

Yesterday, after trying out


in Ubuntu, which installs QEMU, I got this error when trying to open a virtual machine in VirtualBox:

VirtualBox can't operate in VMX root mode

Luckily, there is an easy fix for Linux users. All you have to do is run the following command with root privileges (the command has also been added to the Ubuntu TestDrive post, of course):

For Ubuntu, just use "sudo" in front of the command. Unfortunately I don't know a fix for Windows users other than just using a single virtualization application (so no more than one!).

Hopefully this will help some people. Using it, you can run both Ubuntu TestDrive (which uses QEMU) and VirtualBox without any...

0 0

I'm doing a tutorial through on setting up linux using virtualbox.

It was going fine until I had to create a file in my development folder. It's been set up as a shared folder so I can write html files straight on to the virtual server (I think).

I'm writing small scripts in to the shared folder and I'm getting a 404 error for each. For something like or (with just a 'hello world' in there).

Additional Info;

In VirtualBox if I go settings->shared folders->machine folders, my 'sandbox' folder is definitely the one being used.

When I go to - it works as expected. Information about the server.

I have installed Ubuntu 14.04 LTS. I've installed a lot of packages. Things started going wrong on the 'Configuring the Apache web server' section so maybe it's an apache problem.

I have looked on the server through the command...

0 0