VirtualBox

Ticket #14188 (closed defect: duplicate)

Opened 7 years ago

Last modified 7 years ago

Kernel panic (unable to handle kernel paging request) at __netif_receive_skb_core

Reported by: timretout Owned by:
Component: network Version: VirtualBox 4.3.28
Keywords: Cc:
Guest type: other Host type: other

Description

When starting a Virtualbox VM, I can reliably reproduce a host kernel oops:

[  179.858414]  "kernel tried to execute NX-protected page - exploit attempt? (uid: 1001)
[  179.861529] BUG: unable to handle kernel paging request

It seems to happen when running docker on the same host. The VM has a bridged interface with a static IP, and the stack trace always mentions __netif_receive_skb_core. I'll try to narrow down a test case...

I've tried to rule out these other bugs:

I'm using Debian unstable, with Debian-provided kernel and virtualbox - I'll try to reproduce it with the Oracle binaries:

$ uname -a
Linux thinkpad 4.0.0-1-amd64 #1 SMP Debian 4.0.2-1 (2015-05-11) x86_64 GNU/Linux

$ virtualbox --help
Oracle VM VirtualBox Manager 4.3.28_Debian

When I booted with "nosmap" and "nosmem", I got a slightly different error message, which I'll also attach.

VBox.log is always empty with these crashes.

I've got a kernel core dump, but I'd rather not upload that publicly - I hope I can help with debugging it, though.

Attachments

dmesg.201506091503 Download (67.3 KB) - added by timretout 7 years ago.
dmesg output
dmesg.201506091433 Download (66.9 KB) - added by timretout 7 years ago.
dmesg output (after nosmap and nosmem)
dmesg.201506120908 Download (68.2 KB) - added by timretout 7 years ago.
dmesg output (using official binaries)
vboxdrv.ko.gz Download (139.9 KB) - added by timretout 7 years ago.
vboxnetflt.ko Download (36.6 KB) - added by timretout 7 years ago.
vboxnetadp.ko Download (14.5 KB) - added by timretout 7 years ago.

Change History

Changed 7 years ago by timretout

dmesg output

Changed 7 years ago by timretout

dmesg output (after nosmap and nosmem)

comment:1 follow-up: ↓ 6 Changed 7 years ago by timretout

Might be a dupe of #13795?

comment:2 Changed 7 years ago by timretout

So far I've found two workarounds that stop the crash:

  • Run docker containers with --net=host option (i.e. don't use Docker bridging)
  • Change the virtualbox bridge to use "wlan0" instead of "eth0"

I have no idea why the second one changes anything. wlan0 is the physical interface that is actually connected to the internet at the moment, and eth0 is unplugged.

comment:3 Changed 7 years ago by frank

This has most likely nothing to do with SMAP. Could you try to reproduce the crash again and provide:

  • the outout of 'dmesg'
  • the corresponding VBox.log file
  • the vboxdrv.ko, vboxnetflt.ko and vboxnetadp.ko modules

Thank you!

comment:4 Changed 7 years ago by timretout

Hi frank,

I have reproduced the crash this morning with the official Oracle binaries:

$ virtualbox --help
Oracle VM VirtualBox Manager 4.3.28

I will attach dmesg and the built kernel modules, but VBox.log is always empty when this crash occurs, presumably because the host panics before anything gets written. I'm having to use kdump to get the dmesg output, because the kernel panic doesn't normally get written to disk either.

I do have the kernel core dump produced by kdump, which loads in 'crash', so I can get any debug information if that's useful.

Changed 7 years ago by timretout

dmesg output (using official binaries)

Changed 7 years ago by timretout

Changed 7 years ago by timretout

Changed 7 years ago by timretout

comment:5 Changed 7 years ago by vushakov

  • Component changed from other to network

comment:6 in reply to: ↑ 1 Changed 7 years ago by vushakov

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

Replying to timretout:

Might be a dupe of #13795?

Looks like it indeed. The fix will be in the next release.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use