Crash when disabling network interface => Fixed in 2.0.4

[Andreas]

I have installed Solaris 10 5/08 with the VirtualBox packages

virtualbox-ose-kmp-default-2.0.2_2.6.25.16_0.1-12.1
xorg-x11-driver-virtualbox-ose-2.0.2-12.1
virtualbox-ose-2.0.2-12.1

on openSUSE 11.0/64bit. The inital installation I did with a one network configured as NAT. If I change this network now to "Host Interface" the guest Solaris will not start with the message

Failed to initialize Host Interface Networking.
VBox status code: -3100 (VERR_HOSTIF_INIT_FAILED).


Result Code: 
NS_ERROR_FAILURE (0x80004005)
Component: 
Console
Interface: 
IConsole {d5a1cbda-f5d7-4824-9afe-d640c94c7dcf}

If I start the guest with "Not attached", I the guest starts. Once the guest is in runlevel 3 and I log into it and the JDK is up and running, I tried to change the configuration network configuration. If I click on "Devices" -> "Network Adapters" -> "Adapter 0" the guest crashes immediately. The only message I receive is in the host log "/var/log/messages" saying

...
Sep 27 12:12:45 humpyham kernel: VirtualBox[6562]: segfault at 10 ip 7fd0f1fc03d2 sp 41055b20 error 4 in VBoxDD.so[7fd0f1fac000+75000]
Sep 27 12:19:47 humpyham kernel: VirtualBox[7200]: segfault at 10 ip 7f9afb9db3d2 sp 41ba9b20 error 4 in VBoxDD.so[7f9afb9c7000+75000]
...

[Andreas]

Log of guest clicking on "Adapter 0" in state 'disabled'

[Andreas]

log of guest where network is changed to "Host Interface"

[Frank Mehnert]

Thanks for the report. The crash will be fixed in 2.0.4. The problem with a not working host interface device is the following: You have to add a TAP device using VBoxAddIF, see the user manual (you can download the manual from here). I suggest you to specify the user which is starting the VM as user, don't use the group. Because if you bind the tap interface to a specific group, the user which is about to start the VM must have set this group as primary group.