Opened 13 years ago
Closed 11 years ago
#10546 closed defect (fixed)
kernel panic on ubuntu host when using bridged networking
| Reported by: | Juan Pablo Gonzalez | Owned by: | |
|---|---|---|---|
| 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 (3)
Change History (8)
by , 13 years ago
| Attachment: | WindowsXP-2012-05-11-11-02-37.log added |
|---|
comment:1 by , 12 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Please reopen if still relevant with VBox 4.1.22 / 4.2.0.
comment:3 by , 12 years ago
Any chance to attach a dmesg log of the host kernel after this host crash happened?
by , 12 years ago
| Attachment: | vbox_crash_v2.jpg added |
|---|
screenshot of the host console doing dmesg | tail -f when the crash happened
comment:4 by , 12 years ago
- 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 by , 11 years ago
| Resolution: | → fixed |
|---|---|
| Status: | reopened → closed |
Please reopen if still relevant with VBox 4.2.16.
Virtual Box log file