Virtual Machine won't launch if bridged network is selected

[sha31337]

Hi, I am trying to install Kali Linux amd64bit on my Windows 7 Professional 64bit Host machine. When i choose Bridged Adapter in adapter1 under Networking option then VirtualBox won't launch my VM and it throws this exception below.

Failed to open a session for the virtual machine Kali Linux.

Failed to open/create the internal network 'HostInterfaceNetworking-Intel(R) Dual Band Wireless-AC 3160' (VERR_INTNET_FLT_IF_NOT_FOUND).

Failed to attach the network LUN (VERR_INTNET_FLT_IF_NOT_FOUND).

Result Code: E_FAIL (0x80004005) Component: Console Interface: IConsole {8ab7c520-2442-4b66-8d74-4ff1e195d2b6}

When i choose NAT then my VM launches without any problem. I have Dell Inspiron 5000 Model:5547

I had discussed this on this forum and i couldn't get any answer and more than likely this is virtualbox bug. Below is the link to my forumn discussion on this problem. ​https://forums.virtualbox.org/viewtopic.php?f=6&t=63996

[sha31337]

Actual Error that i get when i try to launch my VM

[sha31337]

VirtualBox bridged network driver listed

[sha31337]

Network Connections

[sha31337]

Device Manager-->Network Adapters

[James McPherson]

tarfile containing vm config, VBox.log.* and VBoxStartup.log files

[James McPherson]

I have had this problem as well, with both 4.3.16 and 4.3.18 on a windows 7/64 host.

My hardware is a Toshiba Portege R700 with Intel 82577LM wired and Centrino 6200AGN wireless interfaces.

My error message from logs is :

00:00:04.419230 IntNet#0: szNetwork={HostInterfaceNetworking-Intel(R) 82577LM Gigabit Network Connection} enmTrunkType=3 szTrunk={\DEVICE\{27BDBA3E-78FF-466F-AD36-13ADD60060B3}} fFlags=0x14000 cbRecv=325632 cbSend=196608 fIgnoreConnectFailure=false
00:00:04.419301 VMSetError: C:\tinderbox\win-4.3\src\VBox\Devices\Network\DrvIntNet.cpp(1752) int __cdecl drvR3IntNetConstruct(struct PDMDRVINS *,struct CFGMNODE *,unsigned int); rc=VERR_INTNET_FLT_IF_NOT_FOUND
00:00:04.419336 VMSetError: Failed to open/create the internal network 'HostInterfaceNetworking-Intel(R) 82577LM Gigabit Network Connection'
00:00:04.419400 VMSetError: C:\tinderbox\win-4.3\src\VBox\Devices\Network\DevE1000.cpp(7693) int __cdecl e1kR3Construct(struct PDMDEVINS *,int,struct CFGMNODE *); rc=VERR_INTNET_FLT_IF_NOT_FOUND
00:00:04.419408 VMSetError: Failed to attach the network LUN
00:00:04.419438 PDM: Failed to construct 'e1000'/0! VERR_INTNET_FLT_IF_NOT_FOUND (-3600) - The networking interface to filter was not found.
00:00:04.427946 AIOMgr: Preparing flush failed with VERR_NOT_SUPPORTED, disabling async flushes
00:00:04.674978 ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={8ab7c520-2442-4b66-8d74-4ff1e195d2b6} aComponent={Console} aText={Failed to open/create the internal network 'HostInterfaceNetworking-Intel(R) 82577LM Gigabit Network Connection' (VERR_INTNET_FLT_IF_NOT_FOUND).
00:00:04.675034 Failed to attach the network LUN (VERR_INTNET_FLT_IF_NOT_FOUND)}, preserve=false
00:00:04.701819 Power up failed (vrc=VERR_INTNET_FLT_IF_NOT_FOUND, rc=E_FAIL (0X80004005))

I'm at a loss for how to proceed with this problem (Windows doesn't have DTrace :( ) so any and all suggestions from the VirtualBox team will be gratefully received and acted upon.

[James McPherson]

One other thing - while I normally only run a Solaris vm in this environment, for testing purposes I created a new 64bit linux vm config also using bridged mode. That resulted in the same errors I c+p'd above.

[Klaus Espenlaub]

This sounds like the necessary driver for bridged networking isn't installed. I assume you didn't deselect it explicitly, which means that it's some unknown install failure of that driver. Typically this can be resolved by uninstalling/reinstalling VirtualBox. If this doesn't help, we need an installer log to track down what's going wrong, see wiki:MSI_Logging.

Of course there are some rate cases where none of this helps, and this is the (extremely few) NIC drivers which somehow sabotage the correct insertion of the filter driver needed for bridging. This can be pinpointed by (just for testing purposes) bridging to a NIC using a different driver, which can be e.g. the Microsoft Loopback Adapter or a VirtualBox Host-Only Adapter. If this fails, too, it's not specific to the NIC, and only the above will help.

[James McPherson]

I tried using the MS Loopback instance for the bridge, but that failed in exactly the same way. Following the instructions in the wiki I've now got some setupapi logs for you - they are, unfortunately, too large to attach here. Please see ~jmcp/vbox/vbox-logging.tar.gz on the internal jurassic.us host for the files.

On perusing the setupapi logfiles, one thing which stood out was

     sto:                {DRIVERSTORE_IMPORT_NOTIFY_VALIDATE} 21:13:57.971
     inf:                     Opened INF: 'C:\Windows\System32\DriverStore\Temp\{5f18b58d-264a-3400-636a-550486e1a316}\VBoxNetFltM.inf' ([strings])
     sig:                     {_VERIFY_FILE_SIGNATURE} 21:13:57.981
     sig:                          Key      = VBoxNetFltM.inf
     sig:                          FilePath = C:\Windows\System32\DriverStore\Temp\{5f18b58d-264a-3400-636a-550486e1a316}\VBoxNetFltM.inf
     sig:                          Catalog  = C:\Windows\System32\DriverStore\Temp\{5f18b58d-264a-3400-636a-550486e1a316}\VBoxNetFlt.cat
!    sig:                          Verifying file against specific (valid) catalog failed! (0x800b0109)
!    sig:                          Error 0x800b0109: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.
     sig:                     {_VERIFY_FILE_SIGNATURE exit(0x800b0109)} 21:13:58.016
     sig:                     {_VERIFY_FILE_SIGNATURE} 21:13:58.017
     sig:                          Key      = VBoxNetFltM.inf
     sig:                          FilePath = C:\Windows\System32\DriverStore\Temp\{5f18b58d-264a-3400-636a-550486e1a316}\VBoxNetFltM.inf
     sig:                          Catalog  = C:\Windows\System32\DriverStore\Temp\{5f18b58d-264a-3400-636a-550486e1a316}\VBoxNetFlt.cat
     sig:                          Success: File is signed in Authenticode(tm) catalog.
     sig:                          Error 0xe0000241: The INF was signed with an Authenticode(tm) catalog from a trusted publisher.
     sig:                     {_VERIFY_FILE_SIGNATURE exit(0xe0000241)} 21:13:58.057
     sto:                     Driver package is valid.
     sto:                {DRIVERSTORE_IMPORT_NOTIFY_VALIDATE exit(0x00000000)} 21:13:58.058

There were quite a few instances of that set of messages relating to the root certificate.

[James McPherson]

I tried another remove/reinstall effort, but this time thought I should run the installation as Administrator.

Lo and behold! It (bridged networking) Worked!

[c0mputerguy72]

Same issue here. VirtualBox 4.3.20 r96997 on Win8.1 X64. Trying to install Kali X64 (Debian). I tried re-installing as Administrator. It did not fix the problem. This problem happens with all OS guests.

Failed to open a session for the virtual machine Kali.

Failed to open/create the internal network 'HostInterfaceNetworking-Intel(R) 82579LM Gigabit Network Connection' (VERR_INTNET_FLT_IF_NOT_FOUND).

Failed to attach the network LUN (VERR_INTNET_FLT_IF_NOT_FOUND).

Result Code: E_FAIL (0x80004005) Component: Console Interface: IConsole {8ab7c520-2442-4b66-8d74-4ff1e195d2b6}

[Frank Mehnert]

Did you uninstall VBox, reboot the host and then install VBox again? The installer log files should tell why the installation of the host drivers was not successful.

[c0mputerguy72]

Yes..it is broken.

[c0mputerguy72]

c0mputerguy72-VBoxInstallLog.txt

[c0mputerguy72]

c0mputerguy72-setupapi.app.log

[c0mputerguy72]

c0mputerguy72-setupapi.dev.log

[c0mputerguy72]

c0mputerguy72-setupapi.setup.log

[c0mputerguy72]

c0mputerguy72-setupapi.app.log

[c0mputerguy72]

I have attached my installer log files. I can't get the Bridged Network Adapter to install and subsequently work.

[Aleksey Ilyushin]

Could anyone confirm if the problem still persists in build 104592? If it is, please provide the output of 'VBoxManage list bridgedifs' and 'VBoxManage list hostonlyifs'.

[sempf]

104592 bridgedifs output

[sempf]

104592 hostonly output

[sempf]

I have confirmed that this error occurs in 104592, and have attached my log files as requested.

[Aleksey Ilyushin]

Please provide VBox.log from VM that fails with VERR_INTNET_FLT_IF_NOT_FOUND.

[sempf]

I have confirmed that this is a problem with a Windows 10 update. ​http://superuser.com/questions/1002160/failed-to-start-virtual-device-in-oracle-virtual-box/1002243#1002243

[lookmomnohands]

I still see this issue in version 5.0.16 r 105871 Win7 x64 host.

[lookmomnohands]

VBox.log requested

[Aleksey Ilyushin]

Please try test build 121161 or more recent from test builds page.