5.1.24 Private Networks Failing on Fedora 26 (#16911)

[socratis]

---

Mod edit
There is a ticket for this: https://www.virtualbox.org/ticket/16911
Test builds > r117090, contain a fix: https://www.virtualbox.org/wiki/Testbuilds

---

After upgrading my VirtualBox to the latest version, I've run into an issue where configured private networks are failing to initialize.

The virbr0 connection is visible in the network configuration, but after bringing up the box the vboxnet# networks never connect.

The guests do show the configured networks in the network list, but they are unable to reach the gateway (.1) host machine.

So it seems like the main issue is that the networks are not starting properly on the host machine.

Downgrading to 5.1.22 fixed this issue immediately.

[Zitch]

I can confirm that this is happening on KDE Neon (Based on Ubuntu 16.04). Reverting back to 5.1.22 fixed private (host only) networking.

[gdbonino]

The same thing happens in Linux Mint 18.2

[Zaka]

Same thing on Ubuntu Trusty (14.04.5), I work around it by manually up the host-only adapter:

Code: Select all   Expand viewCollapse view

sudo ifconfig vboxnet0 up

[ndsrl]

Can also confirm host only adaptor broken on openSUSE Leap 42.2.
host only adaptor vboxnet0 present, DHCP enabled IP assigned but unable to access VM from host via host only adaptor or vice versa, access host from VM via host only adaptor.
Bridged adaptor works fine though.
Reverting to 5.1.22 until rectified

[socratis]

There is a ticket that opened just for this: https://www.virtualbox.org/ticket/16911

[HarryMan]

I'm getting the same problem with 5.1.24 on CentOS 6.8 using hostonly networks. Downgrading back to 5.1.22 restores everything to a working state with no changes required by me.

[Max Modulo]

I can confirm this issue on CentOS 7 3.10.0-514.26.2.el7.x86_64. Downgrading to VirtualBox 1_22 has resolved the issue for now..

[Martin]

Latest update from the ticket with a temporary workaround:

Changed 2 hours ago by aleksey

This appears to be a recent regression in VBoxNetAdpCtl, which now uses 'ip' instead of 'ifconfig' and fails to bring the interface up. The test build will be available shortly. Meanwhile you can work around the issue by manually bringing the interface up with ip link set dev vboxnet0 up.