I resolved this problem, its the mac addr have not config to eth file. 在 2017年2月25日星期六 UTC+8下午4:05:23，Carey Wang写道： > > ### I was change Vagrant version downgrading to > Vagrant 1.8.7 > > ### then got the network error > ``` > c:\www\htdocs\vagrant>vagrant destroy && vagrant up > default: Are you sure you want to destroy the 'default' VM? [y/N] y > ==> default: Forcing shutdown of VM... > ==> default: Destroying VM and associated drives... > Bringing machine 'default' up with 'virtualbox' provider... > ==> default: Importing base box 'CentOS-7-Vagrant-1505-x86_64-01'... > ==> default: Matching MAC address for NAT networking... > ==> default: Setting the name of the VM: > vagrant_default_1488008124029_40480 > ==> 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: 80 (guest) => 8080 (host) (adapter 1) > default: 22 (guest) => 2222 (host) (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: Remote connection disconnect. Retrying... > default: > default: Vagrant insecure key detected. Vagrant will automatically > replace > default: this with a newly generated keypair for better security. > default: > default: Inserting generated public key within guest... > default: Removing insecure key from the guest if it's present... > default: Key inserted! Disconnecting and reconnecting using new SSH > key... > ==> default: Machine booted and ready! > ==> default: Checking for guest additions in VM... > default: No guest additions were detected on the base box for this VM! > Guest > default: additions are required for forwarded ports, shared folders, > host only > default: networking, and more. If SSH fails on this machine, please > install > default: the guest additions and repackage the box to continue. > default: > default: This is not an error message; everything may continue to work > properly, > default: in which case you may ignore this message. > ==> 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! > > # Down the interface before munging the config file. This might > # fail if the interface is not actually set up yet so ignore > # errors. > /sbin/ifdown 'eth1' > # Move new config into place > mv -f '/tmp/vagrant-network-entry-eth1-1488008160-0' > '/etc/sysconfig/network-scripts/ifcfg-eth1' > # attempt to force network manager to reload configurations > nmcli c reload || true > > # Restart network > service network restart > > > Stdout from the command: > > Restarting network (via systemctl): [FAILED] > > > Stderr from the command: > > usage: ifdown <configuration> > Job for network.service failed. See 'systemctl status network.service' and > 'journalctl -xn' for details. > ``` >
-- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/vagrant/issues IRC: #vagrant on Freenode --- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/9bc9d75b-21ff-48f0-a3f9-e6e533993c38%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
