#2875 closed defect (duplicate)
vboxnetflt and kernel Oops, generally unstable
| Reported by: | Mike | Owned by: | |
|---|---|---|---|
| Component: | network | Version: | VirtualBox 2.1.0 |
| Keywords: | ubuntu dapper kernel oops panic | Cc: | rysiek@… |
| Guest type: | other | Host type: | Linux |
Description
After compiling and installing VBox 2.1.0 OSE, and then loading vboxdrv and vboxnetflt kernel modules, trying to run iptables -F panics the kernel.
After reboot, modprobing these modules again and then:
- building the debian packages
- trying to install them
"rmmod vboxnetflt" hangs, and every conecutice cal to any kernel modules-related function (through i.e. insmod, lsmod, modprobe) hangs too. Dmesg output in the attachment.
Attachments (4)
Change History (10)
by , 16 years ago
| Attachment: | configure.command.txt added |
|---|
by , 16 years ago
by , 16 years ago
| Attachment: | ps.aux.grep.mod.txt added |
|---|
comment:1 by , 16 years ago
by , 16 years ago
| Attachment: | dmesg2.txt added |
|---|
VBox installed through generated debian package (after host reboot) oopsed againg. I failed to pinpoint the exact moment/activity that triggered the oopses (to be fixed next time, promise ;) )
comment:3 by , 16 years ago
after these oopses, modprobe -r vboxnetflt hangs again, with CPU usage skyrocketing (same was happening before), but without *any* dmesg output, whatsoever.
I will be able to reboot the machine in a week or two, I'll try to debug further then.
Any pointers on debugging greatly appreciated!
comment:4 by , 16 years ago
Appears to be the same problem as #2827. The fix will be included into the next maintenance release. Since netflt driver always comes with source code those who urgently need the fix may apply the following patch to src/vboxnetflt/linux/VBoxNetFlt-linux.c (the path is relative to your vbox installation directory):
1031c1031 < INIT_WORK(&pThis->u.s.XmitTask, vboxNetFltLinuxXmitTask, NULL); --- > INIT_WORK(&pThis->u.s.XmitTask, vboxNetFltLinuxXmitTask, &pThis->u.s.XmitTask);
Then, kernel modules need to be re-built with
/etc/init.d/vboxdrv setup
comment:5 by , 16 years ago
I confirm this fix does the job - and does it well. Everything seems to work AOK, kernel seems solid again (testing just for 3 hours, so it still might fail), no fsckups upon fiddling with iptables or pinging the virtual machines.
thanks, guys, great job and a great Christmass/New Year present for us here!
have a great 2k9!
rysiek
comment:6 by , 16 years ago
| Resolution: | → duplicate |
|---|---|
| Status: | new → closed |
I will close this bug as duplicate. Additional kernel oops problems with vboxnetflt please to #2885.


Oh, forgot about that:
Guest OS: does not apply, the bug shows itself regardless of Guest OS.