VERR_INTNET_FLT_IF_NOT_FOUND in Virtualbox 4.3.24r98716 on Ubuntu

[Onno]

On clean/new Ubuntu 14.04.1 LTS Virtualbox 4.3.24r98716 won't actually work because of network.

VM will fail to start all together

Message similar to

00:00:00.141768 PIIX3 ATA: Ctl#1: finished processing RESET
00:00:00.141982 IntNet#0: szNetwork={HostInterfaceNetworking-eth0} enmTrunkType=3 szTrunk={eth0} fFlags=0x8000 cbRecv=325632 cbSend=196608 fIgnoreConnectFailure=false
00:00:00.142065 VMSetError: /home/vbox/vbox-4.3.24/src/VBox/Devices/Network/DrvIntNet.cpp(1752) int drvR3IntNetConstruct(PPDMDRVINS, PCFGMNODE, uint32_t); rc=VERR_INTNET_FLT_IF_NOT_FOUND
00:00:00.142079 VMSetError: Failed to open/create the internal network 'HostInterfaceNetworking-eth0'
00:00:00.142141 VMSetError: /home/vbox/vbox-4.3.24/src/VBox/Devices/Network/DevE1000.cpp(7693) int e1kR3Construct(PPDMDEVINS, int, PCFGMNODE); rc=VERR_INTNET_FLT_IF_NOT_FOUND
00:00:00.142147 VMSetError: Failed to attach the network LUN
00:00:00.142166 PDM: Failed to construct 'e1000'/0! VERR_INTNET_FLT_IF_NOT_FOUND (-3600) - The networking interface to filter was not found.
00:00:00.147808 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={8ab7c520-2442-4b66-8d74-4ff1e195d2b6} aComponent={Console} aText={Failed to open/create the internal network 'HostInterfaceNetworking-eth0' (VERR_INTNET_FLT_IF_NOT_FOUND).
00:00:00.147817 Failed to attach the network LUN (VERR_INTNET_FLT_IF_NOT_FOUND)}, preserve=false
00:00:00.156261 Power up failed (vrc=VERR_INTNET_FLT_IF_NOT_FOUND, rc=NS_ERROR_FAILURE (0X80004005))

From quick Google search it seems this is a common problem/bug since VirtualBox 3 or earlier.

[Frank Mehnert]

Next time please use the 'Attach' button and attach the complete VBox.log file of such a VM session.

Regarding your problem: Are all VirtualBox host driver modules loaded, i.e. what is the output of

/sbin/lsmod | grep vbox

? Also, which Ethernet interfaces do exist on your host? Could you post the output of

/sbin/ifconfig

?

[Onno]

startvm btw will report success but the vm will not be running

$ VBoxManage startvm Chef --type headless
Waiting for VM "Chef" to power on...
VM "Chef" has been successfully started.

~$ /sbin/lsmod | grep vbox
vboxpci                23194  0 
vboxnetadp             25670  0 
vboxnetflt             27613  0 
vboxdrv               409935  4 vboxnetadp,vboxnetflt,vboxpci

$ /sbin/ifconfig
lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:16 errors:0 dropped:0 overruns:0 frame:0
          TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:1184 (1.1 KB)  TX bytes:1184 (1.1 KB)

p5p1      Link encap:Ethernet  HWaddr 10:c3:7b:6c:b3:09  
          inet addr:192.168.1.100  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::12c3:7bff:fe6c:b309/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:4317 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3315 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:4668976 (4.6 MB)  TX bytes:405838 (405.8 KB)

[Onno]

Noticing the p5p1 new network interface naming of Ubuntu I created a VM without network. I imported this ova and then I was able to start the VM success.

Of course there is no network so there is not a lot you can do it. So I tried to add the interface

$ VBoxManage modifyvm "Chef" --nic1 bridged --nictype1 Am79C973 --bridgeadapter1 p5p1

This time VM is running

[Onno]

In any case, VM is now starting but no network

It seems it is not possible to see the IP when doing bridged but I also don't see a new device on my router so my conclusion for now is that it is not working.

I see the nic info, it looks okay

NIC 1:           MAC: 08002799425C, Attachment: Bridged Interface 'p5p1', Cable connected: on, Trace: off (file: none), Type: Am79C973, Reported speed: 0 Mbps, Boot priority: 0, Promisc Policy: deny, Bandwidth group: none

[Frank Mehnert]

So it was the wrong network interface which prevented your VM from starting. What's the current problem? I don't understand what you mean by "it is not possible to see the IP when doing bridged". Does that mean that your guest does not get an IP assigned?

Also please attach a VBox.log file with the current VM.

[Valery Ushakov]

Please, reopen with more information if necessary.