Ticket #4236 (closed defect: fixed)
kernel panic in virtualbox 2.2 64bit SMP
Reported by: | supermafete | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 2.2.4 |
Keywords: | kernel panic debian etch vbox virtualbox 2.2 vboxnetflt | Cc: | |
Guest type: | Linux | Host type: | Linux |
Description
Hi there,
I installed today VBox 2.2 in my production server from the VirtualBox official apt repositories.
Host OS: Debian Etch 4.1 AMD64 SMP Host Kernel: 2.6.18-6-vserver-amd64 (debian-patches) Host Hardware: Dell PowerEdge 2950 Dual Quad-Core, 16Gb RAM, SATA Raids.
After a few hours testing VBox with bridged networking guests (debian and fedora), the entire server hangs up with a kernel panic. I suspect that it hangs because a bug in vboxnetflt kernel module.
I attach to this post the syslog relevant lines.
Any suggestions or ideas?
Thank you in advance,
MaF.
Attachments
Change History
comment:1 Changed 14 years ago by frank
After the 2.2.4 release we found a problem with Linux host kernels <= 2.6.18. Could you apply this patch to /usr/src/vboxnetflt/vboxnetflt-2.2.4, then execute
/etc/inid.d/vboxdrv setup
and check if you experience such a host crash again?
comment:2 Changed 14 years ago by supermafete
Thank you Frank!
I'll check the patch next weekend. I don't want to take risks in business time. I'll let you know the results.
If it works maybe we can think in compile a new package for the repositories.
comment:3 Changed 14 years ago by supermafete
Is there any way to compile only the vboxnetflt module for the 2.2.4-47978_Debian_etch version?
comment:4 Changed 14 years ago by frank
I don't understand. Does /etc/init.d/vboxdrv setup not work?
comment:5 Changed 14 years ago by supermafete
Sorry, I thought that the entire sources would be necessaries to recompile the module. I didn't knew that the module source were in the system with the binary apt installation.
I'll test it the next weekend and let you know the results.
Thank you Frank.
comment:6 Changed 14 years ago by supermafete
Hello again,
I tried to apply the patch this way
$ patch -p0 < vboxnetflt.diff
This was the output
Hunk #1 FAILED at 1. Hunk #2 FAILED at 27. Hunk #3 FAILED at 775. 3 out of 3 hunks FAILED -- saving rejects to file linux/VBoxNetFlt-linux.c.rej
I attached the .rej file. Maybe I'm don't patching well...
comment:7 Changed 14 years ago by frank
Thanks for testing. I've fixed the diff and replaced the attachment. Please apply it with
cd /usr/src/vboxnetflt-2.2.4 patch -p0 < vboxnetflt.diff
and don't forget
/etc/init.d/vboxdrv setup
to recompile the kernel module.
comment:8 Changed 14 years ago by supermafete
Hi Frank,
I recompiled the module with the patch. This time it works.
I'll do the tests during this weekend and let you know the results.
Thank you very much for your help,
MaF.
comment:9 Changed 14 years ago by supermafete
Hi Frank,
I couldn't do the tests yet, but I'm on it
As soon as I've the results, I'll let you know.
Greetings.
comment:11 Changed 13 years ago by supermafete
- Status changed from closed to reopened
- Resolution fixed deleted
Hi Frank,
I'm sorry to inform you that the patch didn't work. The server crashed again.
Maybe the new 3.0.x version resolves this?
Thank you very much for your help.
comment:12 Changed 13 years ago by frank
supermafete, which VBox version did you test this time?
comment:13 Changed 13 years ago by supermafete
the same one, 2.2.4. I didn't change anything of the installation, just recompiled the modules with the patch you sent me.
comment:14 Changed 13 years ago by supermafete
Hi there,
I upgraded the host server to lenny (2.6.26) and seems to work fine with VBox 3.0.4
Thank you very much for all your help,
MaF
comment:15 Changed 13 years ago by frank
- Status changed from reopened to closed
- Resolution set to fixed
comment:16 Changed 13 years ago by Barron123
I am seeing this as well with a WinXP SP3 guest running under RHEL5.3. The system has 12GB mem and 8 cores. I saw the issue under 3.02 and 3.04, but not under 2.24. The host is dual monitored and using coupon for zend. Tab-alt works to unlock the mouse. I've tried appending 'force_async_tsc=1' to the modprobe line in /etc/init.d/vboxdrv with no luck.