Page 1 of 1

Why was "Host Interface" removed in 2.2?

Posted: 13. Apr 2009, 16:03
by software
Hello,

Having the option of selecting the specific NIC in the "Host Interface" was a great option for me. I have more than one NIC and having different Guest selecting different NIC was a great thing when it was added. Now with 2.2.0, I am not able to select specific NIC's. Please bring back the selection of specific NIC's.

Re: Why was "Host Interface" removed in 2.2?

Posted: 13. Apr 2009, 16:08
by Sasquatch
It's not removed, it's renamed to Bridged. If you use Windows, repair the setup, that will bring the NIC choice back. A reboot might be needed after the repair.

Re: Why was "Host Interface" removed in 2.2?

Posted: 13. Apr 2009, 16:20
by software
Hello,

It is my understanding that once a NIC is assigned to a "Bridge", the NIC takes on the IP address of the Bridge. You can only assign one NIC to a Bridge. My NIC's are on different networks and that it what was so nice about selecting the specific NIC. If I have three NIC's, 192.168.3.x, 192.168.7.x, 193,145,12,x. How would I setup a "Bridge" for three guest to access the three NIC's?

Re: Why was "Host Interface" removed in 2.2?

Posted: 14. Apr 2009, 14:25
by Sasquatch
Please read the manual and check the settings. Your answer is there right in front of you. You just take a NIC to use, it's only called bridged, it doesn't create one.

Re: Why was "Host Interface" removed in 2.2?

Posted: 15. Apr 2009, 11:58
by Yuufo
Hi,

I am a former 2.1.4 user (Fedora 8 host and guest), using Host Interface Networking. I read here that this networking mode was renamed "Bridged network". I selected this bridged networking mode in the 2.2 interface. However after the 2.2 upgrade, I get the following error popup at VM startup :

Failed to start the virtual machine Fedora 8.
Failed to open/create the internal network 'HostInterfaceNetworking-eth0' (VERR_SUPDRV_INTERFACE_NOT_SUPPORTED).
Unknown error creating VM (VERR_SUPDRV_INTERFACE_NOT_SUPPORTED).

Details :
Result Code:
NS_ERROR_FAILURE (0x80004005)
Component: Console
Interface: IConsole {9511bc54-15ee-4ddf-808e-472aba03809c}

This error popup seems cryptic to me. Does anyone understand where the problem lies?

I enclose the result of /sbin/ifconfig on the host :
br0 Link encap:Ethernet HWaddr 00:1C:C0:7C:9D:57
inet adr:192.168.10.60 Bcast:192.168.10.255 Masque:255.255.255.0
adr inet6: fe80::21c:c0ff:fe7c:9d57/64 Scope:Lien
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:363022 errors:0 dropped:0 overruns:0 frame:0
TX packets:279106 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:0
RX bytes:328230289 (313.0 MiB) TX bytes:46380629 (44.2 MiB)

eth0 Link encap:Ethernet HWaddr 00:1C:C0:7C:9D:57
inet adr:192.168.10.60 Bcast:192.168.10.255 Masque:255.255.255.0
adr inet6: fe80::21c:c0ff:fe7c:9d57/64 Scope:Lien
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:363049 errors:0 dropped:0 overruns:0 frame:0
TX packets:279125 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:1000
RX bytes:333348708 (317.9 MiB) TX bytes:46481241 (44.3 MiB)
Interruption:17 Adresse de base:0x4000

lo Link encap:Boucle locale
inet adr:127.0.0.1 Masque:255.0.0.0
adr inet6: ::1/128 Scope:Hôte
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:9834 errors:0 dropped:0 overruns:0 frame:0
TX packets:9834 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:0
RX bytes:27773134 (26.4 MiB) TX bytes:27773134 (26.4 MiB)

Thanks,
Yuufo

Re: Why was "Host Interface" removed in 2.2?

Posted: 15. Apr 2009, 15:37
by frank
Yuufo wrote: Failed to start the virtual machine Fedora 8.
Failed to open/create the internal network 'HostInterfaceNetworking-eth0' (VERR_SUPDRV_INTERFACE_NOT_SUPPORTED).
Unknown error creating VM (VERR_SUPDRV_INTERFACE_NOT_SUPPORTED).
Yuufo
Hmm, that error message usually means that the vboxnetflt module was not properly loaded. Please can you do

Code: Select all

lsmod|grep vbox
on the host?

Re: Why was "Host Interface" removed in 2.2?

Posted: 15. Apr 2009, 15:45
by Yuufo
Thanks for your reply.
However I previously removed / reinstalled VirtualBox and my bug is no longer here...