Ticket #11026 (new defect)

Opened 19 months ago

Last modified 19 months ago

bridged networking warning skb_warn_bad_offload

Reported by: dudmuck Owned by:
Priority: major Component: network
Version: VirtualBox 4.2.0 Keywords: bridged networking skb_warn_bad_offload
Cc: Guest type: Linux
Host type: Linux


With Linux x86_64 host and Linux x86_64 guest, using tcp/ip over bridged networking results in a stack trace in dmesg logs.


VBox.log Download (46.5 KB) - added by dudmuck 19 months ago.
vbox log
kernel_warning.txt Download (2.7 KB) - added by dudmuck 19 months ago.
stack trace from dmesg

Change History

Changed 19 months ago by dudmuck

vbox log

Changed 19 months ago by dudmuck

stack trace from dmesg

comment:1 Changed 19 months ago by frank

What type of network card provides the host interface eth2?

comment:2 Changed 19 months ago by aleksey

This happens because vboxnetflt.ko receives a GRO packet from the ixgbe driver it cannot understand and it tries to segment it with skb_gso_segment(). The ixgbe driver marks checksum as unnecessary in packet skb while skb_gso_segment() expects it to be partial. The real question is why our netfilter cannot understand the packet. Could you build VirtualBox kernel modules with debug enabled? To do it you need to go <vbox_dir>/src/vboxhost and execute the following commands while logged in as root:

/etc/init.d/vboxdrv stop
USER=aleksey make BUILD_TYPE=debug
insmod ./vboxdrv.ko
insmod ./vboxnetflt.ko
insmod ./vboxnetadp.ko

These will build and load kernel modules. <vbox_dir> is usually /opt/VirtualBox. The debug output goes into the system log (/var/log/messages, most likely). Please send the relevant part of the log to aleksey dot ilyushin at oracle dot com. Or upload it to and send me the name.

Note: See TracTickets for help on using tickets.
ContactPrivacy policyTerms of Use