Vagrant startup error: The following SSH command responded with a non-zero exit status., vagrantnon-zero

Vagrant startup error: The following SSH command responded with a non-zero exit status., vagrantnon-zero

Vagrant package is packaged to generate a box. Based on this box template, create a vagrant environment and start vagrant to report errors.

Angel: vagrant $ vagrant up

Bringing machine 'default' up with 'virtualbox' provider...

[Default] Clearing any previously set forwarded ports...

[Default] Creating shared folders metadata...

[Default] Clearing any previously set network interfaces...

[Default] Available bridged network interfaces:

1) en0: Ethernet

2) en1: Wi-Fi (AirPort)

3) bridge100

What interface shoshould the network bridge? 2

[Default] Preparing network interfaces based on configuration...

[Default] Forwarding ports...

[Default] -- 22 = & gt; 2222 (adapter 1)

[Default] Booting VM...

[Default] Waiting for machine to boot. This may take a few minutes...

[Default] Machine booted and ready!

[Default] grouping and enabling network interfaces...

The following SSH command responded with a non-zero exit status.

Vagrant assumes that this means the command failed!

ARPCHECK = no/sbin/ifup eth1 2>/dev/null

Stdout from the command:

Device eth1 does not seem to be present, delaying initialization.

Stderr from the command:

Solution:

Although an error is reported when vagrant up is started, vagrant ssh can still log on to the VM. after entering the VM, run the following command:

Sudo rm-f/etc/udev/rules. d/70-persistent-net.rules

Yes, the problem is that the persistent network device udev rule (persistent network device udev rules) is set by the original VM. When a new VM is generated using box, these rules need to be updated. This conflicts with the command for setting private network for the new VM in Vagrantfile. Just delete it.

Start again ..