Failed to open Virtual Box when use Bridged Adapter

[Dezmont]

Hello. Some days ago all worked perfectly. Yesterday i reinstalled Windows 7 SP1 at host. Installed last version of VirtualBox and tried to open guest Windows XP. The following error appears in front of me again and again:

Code: Select all

Failed to open a session for the virtual machine Windows XP.

Failed to open/create the internal network 'HostInterfaceNetworking-ASUS USB-N13 300Mbps 11n Wireless USB dongle' (VERR_INTNET_FLT_IF_NOT_FOUND).

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

I tried with older versions of VirtualBox, rebuild machine - but nothing helps me. Maybe anyone know solution for my problem?
Thank you.

*On another PC it works, but I can not understand why.

[Perryg]

The guest is looking for an "ASUS USB-N13 300Mbps 11n Wireless USB dongle" but does not see it. Was the guest shut down ( not saved state )?

[Dezmont]

The guest is looking for an "ASUS USB-N13 300Mbps 11n Wireless USB dongle" but does not see it. Was the guest shut down ( not saved state )?

Was the guest shut down ( not saved state )?

Yes. The Guest is shut down.
I see the next rows in the LOG:

Code: Select all

00:00:01.426172 VMSetError: F:\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:01.426188 VMSetError: Failed to open/create the internal network 'HostInterfaceNetworking-ASUS USB-N13 300Mbps 11n Wireless USB dongle'
00:00:01.426211 PDM: Failed to construct 'pcnet'/0! VERR_INTNET_FLT_IF_NOT_FOUND (-3600) - The networking interface to filter was not found.
00:00:01.435018 ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={8ab7c520-2442-4b66-8d74-4ff1e195d2b6} aComponent={Console} aText={Failed to open/create the internal network 'HostInterfaceNetworking-ASUS USB-N13 300Mbps 11n Wireless USB dongle' (VERR_INTNET_FLT_IF_NOT_FOUND)}, preserve=false
00:00:01.439219 Power up failed (vrc=VERR_INTNET_FLT_IF_NOT_FOUND, rc=E_FAIL (0X80004005))
00:00:01.612745 UIMachineView::storeGuestSizeHint: Storing guest size-hint for screen 0 as 640x480

Google shows that maybe was a problem with vboxnetflt? Or it is not relevant to my situation?

[mpack]

Answer Perry's (implied) question and then we'll know. Does the named NIC exist?

If the named NIC still exists then the lack of a filter driver for it might be relevant, implying that you need to reinstall VBox using "Run as administrator".

[Dezmont]

ASUS USB-N13 300Mbps 11n Wireless USB dongle exists.
Reinstalled Virtual Box one more time using "Run as administrator" - it did not help. :/

[mpack]

"Did not help" is not very diagnostic. However I see that "VirtualBox Bridged Network Driver" is present, so the reinstall at least was successful.

If you have a saved state associated with this VM then you should delete it (right click then choose "Discard Saved State" - or the Russian equivalent).

[Dezmont]

I made a screenshot before reinstall. Now "VirtualBox Bridged Network Driver" is present too. Menu item "Discard Saved State" is non-active.
Maybe I could provide some useful data for you? Just tell me where to get them.

[Dezmont]

No more ideas how to overcome the error?

[mpack]

Not many. The error is telling me one thing, you are telling me another. The only other thing I can think of is to make sure that no other VMs (if you have any) are in a suspended state.

Other notes: I'd increase the VM RAM to 512MB, since your host can easily afford it, and unmount the setup CD ISO.

Does the VM boot if you choose NAT networking?

[Dezmont]

The solution was found. Thanks to cmatte.
Link.

[mpack]

Ah. You'd be very unlucky if the bridging filter driver was the victim of MAX_NUM_FILTERS, though in hindsight it's obviously possible - and to me it looks like that's what the other thread is all about too.

p.s. I'm not sure that cmatte really identified his own solution. He just deletes the current NIC config and lets plug and play rediscover the NIC. With luck the filters are stacked differently by plug and play (the VBox filter won't be in the last few). Until the next VBox update.