Panic: CPU too old (after installing Gutsy i386 server)

[Barrius]

Installed Ubuntu Gutsy i386 server into VirtualBox 1.4.0 successfully (LVM + LAMP). Upon reboot receive "PANIC: CPU too old fro this kernel". Shouldn't the install program check the CPU BEFORE installing?

Upstream bug: http://www.virtualbox.org/ticket/212

[Chuck Short (zulcss)]

This might be a problem with virtual box itself sorry closing

[Ante Karamatić (ivoks)]

This is bug in virtualbox - it doesn't support PAE.

[Ante Karamatić (ivoks)]

Upstream bug:

http://www.virtualbox.org/ticket/212

[bgrupe (bgrupe)]

How about regular installs? I installed gutsy server beta (i386) on my old laptop giving me the message as well... I'd expect the i386-server-kernel to work on a centrino 1g CPU.

[Daniel Hahler (blueyed)]

Changing Ubuntu source package from virtualbox to virtualbox-ose ("virtualbox" was only present during Gutsy development).

[KWierso (kwierso)]

I just installed ubuntu-7.10-server (i386) on my laptop, and it gave me this error. It's a Mobile Pentium 4, so it isn't really old.

[w0arz (fabiengasser)]

Same problem on a core 2 duo with ubuntu-7.10-server i386. ( With the ose version ).

[Baptiste Mille-Mathias (bmillemathias)]

Problem confirmed here with a qemu image converted to vmdk

[Cameron Ford (fordcameron)]

This site offers a workaround by installing a different kernel.
http://tombuntu.com/index.php/2007/09/05/making-ubuntu-server-work-in-virtualbox/

In short:
After booting from cd, select rescue a broken system then execute a shell from the root partition and execute the following
apt-get update
apt-get install linux-386
apt-get remove linux-server

worked for me

[Patrick Salami (pat-entitycom)]

I experienced the same problem on an Intel Core 2 Duo with Win XP as the host system, 2GB RAM (512 for the virtual machine),
and Ubuntu Gutsy (7.10) Server as the guest OS.
After following the above workaround, I was able to boot, but I ended up with a dirty file system, requiring extensive repairs using fsck, which I had to run manually from a maintenance shell that the system dropped me into after rebooting.
After cleaning the file system, I had to reboot two more times in order to get it to mount read-write and to boot properly.

Hope this helped.

[dahas (bogdan-daja)]

Hi to all
This post help me to cure this problem and it works
I try with Gusty guest I hope some time will get fixed this

[Jonathan Hernandez (jbilbo)]

Upstream bug: http://www.virtualbox.org/ticket/212 -> "Supported in SVN and the upcoming 1.6."

So it's fixed in VirtualBox 1.6

[Greg A (etulfetulf)]

Fixed in version 1.6 - Intrepid now has 1.6.