Hi there,

I am attempting to install Slackware on an Oracle VM VirtualBox. The install keeps being interrupted by a kernel panic. Here's a screenshot:

http://i.imgur.com/HDgzWac.png

I'm using the huge.s kernel instead of hugesmp.s, because apparently PAE is not supported. The boot device is the all in one DVD ISO mounted on a virtual drive using Daemon Tools Lite.

I gave the thing 512 MB of RAM, 1 processor, and an 8 GB virtual hard drive.

After looking for solutions for about half an hour, I found a post about this error occuring with Fedora, telling me to activate the COM1 Serial Port in the VM's settings. That did absolutely nothing at all.

Now I've given up. Apparently nobody else has encountered this problem before. Any ideas?

Add a "intel_pstate=disable" boot parameter. I believe that will resolve this.

1 members found this post helpful.

Just to confirm, that's "huge.s intel_pstate=disable" at the boot prompt? I'm afraid that doesn't do anything at all, error persists.

Perhaps this is a different issue than the one I encountered.

Probably. Any other suggestions?

Can I just bump this? I'm still at a loss here...

Please post some additional information. I have installed Slackware many times on VirtualBox and gotten it to work without much trouble.

• What is the version of VirtualBox?
• What is the version of Slackware (and is it 16-bit or 32-bit)?
• What is the Host Operating System (and is it 16-bit or 32-bit)?
• Do you have VT-x or AMD-v enabled for the virtual machine?
• Do you have PAE enabled for the virtual machine?
• Do you have nested paging enabled for the virtual machine?
• Do you have I/O APIC enabled for the virtual machine?
• How much memory have you allocated to the virtual machine?
• How much display memory have you allocated to the virtual machine?
• Did you check the MD5 checksum for the install DVD to make sure that it is not corrupted?
• Are you using an ISO Image or a physical DVD drive?
• Do you have any other guest operating systems working with VirtualBox?

You may find other helpful information in the VirtualBox forums.

This is just to report that I had a similar problem as described by the OP and passing the "intel_pstate=disable" boot parameter to the kernel solved it for me. I am using a Slackware64-multilib-14.1 host and a Slackware32-14.1 guest. I am running virtualbox-4.3.4 built from slackbuilds.org.

Chris

Hi,
When installing Android 4.3 on VirtualBox, this error has occurred. "kernel panic - not syncing attempted to kill the idle task".

Solution:
System Restart
Enter BIOS Configuration (Press Dell Key to Setup)
set "Intel Virtualization : Enable"
Save and exit from BIOS configuration.

Taht is all.
Good Works

Writen By: Ertaç OZENC

and how do you do THAT?? #totalnoob

(I'm going from memory here, struggling to get kvm working atm and don't have any other virtualisation running so can't check)

At the boot prompt where you are given the option to hit F1 to choose your kernel, the one that also says in an emergency you can use root=/dev/sda

After huge.s (or whatever your choice is) add intel_pstate=disable

If that works for you and allows you to boot then add it to the lilo append statement when you create lilo.conf