VirtualBox

Ticket #13795 (closed defect: fixed)

Opened 3 years ago

Last modified 2 years ago

Linux host freezes when starting VirtualBox VM with bridged network adapter and running docker container => Fixed in SVN

Reported by: briceo Owned by:
Priority: major Component: network
Version: VirtualBox 4.3.20 Keywords: bridged network docker
Cc: Guest type: all
Host type: Linux

Description

Here is the environment setup: Host: Ubuntu 14.04 VirtualBox: 4.3.20 r96996 (I've tested with 4.3.21 beta also) Docker: 1.4.1 build 5bc2ff8 (I've tested with docker 1.2.0 also)

When trying to run a VirtualBox VM with a bridged network adapter (guest OS doesn't seem to matter, as I've not even gotten to the point where the guest can be installed), and there is a docker container already running, the host system freezes (completely locks up, and the only solution is to hit the reset button).

If I start the VirtualBox VM first (with a bridged adapter), and then start the docker container, the host does not freeze.

Additionally, If I change the VirtualBox VM network from bridged to NAT, then the host does not freeze (assuming the docker container was started first, and then the VM).

I have not seen any kernel panics, and upon reboot, there is nothing in the logs to indicate an error happened.

Change History

comment:1 Changed 3 years ago by mbentley

I am able to reproduce the same. An issue has also been filed against docker here >>  https://github.com/docker/docker/issues/10031. With there not being a lockup when the networking is switched, I am pretty certain that it is a bug in the VirtualBox networking that is causing this.

comment:2 Changed 3 years ago by francisd

Same thing here. Ubuntu 14.04 with Linux kernel 3.13.0-51.

I'm not using a docker container, but I had an LXC container running... Stopped to crash when I stopped the container before booting the VM.

comment:3 Changed 3 years ago by vbox-lxc

I have the same issue with Ubuntu 15.04

comment:4 Changed 2 years ago by timretout

I think I've duplicated this issue at #14188, but I've added some debug output for the kernel panic there.

comment:5 Changed 2 years ago by cburroughs

FWIW I've also encountered this issue with the the old "2.6.32" Centos6 kernel line.

comment:6 Changed 2 years ago by DO

The same issue with VirtualBox 5.0 + LXC (Ubuntu 14.04)..

comment:7 Changed 2 years ago by vushakov

The workaround tested with LXC is to make VBox guest bridged to the host's bridge br0 instead of its eth0 port. In the container you need to turn off tx checksum offloading with

lxc# ethtool -K eth0 tx off

otherwise packets from the container will be delivered to VBox guest without proper checksums and dropped by the guest.

comment:8 Changed 2 years ago by vushakov

Ah, in the comment:6 setup the VM was bridged to the eth0 that was bridged to host's bridge. The problem of course is that the bug manifests when the VM is bridged to eth0 that is not bridged to anything on the host. It's enough to have a bridge with a veth port (like docker or lxc container).

comment:9 Changed 2 years ago by frank

Can you confirm that this test build fixes your problem?

comment:10 Changed 2 years ago by DO

frank, the recent build 101860 works ok, thanks.

comment:11 Changed 2 years ago by vushakov

  • Summary changed from Linux host freezes when starting VirtualBox VM with bridged network adapter and running docker container to Linux host freezes when starting VirtualBox VM with bridged network adapter and running docker container => Fixed in SVN

The fix will be in the next 4.3.x and 5.x releases.

comment:12 Changed 2 years ago by frank

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

Fix is part of VBox 5.0.2.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use