If you’re working with an ISO file, then this usually means you’ve selected the wrong one for your machine’s architecture. Go back to the website and download the x386 version. The problem would be with Ubuntu, not the virtual environment.
Open up a terminal window from your installation or head over to one of the virtual consoles if your X Windows installation isn’t working. Unable to boot – please use a kernel appropriate for your CPU” it means you are trying to install a 64bit version of ubuntu on the virtual machine. Programs like Windows Virtual PC can not have 64bit Virtual Hosts.

Besides it supports 64 Guests. But later changed the licensing.

This works in most cases, where the issue is originated due to a system corruption. Upcoming Samsung Exynos Flagship SoC Name And Specifications Leak Ahead Of Premium Android Launch? Note: win7 64 bit works just fine, especially the p6100 is fast. Starting with Windows 8, Hyper-V superseded Windows Virtual PC as the hardware virtualization component of the client editions of Windows NT.A server computer running Hyper-V can be configured … Keep in mind that if you’re running a virtual machine and have this error, you might want to use the menus to change the type of processor being emulated. This kernel requires an x86-64 CPU, but only detected an i686 CPU. VM or not, I have 2 pcs’ unable to install Oneiric, or any debian version distro starting at 11.10. whether 32 bit or 64bit.

Setelah saya browsing-browsing di Google dan Youtube ternyata cara mengatasinya sangatlah mudah. Rather than switching to a different type of ISO, you can possibly switch your virtual machine system to a 64-bit processor.

Unable to boot – please use a kernel appropriate for your CPU” it means you are trying to install a 64bit version of ubuntu on the virtual machine.

Once you reboot, select the boot option that matches the device you wrote the new ISO to and you should be able to start the GNU/Linux installer.

In this case, the i686 refers to the traditional Intel architecture. Kevin is a dynamic and self-motivated information technology professional, with a Thorough knowledge of all facets pertaining to network infrastructure design, implementation and administration. Posted in Linux / Redhat, Virtualization Tagged centos, centos 7, i686 cpu, Linux, redhat, rhel 7, this kernel requires an x86-64 CPU, unsupported, virtual box, virtualbox, virtualization Post navigation https://www.experts-exchange.com/questions/24666358/Ubuntu-on-Microsoft-VirtualPC-error-This-kernel-requires-an-x86-64-CPU.html, http://www.cosky.com/installing_ubuntu_lamp_server_within_microsoft_virtual_pc. Fix: Unable to Boot ‘Please Use a Kernel Appropriate for your CPU’. There are several major architectures in current use, but more than likely you’ve tried to start your system with x86_64 code when it has a 32-bit Intel or AMD microprocessor inside.

haha, glad I’m not the only one that wasn’t paying attention and thought “wtf..” Thanks for posting this. Guess I’ll have to use CentOS 64 bits on my VMware servers. Ubuntu and Debian have supported PPC ISO files.

First ESX 3 vwas sold then they decided to make it freee.

Superior record of delivering simultaneous large-scale mission critical projects on time and under budget. Privacy Policy and You could theoretically even use a machine that was running a different non-Linux operating system as long as it could write out an ISO file.

From the bash prompt, type arch or uname -m to immediately find out what kind of processor architecture you’re working with. INtel processors p 631 or p6100, both w/ em64t and dual threads are called i 686 I guess.

Head back to the download page that you were on while you were looking for the the ISO that you downloaded in the first place on a machine that you’re able to boot from.

While the terms i686 and 32-bit aren’t actually interchangeable, because of Intel’s dominance in the personal computer market they essentially have been used this way when selecting ISO files.

Required fields are marked *.

If this is the case, then you merely need to download the appropriate kernel to fix the unable to boot error.

8+ characters (letters, numbers, and a symbol). This kernel requires an x86-64 CPU, but only detected an i686 CPU. This time they have just cliipped the current version so that the free version can not run SNMP!


This si what happens when you're with a closed source program : )) But VirtualPC is another problem in the neck ;-) I'll suggest you to try VirtualBox.