VirtualBox: Failed to open/create the internal network 'HostInterfaceNetworking-en0' (VERR_SUPDRV_COMPONENT_NOT_FOUND)

Oh Dear monitors your entire site, not just the homepage. We crawl and search for broken pages and mixed content, send alerts when your site is down and notify you on expiring SSL certificates.

Start your free 10 day trial! »

Profile image of Mattias Geniar

Mattias Geniar, November 27, 2019

Follow me on Twitter as @mattiasgeniar

There’s an annoying little bug in VirtualBox that can cause your network config in the VM to become invalid after a reboot of your host Mac.

Error message: Failed to open/create the internal network ‘HostInterfaceNetworking-en0’

The error is like this:

Failed to open/create the internal network 'HostInterfaceNetworking-en0'

Failed to open/create internal network

The fix in my case wasn’t to change any of the settings in Virtualbox.

Here’s what was happening on my machine: the VM that needed to boot was a PiHole DNS server. It’s our home DNS server. It has IP

My DHCP is distributing that DNS server to all clients. Including my host mac. Bit of a chicken/egg issue there.

It looks like VirtualBox (or Mac, I’m not sure) tries to validate the network settings before setting up a bridge on the network. It tries to validate that IP address is a valid nameserver that can respond to queries.

But since the VM isn’t booted, that IP is offline …

Mac OS network settings

My fix was to configure a static IP for my DNS server on the host Mac, something like Google’s After I changed that, my problem magically went away and the VM can boot without error message.

Downside: my host Mac is no longer protected via the PiHole …

Want to subscribe to the cron.weekly newsletter?

I write a weekly-ish newsletter on Linux, open source & webdevelopment called cron.weekly.

It features the latest news, guides & tutorials and new open source projects. You can sign up via email below.

No spam. Just some good, practical Linux & open source content.