5.1.24 Private Networks Failing on Fedora 26 (#16911)
5.1.24 Private Networks Failing on Fedora 26 (#16911)
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.
Last edited by socratis on 10. Jan 2018, 00:20, edited 5 times in total.
Reason: Added ticket related information.
Reason: Added ticket related information.
Re: 5.1.24 Private Networks Failing on Fedora 26
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.
Re: 5.1.24 Private Networks Failing on Fedora 26
The same thing happens in Linux Mint 18.2
Re: 5.1.24 Private Networks Failing on Fedora 26
Same thing on Ubuntu Trusty (14.04.5), I work around it by manually up the host-only adapter:
Code: Select all
sudo ifconfig vboxnet0 up
Re: 5.1.24 Private Networks Failing on Fedora 26
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
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
-
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: 5.1.24 Private Networks Failing on Fedora 26
There is a ticket that opened just for this: https://www.virtualbox.org/ticket/16911
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
-
- Posts: 113
- Joined: 15. Jan 2014, 13:54
- Primary OS: Debian other
- VBox Version: OSE Debian
- Guest OSses: devuan, MX-Linux, others
Re: 5.1.24 Private Networks Failing on Fedora 26 (#16911)
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.
-
- Posts: 1
- Joined: 19. Jul 2017, 15:45
Re: 5.1.24 Private Networks Failing on Fedora 26 (#16911)
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..
-
- Volunteer
- Posts: 2561
- Joined: 30. May 2007, 18:05
- Primary OS: Fedora other
- VBox Version: PUEL
- Guest OSses: XP, Win7, Win10, Linux, OS/2
Re: 5.1.24 Private Networks Failing on Fedora 26 (#16911)
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.