Opened 14 years ago
Closed 14 years ago
#7879 closed defect (fixed)
Linux host freezes when started bridged network to a kernel bridge device => Fixed in SVN
Reported by: | Ivo Smits | Owned by: | |
---|---|---|---|
Component: | network | Version: | VirtualBox 4.0.0 |
Keywords: | Cc: | ||
Guest type: | other | Host type: | Linux |
Description
My linux host freezes right after I start a guest that uses bridged networking, bridged to a kernel bridge device (br0, bridge-utils/brctl). It works fine with other devices (eth, tap). This problem did not exist in previous versions of VirtualBox (3.x).
I'm running Ubuntu 10.04 LTS - Lucid Lynx, x64. I'm using a stock Ubuntu kernel version 2.6.32-27-generic #49-Ubuntu SMP.
I've tried to disable VT-x, CSAM, PATM, raw ring 0 and raw ring 3 using VBoxSDL, but this did not help.
The VBox.log file is empty. There's no console output from VirtualBox and syslog only tells me that the bridge device has just entered promiscuous mode.
Attachments (4)
Change History (14)
comment:1 by , 14 years ago
comment:2 by , 14 years ago
I'm having exactly the same issue:
Host system: Ubuntu 10.04 LTS (kernel: 2.6.32-27-generic)
Vbox: VirtualBox 4.0.0
I created a bridge device with bridge-utils, set it a static ip, configured VM's network adapter to connect to the br0 device (win xp) and after a few seconds the whole host system hangs and the capslock and numlock leds light up...
UFO, do you have some news about it?
comment:3 by , 14 years ago
Looks like this might be a duplicate of #7908. I will attach my vboxnetflt.ko as requested in the other ticket.
Guizmo: using a tap device to bind to, instead of a bridge, works somewhat better. It crashes under load, but not immediately. I'm currently successfully using the VDE2 backend, which runs in userspace. The vde_switch then binds to a tap interface on the host.
by , 14 years ago
Attachment: | vboxnetflt.ko added |
---|
vboxnetflt.ko on ubuntu kernel 2.6.32-27-generic, built by dkms
by , 14 years ago
Attachment: | vboxnetflt.2.ko added |
---|
vboxnetflt.ko on ubuntu kernel 2.6.32-27-generic, built by dkms (Guizmo)
comment:4 by , 14 years ago
Thanks for the update UFO.
I'll try your sugestion or maybe go back to 3.2...
Here is my vboxnetflt.ko
p.s.: Do you know if this problem occures on mandriva with the same kernel?
comment:5 by , 14 years ago
This occurs on Fedora 14 host (kernel 2.6.35.10-74.fc14.x86_64.) I tried with centos 5.5 and ubuntu 10.10 guests. If the guest use a bridge, the host freeze with black screen and it's not possible to change the level of the host (CTRL+ALT+FF3 for exemple). Whithout bridge, no crash happens.
by , 14 years ago
Attachment: | vboxnetflt3.ko added |
---|
vboxnetflt.ko on fedora 14 kernel 2.6.35.10-74.fc14.x86_64, built by dkms (bmeunier)
comment:6 by , 14 years ago
follow-up: 8 comment:7 by , 14 years ago
Apply the patch in the directory where you have installed VirtualBox with
patch -p0 -i <path-to-qdisc_noqueue.patch>
then rebuild the modules with
sudo /etc/init.d/vboxdrv setup
comment:8 by , 14 years ago
Replying to aleksey:
Apply the patch in the directory where you have installed VirtualBox with
patch -p0 -i <path-to-qdisc_noqueue.patch>then rebuild the modules with
sudo /etc/init.d/vboxdrv setup
It solves the problem. The patch works.
Thank you
comment:9 by , 14 years ago
Summary: | Linux host freezes when started bridged network to a kernel bridge device → Linux host freezes when started bridged network to a kernel bridge device => Fixed in SVN |
---|
The freeze has now also occured with a NIC bridged to an (unused) tap device, while the guest was loading a large file from a network file share.
Also, the capslock led lights up when the host freezes.