After reversing the commit e587cadd8f47e202a30712e2906a65a0606d5865 (partially) and rebuilding the kernel I now can boot intrepid inside VirtualBox 1.6.4 without having VT-x enabled or 'noreplace-paravirt' boot option set.
Attached is the patch I applied on the intrepid kernel sources. http://packages.ubuntu.com/intrepid/linux-image-2.6.27-1-generic As you can see I was not able to reverse the whole commit, because the code has changed at some points and I have no idea what I actually changed there ;-) http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=e587cadd8f47e202a30712e2906a65a0606d5865 It looks like these spin_unlock() and spin_lock() functions have been replaced by mutex_unlock() and mutex_lock(). So I did not change these lines. ** Attachment added: "Reversed e587cadd8f47e202a30712e2906a65a0606d5865" http://launchpadlibrarian.net/17149169/linux_2.6.27-1.2.diff.gz -- 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
