Host only adapter cannot be configured when its name not is a standard eth* name

[ogarcia]

When you configure a Vagrantfile to set up a Host Only Adapter in a distro that not use standard eth names the "vagrant up" script stops and give an error.

The config line is:
config.vm.network "private_network", ip: "192.168.33.10"

And the output error:

==> default: Configuring and enabling network interfaces...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

ip link set eth1 down

Stdout from the command:

Stderr from the command:

Cannot find device "eth1"

The interface name in this case is enp0s8 not eth1.

If you wish, you can reproduce:
$ vagrant init ogarcia/archlinux-201408-x64
Edit Vagrantfile to add: config.vm.network "private_network", ip: "192.168.33.10"
$ vagrant up

[rockxsj]

I have get the same error on my Mac:
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Clearing any previously set forwarded ports...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
default: Adapter 2: hostonly
==> default: Forwarding ports...
default: 22 => 2222 (adapter 1)
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
default: SSH address: 127.0.0.1:2222
default: SSH username: vagrant
default: SSH auth method: private key
default: Warning: Connection timeout. Retrying...
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
==> default: Configuring and enabling network interfaces...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

ip link set eth1 down

Stdout from the command:

Stderr from the command:

Cannot find device "eth1"

the soft version is:
Vagrant 1.6.3
Virtualbox 4.3.14

[terrywang]

From Linux guest perspective, ethX to enpXsY naming scheme change is due to the move from SysV init to systemd (systemd-udevd).

The following distributions already switched to systemd

• Arch Linux
• Fedora 20
• openSUSE 13.1
• RHEL 7
• CentOS 7
• Oracle Linux 7
• Debian jessie testing (can use systemd as default init system)

Before Vagrant fixes this in code, an easy temporary workaround is to pass net.ifnames=0 to kernel boot parameters to revert to the old NIC naming scheme.

[mitchellh]

This is fixed now.

[mitchellh]

(in master).

I agree with @terrywang we need to make Vagrant more systemd-aware in the future. But for a 1.6.4 release I think this will work fine.

[denderello]

@mitchellh: Sorry, but this won't work for me with vagrant version 1.6.5. Used a self created box as well as terrywang/archlinux. When using the config.vm.network "private_network", ip: "192.168.33.10" vagrant still ends up in the following error:

...

==> default: Configuring and enabling network interfaces...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

ip link set eth1 down

Stdout from the command:



Stderr from the command:

Cannot find device "eth1"

[terrywang]

@denderello Have you tried to pass net.ifnames=0 as kernel boot parameter and try again?

[ogarcia]

I think that while the bug is not fixed this issue must be open.

[denderello]

@terrywang helps with your image, but not on my own one. If I use the parameter there vagrant won't even be able to connect to the machine. :(