Nonexistent host networking interface

[georgeby]

The following error message is displayed when restoring a VM from a Saved state:

Failed to open a session for the virtual machine [VM NAME].

Nonexistent host networking interface, name 'Atheros AR8131 PCI-E Gigabit Ethernet Controller (NDIS 6.20) #2' (VERR_INTERNAL_ERROR).

Result Code: E_FAIL (0x80004005)
Component: Console
Interface: IConsole {db7ab4ca-2a3f-4183-9243-c1208da92392}

This occurs when the following is performed:

1. VM is running fine, and in Bridged networking mode connected to the LAN network interface. This interface is connected to a wireless router
2. The VM state is saved
3. Host is put to sleep
4. Wireless router is unplugged
5. Host is woken up
6. A different network device, in this case a network hub is plugged into the LAN
7. The VM is started again, and the error appears

The workaround is to delete the savestate and start the VM again.

For interest, the VM is Windows 2012 with 8GB RAM, 2 CPUs and apart from Shared Folders there is nothing fancy configured.

This behaviour does occur for all OSs and configurations.

I would assume this has something to do with when a network interface is disabled and enabled again, it adds "#2", "#3" next to it. Note, though that no setting in the Host (in Windows 7) shows that the network interface has been renamed, this appears to be the internal NIC name.

[georgeby]

VBox log file

[oakley99]

Host Windows 7 VM CentOS6.5

I've received the same error while performing similar functions and have a temporary work around:

1. Bridged Adapter Intel Centrino Advanced-N 6200 AGN connected to wireless adapter
2. Close VM and shutdown Host
3. Go to work - connect Host via eth0 (Ethernet) instead of eth1 (wireless)

Error occurs as described above: Nonexistent host networking interface, name 'Intel Centrino Advanced-N 6200 AGN' (VERR_INTERNAL_ERROR).

Result Code: E_FAIL (0x80004005) Component: Console Interface: IConsole

Work around:

1. Disconnect Host eth0 (Ethernet) and allow eth1 (wireless) to activate
2. Power up VM without network connectivity
3. Reconnect Host eth0
4. Update VirtualBox VM Network setting to: NAT (leaving defaults - Adapter Type: Intel PRO 1000 MT Desktop (82540 EM), Promiscuous Mode: Deny, Cable Connected: Checked)
5. Select OK

Wait a few seconds and my VM will connect to the network.

I will have to go through this again once I return home/connect to a wireless network via the host.

[muneer]

I've had a similar issue when trying to resume a VM (that has a saved state) where the wireless network adapter is no longer present.

The workarounds above did not work for me -- what did help was to edit the *.VBOX file manually and replacing the BridgedInterface value from the previous invalid network interface name to a network device that is present e.g. changing from this:

<BridgedInterface name="Linksys AE1000"/>

to this:

<BridgedInterface name="Intel(R) 82579LM Gigabit Network Connection"/>

Hope this helps someone else.