id,summary,reporter,owner,description,type,status,component,version,resolution,keywords,cc,guest,host 11371,Host-only networking not working on Windows 8 host,vnicolici,,"Windows 8 64 bit host, VMs refuse to start after I add a network adapter mapped to a host-only network. Bridged and NAT work fine. Relevant section from the log: {{{ 00:00:03.203210 IntNet#0: szNetwork={HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter} enmTrunkType=4 szTrunk={\DEVICE\{6C789649-F840-44A4-945E-D378B238FCFB}} fFlags=0x8000 cbRecv=325632 cbSend=196608 fIgnoreConnectFailure=false 00:00:03.203266 VMSetError: D:\tinderbox\win-4.2\src\VBox\Devices\Network\DrvIntNet.cpp(1718) int __cdecl drvR3IntNetConstruct(struct PDMDRVINS *,struct CFGMNODE *,unsigned int); rc=VERR_INTNET_FLT_IF_NOT_FOUND 00:00:03.203282 VMSetError: Failed to open/create the internal network 'HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter' 00:00:03.203336 VMSetError: D:\tinderbox\win-4.2\src\VBox\Devices\Network\DevE1000.cpp(7680) int __cdecl e1kConstruct(struct PDMDEVINS *,int,struct CFGMNODE *); rc=VERR_INTNET_FLT_IF_NOT_FOUND 00:00:03.203340 VMSetError: Failed to attach the network LUN 00:00:03.203351 PDM: Failed to construct 'e1000'/1! VERR_INTNET_FLT_IF_NOT_FOUND (-3600) - The networking interface to filter was not found. 00:00:03.206982 AIOMgr: Preparing flush failed with VERR_NOT_SUPPORTED, disabling async flushes 00:00:03.249384 NAT: zone(nm:mbuf_cluster, used:0) 00:00:03.250144 NAT: zone(nm:mbuf_packet, used:0) 00:00:03.250155 NAT: zone(nm:mbuf, used:0) 00:00:03.250303 NAT: zone(nm:mbuf_jumbo_pagesize, used:0) 00:00:03.250960 NAT: zone(nm:mbuf_jumbo_9k, used:0) 00:00:03.251297 NAT: zone(nm:mbuf_jumbo_16k, used:0) 00:00:03.251480 NAT: zone(nm:mbuf_ext_refcnt, used:0) 00:00:03.380627 ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={db7ab4ca-2a3f-4183-9243-c1208da92392} aComponent={Console} aText={Failed to open/create the internal network 'HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter' (VERR_INTNET_FLT_IF_NOT_FOUND). 00:00:03.380668 Failed to attach the network LUN (VERR_INTNET_FLT_IF_NOT_FOUND)}, preserve=false 00:00:03.473543 Power up failed (vrc=VERR_INTNET_FLT_IF_NOT_FOUND, rc=E_FAIL (0X80004005)) }}} and the relevant section from ipconfig showing that the host-only network adapter on the host exists: {{{ Ethernet adapter VirtualBox Host-Only Network: Connection-specific DNS Suffix . : Link-local IPv6 Address . . . . . : fe80::59fb:fbe:619f:1ed8%60 IPv4 Address. . . . . . . . . . . : 192.168.1.200 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : }}} Other issues: - the configuration dialog for host-only networking shows two host-only network adapters instead of one after you reopen the dialog. Deleting one of them deletes both (if you try to delete both it complains that the second one doesn't exist after you delete the first one). - I can only set the correct IP address for the adapter from the Windows network configuration UI, changing the IP from the VirtualBox UI assigns a different IP from the one selected (for example 169.254.0.55 instead of the 192.168.1.200 I specified). - random errors that it cannot rename the network adapter when managing the host-only network. Attached the VM log and some screenshots.",defect,closed,network/hostif,VirtualBox 4.2.6,obsolete,host-only newtorking,,Linux,Windows