Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#54889 - [virtualbox] host-only networking broken

Attached to Project: Community Packages
Opened by Oskar Carl (kalagon) - Thursday, 20 July 2017, 13:40 GMT
Last edited by Christian Hesse (eworm) - Monday, 24 July 2017, 09:19 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Christian Hesse (eworm)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No

Details

Description:
Update 5.1.24 breaks host-only networking for me. Both standard and LTS kernel are affected. Other than this the VMs seem to work fine, the host simply does not have a route to the VM. I have not done any manual configuration on NetworkManager, which works fine with virtualbox<5.1.24.
I was unable to find any indication of this in Virtualbox logs. Everything looks normal and the kernel modules load fine.

Additional info:
* virtualbox 5.1.24
* virtualbox-host-{modules-arch,dkms} 5.1.24
* linux{,-headers} 4.11.9-1 / linux-lts{,-headers} 4.9.37
* networkmanager 1.8.2-1

Steps to reproduce:
Install the newest Virtualbox version, start a VM with previously working host-only networking and try to ssh or ping to it.
This task depends upon

Closed by  Christian Hesse (eworm)
Monday, 24 July 2017, 09:19 GMT
Reason for closing:  Fixed
Additional comments about closing:  virtualbox 5.1.24-2
Comment by Peter Kaukov (Kaukov) - Friday, 21 July 2017, 09:30 GMT
I can confirm this. Upgraded to 5.1.24 and host-only networking broke for the VMs. I was able to ssh into them, but not ping them. Rolled back to 5.1.22 to have host-only networking working.
Comment by Christian Hesse (eworm) - Friday, 21 July 2017, 09:48 GMT
The changelog [0] has one entry about host-only networking...
Possibly that broke anything for us?

[0] https://www.virtualbox.org/wiki/Changelog
Comment by Christian Hesse (eworm) - Friday, 21 July 2017, 09:49 GMT
Upstream bug:
https://www.virtualbox.org/ticket/16911
Comment by Oskar Carl (kalagon) - Friday, 21 July 2017, 12:01 GMT
It looks like it. At the very least it should remove the opt-deps on net-tools.
Currently I'm not able to find the exact changes in the implementation to confirm this, but if the referenced ticket [1] is any indication it might now use iproute2. However, it does not work on my machine, even with iproute2 installed.

[1] https://www.virtualbox.org/ticket/16764

Loading...