Host only network not persistent across vboxdrv reload on Linux => Fixed in SVN

[kalif]

I've created a new interface vboxnet1, this interface is not persistent across reboot/vboxdrv reload If I add it again from the graphical console, every field is already set as i previously did; it seems that VirtualBox store the vboxnet1 configuration somewhere, but it doesn't create the interface automatically on startup.

[kalif]

Running VirtualBox as non root user, anyway the user is in the vboxusers group

[gilboa]

Confirmed. v3.1.4 running Fedora 12/x86_64. Current user is a member of the vboxusers group.

• Gilboa

[gilboa]

Still seeing it. v3.1.6 on F12/x86_64.

[Sm0k1n]

Confirmed on VirtualBox 3.1.6 running on openSuse 11.2 2.6.31.12-0.1-default kernel.

Any host-only interfaces except the first one (vboxnet0) don't show up again after a restart of the service or the host. The interface settings persist in the VirtualBox.xml file.

[ragnar.jensen]

Confirmed on 3.1.6 r59338 running on RedHat EL5 2.6.18-128.el5PAE #1 SMP Wed Dec 17 12:02:33 EST 2008 i686 i686 i386 GNU/Linux

[frank]

Confirmed. Bug still not fixed in the upcoming release 3.1.8 but we hope to get a fix into 3.2.0.

[kalif]

Found a little workaround for this bug: I added the line /usr/lib/virtualbox/VBoxNetAdpCtl add in the init scripts, one line for each adapter previously configured. In this way the devices are created at boot time.

[gilboa]

Still seeing it in v3.2.

[fffuuu]

'Confirmed on 3.2.4_OSEr62467 running on 2.6.32-gentoo-r10 x86_64'

[smazy]

Confirmed on 3.2.8 running on Arch Linux's kernel26-lts-2.6.32.21-1

[uchima]

Confirmed on 3.2.8 as well; host is Ubuntu 9.10 64-bit...

[ronelliott]

Same issue still with 4.0.2 in Ubuntu 10.10 amd64 and Cent 5.5 amd64

[frank]

This bug will be finally fixed in the next maintenance release.