virtualbox.org

Hi !
Recently installed 1.5.0 on Suse from packages
guest OS - WinXP normally installed and work in NAT mode

But if I change network set from NAT to Host interface - then accept this error message on start machine

Unknown error creating VM (VERR_HOSTIF_INIT_FAILED).
VBox status code: -3100 (VERR_HOSTIF_INIT_FAILED).

Result Code: 0x80004005
Component: Console
Interface: IConsole {1dea5c4b-0753-4193-b909-22330f64ec45}

Also , vbox0 not seen in ifconfig output

What it's mean and how to correct this ?

Before I'm setup VB on Debian whithout this problem

cross topic here, please let me know if there is solution found. thanks

dubov wrote:Unknown error creating VM (VERR_HOSTIF_INIT_FAILED).
VBox status code: -3100 (VERR_HOSTIF_INIT_FAILED).

Just two possibilities for this in short:
- vbox0 isn't initiated to the right user (see user manual for vbox0 setup).
- /dev/net/tun has the wrong modes and/or owner.

Updated the same topic mentioned above, wireless networking does not support bridging. I guess no luck for this moment unless in the near future either wireless spec supports bridging or linux kernel have some special feature.

vbox 1.6.0 opensuse 10.3 bridged: /etc/init.d/vboxnet patch

I had the same problem (after using VBoxAddIF!)

It turned out that '/etc/init.d/vboxnet start' does not work as expected.
the interface vbox00 gets created and is upped, gets added to the bridge, but disappears after that.

this can be solved with this patch:

Code: Select all

--- vboxnet	2008-05-09 15:17:09.000000000 +0200
+++ vboxnet-v1.60-opensuse-10.3	2008-05-09 15:34:21.000000000 +0200
@@ -198,11 +198,13 @@
             i=1
             while [ $i -le 10 ]; do
               ifconfig "$1" up 2> /dev/null
+              sleep .5 # opensuse 10.3 + VB 1.6.0: without this, interface $1 comes up, gets added to the bridge and dissapears !
 	      if ifconfig | grep "$1" > /dev/null; then
                 # Add the interface to a bridge if one was specified
                 if [ -n "$3" ]; then
                   if brctl addif "$3" "$1" 2> /dev/null; then
-                    echo "$1 $2 $3" >> "$VARFILE"
+                    # interface $1 will be gone here, without 'sleep .5'
+		    echo "$1 $2 $3" >> "$VARFILE"
                   else
                     echo "$1 $2" >> "$VARFILE"
                     echo "Warning - failed to add interface $1 to the bridge $3"

Is it as simple as that? Adding a 5 second sleep?

Now I have to try this on Fedora. If it's that easy, I will laugh.

BTW, as for wireless bridging, I have a page on how I got it working on Fedora at http://home.nyc.rr.com/computertaijutsu/vboxbridge.html

NOTE THAT IT'S FOR VERSIONS LESS THAN 1.6. (Although using subversion with Fedora 9, it also worked.)

Actually, at first glance I hadn't realized it's only a half second. Of course, since seeing this, I can't get 1.6 to NOT work--that is, the problem was always sporadic, so I wanted to get it booting, not being able to network, then try your patch. I'm too lazy to redo the whole patch for Fedora, I was planning to just stick in the .5 delay.

Regardless, thanks very much for it.

Ok, unfortunately, it wasn't consistant for me. What I did find is that without using that, host interface networking would work perhaps 1 out of 5 times. With that sleep .5 host interface networking worked about 4 out of 5 times. So, definitely an improvement, but at least with Fedora and CentOS, apparently not a complete fix.

Thank you again.

davidv00 wrote:Updated the same topic mentioned above, wireless networking does not support bridging. I guess no luck for this moment unless in the near future either wireless spec supports bridging or linux kernel have some special feature.

You are right. I could not get my Vbox working until I changed back to NAT.

bridged networking script of 1.6.2 totally not working with opensuse10.3

the fix mentioned above helps.

My configuration:
openSUSE 10.3
VirtualBox 1.6 i586

All I had to do was put the 'sleep .5' (without quotes) just below the
ifconfig "$1" up 2> /dev/null
line in the /etc/init.d/vboxnet script and restart the box & my virtual Win2K.

AWESOME!! Thanks again madworm!

sorry guys, I have the same problem here:
OpenSuSE 10.3
Vbox 1.6.2_31466_openSUSE103-1.i586

I was wondering if the setup script is executed by the vbox program, so that I put following line in a early part of my startup script:
echo $* > /tmp/1

then I remove the file /tmp/1 before double clicking on the virtual machine's icon. However I have the same problem shown as above, and the file /tmp/1 was not created at all.

anybody out there can help?
thanks in advance.

p.s.
i found another topic which is very close to my problem after i posted the question:
http://forums.virtualbox.org/viewtopic.php?t=933
however, it dosen't help me much since the script was still not running.

virtualbox.org

Host interface net mode not work on OPenSuse 10.3

Host interface net mode not work on OPenSuse 10.3

Re: Host interface net mode not work on OPenSuse 10.3

The patch works great!