bridge networking on Mandriva fails on reboot

[jim whitby]

The system is Mandriva 2008.1 x86_64, using vbox 1.6.2.

The problem is during boot. The vbox0 device fails. The error is vbox0 doesn't exist. There is a device created named vbox??, whose suffice varies. The "cure" seems to be to remove the unwanted/unneeded vbox?? and the vbox0 files from /etc/sconfig/network-scripts. Remove the vbox0 line from interfaces. Run VBoxAddif for vobx0, restart the network.

The same error is reproduced on a different machine running 2008.1, but is only 32 bit.

[Frank Mehnert]

Does this problem still happens with VirtualBox 1.6.4? If so, can you check if /etc/init.d/vboxnet is called during boot?

[jim whitby]

Replying to frank:

Does this problem still happens with VirtualBox 1.6.4? If so, can you check if /etc/init.d/vboxnet is called during boot?

Yes to both.

[jim whitby]

Replying to domattps:

Replying to frank:

Does this problem still happens with VirtualBox 1.6.4? If so, can you check if /etc/init.d/vboxnet is called during boot?

Yes to both.

Don't if this helps or not...

In order to function properly, I have an init script running that removes the ifcfg-vbox?? files, removes the vbox/interfaces file, then reboots, adds a vbox0 interface and everything runs fine.

Without this: There is an error ( only onscreen ) that indicates an error with br0 when the network startup script runs and the strange vbox?? interface is created.

If you need it, I'll try and write down the the exact error ( its over 120 char long ) and isn't in any of the log files that I can find.

[Frank Mehnert]

Hmm, I didn't fully understand you. Which ifcfg-vbox?? files? Actually I assume that you installed the PUEL package. This package creates a file /etc/vbox/interfaces using the VBoxAddIF tool. Didn't you use that tool?

[jim whitby]

Replying to frank:

Hmm, I didn't fully understand you. Which ifcfg-vbox?? files? Actually I assume that you installed the PUEL package. This package creates a file /etc/vbox/interfaces using the VBoxAddIF tool. Didn't you use that tool?

Sorry.. hope I'm explaining better now... Stop the network from running, delete the ifcfg-vbox?? file(s) in the network-scripts dir, delete the vbox/interface file and then restart the network, then create a new vbox0, using VBoxAddIF.

[Frank Mehnert]

Please reopen if this problem persists with VBox 2.2.0. Networking was completely changed in VBox 2.1.0.