Page 1 of 1
Using VB64 on WindowsVista64 Will not run Ubuntu64
Posted: 24. Nov 2008, 04:06
by mrhobbeys
I have an AMD 64 Turion 2x
When I try to run Ubuntu 64 I get this error from Ubuntu;
"This kernel requires an x86-64 CPU, but only detected an i686 CPU. Unable to boot - Please use a kernel appropriate for your CPU."
VB 2.0.4 Win 64
Posted: 24. Nov 2008, 16:04
by Sasquatch
Did you check the manual (chapter 1.6) to see if you have the proper hardware and settings?
Posted: 14. Dec 2008, 17:11
by BajaPaul
Same error here. Ubuntu 8.04 wants a 64-bit CPU but only see a i686 CPU. It is Virtualbox not showing a 64-bit CPU.
It only happens intermitantly. Otherwise it runs like a champ. Might have something to do with host system coming out of sleep mode.
A complete power down of the host seemed to fix it last time. It just happened again. I will post back if I figure it out.
Posted: 15. Dec 2008, 21:46
by Sasquatch
BajaPaul wrote:Same error here. Ubuntu 8.04 wants a 64-bit CPU but only see a i686 CPU. It is Virtualbox not showing a 64-bit CPU.
It only happens intermitantly. Otherwise it runs like a champ. Might have something to do with host system coming out of sleep mode.
A complete power down of the host seemed to fix it last time. It just happened again. I will post back if I figure it out.
Check if there is a known bug for your motherboard. Maybe a BIOS update can fix this.
Using VB64 on WindowsVista64 Will not run Ubuntu64
Posted: 20. Dec 2008, 22:08
by dwhiting
Same problem for me. I'm running 64-bit Vista on a Lenovo T61 (Core 2 Duo T8300 CPU). I installed the latest BIOS and enabled VT-x in the BIOS. All the required settings in the VM are enabled, I think (VT-x, IO APIC, PAE/NX). I've rebooted several times, and re-installed VBox 2.10.
Any suggestions?
Posted: 21. Dec 2008, 02:57
by dwhiting
Strange -- it's working now. I uninstalled and deleted previous VDI files. Apparently my previous uninstalls weren't really working. I had a hard time getting Windows to really uninstall VB. After I got it out of my system, I then rebooted and reinstalled. This time everything worked fine. So maybe the problem was that I installed 2.10 on top of 2.06 or something. Anyway, I'm not quite sure why it started working, but I'm happy at this point.