Vagrant start error The following SSH command responded with a no source: Internet anonymity time: 2015-03-08 22:27the 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/
Vagrant package generates box, with this box as the base template, to create vagrant environment, start vagrant Error
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 is interface should the network Bridge to? 2
[Default] Preparing network interfaces based on configuration ...
[Default] Forwarding ports ...
[Default]--2222 (adapter 1)
[Default] Booting VM ...
[Default] Waiting to boot. This could take a few minutes ...
[Default] Machine booted and ready!
[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!
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 vagrant up error, but vagrant SSH can still log on to the virtual machine, after entering the virtual machine, execute the following command
sudo rm-f/etc/udev/rules.d/70-persistent-net.rules
Yes, the problem is in the persistent network device Udev rules, which are set by the original VM and then generated by box, are updated when the new VM is persistent. This conflicts with the instructions in Vagrantfile to set the private network for the new VM. Delete it just fine.
It's no problem to start again.
Vagrant Start error The following SSH command responded with a No