Slackware32 won't install in VirtualBox - Kernel Panic
 

I've downloaded Slackware 14 (three times because of bad MD5SUM's). I can't
get the download to start by using a torrent, because of a tracker error.
I've attached a png showing the error. I'm using Debian 6.0 and Transmission
Bit Torrent Client Version 2.03. I've never had any problems with the Bit
Torrent Client before.

After getting a good download, where the md5sum's match, I still can't get
Slackware to install in VirtualBox 4.0.16.r75491, because of a Kernel Panic
error. I've attached a png of that error. I've tried hugesmp.s & huge.s,
with pae checked/not checked as required with h*smp.s

Does anyone have any ideas/suggestion on why I'm getting the above errors or how
to get Slackware installed in VirtualBox?

Thanks.


Larry

Have seen a similar problem recently and it was resolved by going into the bios of the machine and enabling the "Virtualization Technology" setting, which is probably disabled by default.

I had the same problem yesterday. When using the default kernel from the DVD ISO image, I had to enable PAE. I don't remember now, but I think everythnig else was default settings.

dr.s & Woodsman,
I've got the PAE checkbox ticked, and my BIOS has VT on MCH also ENABLED. I have Centos 6.3 & Vector Linux 7 installed
in Virtualbox along with XP. They worked without the PAE checkbox ticked. I'm at a loss of why I get the Kernel Panic.

Any other ideas or suggestions?

Thanks.


Larry

try updating Virtual box to 4.1.20?

Got 2 Slackware VM's running on a desktop and a laptop here (Intel hosts) so I enabled PAE as well as VT-x and Nested Paging and the related BIOS setting. I think that's about it as far as VM system settings go. I'm running the 4.2 edition of VirtualBox (switched recently from 4.1.x).
Could this be kernel specific since you mentioned other Linux distro VM's having no issues? You might want to try booting an older Slackware ISO or CD (13.x may be) to see if that makes a difference. If that were the case then perhaps passing an extra kernel parm at the boot prompt might help (sorry just guessing I'm no kernel expert).