virtualbox.org

Hi,
I was using:
VirtualBox version: 4.2.x
Host: Windows 8.1 x64
Guest: Ubuntu Server
I accepted to upgrade to 4.3.4 r91027. Everything went alright, except when I try to open my VM, this is what I get:

Code: Select all

Failed to open/create the internal network 'HostInterfaceNetworking-Controller Gigabit Ethernet PCI-E Marvell Yukon 88E8056' (VERR_INTNET_FLT_IF_NOT_FOUND).
Exit code: E_FAIL (0x80004005)
Component: Console
Interface: IConsole {8ab7c520-2442-4b66-8d74-4ff1e195d2b6}

The machine is configured with a nic1 bridged with my (only) mentioned network controller by Marvell. Its drivers are updated, 12.10.13.3, source is Microsoft, 11/4/13: the downloadable drivers from Marvell are older and with lower version number. The internal network card kind of the VM is PCnet-PCI II (Am79C970A), not promiscuous, but I don't think this is influencing, changing this doesn't work.
I tried many things: search in the forum; bugtracker; google; a way to reset the configuration card of the VM by command line; complete uninstall, reboot and reinstall; tried to export virtual application, uninstall, reinstall, re-import (deleting configuration files before doing this (.vbox)); completely removed any network driver found in devices manager, uninstall, reinstall. None of them worked.

My devices manager screenshot is attached (shot.jpg):

: shot.jpg: devices manager and networking; shot.jpg (118.07 KiB) Viewed 8089 times

ipconfig /all gives:

Configurazione IP di Windows

Nome host . . . . . . . . . . . . . . : Home-PC
Suffisso DNS primario . . . . . . . . :
Tipo nodo . . . . . . . . . . . . . . : Ibrido
Routing IP abilitato. . . . . . . . . : No
Proxy WINS abilitato . . . . . . . . : No
Elenco di ricerca suffissi DNS. . . . : MYGRP

Scheda Ethernet Ethernet:

Suffisso DNS specifico per connessione: MYGRP
Descrizione . . . . . . . . . . . . . : Controller Gigabit Ethernet PCI-E Marvell Yukon 88E8056
Indirizzo fisico. . . . . . . . . . . : 00-**-**-**-**-*6
DHCP abilitato. . . . . . . . . . . . : S
Configurazione automatica abilitata : S
Indirizzo IPv6 . . . . . . . . . . . . . . . . . : ****:***:****:****::****:f1f8(Preferenziale)
Lease ottenuto. . . . . . . . . . . . : domenica 15 dicembre 2013 11.08.34
Scadenza lease . . . . . . . . . . . : domenica 15 dicembre 2013 23.08.33
Indirizzo IPv6 . . . . . . . . . . . . . . . . . : ****:***:****:****:****:****:****:78f4(Preferenziale)
Indirizzo IPv6 temporaneo. . . . . . . . . . . . : ****:***:****:****:****:****:****:262b(Preferenziale)
Indirizzo IPv6 locale rispetto al collegamento . : ****::****:****:****:78f4%56(Preferenziale)
Indirizzo IPv4. . . . . . . . . . . . : 192.168.3.100(Preferenziale)
Subnet mask . . . . . . . . . . . . . : 255.255.255.0
Lease ottenuto. . . . . . . . . . . . : domenica 15 dicembre 2013 11.08.34
Scadenza lease . . . . . . . . . . . : mercoled 21 gennaio 2150 18.39.37
Gateway predefinito . . . . . . . . . : ****::****:****:****:35bd%56
192.168.3.1
Server DHCP . . . . . . . . . . . . . : 192.168.3.1
IAID DHCPv6 . . . . . . . . . . . : *******30
DUID Client DHCPv6. . . . . . . . : 00-01-00-01-18-1C-91-A5-00-**-**-**-**-*6
Server DNS . . . . . . . . . . . . . : ****:***:****:****::1
192.168.3.1
Server WINS primario . . . . . . . . : 192.168.3.1
NetBIOS su TCP/IP . . . . . . . . . . : Attivato

Scheda Ethernet VirtualBox Host-Only Network:

Suffisso DNS specifico per connessione:
Descrizione . . . . . . . . . . . . . : VirtualBox Host-Only Ethernet Adapter
Indirizzo fisico. . . . . . . . . . . : **-**-**-**-**-1D
DHCP abilitato. . . . . . . . . . . . : No
Configurazione automatica abilitata : S
Indirizzo IPv6 locale rispetto al collegamento . : ****::****:****:****:ef49%145(Preferenziale)
Indirizzo IPv4. . . . . . . . . . . . : 192.168.56.1(Preferenziale)
Subnet mask . . . . . . . . . . . . . : 255.255.255.0
Gateway predefinito . . . . . . . . . :
IAID DHCPv6 . . . . . . . . . . . : -********49
DUID Client DHCPv6. . . . . . . . : 00-01-00-01-18-1C-91-A5-00-**-**-**-**-*6
Server DNS . . . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS su TCP/IP . . . . . . . . . . : Attivato

Scheda Tunnel isatap.{5A23667C-7BF9-43F8-965F-F04214E59C0B}:

Stato supporto. . . . . . . . . . . . : Supporto disconnesso
Suffisso DNS specifico per connessione:
Descrizione . . . . . . . . . . . . . : Microsoft ISATAP Adapter
Indirizzo fisico. . . . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP abilitato. . . . . . . . . . . . : No
Configurazione automatica abilitata : S

Scheda Tunnel isatap.MYGRP:

Stato supporto. . . . . . . . . . . . : Supporto disconnesso
Suffisso DNS specifico per connessione: MYGRP
Descrizione . . . . . . . . . . . . . : Microsoft ISATAP Adapter #3
Indirizzo fisico. . . . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP abilitato. . . . . . . . . . . . : No
Configurazione automatica abilitata : S

VM log lines:

00:00:02.457095 IntNet#0: szNetwork={HostInterfaceNetworking-Controller Gigabit Ethernet PCI-E Marvell Yukon 88E8056} enmTrunkType=3 szTrunk={\DEVICE\{BE6170BD-0694-41F6-94E9-557FEEE799DE}} fFlags=0x8000 cbRecv=325632 cbSend=196608 fIgnoreConnectFailure=false
00:00:02.457178 VMSetError: D:\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:02.457208 VMSetError: Failed to open/create the internal network 'HostInterfaceNetworking-Controller Gigabit Ethernet PCI-E Marvell Yukon 88E8056'
00:00:02.457250 PDM: Failed to construct 'pcnet'/0! VERR_INTNET_FLT_IF_NOT_FOUND (-3600) - The networking interface to filter was not found.
00:00:02.655896 ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={8ab7c520-2442-4b66-8d74-4ff1e195d2b6} aComponent={Console} aText={Failed to open/create the internal network 'HostInterfaceNetworking-Controller Gigabit Ethernet PCI-E Marvell Yukon 88E8056' (VERR_INTNET_FLT_IF_NOT_FOUND)}, preserve=false
00:00:02.661810 Power up failed (vrc=VERR_INTNET_FLT_IF_NOT_FOUND, rc=E_FAIL (0X80004005))

p.s. not sure if it is relevant but that D:\tinderbox\.. etc does not exist.

Do you have any idea on what's going on? I'm out of bullets

Thank you.
Regards,
Matteo.

Seems like your network is very much screwed up. Whatever happened is very nasty and I doubt it is Virtualbox which did it.

All these interfaces are suspiscious to me and should be removed, unless you know what they are for :
2x Miniport
2x ISATAP
2x NDIS
Terdo Tunneling

then uninstall Virtualbox, reboot, install Virtualbox again with admin priviledges, reboot.

Thanks for your answer. I would like to add that these interfaces are shown due to I activated "show hidden devices" under the "View" menu of devices manager. I'm not sure when/why they have been installed but I see ISATAP and Teredo use Microsoft-made drivers, both signed-by and made-by, even in their files, and are also automatically reinstalled as soon as I uninstall them. The others are gone OK now. It could also be these two are needed by Kaspersky antivirus/firewall. Or by my previous implementation of IPv6. Also, doing a little research, I can read here and there that it is quite normal for Windows to auto-install them. They are actually hidden without the "show hidden devices" checkbox activated, except the Marvell (and VirtualBox) drivers.

I will be back to you as soon as I can try to go on, reboot, and re-install VirtualBox again to see if the problem is fixed.

Thank you.

Hi, I tried doing the removal, reboot, re-install cycle. VirtualBox re-installed the host-only adapter, another ISATAP appeared, and also two miniport driver(s) have been installed, linked to the Marvell actual network card. I don't really know if/why they should be two...or just one...

Anyway, VirtualBox behaves the same way:

Failed to open/create the internal network 'HostInterfaceNetworking-Controller Gigabit Ethernet PCI-E Marvell Yukon 88E8056' (VERR_INTNET_FLT_IF_NOT_FOUND).

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

The VM's log reports this:

00:00:02.040544 IntNet#0: szNetwork={HostInterfaceNetworking-Controller Gigabit Ethernet PCI-E Marvell Yukon 88E8056} enmTrunkType=3 szTrunk={\DEVICE\{BE6170BD-0694-41F6-94E9-557FEEE799DE}} fFlags=0x8000 cbRecv=325632 cbSend=196608 fIgnoreConnectFailure=false
00:00:02.040614 VMSetError: D:\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:02.040708 VMSetError: Failed to open/create the internal network 'HostInterfaceNetworking-Controller Gigabit Ethernet PCI-E Marvell Yukon 88E8056'
00:00:02.040769 PDM: Failed to construct 'pcnet'/0! VERR_INTNET_FLT_IF_NOT_FOUND (-3600) - The networking interface to filter was not found.
00:00:02.237702 ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={8ab7c520-2442-4b66-8d74-4ff1e195d2b6} aComponent={Console} aText={Failed to open/create the internal network 'HostInterfaceNetworking-Controller Gigabit Ethernet PCI-E Marvell Yukon 88E8056' (VERR_INTNET_FLT_IF_NOT_FOUND)}, preserve=false
00:00:02.241753 Power up failed (vrc=VERR_INTNET_FLT_IF_NOT_FOUND, rc=E_FAIL (0X80004005))

which seems the same as before.

I went through many troubleshootings and obtained nothing. Reset winsock / network on Windows in any kind, re-installing antivirus/firewall, drivers, and so on. No way.

I came to a resolution using system restore to a previous version. VirtualBox started working fine again then, in its old version installed at that time. PC is OK too.
BUT, here comes the but, I tried to upgrade it again. Problem is there again

It's evident VirtualBox installation is what causes all the network problems so.

What if you totally disable the antivirus/firewall before doing anything with Virtualbox, and keep it disabled until you try to start a VM and see if it works?

Hi,
disabling the AV doesn't help at all.
Untill today I stayed with the old version.
Today I tried to upgrade again to 4.3.6. Still the same exact problem: VMs are unusable.

Check that Windows doesn't silently refuse device installation due to non-signed driver

Which drivers should I check for? I would like to use only the bridged mode. Other modes work (host only for example, which has a driver installed)

Thanks.

Any driver, it's a limitation of Windows 8 to block installation of non-signed drivers. Bridged mode require the additions of a filter on the NIC, so you could be impacted.

Does this mean Virtual Box has no drivers correctly signed and recognised by the 64bit system's driver signature enforcement?
I'm quite confused. I mean, if the host-only driver is there, for which reason other companions, ie the filter driver, should be blocked? How to check if that's the case?

Thank you!

It's more a mix of some drivers/installers not being signed, the stupid new security system in Windows and the UAT prompts issue.
a Dev could give more the exact details here, but on the forum we always see issues with this due to Windows silent enforcement and UAT.

Was this VM moved from another host? I ask since I think you get an error message similar to that when a particular VM is configured to bridge to a particular named network card - and it doesn't exist. You may not be able to fix this in the GUI, since it has a nasty habit of complaining about things when you try to run the VM which it hides when you try to edit the VM settings.

Perhaps the simplest thing is: zip up the .vbox file and post it here.

This is the same machine. But, wait, the error just changed, after the upgrade, and I didn't notice. It's still complaining about the network card not found, but in particular now it says:

Unable to open a session for the Virtual Machine MyGO_1.

Failed to open/create the internal network 'HostInterfaceNetworking-Controller Gigabit Ethernet PCI-E Marvell Yukon 88E8056' (VERR_SUPDRV_COMPONENT_NOT_FOUND).

Failed to attach the network LUN (VERR_SUPDRV_COMPONENT_NOT_FOUND).

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

I translated manually the Italian parts (forst message and exit code..till the end) for making it understandable. The controller is there and has that exact name.

I tried to delete the VM and create it again (new .vbox) but the issue is still present, and the machine works with the network as host-only.
Also brand new machines do have the same problem.

Thank you.
Matteo.

If the host network card "Gigabit Ethernet PCI-E Marvell Yukon 88E8056" definitely exists then the other possibility is a bad installation - this is particularly common on Win8-64 hosts because of Driver Signature Enforcement - Google for info. Win8-64 defaults to silently rejecting installation of drivers when it doesn't like the certification.

You need to make sure that Driver Signature Enforcement is set to at least prompt you if the Windows installer is asked to install a device driver. This is in addition to making sure that you "Run as admininstator" when installing VirtualBox for the correct user.

Uninstall VirtualBox completely before you try again - including deleting the "Program Files/Oracle/VirtualBox" folder.

virtualbox.org

Stuck at VERR_INTNET_FLT_IF_NOT_FOUND

Stuck at VERR_INTNET_FLT_IF_NOT_FOUND

Re: Stuck at VERR_INTNET_FLT_IF_NOT_FOUND

Re: Stuck at VERR_INTNET_FLT_IF_NOT_FOUND

Re: Stuck at VERR_INTNET_FLT_IF_NOT_FOUND

Re: Stuck at VERR_INTNET_FLT_IF_NOT_FOUND

Re: Stuck at VERR_INTNET_FLT_IF_NOT_FOUND

Re: Stuck at VERR_INTNET_FLT_IF_NOT_FOUND

Re: Stuck at VERR_INTNET_FLT_IF_NOT_FOUND

Re: Stuck at VERR_INTNET_FLT_IF_NOT_FOUND

Re: Stuck at VERR_INTNET_FLT_IF_NOT_FOUND

Re: Stuck at VERR_INTNET_FLT_IF_NOT_FOUND

Re: Stuck at VERR_INTNET_FLT_IF_NOT_FOUND

Re: Stuck at VERR_INTNET_FLT_IF_NOT_FOUND

Re: Stuck at VERR_INTNET_FLT_IF_NOT_FOUND

Re: Stuck at VERR_INTNET_FLT_IF_NOT_FOUND