vagrant up命令出现错误,eth1未显示可解析的ip地址

vagrant up命令出现错误,eth1未显示可解析的ip地址,ip,vagrant,ethernet,Ip,Vagrant,Ethernet,我不熟悉虚拟机,但一直在使用vagrant在Ubuntu14.04上运行Centos虚拟机。突然vagrant up命令出现以下错误: root@shanky:~/centos# vagrant up Bringing machine 'default' up with 'virtualbox' provider... ==> default: Checking if box 'chef/centos-6.5' is up to date... ==> default: Clear

我不熟悉虚拟机,但一直在使用vagrant在Ubuntu14.04上运行Centos虚拟机。突然
vagrant up
命令出现以下错误:

root@shanky:~/centos# vagrant  up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'chef/centos-6.5' is up to date...
==> default: Clearing any previously set forwarded ports...
==> default: Clearing any previously set network interfaces...
==> default: Available bridged network interfaces:
1) eth0
2) wlan0
==> default: When choosing an interface, it is usually the one that is
==> default: being used to connect to the internet.
    default: Which interface should the network bridge to? 1
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
    default: Adapter 2: bridged
==> default: Forwarding ports...
    default: 80 => 5444 (adapter 1)
    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: Warning: Remote connection disconnect. 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!

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

Stdout from the command:


Determining IP information for eth1...PING 10.1.34.1 (10.1.34.1) from 10.1.34.183 eth1: 56(84) bytes of data.

--- 10.1.34.1 ping statistics ---
3 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2999ms
pipe 3
PING 10.2.56.1 (10.2.56.1) from 10.2.56.156 eth1: 56(84) bytes of data.

--- 10.2.56.1 ping statistics ---
3 packets transmitted, 0 received, +3 errors, 100% packet loss, time 3000ms
pipe 3
 failed.
Stderr from the command:
我可以将ssh漫游到VM,但eth1不再提供可解析的ip(即,它不提供
inet addr
paramater。如何解决此问题

附言。

我已经尝试了一些修补eth1的建议,在上面的链接,但没有用。PLz帮助。
谢谢。

事实证明,eth2是将虚拟机直接连接到外部互联网的适配器,所以评论说

config.vm.network :public_network

从VagrantFile中,停止加载公共网络接口,从而解决了问题。

原来eth2是将虚拟机直接连接到外部Internet的适配器,因此评论指出

config.vm.network :public_network

从VagrantFile中,停止加载公共网络接口,从而解决了问题。

原来eth2是将虚拟机直接连接到外部Internet的适配器,因此评论指出

config.vm.network :public_network

从VagrantFile中,停止加载公共网络接口,从而解决了问题。

原来eth2是将虚拟机直接连接到外部Internet的适配器,因此评论指出

config.vm.network :public_network

从VagrantFile停止加载公共网络接口,从而解决了问题。

这似乎发生在启动网络配置中

虽然无法启动网络接口,但您应该能够通过ssh将其连接到该框中

vagrant ssh
sudo rm /etc/udev/rules.d/70-persistent-net.rules
exit
vagrant reload

来源:

这似乎发生在启动网络配置中

虽然无法启动网络接口,但您应该能够通过ssh将其连接到该框中

vagrant ssh
sudo rm /etc/udev/rules.d/70-persistent-net.rules
exit
vagrant reload

来源:

这似乎发生在启动网络配置中

虽然无法启动网络接口,但您应该能够通过ssh将其连接到该框中

vagrant ssh
sudo rm /etc/udev/rules.d/70-persistent-net.rules
exit
vagrant reload

来源:

这似乎发生在启动网络配置中

虽然无法启动网络接口,但您应该能够通过ssh将其连接到该框中

vagrant ssh
sudo rm /etc/udev/rules.d/70-persistent-net.rules
exit
vagrant reload

来源:

My
config.vm.network:public_-network
行已被注释掉;这个答案对我有效。My
config.vm.network:public_-network
行已被注释掉;这个答案对我有效。My
config.vm.network:public_-network
行已被注释掉;这个答案是什么对我有效。我的
config.vm.network:public_network
行已经被注释掉了;这个答案对我有效。