GitLab

Created by: juadde

When using archlinux vagrant boxes hostonly static IP assgnation is failing.

To Reproduce Steps to reproduce the behavior:

1. Use following Vagrantfile Vagrant.configure("2") do |config| config.vm.box = "archlinux/archlinux" config.vm.network "private_network", ip: "192.168.0.50" end
2. Run vagrant up (tested with virtualbox as backend)
3. See 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! # Configure eth1 mv '/tmp/vagrant-network-eth1-1576228056-0' '/etc/netctl/eth1' && ip link set 'eth1' down && netctl restart 'eth1' && netctl enable 'eth1' Stdout from the command: Stderr from the command: mv: cannot move '/tmp/vagrant-network-eth1-1576228056-0' to '/etc/netctl/eth1': No such file or directory

Expected behavior Expected ip: "192.168.0.50" assigned instead of: 3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 08:00:27:11:75:00 brd ff:ff:ff:ff:ff:ff

Host Software (please complete the following information):

• OS: Windows
• Distribution: 10 Pro
• Vagrant Version: 2.2.6
• Hypervisor: Virtualbox
• Hypervisor Version: 6.0.14
• Image Version: 2019.12.02
• Host Modules: N/A
• Host Modules Version: N/A
• Output of id command: N/A
• Output of uname -a: N/A
• Vagrant Plugins: vagrant-reload (0.0.1, global) [Not used], vagrant-vbguest (0.20.0, global) [Disabled through config.vbguest.auto_update = false in Vagrantfile], vagrant-windows-update (0.0.7, global) [Not relevant here I guess]

Additional context I don't know if it is a bug or not, but once netctl is installed the behavior is the good one, static IP is assigned as expected.