VirtualBox

Ticket #10546 (closed defect: fixed)

Opened 2 years ago

Last modified 8 months ago

kernel panic on ubuntu host when using bridged networking

Reported by: jpg Owned by:
Priority: major Component: other
Version: VirtualBox 4.1.14 Keywords:
Cc: Guest type: Windows
Host type: Linux

Description

I am running virtualbox 4.1.14 on a dell E6410. Until yesterday I had virtualbox 4.1.6 and everything was working great. I then updated to 4.1.14 and I started having kernel panics on my ubuntu 10.04 (LTS) host whenever I enable bridged networking. The kernel panic happens as soon as I start virtualbox (XP Guest). Attached is the log that virtualbox produces before halting (not much)

If I use NAT instead of bridged networking everything works. I tried going back to 4.1.6 (after removing 4.1.14), but the same thing still happens.

The NIC in my laptop is an "Intel Corporation 82577LM Gigabit Network Connection (rev 05)", using the e1000e driver. I have used the stock kernel drivers and the latest ones to no avail.

Attachments

WindowsXP-2012-05-11-11-02-37.log Download (547 bytes) - added by jpg 2 years ago.
Virtual Box log file
dmesg.0 Download (57.2 KB) - added by jpg 18 months ago.
dmesg --- but writing stops before the kernel panic
vbox_crash_v2.jpg Download (327.7 KB) - added by jpg 18 months ago.
screenshot of the host console doing dmesg | tail -f when the crash happened

Change History

Changed 2 years ago by jpg

Virtual Box log file

comment:1 Changed 19 months ago by frank

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

Please reopen if still relevant with VBox 4.1.22 / 4.2.0.

comment:2 Changed 18 months ago by jpg

  • Status changed from closed to reopened
  • Resolution fixed deleted

Still happening on 4.1.22

comment:3 Changed 18 months ago by frank

Any chance to attach a dmesg log of the host kernel after this host crash happened?

Changed 18 months ago by jpg

dmesg --- but writing stops before the kernel panic

Changed 18 months ago by jpg

screenshot of the host console doing dmesg | tail -f when the crash happened

comment:4 Changed 18 months ago by jpg

  • I attached a dmesg log, but the writing stops before the kernel panic. I also attached a screenshot of the host console, while doing "dmesg | tail -f".

comment:5 Changed 8 months ago by frank

  • Status changed from reopened to closed
  • Resolution set to fixed

Please reopen if still relevant with VBox 4.2.16.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use