I think I may know the cause to this (though I can't say this with any certainty).
I think this may be due to a feature I've termed "SMP on a single chip" (i.e. multicore and hyperthreading). I say this, because I've noticed most times, when I get the kernel bug, I notice the line prior mentions SMP, as well as I use a P4 with HT, and have noticed most everyone else is using Dual Core. I'm assuming that when the kernel probes for CPU features, VirtualBox simply passes it through to the real hardware, but VirtualBox will not "emulate" SMP, thus causing the error. This would also explain why many people seem to find enabling VT fixes it, as the "emulated" CPU is more compatible. The "final straw" that has me believing this, however, (note, I'm using Debian and not Ubuntu here), when I installed 2.6.18 for 686, it ran fine, however upon upgrading to 2.6.26, I have the panic (I'm assuming the SMP feature would have been added between), as well when I decided to.... "sidegrade" to 2.6.26 for 486, it booted just fine (I'm assuming, since no 80486 processor had HT or multiple cores or any feature similar to that, it doesn't even attempt such features). -- Kernel panic during boot in VirtualBox with kernel 2.6.26.*-generic https://bugs.launchpad.net/bugs/246067 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
