LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   VirtualBox - kernel panic after kernel upgrade (http://www.linuxquestions.org/questions/slackware-14/virtualbox-kernel-panic-after-kernel-upgrade-4175471260/)

Poprocks 07-28-2013 08:08 PM

VirtualBox - kernel panic after kernel upgrade
 
1 Attachment(s)
Perhaps this is not Slackware-specific, but I have Slackware 14.0 installed on VirtualBox, and when I apply the kernel upgrade from 3.2.29 to 3.2.45, I get a kernel panic on booting the virtual machine. Happens on both generic and huge, both SMP and non-SMP. Running 32-bit Slackware.

The most bizarre thing of all, though, is that I get the same kernel panic even if I downgrade the kernel back to 3.2.29! Loading my machine state back to an older state gets the virtual machine working again, but then if I try the upgrade again, same problem.

I was originally using VBox 4.2.10 from SBo and then upgraded to 4.2.16 manually using Oracle's installer. Same problem on both.

See screenshot attached. Not the most context, I know, but that's the best I can do at this juncture.

Anyone have any ideas? Anyone experienced this problem and able to work through it?

willysr 07-28-2013 08:31 PM

have you re-run lilo after upgrading the kernel?

Poprocks 07-28-2013 08:33 PM

Quote:

Originally Posted by willysr (Post 4998606)
have you re-run lilo after upgrading the kernel?

Yes.

willysr 07-28-2013 11:17 PM

have you created initrd for generic kernel?

Poprocks 07-29-2013 10:25 AM

Quote:

Originally Posted by willysr (Post 4998648)
have you created initrd for generic kernel?

Yes. Actually, come to think of it, I recorded a video of what I was trying to do, so perhaps I'll post it as an unlisted video on Youtube and post the link here.

Poprocks 07-29-2013 10:49 AM

Here 'tis:

http://youtu.be/aZ0iRa396XE

I noticed one thing. When I downgraded again, I forgot to uncomment my initrd line in lilo.conf, so that might have been the issue with 3.2.29 "not working". Will retry.

guanx 07-29-2013 03:23 PM

Does this thread help?
http://www.linuxquestions.org/questi...ml#post4752754

ReaperX7 07-29-2013 11:36 PM

I've had some hiccups with the latest release of VirtualBox myself. The last update caused some problems especially with various Linux programs and kernels. My Slackware 14.0's temp install was all weird with the mouse jumping randomly around the screen making copy-paste nearly impossible for my building my Linux From Scratch virtual hard disk for my home machine, and typing out script files for LFS isn't a picnic.

My VMware Workstation install on my Windows 8 box however has no such issues, though VMware does not play nice with .VHD files, so now I'm kinda stuck.

Not sure why but both VirtualBox OSE and the official version have been getting rather slipshod with quality as of late.

phenixia2003 07-30-2013 02:33 AM

Hello,

Quote:

Originally Posted by ReaperX7 (Post 4999339)
I've had some hiccups with the latest release of VirtualBox myself. The last update caused some problems especially with various Linux programs and kernels. My Slackware 14.0's temp install was all weird with the mouse jumping randomly around the screen making copy-paste nearly impossible for my building my Linux From Scratch virtual hard disk for my home machine, and typing out script files for LFS isn't a picnic.

The option "Machine->Disable mouse integration" (or host+I) should solve this mouse issue.

--
SeB

Poprocks 07-31-2013 02:59 AM

Yes, downgrading to 3.2.29 and NOT forgetting to uncomment the initrd line resolves the issue. Hmm...

Poprocks 07-31-2013 09:42 PM

Quote:

Originally Posted by guanx (Post 4999119)

Yes. That made 3.2.45 work on my VirtualBox. Thanks! I saw that thread before but I must have skipped over the solution.

I'm running an Intel i5. If anyone else is having this issue, try enabling "Intel Virtualization Technology" in your BIOS settings.


All times are GMT -5. The time now is 03:26 PM.