VirtualBox

Ticket #2875 (closed defect: duplicate)

Opened 5 years ago

Last modified 4 years ago

vboxnetflt and kernel Oops, generally unstable

Reported by: rysiek Owned by:
Priority: blocker 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:

  1. building the debian packages
  2. 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

configure.command.txt Download (127 bytes) - added by rysiek 5 years ago.
dmesg.txt Download (8.2 KB) - added by rysiek 5 years ago.
ps.aux.grep.mod.txt Download (596 bytes) - added by rysiek 5 years ago.
dmesg2.txt Download (5.1 KB) - added by rysiek 5 years ago.
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 ;) )

Change History

Changed 5 years ago by rysiek

Changed 5 years ago by rysiek

Changed 5 years ago by rysiek

comment:1 Changed 5 years ago by rysiek

Oh, forgot about that:

  • system - Ubuntu Dapper Sever 6.06.2
  • kerel - 2.6.15-52-server
  • arch - i386

Guest OS: does not apply, the bug shows itself regardless of Guest OS.

comment:2 Changed 5 years ago by frank

The problem seems to be the old host kernel. We will investigate that.

Changed 5 years ago by rysiek

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 Changed 5 years ago by rysiek

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 Changed 5 years ago by aleksey

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 Changed 5 years ago by rysiek

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 Changed 5 years ago by frank

  • Status changed from new to closed
  • Resolution set to duplicate

I will close this bug as duplicate. Additional kernel oops problems with vboxnetflt please to #2885.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use