Tuesday, April 19, 2016

2016-04-19 Tuesday - VirtualBox Host-Only Ethernet Adapter Problem

2016-04-19 3:35pm Update:
Uninstalling 5.0.16, rebooting, and doing a clean install of 5.0.18 appears to have resolved my issue.

I'm researching an issue setting up a VirtualBox Host-Only Ethernet Adapter in a Mint 17.3 Linux Guest OS (on Windows 10). Note: I have successfully configured this in a prior version (4.3.x) of VirtualBox.

You can see the error below.

I've been using VirtualBox 5.0.16 - but will uninstall and upgrade to the latest (5.0.18) today.

It is worth noting that I do have a Host-Only Ethernet Adapter installed - and Windows reports that the driver is up-to-date (confirmed, after I removed the device, and had it re-install the drivers). However, it appears that there is no entry in the Properties list for a Host-Only Ethernet Adapter connection item.

A number of posts have described a similar problem - going back to several prior releases of VirtualBox.

Helpful References:

Some conjectures on how this problem might arise:
  • Not properly shutting down a Guest OS before upgrading to a new version of VirtualBox
  • Not doing a clean uninstall of VirtualBox before upgrading
  • Not physically deleting the left-over contents of the VirtualBox directory after an uninstall
  • A default Windows setting of [8] in the Windows Registry Key for MaxNumFilters
  • Possibly needing to specify this as a parameter when installing some older release of VirtualBox? 
    • -msiparams NETWORKTYPE=NDIS6
  • Not running the Windows MSI installer as Admin?
  • ...?

Error Encountered..

Failed to open/create the internal network 'HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter' (VERR_SUPDRV_COMPONENT_NOT_FOUND).
Failed to attach the network LUN (VERR_SUPDRV_COMPONENT_NOT_FOUND).

Result Code:
E_FAIL (0x80004005)
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

No comments: