virtualbox.org

After un-installing and re-installing VirtualBox, rebooting the host machine, and trying again; I can't get VMs to boot with a host-only networking adapter. Please help me identify what the problem is, and a resolution or a workaround.

Pertinent rows from one of the VMs' logs below:

00:00:04.648726 IntNet#0: szNetwork={HostInterfaceNetworking-Qualcomm Atheros AR5B93 Wireless Network Adapter} enmTrunkType=3 szTrunk={\DEVICE\{7275B19E-2CC9-4795-950F-9AFDC65C9415}} fFlags=0x8001 cbRecv=325632 cbSend=196608 fIgnoreConnectFailure=false
00:00:04.651752 IntNet#1: szNetwork={HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter} enmTrunkType=4 szTrunk={\DEVICE\{87985CFB-585B-443C-89E6-1E76D71415F4}} fFlags=0x8000 cbRecv=325632 cbSend=196608 fIgnoreConnectFailure=false
00:00:04.652603 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:04.652662 VMSetError: Failed to open/create the internal network 'HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter'
00:00:04.652846 VMSetError: D:\tinderbox\win-4.2\src\VBox\Devices\Network\DevVirtioNet.cpp(2147) int __cdecl vnetConstruct(struct PDMDEVINS *,int,struct CFGMNODE *); rc=VERR_INTNET_FLT_IF_NOT_FOUND
00:00:04.652861 VMSetError: Failed to attach the network LUN
00:00:04.652897 PDM: Failed to construct 'virtio-net'/1! VERR_INTNET_FLT_IF_NOT_FOUND (-3600) - The networking interface to filter was not found.
00:00:04.666210 AIOMgr: Preparing flush failed with VERR_NOT_SUPPORTED, disabling async flushes
00:00:04.839144 TxTimer stats (avg/min/max): 0 usec -1 usec 0 usec
00:00:04.847592 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:04.848173 Failed to attach the network LUN (VERR_INTNET_FLT_IF_NOT_FOUND)}, preserve=false
00:00:04.923710 Power up failed (vrc=VERR_INTNET_FLT_IF_NOT_FOUND, rc=E_FAIL (0X80004005))

What does VBoxManage list hostonlyifs report?

Note: you must be in the folder that has VBoxManage.exe to use the command.

Microsoft Windows [Version 6.2.9200]

C:\Program Files\Oracle\VirtualBox>VBoxManage list hostonlyifs

Name: VirtualBox Host-Only Ethernet Adapter
GUID: 79634597-9830-406b-bf77-9283b69e5433
DHCP: Disabled
IPAddress: 192.168.56.1
NetworkMask: 255.255.255.0
IPV6Address: fe80:0000:0000:0000:74c03ecb:2a93
IPV6NetworkMaskPrefixLength: 64
HardwareAddress: 08:00:27:00:30:65
MediumType: Ethernet
Status: Up
VBoxNetworkName: HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter

Name: VirtualBox Host-Only Ethernet Adapter
GUID: 87985cfb-585b-443c-89e6-1e76d71415f4
DHCP: Disabled
IPAddress: 0.0.0.0
NetworkMask: 0.0.0.0
IPV6Address:
IPV6NetworkMaskPrefixLength: 0
HardwareAddress: 00:00:00:00:00:00
MediumType: Unknown
Status: Unknown
VBoxNetworkName: HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter

Thank you for the quick reply perryg! It appears as though an empty/unconfigured host-only adapter remained stuck in the host; even after VirtualBox was un-installed. Am I correct in diagnosing this as the issue? If so, how could I get rid of it?

Look in the VirtualBox preference -> network section and see if you have two entries. If so delete the one that is bad.

Perryg wrote:Look in the VirtualBox preference -> network section and see if you have two entries. If so delete the one that is bad.

deleted one (unconfigured), saved, closed pref. and found that the other network adapter disappeared. Added new adapter through VirtualBox preference --> network section, configured dhcp, machine failed with reason:

---
Failed to open a session for the virtual machine Ubuntu Server Researcher 2.

Failed to open/create the internal network 'HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter' (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 {db7ab4ca-2a3f-4183-9243-c1208da92392}
---

checked preferences & found that both (the rogue unconfigured & the configured network adapter) had come back

This seems to come up from time to time on a Windows host. I am not sure why but it appears that if you delete them both (in the preference). close the VirtualBox manager and wait 30 seconds or so and then add one back and set it up. Then save, close the manager and reboot the Windows host it usually fixes the issue.

Perryg wrote:This seems to come up from time to time on a Windows host. I am not sure why but it appears that if you delete them both (in the preference). close the VirtualBox manager and wait 30 seconds or so and then add one back and set it up. Then save, close the manager and reboot the Windows host it usually fixes the issue.

Done as requested, power-cycled host after 30 sec wait post interface delete to ensure full removal. Attempted to boot guest after save, close, and reboot host; VM failed with:

---
Failed to open a session for the virtual machine Ubuntu Server Researcher 2.

Failed to open/create the internal network 'HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter' (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 {db7ab4ca-2a3f-4183-9243-c1208da92392}
---

Is there anything else I can provide that will help troubleshoot this?

Does VBoxManage list hostonlyifs still show two?

It does:

Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.

C:\Program Files\Oracle\VirtualBox>VBoxManage list hostonlyifs
Name: VirtualBox Host-Only Ethernet Adapter
GUID: 1b6ad744-a93a-46ec-b91c-6f09e03fb55d
DHCP: Disabled
IPAddress: 192.168.190.1
NetworkMask: 255.255.255.0
IPV6Address: fe80:0000:0000:0000:b951:c5c4:602d:f4dc
IPV6NetworkMaskPrefixLength: 64
HardwareAddress: 08:00:27:00:dc:e6
MediumType: Ethernet
Status: Up
VBoxNetworkName: HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter

Name: VirtualBox Host-Only Ethernet Adapter
GUID: 87985cfb-585b-443c-89e6-1e76d71415f4
DHCP: Disabled
IPAddress: 0.0.0.0
NetworkMask: 0.0.0.0
IPV6Address:
IPV6NetworkMaskPrefixLength: 0
HardwareAddress: 00:00:00:00:00:00
MediumType: Unknown
Status: Unknown
VBoxNetworkName: HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter

Probably the least destructive course of action is to uninstall VirtualBox, reboot the host, then install it again. There has to be something in the registry that is carrying this extra baggage around. Your guest should remain intact and available.

Perryg wrote:Probably the least destructive course of action is to uninstall VirtualBox, reboot the host, then install it again. There has to be something in the registry that is carrying this extra baggage around. Your guest should remain intact and available.

Un-installed and power cycled, as requested. Installed using VirtualBox-4.2.10-84105-Win.exe (MD5 Hash: 3220F0038C402F30F3E85AFC7247B166), guest fails with:

---
Failed to open a session for the virtual machine Ubuntu Server Researcher 2.

Failed to open/create the internal network 'HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter' (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 {db7ab4ca-2a3f-4183-9243-c1208da92392}
---

I'm open to any solution or workaround at this point, regardless of how intrusive and/or destructive.

I've seen other solutions that call for simply removing any network interface for the guest, boot with no network, shutdown guest, add a bridged or NAT'ed network, then boot; however, this is not an option for me. I need a closed, controlled environment to set up a three host lab in which no VMs have communication with my LAN outside of the virtual network. The host-only adapter is the only solution I have found for creating this type of environment, so I simply must have a resolution or workaround to this issue.

You need to remove the host-only from the Windows network. Depending on how comfortable you are with that once removed then look in the VBox preference network and try adding a host-only from there. This may require a reboot (not certain)

Perryg wrote:You need to remove the host-only from the Windows network. Depending on how comfortable you are with that once removed then look in the VBox preference network and try adding a host-only from there. This may require a reboot (not certain)

I checked, un-installing VirtualBox appeared to also remove the VirtualBox adapter from the Windows side. I'll un-install VirtualBox, reboot, verify the Windows networking adapters (with screenshot) and attempt to re-add the host-only adapter manually (comfort level - cake walk). Will post back with results.