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

Bug #126863 reported by Barrius
Affects Status Importance Assigned to Milestone
Fix Released
virtualbox-ose (Ubuntu)
Fix Released

Bug Description

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:

Tags: iso-testing
Revision history for this message
Chuck Short (zulcss) wrote :

This might be a problem with virtual box itself sorry closing

Changed in linux-source-2.6.22:
status: New → Invalid
Revision history for this message
Ante Karamatić (ivoks) wrote :

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

Changed in linux-source-2.6.22:
importance: Undecided → Medium
status: Invalid → Confirmed
Revision history for this message
Ante Karamatić (ivoks) wrote :
Revision history for this message
bgrupe (bgrupe) wrote :

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.

Revision history for this message
Daniel Hahler (blueyed) wrote :

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

Revision history for this message
KWierso (kwierso) wrote :

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.

Revision history for this message
w0arz (fabiengasser) wrote :

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

Revision history for this message
Baptiste Mille-Mathias (bmillemathias) wrote :

Problem confirmed here with a qemu image converted to vmdk

Revision history for this message
Cameron Ford (fordcameron) wrote :

This site offers a workaround by installing a different kernel.

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

Daniel Hahler (blueyed)
description: updated
Revision history for this message
Patrick Salami (pat-entitycom) wrote :

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.

Revision history for this message
dahas (bogdan-daja) wrote :

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

Revision history for this message
Jonathan Hernandez (jbilbo) wrote :

Upstream bug: -> "Supported in SVN and the upcoming 1.6."

So it's fixed in VirtualBox 1.6

Changed in virtualbox:
status: Unknown → Fix Released
Revision history for this message
Greg A (etulfetulf) wrote :

Fixed in version 1.6 - Intrepid now has 1.6.

Changed in virtualbox-ose:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.