$ cat ./Vagrantfile
# -*- mode: ruby -*-
# vi: set ft=ruby :

# All Vagrant configuration is done below. The "2" in Vagrant.configure
# configures the configuration version (we support older styles for
# backwards compatibility). Please don't change it unless you know what
# you're doing.
Vagrant.configure("2") do |config|
  config.vm.box = "xxx.box"
  config.vm.define :xxx do |app|
    app.vm.hostname = 'xxx'
    app.vm.network 'private_network', ip: '192.168.33.52'
    app.vm.network 'public_network', bridge: 'en0: air Wi-Fi (AirPort)'
  end
  config.vm.provider :virtualbox do |v|
    v.customize ['modifyvm', :id, '--memory', 1024]
  end
end

$ vagrant reload
==> xxx: Attempting graceful shutdown of VM...
==> xxx: Clearing any previously set forwarded ports...
==> xxx: Clearing any previously set network interfaces...
==> xxx: Preparing network interfaces based on configuration...
    xxx: Adapter 1: nat
    xxx: Adapter 2: hostonly
    xxx: Adapter 3: bridged
==> xxx: Forwarding ports...
    xxx: 22 (guest) => 2222 (host) (adapter 1)
==> xxx: Running 'pre-boot' VM customizations...
==> xxx: Booting VM...
==> xxx: Waiting for machine to boot. This may take a few minutes...
    xxx: SSH address: 127.0.0.1:2222
    xxx: SSH username: vagrant
    xxx: SSH auth method: private key
    xxx: Warning: Remote connection disconnect. Retrying...
==> xxx: Machine booted and ready!
[xxx] GuestAdditions 5.1.22 running --- OK.
==> xxx: Checking for guest additions in VM...
==> xxx: Setting hostname...
==> xxx: 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-1498836932-0' '/etc/sysconfig/network-scripts/ifcfg-eth1'
# attempt to force network manager to reload configurations
nmcli c reload || true

# 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 'eth2'
# Move new config into place
mv -f '/tmp/vagrant-network-entry-eth2-1498836932-1' '/etc/sysconfig/network-scripts/ifcfg-eth2'
# attempt to force network manager to reload configurations
nmcli c reload || true

# Restart network
service network restart


Stdout from the command:

Shutting down interface eth0:  [  OK  ]
Shutting down loopback interface:  [  OK  ]
Bringing up loopback interface:  [  OK  ]
Bringing up interface eth0:
Determining IP information for eth0... done.
[  OK  ]
Bringing up interface eth1:  Determining if ip address 192.168.33.52 is already in use for device eth1...
[  OK  ]
Bringing up interface eth2:
Determining IP information for eth2... done.
[  OK  ]
Bringing up interface eth3:  Device eth3 does not seem to be present, delaying initialization.
[FAILED]
Bringing up interface eth4:  Device eth4 does not seem to be present, delaying initialization.
[FAILED]


Stderr from the command:

bash: line 11: nmcli: command not found
bash: line 20: nmcli: command not found

$ sudo service network restart

$ ls -la /etc/sysconfig/network-scripts/ifcfg-*
-rw-r--r-- 1 root    root    197 Jun 30 14:52 /etc/sysconfig/network-scripts/ifcfg-eth0
-rw------- 1 vagrant vagrant 213 Jun 30 17:44 /etc/sysconfig/network-scripts/ifcfg-eth1
-rw------- 1 vagrant vagrant 142 Jun 30 17:44 /etc/sysconfig/network-scripts/ifcfg-eth2
-rw-r--r-- 1 root    root    254 Jun 30 14:52 /etc/sysconfig/network-scripts/ifcfg-lo

$ sudo service network restart

$ ifconifg

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