LinuxQuestions.org - Slackware 13.37/2.6.37.6-smp on VirtualBox kernel panic on Intel i3/i5/i7

- Linux - Virtualization and Cloud (https://www.linuxquestions.org/questions/linux-virtualization-and-cloud-90/)

- - Slackware 13.37/2.6.37.6-smp on VirtualBox kernel panic on Intel i3/i5/i7 (https://www.linuxquestions.org/questions/linux-virtualization-and-cloud-90/slackware-13-37-2-6-37-6-smp-on-virtualbox-kernel-panic-on-intel-i3-i5-i7-894471/)

Slackware 13.37/2.6.37.6-smp on VirtualBox kernel panic on Intel i3/i5/i7

Slackware 13.37 kernel 2.6.37.6-smp on VirtualBox kernel panics on start up Intel i3/i5/i7 but not on Intel Core Dual 2 or 4 cores. I've tried Windows 7 and Linux physical hosts.

I get the same statistics on all VirtualBox 4 versions.

It may be the 2.6.37.6-smp kernel + VirtualBox + Intel i3/i5/i7.

I encountered this too last night, I have an i5 2400. Haven't tried disabling hardware virualization (VT-x) though.

Nope. That didn't work.

Here's another guy with the same problem:
http://forums.virtualbox.org/viewtopic.php?f=3&t=43394
No answers as of yet....

I do believe its the kernel .37 + virtualbox + i3/i5/i7 combination.

Well, I tried older 2.6 kernels and newer 2.6 kernels including 2.6.39. Didn't work.
I've even tried kernel 3.01 from kernel.org, nope. I tried 2.6.38 from the slackware "current", but nope.

It verx! It verx!
I booted up slack 13.37 on another virtualbox host. Then I recompiled kernel 3.0.
Then I moved the guest vm back to the offending machine with the i3/i5/i7. Yes it failed on all three "i" cpus.
And lo and behold it worked!!

The problem is that the included kernel does not work with this combination (mentioned in my first post).

I'll post the diff later.

Hi, could you please tell me how you solved this problem? I got the same problem on my Acer 5742ZG laptop.

The processor is an Intel Pentium P6100.

This is my hardware:

Code:

00:00.0 Host bridge: Intel Corporation Core Processor DRAM Controller (rev 02)

00:01.0 PCI bridge: Intel Corporation Core Processor PCI Express x16 Root Port (rev 02)

00:16.0 Communication controller: Intel Corporation 5 Series/3400 Series Chipset HECI Controller (rev 06)

00:1a.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05)

00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 05)

00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 (rev 05)

00:1c.1 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 2 (rev 05)

00:1d.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05)

00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev a5)

00:1f.0 ISA bridge: Intel Corporation Mobile 5 Series Chipset LPC Interface Controller (rev 05)

00:1f.2 SATA controller: Intel Corporation 5 Series/3400 Series Chipset 4 port SATA AHCI Controller (rev 05)

00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller (rev 05)

01:00.0 VGA compatible controller: ATI Technologies Inc Manhattan [Mobility Radeon HD 5000 Series]

01:00.1 Audio device: ATI Technologies Inc Manhattan HDMI Audio [Mobility Radeon HD 5000 Series]

02:00.0 Ethernet controller: Broadcom Corporation NetLink BCM57780 Gigabit Ethernet PCIe (rev 01)

03:00.0 Network controller: Atheros Communications Inc. AR9287 Wireless Network Adapter (PCI-Express) (rev 01)

ff:00.0 Host bridge: Intel Corporation Core Processor QuickPath Architecture Generic Non-core Registers (rev 02)

ff:00.1 Host bridge: Intel Corporation Core Processor QuickPath Architecture System Address Decoder (rev 02)

ff:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev 02)

ff:02.1 Host bridge: Intel Corporation Core Processor QPI Physical 0 (rev 02)

ff:02.2 Host bridge: Intel Corporation Core Processor Reserved (rev 02)

ff:02.3 Host bridge: Intel Corporation Core Processor Reserved (rev 02)

I boot the .iso (32 bit version, the host machine is debian squeeze 64bit) and then press Enter (to boot hugesmp.s) but then it fails during the loading. I tried huge.s too, just for curiosity, without different results.

This is a screenshot of the error:
http://img39.imageshack.us/img39/6319/screen02u.png

Well, much later, the developers of virtualbox finally admitted that it was THEIR problem!
The kernel panics had nothing to do with the linux kernels (kernel.org) but were entirely virtualbox bugs. It seems that these problems have mostly been solved. It still shows up on some machines.

I will test it on VirtualBox again as soon as possible :) I'd like to make some experience with Slackware (and yes, I was talking about virtual machine / virtualbox, as you asked in the email preview). :)

I tried it again on my Debian 64bit system. I run the slackware .iso into Virtualbox and then it gives me a kernel panic.
Screen:
http://imageshack.us/a/img442/9342/gjeifj.png

Sorry I haven't been checking back.
Has this problem been solved?
Lately, virtualbox has been much improved. Very few weird crashes lately.

I believe the problems come from my CPU not supporting some Virtualization technologies like VT-x.
Infact, I've tried some other distributions... but they work very slow under virtualbox.
I've also tried Slackware not so much time ago, still the same problems. Probably it's my CPU's fault.

Thanks for support!