Having trouble setting up Vagrant 2.0.1 with VMware Workstation 14.1.1
build-7528167 on linux 4.13.0-32-generic Ubuntu 17.10
vagrant file is as follows:
-*- mode: ruby -*-
# vi: set ft=ruby :
VAGRANTFILE_API_VERSION = "2"
Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
config.vm.box = "redacted"
config.vm.hostname = "dev"
config.ssh.username = "foo"
config.ssh.insert_key = false
# network config
config.vm.network "private_network", ip: "10.11.12.13"
# VMware Workstation specific config
config.vm.provider "vmware_workstation" do |v,o|
o.vm.box_url = "file:////home/user/Downloads/redacted.box"
v.gui = false
v.name = "DEV"
v.cpus = 4
v.memory = 4096
v.update_guest_tools = true
end
## Salt configuration
# For masterless, mount your file roots file root
config.vm.synced_folder "salt/roots/", "/srv/"
# Set your salt configs here
config.vm.provision :salt , run: "always" do |salt|
# added -X to disable daemon check (not required for masterless)
salt.bootstrap_options = "-F -c /tmp -X"
## Minion config is set to ``file_client: local`` for masterless
salt.minion_config = "salt/minion"
salt.masterless = true
## Installs our example formula in "salt/roots/salt"
salt.run_highstate = true
end
# Shared folders
config.vm.synced_folder "build", "/build", type: "rsync"
config.vm.synced_folder '', '/vagrant', disabled: true
end
vmware network setup are:
<https://lh3.googleusercontent.com/-9E7aiLL-NIQ/WnNjweijGGI/AAAAAAABAx4/0yHNhH0Gqrg45ogOUL5r9q-BzwO0WR7rACLcBGAs/s1600/Screenshot%2Bfrom%2B2018-02-01%2B19-59-13.png>
<https://lh3.googleusercontent.com/-8H6rjq59HOc/WnNkHJC3r9I/AAAAAAABAx8/e31sEpULsKkbVnw3PN_WnTIUy9PEDOGawCLcBGAs/s1600/Screenshot%2Bfrom%2B2018-02-01%2B19-59-20.png>
<https://lh3.googleusercontent.com/-4mMLZFQllf4/WnNkLOqJgPI/AAAAAAABAyA/c2zNO2xSEc8cNM7IqVCTOnM4_-iDXMiNwCLcBGAs/s1600/Screenshot%2Bfrom%2B2018-02-01%2B19-59-30.png>
<https://lh3.googleusercontent.com/-4mMLZFQllf4/WnNkLOqJgPI/AAAAAAABAyA/c2zNO2xSEc8cNM7IqVCTOnM4_-iDXMiNwCLcBGAs/s1600/Screenshot%2Bfrom%2B2018-02-01%2B19-59-30.png>
when running `vagrant up`, I get the following when forwarding ports:
Vagrant failed to start the VMware network interfaces! The output
of the failed command, if any, is below. The usual cause for this
is invalid configuration of the VMware network components. If
the problem persists, please contact support.
Subnet on vmnet1 is no longer available for usage, please run the network
editor to reconfigure different subnet
Failed to start some/all services
performing an ifconfig shows that vmnet1 is no longer present, preventing
ssh and further vagrant setup. Re-saving the vmware network settings
brings vmnet1 back and able to ssh into the box.
--
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 vagrant-up+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/vagrant-up/fba4e4c5-748f-45b4-9e09-ac55b245055b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
