Skip to content

Instantly share code, notes, and snippets.

@quasiben
Created November 11, 2015 21:25
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save quasiben/33cf1e7f1f4df3319cc4 to your computer and use it in GitHub Desktop.
Save quasiben/33cf1e7f1f4df3319cc4 to your computer and use it in GitHub Desktop.
INFO global: Vagrant version: 1.7.4
INFO global: Ruby version: 2.0.0
INFO global: RubyGems version: 2.0.14
INFO global: VAGRANT_LOG="debug"
INFO global: VAGRANT_OLD_ENV_SPARK_HOME="/Users/quasiben/Research/GitClones/spark"
INFO global: VAGRANT_OLD_ENV_HOME="/Users/quasiben"
INFO global: VAGRANT_OLD_ENV__="/usr/local/bin/vagrant"
INFO global: VAGRANT_OLD_ENV_XPC_FLAGS="0x0"
INFO global: VAGRANT_INSTALLER_VERSION="2"
INFO global: VAGRANT_OLD_ENV_VAGRANT_LOG="debug"
INFO global: VAGRANT_OLD_ENV_TMPDIR="/var/folders/1t/t94brwgx7sjcn8jgz4gr3_c00000gq/T/"
INFO global: VAGRANT_OLD_ENV_Apple_PubSub_Socket_Render="/private/tmp/com.apple.launchd.KW13obTzd8/Render"
INFO global: VAGRANT_OLD_ENV_JAVA_HOME="/Library/Java/JavaVirtualMachines/jdk1.7.0_45.jdk/Contents/Home"
INFO global: VAGRANT_OLD_ENV_ACHE_HOME="/Users/quasiben/anaconda/envs/memex-explorer/lib/python2.7/site-packages/ache/"
INFO global: VAGRANT_OLD_ENV_CONDA_ENV_PATH="/Users/quasiben/anaconda/envs/clusto"
INFO global: VAGRANT_OLD_ENV_PYTHONPATH="/Users/quasiben/Research/ContinuumDev/GitRepo/conda-cluster/::/Users/quasiben/Research/GitClones/spark/python"
INFO global: VAGRANT_OLD_ENV_PATH="/Users/quasiben/anaconda/envs/clusto/bin:/usr/local/bin:/usr/local/heroku/bin:/Users/quasiben/google-cloud-sdk/bin:/usr/local/sbin:/Users/quasiben/.cabal/bin/:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/texbin:/Users/quasiben/Research/ContinuumDev/GitRepo/libdynd/build"
INFO global: VAGRANT_OLD_ENV_PWD="/Users/quasiben"
INFO global: VAGRANT_OLD_ENV_ITERM_PROFILE="Default"
INFO global: VAGRANT_OLD_ENV_JDK_HOME="/Library/Java/JavaVirtualMachines/jdk1.7.0_45.jdk/Contents/Home/"
INFO global: VAGRANT_OLD_ENV_COLORFGBG="7;0"
INFO global: VAGRANT_OLD_ENV_CONDA_DEFAULT_ENV="clusto"
INFO global: VAGRANT_INSTALLER_ENV="1"
INFO global: VAGRANT_EXECUTABLE="/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/bin/vagrant"
INFO global: VAGRANT_INSTALLER_EMBEDDED_DIR="/opt/vagrant/embedded"
INFO global: VAGRANT_OLD_ENV_COMMAND_MODE="unix2003"
INFO global: VAGRANT_OLD_ENV_SSH_AUTH_SOCK="/private/tmp/com.apple.launchd.CSjdOMPkpG/Listeners"
INFO global: VAGRANT_OLD_ENV_LANG="en_US.UTF-8"
INFO global: VAGRANT_OLD_ENV_TERM_PROGRAM="iTerm.app"
INFO global: VAGRANT_OLD_ENV_XPC_SERVICE_NAME="0"
INFO global: VAGRANT_OLD_ENV_SHLVL="1"
INFO global: VAGRANT_OLD_ENV_SECURITYSESSIONID="186a5"
INFO global: VAGRANT_OLD_ENV_TERM="xterm-color"
INFO global: VAGRANT_OLD_ENV_USER="quasiben"
INFO global: VAGRANT_OLD_ENV___CF_USER_TEXT_ENCODING="0x1F7:0x0:0x0"
INFO global: VAGRANT_OLD_ENV_ITERM_SESSION_ID="w0t1p0"
INFO global: VAGRANT_OLD_ENV_SHELL="/bin/bash"
INFO global: VAGRANT_OLD_ENV_PS1="(clusto)\\[\\033[01;32m\\]\\u@\\h\\[\\033[00m\\]:\\[\\033[01;36m\\]\\w\\[\\033[00m\\]\\$ "
INFO global: VAGRANT_OLD_ENV_OLDPWD="/Users/quasiben/Research/ContinuumDev/AC_AS_Vagrant/Head+Compute/test"
INFO global: VAGRANT_OLD_ENV_JRE_HOME="/Library/Java/JavaVirtualMachines/jdk1.7.0_45.jdk/Contents/Home/jre/"
INFO global: VAGRANT_OLD_ENV_LOGNAME="quasiben"
INFO global: VAGRANT_INTERNAL_BUNDLERIZED="1"
INFO global: Plugins:
INFO global: - bundler = 1.10.5
INFO global: - mime-types = 1.25.1
INFO global: - rest-client = 1.6.9
INFO global: - vagrant-share = 1.1.4
INFO global: - vagrant-vmware-fusion = 4.0.2
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/box/plugin.rb
INFO manager: Registered plugin: box command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/destroy/plugin.rb
INFO manager: Registered plugin: destroy command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/global-status/plugin.rb
INFO manager: Registered plugin: global-status command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/halt/plugin.rb
INFO manager: Registered plugin: halt command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/help/plugin.rb
INFO manager: Registered plugin: help command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/init/plugin.rb
INFO manager: Registered plugin: init command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/list-commands/plugin.rb
INFO manager: Registered plugin: list-commands command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/login/plugin.rb
INFO manager: Registered plugin: vagrant-login
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/package/plugin.rb
INFO manager: Registered plugin: package command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/plugin/plugin.rb
INFO manager: Registered plugin: plugin command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/provision/plugin.rb
INFO manager: Registered plugin: provision command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/push/plugin.rb
INFO manager: Registered plugin: push command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/rdp/plugin.rb
INFO manager: Registered plugin: rdp command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/reload/plugin.rb
INFO manager: Registered plugin: reload command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/resume/plugin.rb
INFO manager: Registered plugin: resume command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/ssh/plugin.rb
INFO manager: Registered plugin: ssh command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/ssh_config/plugin.rb
INFO manager: Registered plugin: ssh-config command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/status/plugin.rb
INFO manager: Registered plugin: status command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/suspend/plugin.rb
INFO manager: Registered plugin: suspend command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/up/plugin.rb
INFO manager: Registered plugin: up command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/version/plugin.rb
INFO manager: Registered plugin: version command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/communicators/ssh/plugin.rb
INFO manager: Registered plugin: ssh communicator
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/communicators/winrm/plugin.rb
INFO manager: Registered plugin: winrm communicator
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/arch/plugin.rb
INFO manager: Registered plugin: Arch guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/atomic/plugin.rb
INFO manager: Registered plugin: Atomic Host guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/coreos/plugin.rb
INFO manager: Registered plugin: CoreOS guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/darwin/plugin.rb
INFO manager: Registered plugin: Darwin guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/debian/plugin.rb
INFO manager: Registered plugin: Debian guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/debian8/plugin.rb
INFO manager: Registered plugin: Debian Jessie guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/esxi/plugin.rb
INFO manager: Registered plugin: ESXi guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/fedora/plugin.rb
INFO manager: Registered plugin: Fedora guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/freebsd/plugin.rb
INFO manager: Registered plugin: FreeBSD guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/funtoo/plugin.rb
INFO manager: Registered plugin: Funtoo guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/gentoo/plugin.rb
INFO manager: Registered plugin: Gentoo guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/linux/plugin.rb
INFO manager: Registered plugin: Linux guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/mint/plugin.rb
INFO manager: Registered plugin: Mint guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/netbsd/plugin.rb
INFO manager: Registered plugin: NetBSD guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/nixos/plugin.rb
INFO manager: Registered plugin: NixOS guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/omnios/plugin.rb
INFO manager: Registered plugin: OmniOS guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/openbsd/plugin.rb
INFO manager: Registered plugin: OpenBSD guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/photon/plugin.rb
INFO manager: Registered plugin: VMware Photon guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/pld/plugin.rb
INFO manager: Registered plugin: PLD Linux guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/redhat/plugin.rb
INFO manager: Registered plugin: Red Hat Enterprise Linux guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/smartos/plugin.rb
INFO manager: Registered plugin: SmartOS guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/solaris/plugin.rb
INFO manager: Registered plugin: Solaris guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/solaris11/plugin.rb
INFO manager: Registered plugin: Solaris 11 guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/suse/plugin.rb
INFO manager: Registered plugin: SUSE guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/tinycore/plugin.rb
INFO manager: Registered plugin: TinyCore Linux guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/ubuntu/plugin.rb
INFO manager: Registered plugin: Ubuntu guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/windows/plugin.rb
INFO manager: Registered plugin: Windows guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/arch/plugin.rb
INFO manager: Registered plugin: Arch host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/bsd/plugin.rb
INFO manager: Registered plugin: BSD host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/darwin/plugin.rb
INFO manager: Registered plugin: Mac OS X host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/freebsd/plugin.rb
INFO manager: Registered plugin: FreeBSD host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/gentoo/plugin.rb
INFO manager: Registered plugin: Gentoo host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/linux/plugin.rb
INFO manager: Registered plugin: Linux host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/null/plugin.rb
INFO manager: Registered plugin: null host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/redhat/plugin.rb
INFO manager: Registered plugin: Red Hat Enterprise Linux host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/slackware/plugin.rb
INFO manager: Registered plugin: Slackware host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/suse/plugin.rb
INFO manager: Registered plugin: SUSE host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/windows/plugin.rb
INFO manager: Registered plugin: Windows host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/kernel_v1/plugin.rb
INFO manager: Registered plugin: kernel
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/kernel_v2/plugin.rb
INFO manager: Registered plugin: kernel
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/providers/docker/plugin.rb
INFO manager: Registered plugin: docker-provider
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/providers/hyperv/plugin.rb
INFO manager: Registered plugin: Hyper-V provider
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/providers/virtualbox/plugin.rb
INFO manager: Registered plugin: VirtualBox provider
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/ansible/plugin.rb
INFO manager: Registered plugin: ansible
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/cfengine/plugin.rb
INFO manager: Registered plugin: CFEngine Provisioner
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/chef/plugin.rb
INFO manager: Registered plugin: chef
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/docker/plugin.rb
INFO manager: Registered plugin: docker
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/file/plugin.rb
INFO manager: Registered plugin: file
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/puppet/plugin.rb
INFO manager: Registered plugin: puppet
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/salt/plugin.rb
INFO manager: Registered plugin: salt
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/shell/plugin.rb
INFO manager: Registered plugin: shell
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/pushes/atlas/plugin.rb
INFO manager: Registered plugin: atlas
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/pushes/ftp/plugin.rb
INFO manager: Registered plugin: ftp
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/pushes/heroku/plugin.rb
INFO manager: Registered plugin: heroku
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/pushes/local-exec/plugin.rb
INFO manager: Registered plugin: local-exec
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/pushes/noop/plugin.rb
INFO manager: Registered plugin: noop
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/synced_folders/nfs/plugin.rb
INFO manager: Registered plugin: NFS synced folders
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/synced_folders/rsync/plugin.rb
INFO manager: Registered plugin: RSync synced folders
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/synced_folders/smb/plugin.rb
INFO manager: Registered plugin: SMB synced folders
INFO global: Loading plugins!
INFO manager: Registered plugin: vagrant-share
INFO manager: Registered plugin: VMware Fusion Provider
INFO vagrant: `vagrant` invoked: ["up"]
DEBUG vagrant: Creating Vagrant environment
INFO environment: Environment initialized (#<Vagrant::Environment:0x00000101a99370>)
INFO environment: - cwd: /Users/quasiben
INFO environment: Home path: /Users/quasiben/.vagrant.d
INFO environment: Local data path: /Users/quasiben/.vagrant
DEBUG environment: Creating: /Users/quasiben/.vagrant
INFO environment: Running hook: environment_plugins_loaded
INFO runner: Preparing hooks for middleware sequence...
INFO runner: 1 hooks defined.
INFO runner: Running action: environment_plugins_loaded #<Vagrant::Action::Builder:0x0000010122eac8>
INFO environment: Running hook: environment_load
INFO runner: Preparing hooks for middleware sequence...
INFO runner: 2 hooks defined.
INFO runner: Running action: environment_load #<Vagrant::Action::Builder:0x00000101b80ef0>
INFO warden: Calling IN action: #<HashiCorp::VagrantVMwarefusion::SetupPlugin:0x00000101b79858>
INFO warden: Calling IN action: HashiCorp Background Check: Start
DEBUG activation: Last ping time: 1447276167
DEBUG activation: License file ID: 0662e445-1b59-480b-8786-3412567c736b
INFO warden: Calling OUT action: HashiCorp Background Check: Start
INFO warden: Calling OUT action: #<HashiCorp::VagrantVMwarefusion::SetupPlugin:0x00000101b79858>
INFO cli: CLI: [] "up" []
DEBUG cli: Invoking command class: VagrantPlugins::CommandUp::Command []
DEBUG command: 'Up' each target VM...
INFO loader: Set :root = #<Pathname:/Users/quasiben/Vagrantfile>
DEBUG loader: Populating proc cache for #<Pathname:/Users/quasiben/Vagrantfile>
DEBUG loader: Load procs for pathname: /Users/quasiben/Vagrantfile
INFO loader: Loading configuration in order: [:home, :root]
DEBUG loader: Loading from: root (evaluating)
DEBUG loader: Configuration loaded successfully, finalizing and returning
DEBUG push: finalizing
DEBUG command: Getting target VMs for command. Arguments:
DEBUG command: -- names: ["dev"]
DEBUG command: -- options: {:provider=>nil}
DEBUG command: Finding machine that match name: dev
INFO loader: Set "2161886140_machine_dev" = [["2", #<Proc:0x000001010e6d78@/Users/quasiben/Vagrantfile:7>]]
DEBUG loader: Populating proc cache for ["2", #<Proc:0x000001010e6d78@/Users/quasiben/Vagrantfile:7>]
INFO loader: Loading configuration in order: [:home, :root, "2161886140_machine_dev"]
DEBUG loader: Loading from: root (cache)
DEBUG loader: Loading from: 2161886140_machine_dev (evaluating)
DEBUG loader: Configuration loaded successfully, finalizing and returning
DEBUG push: finalizing
INFO environment: Getting machine: dev (vmware_fusion)
INFO environment: Uncached load of machine.
INFO loader: Set "2161886140_machine_dev" = [["2", #<Proc:0x000001010e6d78@/Users/quasiben/Vagrantfile:7>]]
INFO loader: Loading configuration in order: [:home, :root, "2161886140_machine_dev"]
DEBUG loader: Loading from: root (cache)
DEBUG loader: Loading from: 2161886140_machine_dev (cache)
DEBUG loader: Configuration loaded successfully, finalizing and returning
DEBUG push: finalizing
INFO box_collection: Box found: 1vq9/trusty64 (vmware_fusion)
INFO environment: Running hook: authenticate_box_url
INFO host: Autodetecting host type for [#<Vagrant::Environment: /Users/quasiben>]
DEBUG host: Trying: arch
DEBUG host: Trying: darwin
INFO host: Detected: darwin!
INFO runner: Preparing hooks for middleware sequence...
INFO runner: 2 hooks defined.
INFO runner: Running action: authenticate_box_url #<Vagrant::Action::Builder:0x000001028bd708>
INFO warden: Calling IN action: #<VagrantPlugins::LoginCommand::AddAuthentication:0x00000102971280>
DEBUG client: No authentication token in environment or /Users/quasiben/.vagrant.d/data/vagrant_login_token
INFO warden: Calling OUT action: #<VagrantPlugins::LoginCommand::AddAuthentication:0x00000102971280>
INFO machine: Initializing machine: dev
INFO machine: - Provider: HashiCorp::VagrantVMwarefusion::Provider
INFO machine: - Box: #<Vagrant::Box:0x00000102a00cc8>
INFO machine: - Data dir: /Users/quasiben/.vagrant/machines/dev/vmware_fusion
DEBUG vmware: Re-initializing driver for new ID: nil
INFO vmware_driver: VMX file:
INFO vmware_driver: Looking for VMware Fusion: /Applications/VMware Fusion.app
INFO vmware_driver: VMware Fusion path: #<Pathname:/Applications/VMware Fusion.app>
DEBUG vmware_driver: Attempting to read VMware version...
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmware-vmx", "-v"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command is setuid/setgid, clearing DYLD_LIBRARY_PATH
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr:
VMware Fusion Information:
VMware Fusion 7.1.0 build-2314774 Release
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 31999
DEBUG subprocess: Exit status: 0
INFO vmware_driver: Detected VMware version: 7.1.0
DEBUG vmware_driver: service starter path: /Applications/VMware Fusion.app/Contents/Library/services/Open VMware Fusion Services
DEBUG vmware_driver: vmnet-cli path: /Applications/VMware Fusion.app/Contents/Library/vmnet-cli
DEBUG vmware: VM state requested. Current state: not_created
INFO machine: New machine ID: nil
DEBUG vmware: Re-initializing driver for new ID: nil
INFO vmware_driver: VMX file:
INFO vmware_driver: Looking for VMware Fusion: /Applications/VMware Fusion.app
INFO vmware_driver: VMware Fusion path: #<Pathname:/Applications/VMware Fusion.app>
DEBUG vmware_driver: Attempting to read VMware version...
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmware-vmx", "-v"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command is setuid/setgid, clearing DYLD_LIBRARY_PATH
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr:
VMware Fusion Information:
VMware Fusion 7.1.0 build-2314774 Release
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO vmware_driver: Detected VMware version: 7.1.0
DEBUG vmware_driver: service starter path: /Applications/VMware Fusion.app/Contents/Library/services/Open VMware Fusion Services
DEBUG vmware_driver: vmnet-cli path: /Applications/VMware Fusion.app/Contents/Library/vmnet-cli
INFO command: With machine: dev (#<HashiCorp::VagrantVMwarefusion::Provider:0x00000102b001c8 @logger=#<Log4r::Logger:0x00000102b00178 @fullname="hashicorp::vagrant::vmware", @outputters=[], @additive=true, @name="vmware", @path="hashicorp::vagrant", @parent=#<Log4r::Logger:0x00000101ada690 @fullname="hashicorp", @outputters=[#<Log4r::StderrOutputter:0x00000100864b00 @mon_owner=nil, @mon_count=0, @mon_mutex=#<Mutex:0x00000100864920>, @name="stderr", @level=0, @formatter=#<Log4r::DefaultFormatter:0x0000010087f8b0 @depth=7>, @out=#<IO:<STDERR>>>], @additive=true, @name="hashicorp", @path="", @parent=#<Log4r::RootLogger:0x000001009da3b8 @level=0, @outputters=[]>, @level=1, @trace=false>, @level=1, @trace=false>, @machine=#<Vagrant::Machine: dev (HashiCorp::VagrantVMwarefusion::Provider)>, @driver=#<HashiCorp::VagrantVMwarefusion::Driver::Fusion:0x00000101c979b0 @lic_features=["fusion", "fusion6", "fusion7", "fusion6"], @logger=#<Log4r::Logger:0x00000101c977f8 @fullname="hashicorp::provider::vmware_driver", @outputters=[], @additive=true, @name="vmware_driver", @path="hashicorp::provider", @parent=#<Log4r::Logger:0x00000101ada690 @fullname="hashicorp", @outputters=[#<Log4r::StderrOutputter:0x00000100864b00 @mon_owner=nil, @mon_count=0, @mon_mutex=#<Mutex:0x00000100864920>, @name="stderr", @level=0, @formatter=#<Log4r::DefaultFormatter:0x0000010087f8b0 @depth=7>, @out=#<IO:<STDERR>>>], @additive=true, @name="hashicorp", @path="", @parent=#<Log4r::RootLogger:0x000001009da3b8 @level=0, @outputters=[]>, @level=1, @trace=false>, @level=1, @trace=false>, @vmx_path=nil, @vm_dir=nil, @allow_exp=false, @install_dir=#<Pathname:/Applications/VMware Fusion.app>, @networking_file=#<Pathname:/Library/Preferences/VMware Fusion/networking>, @service_starter=#<Pathname:/Applications/VMware Fusion.app/Contents/Library/services/Open VMware Fusion Services>, @vmnet_bridge_pidfile=#<Pathname:/var/run/vmnet-bridge.pid>, @vmnet_cli=#<Pathname:/Applications/VMware Fusion.app/Contents/Library/vmnet-cli>, @vmrun_path=#<Pathname:/Applications/VMware Fusion.app/Contents/Library/vmrun>, @vmware_vmx_path=#<Pathname:/Applications/VMware Fusion.app/Contents/Library/vmware-vmx>, @fusion_6=true, @fusion_7=true, @fusion_8=false, @version="7.1.0">, @cap_logger=#<Log4r::Logger:0x00000101b8c200 @fullname="vagrant::capability_host::hashicorp::vagrantvmwarefusion::provider", @outputters=[], @additive=true, @name="provider", @path="vagrant::capability_host::hashicorp::vagrantvmwarefusion", @parent=#<Log4r::Logger:0x000001009da520 @fullname="vagrant", @outputters=[#<Log4r::StderrOutputter:0x00000100864b00 @mon_owner=nil, @mon_count=0, @mon_mutex=#<Mutex:0x00000100864920>, @name="stderr", @level=0, @formatter=#<Log4r::DefaultFormatter:0x0000010087f8b0 @depth=7>, @out=#<IO:<STDERR>>>], @additive=true, @name="vagrant", @path="", @parent=#<Log4r::RootLogger:0x000001009da3b8 @level=0, @outputters=[]>, @level=1, @trace=false>, @level=1, @trace=false>, @cap_host_chain=[[:vmware_fusion, #<#<Class:0x00000101b8cb10>:0x00000100a95898>]], @cap_args=[#<Vagrant::Machine: dev (HashiCorp::VagrantVMwarefusion::Provider)>], @cap_caps={:docker=>#<Vagrant::Registry:0x00000101b8c750 @items={:public_address=>#<Proc:0x00000100924310@/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/providers/docker/plugin.rb:54>, :proxy_machine=>#<Proc:0x0000010092f1e8@/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/providers/docker/plugin.rb:59>}, @results_cache={}>, :hyperv=>#<Vagrant::Registry:0x00000101b8c688 @items={:public_address=>#<Proc:0x000001011fd338@/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/providers/hyperv/plugin.rb:25>}, @results_cache={}>, :virtualbox=>#<Vagrant::Registry:0x00000101b8c5c0 @items={:forwarded_ports=>#<Proc:0x000001010a7fb0@/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/providers/virtualbox/plugin.rb:27>, :nic_mac_addresses=>#<Proc:0x000001010a7e48@/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/providers/virtualbox/plugin.rb:32>, :public_address=>#<Proc:0x00000100a22820@/opt/vagrant/embedded/gems/gems/vagrant-share-1.1.4/lib/vagrant-share.rb:39>}, @results_cache={}>, :vmware_fusion=>#<Vagrant::Registry:0x00000101b8c408 @items={:forwarded_ports=>#<Proc:0x00000101af8be0@/Users/quasiben/.vagrant.d/gems/gems/vagrant-vmware-fusion-4.0.2/lib/vagrant-vmware-fusion/plugin.rb:92>, :public_address=>#<Proc:0x00000101af8b18@/Users/quasiben/.vagrant.d/gems/gems/vagrant-vmware-fusion-4.0.2/lib/vagrant-vmware-fusion/plugin.rb:97>, :snapshot_list=>#<Proc:0x00000101af8ac8@/Users/quasiben/.vagrant.d/gems/gems/vagrant-vmware-fusion-4.0.2/lib/vagrant-vmware-fusion/plugin.rb:102>}, @results_cache={}>}>)
INFO interface: info: Bringing machine 'dev' up with 'vmware_fusion' provider...
DEBUG vmware: VM state requested. Current state: not_created
INFO batch_action: Enabling parallelization by default.
INFO batch_action: Disabling parallelization because provider doesn't support it: vmware_fusion
INFO batch_action: Batch action will parallelize: false
INFO batch_action: Starting action: #<Vagrant::Machine:0x00000102aa2c58> up {:destroy_on_error=>true, :parallel=>true, :provision_ignore_sentinel=>false, :provision_types=>nil}
INFO machine: Calling action: up on provider VMware Fusion
DEBUG environment: Attempting to acquire process-lock: machine-action-5af8e8d0e46bf4726d0a29fe0f7ac441
DEBUG environment: Attempting to acquire process-lock: dotlock
INFO environment: Acquired process lock: dotlock
INFO environment: Released process lock: dotlock
INFO environment: Acquired process lock: machine-action-5af8e8d0e46bf4726d0a29fe0f7ac441
INFO runner: Preparing hooks for middleware sequence...
INFO runner: 1 hooks defined.
INFO runner: Running action: machine_action_up #<Vagrant::Action::Builder:0x00000101a5ca60>
INFO warden: Calling IN action: VMware Middleware: Compatibility
INFO warden: Calling IN action: #<Vagrant::Action::Builtin::ConfigValidate:0x000001028b5378>
INFO warden: Calling IN action: VMware Middleware: FixOldMachineID
INFO warden: Calling IN action: VMware Middleware: CheckVMware
INFO warden: Calling IN action: VMware Middleware: SudoHelperInstall
DEBUG sudo_helper_install: Checking if the sudo helper is installed...
INFO sudo_helper: Sudo helper bin path: /Users/quasiben/.vagrant.d/gems/gems/vagrant-vmware-fusion-4.0.2/bin/vagrant_vmware_desktop_sudo_helper_wrapper_darwin_amd64
DEBUG sudo_helper_install: Sudo helper is installed.
INFO warden: Calling IN action: #<Vagrant::Action::Builtin::Call:0x000001011ccda0>
INFO runner: Preparing hooks for middleware sequence...
INFO runner: 1 hooks defined.
INFO runner: Running action: machine_action_up #<Vagrant::Action::Builder:0x00000100a8d878>
INFO warden: Calling IN action: VMware Middleware: Created
DEBUG vmware: VM state requested. Current state: not_created
INFO warden: Calling OUT action: VMware Middleware: Created
INFO runner: Preparing hooks for middleware sequence...
INFO runner: 1 hooks defined.
INFO runner: Running action: machine_action_up #<Vagrant::Action::Warden:0x00000101beed38>
INFO warden: Calling IN action: #<Proc:0x000001029d8b88@/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:94 (lambda)>
INFO warden: Calling IN action: #<Vagrant::Action::Builtin::HandleBox:0x00000101beec98>
INFO handle_box: Machine already has box. HandleBox will not run.
INFO warden: Calling IN action: VMware Middleware: Import
INFO import: VMX file not in metadata, attempting to discover...
DEBUG import: Cloning into: /Users/quasiben/.vagrant/machines/dev/vmware_fusion/7890b8d8-98e2-4cd5-a989-d65c4e0279ae
INFO import: VMX file: /Users/quasiben/.vagrant.d/boxes/1vq9-VAGRANTSLASH-trusty64/0.1.0/vmware_fusion/trusty64.vmx
INFO interface: info: Cloning VMware VM: '1vq9/trusty64'. This can take some time...
INFO interface: info: ==> dev: Cloning VMware VM: '1vq9/trusty64'. This can take some time...
INFO vmware_driver: Cloning VM to /Users/quasiben/.vagrant/machines/dev/vmware_fusion/7890b8d8-98e2-4cd5-a989-d65c4e0279ae
DEBUG vmware_driver: Copying: metadata.json
DEBUG vmware_driver: Copying: trusty64-s001.vmdk
DEBUG vmware_driver: Copying: trusty64-s002.vmdk
DEBUG vmware_driver: Copying: trusty64-s003.vmdk
DEBUG vmware_driver: Copying: trusty64-s004.vmdk
DEBUG vmware_driver: Copying: trusty64-s005.vmdk
DEBUG vmware_driver: Copying: trusty64-s006.vmdk
DEBUG vmware_driver: Copying: trusty64-s007.vmdk
DEBUG vmware_driver: Copying: trusty64-s008.vmdk
DEBUG vmware_driver: Copying: trusty64-s009.vmdk
DEBUG vmware_driver: Copying: trusty64-s010.vmdk
DEBUG vmware_driver: Copying: trusty64-s011.vmdk
DEBUG vmware_driver: Copying: trusty64-s012.vmdk
DEBUG vmware_driver: Copying: trusty64.nvram
DEBUG vmware_driver: Copying: trusty64.vmdk
DEBUG vmware_driver: Copying: trusty64.vmsd
DEBUG vmware_driver: Copying: trusty64.vmx
DEBUG vmware_driver: Copying: trusty64.vmxf
INFO vmware_driver: VMX file: /Users/quasiben/.vagrant/machines/dev/vmware_fusion/7890b8d8-98e2-4cd5-a989-d65c4e0279ae/trusty64.vmx
INFO vmware_driver: Looking for VMware Fusion: /Applications/VMware Fusion.app
INFO vmware_driver: VMware Fusion path: #<Pathname:/Applications/VMware Fusion.app>
DEBUG vmware_driver: Attempting to read VMware version...
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmware-vmx", "-v"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command is setuid/setgid, clearing DYLD_LIBRARY_PATH
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr:
VMware Fusion Information:
VMware Fusion 7.1.0 build-2314774 Release
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO vmware_driver: Detected VMware version: 7.1.0
DEBUG vmware_driver: service starter path: /Applications/VMware Fusion.app/Contents/Library/services/Open VMware Fusion Services
DEBUG vmware_driver: vmnet-cli path: /Applications/VMware Fusion.app/Contents/Library/vmnet-cli
INFO vmware_driver: Reading VMX data...
DEBUG vmware_driver: - .encoding = UTF-8
DEBUG vmware_driver: - config.version = 8
DEBUG vmware_driver: - virtualhw.version = 10
DEBUG vmware_driver: - vcpu.hotadd = TRUE
DEBUG vmware_driver: - scsi0.present = TRUE
DEBUG vmware_driver: - scsi0.virtualdev = lsilogic
DEBUG vmware_driver: - sata0.present = TRUE
DEBUG vmware_driver: - memsize = 1024
DEBUG vmware_driver: - mem.hotadd = TRUE
DEBUG vmware_driver: - scsi0:0.present = TRUE
DEBUG vmware_driver: - scsi0:0.filename = trusty64.vmdk
DEBUG vmware_driver: - sata0:1.present = TRUE
DEBUG vmware_driver: - sata0:1.autodetect = TRUE
DEBUG vmware_driver: - sata0:1.devicetype = cdrom-image
DEBUG vmware_driver: - sata0:1.startconnected = FALSE
DEBUG vmware_driver: - ethernet0.present = TRUE
DEBUG vmware_driver: - ethernet0.connectiontype = nat
DEBUG vmware_driver: - ethernet0.virtualdev = e1000
DEBUG vmware_driver: - ethernet0.wakeonpcktrcv = FALSE
DEBUG vmware_driver: - ethernet0.addresstype = generated
DEBUG vmware_driver: - ethernet0.linkstatepropagation.enable = TRUE
DEBUG vmware_driver: - usb.present = TRUE
DEBUG vmware_driver: - ehci.present = TRUE
DEBUG vmware_driver: - ehci.pcislotnumber = 35
DEBUG vmware_driver: - sound.present = TRUE
DEBUG vmware_driver: - sound.filename = -1
DEBUG vmware_driver: - sound.autodetect = TRUE
DEBUG vmware_driver: - mks.enable3d = TRUE
DEBUG vmware_driver: - serial0.present = TRUE
DEBUG vmware_driver: - serial0.filetype = thinprint
DEBUG vmware_driver: - pcibridge0.present = TRUE
DEBUG vmware_driver: - pcibridge4.present = TRUE
DEBUG vmware_driver: - pcibridge4.virtualdev = pcieRootPort
DEBUG vmware_driver: - pcibridge4.functions = 8
DEBUG vmware_driver: - pcibridge5.present = TRUE
DEBUG vmware_driver: - pcibridge5.virtualdev = pcieRootPort
DEBUG vmware_driver: - pcibridge5.functions = 8
DEBUG vmware_driver: - pcibridge6.present = TRUE
DEBUG vmware_driver: - pcibridge6.virtualdev = pcieRootPort
DEBUG vmware_driver: - pcibridge6.functions = 8
DEBUG vmware_driver: - pcibridge7.present = TRUE
DEBUG vmware_driver: - pcibridge7.virtualdev = pcieRootPort
DEBUG vmware_driver: - pcibridge7.functions = 8
DEBUG vmware_driver: - vmci0.present = TRUE
DEBUG vmware_driver: - hpet0.present = TRUE
DEBUG vmware_driver: - usb.vbluetooth.startconnected = TRUE
DEBUG vmware_driver: - tools.synctime = TRUE
DEBUG vmware_driver: - displayname = trusty64
DEBUG vmware_driver: - guestos = ubuntu-64
DEBUG vmware_driver: - nvram = trusty64.nvram
DEBUG vmware_driver: - virtualhw.productcompatibility = hosted
DEBUG vmware_driver: - tools.upgrade.policy = upgradeAtPowerCycle
DEBUG vmware_driver: - powertype.poweroff = soft
DEBUG vmware_driver: - powertype.poweron = soft
DEBUG vmware_driver: - powertype.suspend = soft
DEBUG vmware_driver: - powertype.reset = soft
DEBUG vmware_driver: - extendedconfigfile = trusty64.vmxf
DEBUG vmware_driver: - sata0:1.filename = /Applications/VMware Fusion.app/Contents/Library/isoimages/linux.iso
DEBUG vmware_driver: - uuid.bios = 56 4d 4b b0 00 29 29 c2-4f 9c 63 f0 4f 67 55 52
DEBUG vmware_driver: - uuid.location = 56 4d 4b b0 00 29 29 c2-4f 9c 63 f0 4f 67 55 52
DEBUG vmware_driver: - replay.supported = FALSE
DEBUG vmware_driver: - replay.filename =
DEBUG vmware_driver: - scsi0:0.redo =
DEBUG vmware_driver: - pcibridge0.pcislotnumber = 17
DEBUG vmware_driver: - pcibridge4.pcislotnumber = 21
DEBUG vmware_driver: - pcibridge5.pcislotnumber = 22
DEBUG vmware_driver: - pcibridge6.pcislotnumber = 23
DEBUG vmware_driver: - pcibridge7.pcislotnumber = 24
DEBUG vmware_driver: - scsi0.pcislotnumber = 16
DEBUG vmware_driver: - usb.pcislotnumber = 32
DEBUG vmware_driver: - ethernet0.pcislotnumber = 33
DEBUG vmware_driver: - sound.pcislotnumber = 34
DEBUG vmware_driver: - vmci0.pcislotnumber = 36
DEBUG vmware_driver: - sata0.pcislotnumber = 37
DEBUG vmware_driver: - ethernet0.generatedaddress = 00:0c:29:67:55:52
DEBUG vmware_driver: - ethernet0.generatedaddressoffset = 0
DEBUG vmware_driver: - vmci0.id = 1332172114
DEBUG vmware_driver: - monitor.phys_bits_used = 40
DEBUG vmware_driver: - vmotion.checkpointfbsize = 134217728
DEBUG vmware_driver: - cleanshutdown = TRUE
DEBUG vmware_driver: - softpoweroff = TRUE
DEBUG vmware_driver: - usb:1.speed = 2
DEBUG vmware_driver: - usb:1.present = TRUE
DEBUG vmware_driver: - usb:1.devicetype = hub
DEBUG vmware_driver: - usb:1.port = 1
DEBUG vmware_driver: - usb:1.parent = -1
DEBUG vmware_driver: - toolsinstallmanager.updatecounter = 3
DEBUG vmware_driver: - filesearchpath = /Users/hiroyuki/Documents/Virtual Machines.localized/trusty64.vmwarevm;.
DEBUG vmware_driver: - bios.bootorder = CDROM
DEBUG vmware_driver: - floppy0.present = FALSE
DEBUG vmware_driver: - usb:0.present = TRUE
DEBUG vmware_driver: - usb:0.devicetype = hid
DEBUG vmware_driver: - usb:0.port = 0
DEBUG vmware_driver: - usb:0.parent = -1
DEBUG vmware_driver: - tools.remindinstall = FALSE
INFO vmware_driver: Modifying VMX data...
DEBUG vmware_driver: - SET .encoding = "UTF-8"
DEBUG vmware_driver: - SET bios.bootorder = "CDROM"
DEBUG vmware_driver: - SET cleanshutdown = "TRUE"
DEBUG vmware_driver: - SET config.version = "8"
DEBUG vmware_driver: - SET displayname = "trusty64"
DEBUG vmware_driver: - SET ehci.pcislotnumber = "35"
DEBUG vmware_driver: - SET ehci.present = "TRUE"
DEBUG vmware_driver: - SET ethernet0.addresstype = "generated"
DEBUG vmware_driver: - SET ethernet0.connectiontype = "nat"
DEBUG vmware_driver: - SET ethernet0.generatedaddress = "00:0c:29:67:55:52"
DEBUG vmware_driver: - SET ethernet0.generatedaddressoffset = "0"
DEBUG vmware_driver: - SET ethernet0.linkstatepropagation.enable = "TRUE"
DEBUG vmware_driver: - SET ethernet0.pcislotnumber = "33"
DEBUG vmware_driver: - SET ethernet0.present = "TRUE"
DEBUG vmware_driver: - SET ethernet0.virtualdev = "e1000"
DEBUG vmware_driver: - SET ethernet0.wakeonpcktrcv = "FALSE"
DEBUG vmware_driver: - SET extendedconfigfile = "trusty64.vmxf"
DEBUG vmware_driver: - SET filesearchpath = "/Users/hiroyuki/Documents/Virtual Machines.localized/trusty64.vmwarevm;."
DEBUG vmware_driver: - SET floppy0.present = "FALSE"
DEBUG vmware_driver: - SET guestos = "ubuntu-64"
DEBUG vmware_driver: - SET hpet0.present = "TRUE"
DEBUG vmware_driver: - SET mem.hotadd = "TRUE"
DEBUG vmware_driver: - SET memsize = "1024"
DEBUG vmware_driver: - SET mks.enable3d = "TRUE"
DEBUG vmware_driver: - SET monitor.phys_bits_used = "40"
DEBUG vmware_driver: - SET msg.autoanswer = "true"
DEBUG vmware_driver: - SET nvram = "trusty64.nvram"
DEBUG vmware_driver: - SET pcibridge0.pcislotnumber = "17"
DEBUG vmware_driver: - SET pcibridge0.present = "TRUE"
DEBUG vmware_driver: - SET pcibridge4.functions = "8"
DEBUG vmware_driver: - SET pcibridge4.pcislotnumber = "21"
DEBUG vmware_driver: - SET pcibridge4.present = "TRUE"
DEBUG vmware_driver: - SET pcibridge4.virtualdev = "pcieRootPort"
DEBUG vmware_driver: - SET pcibridge5.functions = "8"
DEBUG vmware_driver: - SET pcibridge5.pcislotnumber = "22"
DEBUG vmware_driver: - SET pcibridge5.present = "TRUE"
DEBUG vmware_driver: - SET pcibridge5.virtualdev = "pcieRootPort"
DEBUG vmware_driver: - SET pcibridge6.functions = "8"
DEBUG vmware_driver: - SET pcibridge6.pcislotnumber = "23"
DEBUG vmware_driver: - SET pcibridge6.present = "TRUE"
DEBUG vmware_driver: - SET pcibridge6.virtualdev = "pcieRootPort"
DEBUG vmware_driver: - SET pcibridge7.functions = "8"
DEBUG vmware_driver: - SET pcibridge7.pcislotnumber = "24"
DEBUG vmware_driver: - SET pcibridge7.present = "TRUE"
DEBUG vmware_driver: - SET pcibridge7.virtualdev = "pcieRootPort"
DEBUG vmware_driver: - SET powertype.poweroff = "soft"
DEBUG vmware_driver: - SET powertype.poweron = "soft"
DEBUG vmware_driver: - SET powertype.reset = "soft"
DEBUG vmware_driver: - SET powertype.suspend = "soft"
DEBUG vmware_driver: - SET replay.filename = ""
DEBUG vmware_driver: - SET replay.supported = "FALSE"
DEBUG vmware_driver: - SET sata0.pcislotnumber = "37"
DEBUG vmware_driver: - SET sata0.present = "TRUE"
DEBUG vmware_driver: - SET sata0:1.autodetect = "TRUE"
DEBUG vmware_driver: - SET sata0:1.devicetype = "cdrom-image"
DEBUG vmware_driver: - SET sata0:1.filename = "/Applications/VMware Fusion.app/Contents/Library/isoimages/linux.iso"
DEBUG vmware_driver: - SET sata0:1.present = "TRUE"
DEBUG vmware_driver: - SET sata0:1.startconnected = "FALSE"
DEBUG vmware_driver: - SET scsi0.pcislotnumber = "16"
DEBUG vmware_driver: - SET scsi0.present = "TRUE"
DEBUG vmware_driver: - SET scsi0.virtualdev = "lsilogic"
DEBUG vmware_driver: - SET scsi0:0.filename = "trusty64.vmdk"
DEBUG vmware_driver: - SET scsi0:0.present = "TRUE"
DEBUG vmware_driver: - SET scsi0:0.redo = ""
DEBUG vmware_driver: - SET serial0.filetype = "thinprint"
DEBUG vmware_driver: - SET serial0.present = "TRUE"
DEBUG vmware_driver: - SET softpoweroff = "TRUE"
DEBUG vmware_driver: - SET sound.autodetect = "TRUE"
DEBUG vmware_driver: - SET sound.filename = "-1"
DEBUG vmware_driver: - SET sound.pcislotnumber = "34"
DEBUG vmware_driver: - SET sound.present = "TRUE"
DEBUG vmware_driver: - SET tools.remindinstall = "FALSE"
DEBUG vmware_driver: - SET tools.synctime = "TRUE"
DEBUG vmware_driver: - SET tools.upgrade.policy = "upgradeAtPowerCycle"
DEBUG vmware_driver: - SET toolsinstallmanager.updatecounter = "3"
DEBUG vmware_driver: - SET usb.pcislotnumber = "32"
DEBUG vmware_driver: - SET usb.present = "TRUE"
DEBUG vmware_driver: - SET usb.vbluetooth.startconnected = "TRUE"
DEBUG vmware_driver: - SET usb:0.devicetype = "hid"
DEBUG vmware_driver: - SET usb:0.parent = "-1"
DEBUG vmware_driver: - SET usb:0.port = "0"
DEBUG vmware_driver: - SET usb:0.present = "TRUE"
DEBUG vmware_driver: - SET usb:1.devicetype = "hub"
DEBUG vmware_driver: - SET usb:1.parent = "-1"
DEBUG vmware_driver: - SET usb:1.port = "1"
DEBUG vmware_driver: - SET usb:1.present = "TRUE"
DEBUG vmware_driver: - SET usb:1.speed = "2"
DEBUG vmware_driver: - SET uuid.action = "create"
DEBUG vmware_driver: - SET uuid.bios = "56 4d 4b b0 00 29 29 c2-4f 9c 63 f0 4f 67 55 52"
DEBUG vmware_driver: - SET uuid.location = "56 4d 4b b0 00 29 29 c2-4f 9c 63 f0 4f 67 55 52"
DEBUG vmware_driver: - SET vcpu.hotadd = "TRUE"
DEBUG vmware_driver: - SET virtualhw.productcompatibility = "hosted"
DEBUG vmware_driver: - SET virtualhw.version = "10"
DEBUG vmware_driver: - SET vmci0.id = "1332172114"
DEBUG vmware_driver: - SET vmci0.pcislotnumber = "36"
DEBUG vmware_driver: - SET vmci0.present = "TRUE"
DEBUG vmware_driver: - SET vmotion.checkpointfbsize = "134217728"
INFO machine: New machine ID: "/Users/quasiben/.vagrant/machines/dev/vmware_fusion/7890b8d8-98e2-4cd5-a989-d65c4e0279ae/trusty64.vmx"
DEBUG vmware: Re-initializing driver for new ID: "/Users/quasiben/.vagrant/machines/dev/vmware_fusion/7890b8d8-98e2-4cd5-a989-d65c4e0279ae/trusty64.vmx"
INFO vmware_driver: VMX file: /Users/quasiben/.vagrant/machines/dev/vmware_fusion/7890b8d8-98e2-4cd5-a989-d65c4e0279ae/trusty64.vmx
INFO vmware_driver: Looking for VMware Fusion: /Applications/VMware Fusion.app
INFO vmware_driver: VMware Fusion path: #<Pathname:/Applications/VMware Fusion.app>
DEBUG vmware_driver: Attempting to read VMware version...
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmware-vmx", "-v"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command is setuid/setgid, clearing DYLD_LIBRARY_PATH
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr:
VMware Fusion Information:
VMware Fusion 7.1.0 build-2314774 Release
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 31999
DEBUG subprocess: Exit status: 0
INFO vmware_driver: Detected VMware version: 7.1.0
DEBUG vmware_driver: service starter path: /Applications/VMware Fusion.app/Contents/Library/services/Open VMware Fusion Services
DEBUG vmware_driver: vmnet-cli path: /Applications/VMware Fusion.app/Contents/Library/vmnet-cli
INFO warden: Calling IN action: VMware Middleware: SetDisplayName
INFO vmx_modify: Setting the default display name: quasiben: dev
INFO vmware_driver: Reading VMX data...
DEBUG vmware_driver: - .encoding = UTF-8
DEBUG vmware_driver: - bios.bootorder = CDROM
DEBUG vmware_driver: - cleanshutdown = TRUE
DEBUG vmware_driver: - config.version = 8
DEBUG vmware_driver: - displayname = trusty64
DEBUG vmware_driver: - ehci.pcislotnumber = 35
DEBUG vmware_driver: - ehci.present = TRUE
DEBUG vmware_driver: - ethernet0.addresstype = generated
DEBUG vmware_driver: - ethernet0.connectiontype = nat
DEBUG vmware_driver: - ethernet0.generatedaddress = 00:0c:29:67:55:52
DEBUG vmware_driver: - ethernet0.generatedaddressoffset = 0
DEBUG vmware_driver: - ethernet0.linkstatepropagation.enable = TRUE
DEBUG vmware_driver: - ethernet0.pcislotnumber = 33
DEBUG vmware_driver: - ethernet0.present = TRUE
DEBUG vmware_driver: - ethernet0.virtualdev = e1000
DEBUG vmware_driver: - ethernet0.wakeonpcktrcv = FALSE
DEBUG vmware_driver: - extendedconfigfile = trusty64.vmxf
DEBUG vmware_driver: - filesearchpath = /Users/hiroyuki/Documents/Virtual Machines.localized/trusty64.vmwarevm;.
DEBUG vmware_driver: - floppy0.present = FALSE
DEBUG vmware_driver: - guestos = ubuntu-64
DEBUG vmware_driver: - hpet0.present = TRUE
DEBUG vmware_driver: - mem.hotadd = TRUE
DEBUG vmware_driver: - memsize = 1024
DEBUG vmware_driver: - mks.enable3d = TRUE
DEBUG vmware_driver: - monitor.phys_bits_used = 40
DEBUG vmware_driver: - msg.autoanswer = true
DEBUG vmware_driver: - nvram = trusty64.nvram
DEBUG vmware_driver: - pcibridge0.pcislotnumber = 17
DEBUG vmware_driver: - pcibridge0.present = TRUE
DEBUG vmware_driver: - pcibridge4.functions = 8
DEBUG vmware_driver: - pcibridge4.pcislotnumber = 21
DEBUG vmware_driver: - pcibridge4.present = TRUE
DEBUG vmware_driver: - pcibridge4.virtualdev = pcieRootPort
DEBUG vmware_driver: - pcibridge5.functions = 8
DEBUG vmware_driver: - pcibridge5.pcislotnumber = 22
DEBUG vmware_driver: - pcibridge5.present = TRUE
DEBUG vmware_driver: - pcibridge5.virtualdev = pcieRootPort
DEBUG vmware_driver: - pcibridge6.functions = 8
DEBUG vmware_driver: - pcibridge6.pcislotnumber = 23
DEBUG vmware_driver: - pcibridge6.present = TRUE
DEBUG vmware_driver: - pcibridge6.virtualdev = pcieRootPort
DEBUG vmware_driver: - pcibridge7.functions = 8
DEBUG vmware_driver: - pcibridge7.pcislotnumber = 24
DEBUG vmware_driver: - pcibridge7.present = TRUE
DEBUG vmware_driver: - pcibridge7.virtualdev = pcieRootPort
DEBUG vmware_driver: - powertype.poweroff = soft
DEBUG vmware_driver: - powertype.poweron = soft
DEBUG vmware_driver: - powertype.reset = soft
DEBUG vmware_driver: - powertype.suspend = soft
DEBUG vmware_driver: - replay.filename =
DEBUG vmware_driver: - replay.supported = FALSE
DEBUG vmware_driver: - sata0.pcislotnumber = 37
DEBUG vmware_driver: - sata0.present = TRUE
DEBUG vmware_driver: - sata0:1.autodetect = TRUE
DEBUG vmware_driver: - sata0:1.devicetype = cdrom-image
DEBUG vmware_driver: - sata0:1.filename = /Applications/VMware Fusion.app/Contents/Library/isoimages/linux.iso
DEBUG vmware_driver: - sata0:1.present = TRUE
DEBUG vmware_driver: - sata0:1.startconnected = FALSE
DEBUG vmware_driver: - scsi0.pcislotnumber = 16
DEBUG vmware_driver: - scsi0.present = TRUE
DEBUG vmware_driver: - scsi0.virtualdev = lsilogic
DEBUG vmware_driver: - scsi0:0.filename = trusty64.vmdk
DEBUG vmware_driver: - scsi0:0.present = TRUE
DEBUG vmware_driver: - scsi0:0.redo =
DEBUG vmware_driver: - serial0.filetype = thinprint
DEBUG vmware_driver: - serial0.present = TRUE
DEBUG vmware_driver: - softpoweroff = TRUE
DEBUG vmware_driver: - sound.autodetect = TRUE
DEBUG vmware_driver: - sound.filename = -1
DEBUG vmware_driver: - sound.pcislotnumber = 34
DEBUG vmware_driver: - sound.present = TRUE
DEBUG vmware_driver: - tools.remindinstall = FALSE
DEBUG vmware_driver: - tools.synctime = TRUE
DEBUG vmware_driver: - tools.upgrade.policy = upgradeAtPowerCycle
DEBUG vmware_driver: - toolsinstallmanager.updatecounter = 3
DEBUG vmware_driver: - usb.pcislotnumber = 32
DEBUG vmware_driver: - usb.present = TRUE
DEBUG vmware_driver: - usb.vbluetooth.startconnected = TRUE
DEBUG vmware_driver: - usb:0.devicetype = hid
DEBUG vmware_driver: - usb:0.parent = -1
DEBUG vmware_driver: - usb:0.port = 0
DEBUG vmware_driver: - usb:0.present = TRUE
DEBUG vmware_driver: - usb:1.devicetype = hub
DEBUG vmware_driver: - usb:1.parent = -1
DEBUG vmware_driver: - usb:1.port = 1
DEBUG vmware_driver: - usb:1.present = TRUE
DEBUG vmware_driver: - usb:1.speed = 2
DEBUG vmware_driver: - uuid.action = create
DEBUG vmware_driver: - uuid.bios = 56 4d 4b b0 00 29 29 c2-4f 9c 63 f0 4f 67 55 52
DEBUG vmware_driver: - uuid.location = 56 4d 4b b0 00 29 29 c2-4f 9c 63 f0 4f 67 55 52
DEBUG vmware_driver: - vcpu.hotadd = TRUE
DEBUG vmware_driver: - virtualhw.productcompatibility = hosted
DEBUG vmware_driver: - virtualhw.version = 10
DEBUG vmware_driver: - vmci0.id = 1332172114
DEBUG vmware_driver: - vmci0.pcislotnumber = 36
DEBUG vmware_driver: - vmci0.present = TRUE
DEBUG vmware_driver: - vmotion.checkpointfbsize = 134217728
INFO vmware_driver: Modifying VMX data...
DEBUG vmware_driver: - SET .encoding = "UTF-8"
DEBUG vmware_driver: - SET bios.bootorder = "CDROM"
DEBUG vmware_driver: - SET cleanshutdown = "TRUE"
DEBUG vmware_driver: - SET config.version = "8"
DEBUG vmware_driver: - SET displayname = "quasiben: dev"
DEBUG vmware_driver: - SET ehci.pcislotnumber = "35"
DEBUG vmware_driver: - SET ehci.present = "TRUE"
DEBUG vmware_driver: - SET ethernet0.addresstype = "generated"
DEBUG vmware_driver: - SET ethernet0.connectiontype = "nat"
DEBUG vmware_driver: - SET ethernet0.generatedaddress = "00:0c:29:67:55:52"
DEBUG vmware_driver: - SET ethernet0.generatedaddressoffset = "0"
DEBUG vmware_driver: - SET ethernet0.linkstatepropagation.enable = "TRUE"
DEBUG vmware_driver: - SET ethernet0.pcislotnumber = "33"
DEBUG vmware_driver: - SET ethernet0.present = "TRUE"
DEBUG vmware_driver: - SET ethernet0.virtualdev = "e1000"
DEBUG vmware_driver: - SET ethernet0.wakeonpcktrcv = "FALSE"
DEBUG vmware_driver: - SET extendedconfigfile = "trusty64.vmxf"
DEBUG vmware_driver: - SET filesearchpath = "/Users/hiroyuki/Documents/Virtual Machines.localized/trusty64.vmwarevm;."
DEBUG vmware_driver: - SET floppy0.present = "FALSE"
DEBUG vmware_driver: - SET guestos = "ubuntu-64"
DEBUG vmware_driver: - SET hpet0.present = "TRUE"
DEBUG vmware_driver: - SET mem.hotadd = "TRUE"
DEBUG vmware_driver: - SET memsize = "1024"
DEBUG vmware_driver: - SET mks.enable3d = "TRUE"
DEBUG vmware_driver: - SET monitor.phys_bits_used = "40"
DEBUG vmware_driver: - SET msg.autoanswer = "true"
DEBUG vmware_driver: - SET nvram = "trusty64.nvram"
DEBUG vmware_driver: - SET pcibridge0.pcislotnumber = "17"
DEBUG vmware_driver: - SET pcibridge0.present = "TRUE"
DEBUG vmware_driver: - SET pcibridge4.functions = "8"
DEBUG vmware_driver: - SET pcibridge4.pcislotnumber = "21"
DEBUG vmware_driver: - SET pcibridge4.present = "TRUE"
DEBUG vmware_driver: - SET pcibridge4.virtualdev = "pcieRootPort"
DEBUG vmware_driver: - SET pcibridge5.functions = "8"
DEBUG vmware_driver: - SET pcibridge5.pcislotnumber = "22"
DEBUG vmware_driver: - SET pcibridge5.present = "TRUE"
DEBUG vmware_driver: - SET pcibridge5.virtualdev = "pcieRootPort"
DEBUG vmware_driver: - SET pcibridge6.functions = "8"
DEBUG vmware_driver: - SET pcibridge6.pcislotnumber = "23"
DEBUG vmware_driver: - SET pcibridge6.present = "TRUE"
DEBUG vmware_driver: - SET pcibridge6.virtualdev = "pcieRootPort"
DEBUG vmware_driver: - SET pcibridge7.functions = "8"
DEBUG vmware_driver: - SET pcibridge7.pcislotnumber = "24"
DEBUG vmware_driver: - SET pcibridge7.present = "TRUE"
DEBUG vmware_driver: - SET pcibridge7.virtualdev = "pcieRootPort"
DEBUG vmware_driver: - SET powertype.poweroff = "soft"
DEBUG vmware_driver: - SET powertype.poweron = "soft"
DEBUG vmware_driver: - SET powertype.reset = "soft"
DEBUG vmware_driver: - SET powertype.suspend = "soft"
DEBUG vmware_driver: - SET replay.filename = ""
DEBUG vmware_driver: - SET replay.supported = "FALSE"
DEBUG vmware_driver: - SET sata0.pcislotnumber = "37"
DEBUG vmware_driver: - SET sata0.present = "TRUE"
DEBUG vmware_driver: - SET sata0:1.autodetect = "TRUE"
DEBUG vmware_driver: - SET sata0:1.devicetype = "cdrom-image"
DEBUG vmware_driver: - SET sata0:1.filename = "/Applications/VMware Fusion.app/Contents/Library/isoimages/linux.iso"
DEBUG vmware_driver: - SET sata0:1.present = "TRUE"
DEBUG vmware_driver: - SET sata0:1.startconnected = "FALSE"
DEBUG vmware_driver: - SET scsi0.pcislotnumber = "16"
DEBUG vmware_driver: - SET scsi0.present = "TRUE"
DEBUG vmware_driver: - SET scsi0.virtualdev = "lsilogic"
DEBUG vmware_driver: - SET scsi0:0.filename = "trusty64.vmdk"
DEBUG vmware_driver: - SET scsi0:0.present = "TRUE"
DEBUG vmware_driver: - SET scsi0:0.redo = ""
DEBUG vmware_driver: - SET serial0.filetype = "thinprint"
DEBUG vmware_driver: - SET serial0.present = "TRUE"
DEBUG vmware_driver: - SET softpoweroff = "TRUE"
DEBUG vmware_driver: - SET sound.autodetect = "TRUE"
DEBUG vmware_driver: - SET sound.filename = "-1"
DEBUG vmware_driver: - SET sound.pcislotnumber = "34"
DEBUG vmware_driver: - SET sound.present = "TRUE"
DEBUG vmware_driver: - SET tools.remindinstall = "FALSE"
DEBUG vmware_driver: - SET tools.synctime = "TRUE"
DEBUG vmware_driver: - SET tools.upgrade.policy = "upgradeAtPowerCycle"
DEBUG vmware_driver: - SET toolsinstallmanager.updatecounter = "3"
DEBUG vmware_driver: - SET usb.pcislotnumber = "32"
DEBUG vmware_driver: - SET usb.present = "TRUE"
DEBUG vmware_driver: - SET usb.vbluetooth.startconnected = "TRUE"
DEBUG vmware_driver: - SET usb:0.devicetype = "hid"
DEBUG vmware_driver: - SET usb:0.parent = "-1"
DEBUG vmware_driver: - SET usb:0.port = "0"
DEBUG vmware_driver: - SET usb:0.present = "TRUE"
DEBUG vmware_driver: - SET usb:1.devicetype = "hub"
DEBUG vmware_driver: - SET usb:1.parent = "-1"
DEBUG vmware_driver: - SET usb:1.port = "1"
DEBUG vmware_driver: - SET usb:1.present = "TRUE"
DEBUG vmware_driver: - SET usb:1.speed = "2"
DEBUG vmware_driver: - SET uuid.action = "create"
DEBUG vmware_driver: - SET uuid.bios = "56 4d 4b b0 00 29 29 c2-4f 9c 63 f0 4f 67 55 52"
DEBUG vmware_driver: - SET uuid.location = "56 4d 4b b0 00 29 29 c2-4f 9c 63 f0 4f 67 55 52"
DEBUG vmware_driver: - SET vcpu.hotadd = "TRUE"
DEBUG vmware_driver: - SET virtualhw.productcompatibility = "hosted"
DEBUG vmware_driver: - SET virtualhw.version = "10"
DEBUG vmware_driver: - SET vmci0.id = "1332172114"
DEBUG vmware_driver: - SET vmci0.pcislotnumber = "36"
DEBUG vmware_driver: - SET vmci0.present = "TRUE"
DEBUG vmware_driver: - SET vmotion.checkpointfbsize = "134217728"
INFO warden: Calling IN action: VMware Middleware: Compatibility
INFO warden: Calling IN action: VMware Middleware: FixOldMachineID
INFO warden: Calling IN action: VMware Middleware: SudoHelperInstall
DEBUG sudo_helper_install: Checking if the sudo helper is installed...
INFO sudo_helper: Sudo helper bin path: /Users/quasiben/.vagrant.d/gems/gems/vagrant-vmware-fusion-4.0.2/bin/vagrant_vmware_desktop_sudo_helper_wrapper_darwin_amd64
DEBUG sudo_helper_install: Sudo helper is installed.
INFO warden: Calling IN action: #<Vagrant::Action::Builtin::BoxCheckOutdated:0x00000102948178>
INFO interface: output: Checking if box '1vq9/trusty64' is up to date...
INFO interface: output: ==> dev: Checking if box '1vq9/trusty64' is up to date...
INFO downloader: Downloader starting download:
INFO downloader: -- Source: https://atlas.hashicorp.com/1vq9/trusty64
INFO downloader: -- Destination: /var/folders/1t/t94brwgx7sjcn8jgz4gr3_c00000gq/T/vagrant20151111-6218-12skib8
INFO subprocess: Starting process: ["/opt/vagrant/embedded/bin/curl", "-q", "--fail", "--location", "--max-redirs", "10", "--user-agent", "Vagrant/1.7.4", "-H", "Accept: application/json", "--output", "/var/folders/1t/t94brwgx7sjcn8jgz4gr3_c00000gq/T/vagrant20151111-6218-12skib8", "https://atlas.hashicorp.com/1vq9/trusty64"]
INFO subprocess: Command in the installer. Specifying DYLD_LIBRARY_PATH...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: % Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
DEBUG subprocess: stderr:
100 113 100 113 0 0 164 0 --:--:-- --:--:-- --:--:-- 719
DEBUG subprocess: stderr:
100 590 100 590 0 0 775 0 --:--:-- --:--:-- --:--:-- 775
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO warden: Calling IN action: #<Vagrant::Action::Builtin::Call:0x000001029aaee0>
INFO runner: Preparing hooks for middleware sequence...
INFO runner: 1 hooks defined.
INFO runner: Running action: machine_action_up #<Vagrant::Action::Builder:0x00000102939a60>
INFO warden: Calling IN action: VMware Middleware: Running
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmrun", "list"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stdout: Total running VMs: 0
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 31999
DEBUG subprocess: Exit status: 0
DEBUG vmware: VM state requested. Current state: not_running
INFO warden: Calling OUT action: VMware Middleware: Running
INFO runner: Preparing hooks for middleware sequence...
INFO runner: 1 hooks defined.
INFO runner: Running action: machine_action_up #<Vagrant::Action::Warden:0x000001029e2520>
INFO warden: Calling IN action: #<Proc:0x00000102a7aa50@/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:94 (lambda)>
INFO warden: Calling IN action: VMware Middleware: PruneForwardedPorts
INFO prune_forwarded_ports: Pruning forwarded ports...
DEBUG environment: Attempting to acquire process-lock: vmware-network
DEBUG environment: Attempting to acquire process-lock: dotlock
INFO environment: Acquired process lock: dotlock
INFO environment: Released process lock: dotlock
INFO environment: Acquired process lock: vmware-network
INFO subprocess: Starting process: ["/Users/quasiben/.vagrant.d/gems/gems/vagrant-vmware-fusion-4.0.2/bin/vagrant_vmware_desktop_sudo_helper_wrapper_darwin_amd64", "prune-forwarded-ports", "/var/folders/1t/t94brwgx7sjcn8jgz4gr3_c00000gq/T/vagrant-sudo-helper20151111-6218-cvhkv8"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command is setuid/setgid, clearing DYLD_LIBRARY_PATH
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: INFO global: Vagrant version: 1.7.4
INFO global: Ruby version: 2.0.0
INFO global: RubyGems version: 2.0.14
DEBUG subprocess: stderr: INFO global: VAGRANT_LOG="debug"
INFO global: VAGRANT_OLD_ENV_SPARK_HOME="/Users/quasiben/Research/GitClones/spark"
INFO global: VAGRANT_OLD_ENV_HOME="/Users/quasiben"
INFO global: VAGRANT_OLD_ENV__="/usr/local/bin/vagrant"
DEBUG subprocess: stderr: INFO global: VAGRANT_OLD_ENV_XPC_FLAGS="0x0"
INFO global: VAGRANT_INSTALLER_VERSION="2"
INFO global: VAGRANT_OLD_ENV_VAGRANT_LOG="debug"
INFO global: VAGRANT_OLD_ENV_TMPDIR="/var/folders/1t/t94brwgx7sjcn8jgz4gr3_c00000gq/T/"
INFO global: VAGRANT_OLD_ENV_Apple_PubSub_Socket_Render="/private/tmp/com.apple.launchd.KW13obTzd8/Render"
INFO global: VAGRANT_OLD_ENV_JAVA_HOME="/Library/Java/JavaVirtualMachines/jdk1.7.0_45.jdk/Contents/Home"
INFO global: VAGRANT_OLD_ENV_ACHE_HOME="/Users/quasiben/anaconda/envs/memex-explorer/lib/python2.7/site-packages/ache/"
INFO global: VAGRANT_OLD_ENV_CONDA_ENV_PATH="/Users/quasiben/anaconda/envs/clusto"
INFO global: VAGRANT_OLD_ENV_PYTHONPATH="/Users/quasiben/Research/ContinuumDev/GitRepo/conda-cluster/::/Users/quasiben/Research/GitClones/spark/python"
INFO global: VAGRANT_OLD_ENV_PATH="/Users/quasiben/anaconda/envs/clusto/bin:/usr/local/bin:/usr/local/heroku/bin:/Users/quasiben/google-cloud-sdk/bin:/usr/local/sbin:/Users/quasiben/.cabal/bin/:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/texbin:/Users/quasiben/Research/ContinuumDev/GitRepo/libdynd/build"
INFO global: VAGRANT_OLD_ENV_PWD="/Users/quasiben"
INFO global: VAGRANT_OLD_ENV_ITERM_PROFILE="Default"
DEBUG subprocess: stderr: INFO global: VAGRANT_OLD_ENV_JDK_HOME="/Library/Java/JavaVirtualMachines/jdk1.7.0_45.jdk/Contents/Home/"
INFO global: VAGRANT_OLD_ENV_COLORFGBG="7;0"
INFO global: VAGRANT_OLD_ENV_CONDA_DEFAULT_ENV="clusto"
INFO global: VAGRANT_INSTALLER_ENV="1"
INFO global: VAGRANT_EXECUTABLE="/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/bin/vagrant"
INFO global: VAGRANT_INSTALLER_EMBEDDED_DIR="/opt/vagrant/embedded"
INFO global: VAGRANT_OLD_ENV_COMMAND_MODE="unix2003"
INFO global: VAGRANT_OLD_ENV_SSH_AUTH_SOCK="/private/tmp/com.apple.launchd.CSjdOMPkpG/Listeners"
INFO global: VAGRANT_OLD_ENV_LANG="en_US.UTF-8"
DEBUG subprocess: stderr: INFO global: VAGRANT_OLD_ENV_TERM_PROGRAM="iTerm.app"
DEBUG subprocess: stderr: INFO global: VAGRANT_OLD_ENV_XPC_SERVICE_NAME="0"
DEBUG subprocess: stderr: INFO global: VAGRANT_OLD_ENV_SHLVL="1"
INFO global: VAGRANT_OLD_ENV_SECURITYSESSIONID="186a5"
DEBUG subprocess: stderr: INFO global: VAGRANT_OLD_ENV_TERM="xterm-color"
INFO global: VAGRANT_OLD_ENV_USER="quasiben"
INFO global: VAGRANT_OLD_ENV___CF_USER_TEXT_ENCODING="0x1F7:0x0:0x0"
INFO global: VAGRANT_OLD_ENV_ITERM_SESSION_ID="w0t1p0"
INFO global: VAGRANT_OLD_ENV_SHELL="/bin/bash"
DEBUG subprocess: stderr: INFO global: VAGRANT_OLD_ENV_PS1="(clusto)\\[\\033[01;32m\\]\\u@\\h\\[\\033[00m\\]:\\[\\033[01;36m\\]\\w\\[\\033[00m\\]\\$ "
INFO global: VAGRANT_OLD_ENV_OLDPWD="/Users/quasiben/Research/ContinuumDev/AC_AS_Vagrant/Head+Compute/test"
DEBUG subprocess: stderr: INFO global: VAGRANT_OLD_ENV_JRE_HOME="/Library/Java/JavaVirtualMachines/jdk1.7.0_45.jdk/Contents/Home/jre/"
DEBUG subprocess: stderr: INFO global: VAGRANT_OLD_ENV_LOGNAME="quasiben"
INFO global: VAGRANT_INTERNAL_BUNDLERIZED="1"
INFO global: Plugins:
DEBUG subprocess: stderr: INFO global: - bundler = 1.10.5
INFO global: - mime-types = 1.25.1
INFO global: - rest-client = 1.6.9
INFO global: - vagrant-share = 1.1.4
INFO global: - vagrant-vmware-fusion = 4.0.2
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/box/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: box command
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/destroy/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: destroy command
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/global-status/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: global-status command
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/halt/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: halt command
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/help/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: help command
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/init/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: init command
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/list-commands/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: list-commands command
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/login/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: vagrant-login
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/package/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: package command
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/plugin/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: plugin command
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/provision/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: provision command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/push/plugin.rb
INFO manager: Registered plugin: push command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/rdp/plugin.rb
INFO manager: Registered plugin: rdp command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/reload/plugin.rb
INFO manager: Registered plugin: reload command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/resume/plugin.rb
INFO manager: Registered plugin: resume command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/ssh/plugin.rb
INFO manager: Registered plugin: ssh command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/ssh_config/plugin.rb
INFO manager: Registered plugin: ssh-config command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/status/plugin.rb
INFO manager: Registered plugin: status command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/suspend/plugin.rb
INFO manager: Registered plugin: suspend command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/up/plugin.rb
INFO manager: Registered plugin: up command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/version/plugin.rb
INFO manager: Registered plugin: version command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/communicators/ssh/plugin.rb
INFO manager: Registered plugin: ssh communicator
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/communicators/winrm/plugin.rb
INFO manager: Registered plugin: winrm communicator
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/arch/plugin.rb
INFO manager: Registered plugin: Arch guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/atomic/plugin.rb
INFO manager: Registered plugin: Atomic Host guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/coreos/plugin.rb
INFO manager: Registered plugin: CoreOS guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/darwin/plugin.rb
INFO manager: Registered plugin: Darwin guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/debian/plugin.rb
INFO manager: Registered plugin: Debian guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/debian8/plugin.rb
INFO manager: Registered plugin: Debian Jessie guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/esxi/plugin.rb
INFO manager: Registered plugin: ESXi guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/fedora/plugin.rb
INFO manager: Registered plugin: Fedora guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/freebsd/plugin.rb
INFO manager: Registered plugin: FreeBSD guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/funtoo/plugin.rb
INFO manager: Registered plugin: Funtoo guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/gentoo/plugin.rb
INFO manager: Registered plugin: Gentoo guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/linux/plugin.rb
INFO manager: Registered plugin: Linux guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/mint/plugin.rb
INFO manager: Registered plugin: Mint guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/netbsd/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: NetBSD guest
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/nixos/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: NixOS guest
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/omnios/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: OmniOS guest.
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/openbsd/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: OpenBSD guest
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/photon/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: VMware Photon guest
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/pld/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: PLD Linux guest
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/redhat/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: Red Hat Enterprise Linux guest
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/smartos/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: SmartOS guest.
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/solaris/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: Solaris guest.
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/solaris11/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: Solaris 11 guest.
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/suse/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: SUSE guest
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/tinycore/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: TinyCore Linux guest.
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/ubuntu/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: Ubuntu guest
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/windows/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: Windows guest.
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/arch/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: Arch host
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/bsd/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: BSD host
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/darwin/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: Mac OS X host
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/freebsd/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: FreeBSD host
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/gentoo/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: Gentoo host
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/linux/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: Linux host
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/null/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: null host
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/redhat/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: Red Hat Enterprise Linux host
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/slackware/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: Slackware host
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/suse/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: SUSE host
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/windows/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: Windows host
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/kernel_v1/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: kernel
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/kernel_v2/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: kernel
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/providers/docker/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: docker-provider
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/providers/hyperv/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: Hyper-V provider
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/providers/virtualbox/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: VirtualBox provider
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/ansible/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: ansible
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/cfengine/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: CFEngine Provisioner
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/chef/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: chef
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/docker/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: docker
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/file/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: file
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/puppet/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: puppet
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/salt/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: salt
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/shell/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: shell
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/pushes/atlas/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: atlas
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/pushes/ftp/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: ftp
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/pushes/heroku/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: heroku
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/pushes/local-exec/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: local-exec
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/pushes/noop/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: noop
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/synced_folders/nfs/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: NFS synced folders
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/synced_folders/rsync/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: RSync synced folders
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/synced_folders/smb/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: SMB synced folders
DEBUG subprocess: stderr: INFO manager: Registered plugin: VMware Fusion Provider
DEBUG subprocess: stderr: INFO vmware_driver: VMX file:
DEBUG subprocess: stderr: INFO vmware_driver: Looking for VMware Fusion: /Applications/VMware Fusion.app
DEBUG subprocess: stderr: INFO vmware_driver: VMware Fusion path: #<Pathname:/Applications/VMware Fusion.app>
DEBUG subprocess: stderr: DEBUG vmware_driver: Attempting to read VMware version...
DEBUG subprocess: stderr: INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmware-vmx", "-v"]
DEBUG subprocess: stderr: DEBUG subprocess: Command not in installer, not touching env vars.
DEBUG subprocess: stderr: INFO subprocess: Command is setuid/setgid, clearing DYLD_LIBRARY_PATH
DEBUG subprocess: stderr: INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: stderr: DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: DEBUG subprocess: stderr:
VMware Fusion Information:
VMware Fusion 7.1.0 build-2314774 Release
DEBUG subprocess: stderr: DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
DEBUG subprocess: stderr: INFO vmware_driver: Detected VMware version: 7.1.0
DEBUG subprocess: stderr: DEBUG vmware_driver: service starter path: /Applications/VMware Fusion.app/Contents/Library/services/Open VMware Fusion Services
DEBUG vmware_driver: vmnet-cli path: /Applications/VMware Fusion.app/Contents/Library/vmnet-cli
DEBUG subprocess: stderr: INFO vmware:sudo_helper: Calling command: prune-forwarded-ports
DEBUG subprocess: stderr: INFO vmware_driver: Pruning forwarded ports from: /Library/Preferences/VMware Fusion/vmnet8/nat.conf
DEBUG subprocess: stderr: DEBUG nat_conf: Read section: incomingtcp
DEBUG subprocess: stderr: DEBUG nat_conf: -- Value: "[incomingtcp]\n\n# Use these with care - anyone can enter into your VM through these...\n# The format and example are as follows:\n#<external port number> = <VM's IP address>:<VM's port number>\n#8080 = 172.16.3.128:80\n"
DEBUG nat_conf: Read section: incomingudp
DEBUG subprocess: stderr: DEBUG nat_conf: -- Value: "[incomingudp]\n\n# UDP port forwarding example\n#6000 = 172.16.3.0:6001\n\n"
DEBUG subprocess: stderr: INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmrun", "list"]
DEBUG subprocess: stderr: DEBUG subprocess: Command not in installer, not touching env vars.
DEBUG subprocess: stderr: INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: stderr: DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: DEBUG subprocess: stdout: Total running VMs: 0
DEBUG subprocess: stderr: DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
DEBUG subprocess: stderr: DEBUG nat_conf: Replace section: incomingtcp
DEBUG subprocess: stderr: DEBUG nat_conf: Replace section: incomingudp
DEBUG subprocess: stderr: DEBUG nat_conf: Writing NAT file: "# VMware NAT configuration file\n\n[host]\n\n# NAT gateway address\nip = 192.168.186.2\nnetmask = 255.255.255.0\n\n# VMnet device if not specified on command line\ndevice = vmnet8\n\n# Allow PORT/EPRT FTP commands (they need incoming TCP stream ...)\nactiveFTP = 1\n\n# Allows the source to have any OUI. Turn this on if you change the OUI\n# in the MAC address of your virtual machines.\nallowAnyOUI = 1\n\n# Controls if (TCP) connections should be reset when the adapter they are\n# bound to goes down\nresetConnectionOnLinkDown = 1\n\n# Controls if (TCP) connection should be reset when guest packet's destination\n# is NAT's IP address\nresetConnectionOnDestLocalHost = 1\n\n[tcp]\n\n# Value of timeout in TCP TIME_WAIT state, in seconds\ntimeWaitTimeout = 30\n\n[udp]\n\n# Timeout in seconds. Dynamically-created UDP mappings will purged if\n# idle for this duration of time 0 = no timeout, default = 60; real\n# value might be up to 100% longer\ntimeout = 60\n\n[netbios]\n# Timeout for NBNS queries.\nnbnsTimeout = 2\n\n# Number of retries for each NBNS query.\nnbnsRetries = 3\n\n# Timeout for NBDS queries.\nnbdsTimeout = 3\n\n[incomingtcp]\n\n# Use these with care - anyone can enter into your VM through these...\n# The format and example are as follows:\n#<external port number> = <VM's IP address>:<VM's port number>\n#8080 = 172.16.3.128:80\n\n[incomingudp]\n\n# UDP port forwarding example\n#6000 = 172.16.3.0:6001\n\n"
DEBUG subprocess: stderr: DEBUG nat_conf: Read section: incomingtcp
DEBUG subprocess: stderr: DEBUG nat_conf: -- Value: "[incomingtcp]\n\n# Use these with care - anyone can enter into your VM through these...\n# The format and example are as follows:\n#<external port number> = <VM's IP address>:<VM's port number>\n#8080 = 172.16.3.128:80\n"
DEBUG nat_conf: Read section: incomingudp
DEBUG subprocess: stderr: DEBUG nat_conf: -- Value: "[incomingudp]\n\n# UDP port forwarding example\n#6000 = 172.16.3.0:6001\n\n"
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 31999
DEBUG subprocess: Exit status: 0
INFO environment: Released process lock: vmware-network
DEBUG environment: Attempting to acquire process-lock: dotlock
INFO environment: Acquired process lock: dotlock
INFO environment: Released process lock: dotlock
INFO warden: Calling IN action: VMware Middleware: CheckExistingNetwork
INFO check_existing_network: Checking if the vmnet devices are healthy...
DEBUG environment: Attempting to acquire process-lock: vmware-network
DEBUG environment: Attempting to acquire process-lock: dotlock
INFO environment: Acquired process lock: dotlock
INFO environment: Released process lock: dotlock
INFO environment: Acquired process lock: vmware-network
INFO interface: info: Verifying vmnet devices are healthy...
INFO interface: info: ==> dev: Verifying vmnet devices are healthy...
INFO subprocess: Starting process: ["/Users/quasiben/.vagrant.d/gems/gems/vagrant-vmware-fusion-4.0.2/bin/vagrant_vmware_desktop_sudo_helper_wrapper_darwin_amd64", "verify-vmnet", "/var/folders/1t/t94brwgx7sjcn8jgz4gr3_c00000gq/T/vagrant-sudo-helper20151111-6218-175ruux"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command is setuid/setgid, clearing DYLD_LIBRARY_PATH
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: INFO global: Vagrant version: 1.7.4
INFO global: Ruby version: 2.0.0
INFO global: RubyGems version: 2.0.14
DEBUG subprocess: stderr: INFO global: VAGRANT_LOG="debug"
INFO global: VAGRANT_OLD_ENV_SPARK_HOME="/Users/quasiben/Research/GitClones/spark"
INFO global: VAGRANT_OLD_ENV_HOME="/Users/quasiben"
INFO global: VAGRANT_OLD_ENV__="/usr/local/bin/vagrant"
INFO global: VAGRANT_OLD_ENV_XPC_FLAGS="0x0"
INFO global: VAGRANT_INSTALLER_VERSION="2"
INFO global: VAGRANT_OLD_ENV_VAGRANT_LOG="debug"
DEBUG subprocess: stderr: INFO global: VAGRANT_OLD_ENV_TMPDIR="/var/folders/1t/t94brwgx7sjcn8jgz4gr3_c00000gq/T/"
INFO global: VAGRANT_OLD_ENV_Apple_PubSub_Socket_Render="/private/tmp/com.apple.launchd.KW13obTzd8/Render"
INFO global: VAGRANT_OLD_ENV_JAVA_HOME="/Library/Java/JavaVirtualMachines/jdk1.7.0_45.jdk/Contents/Home"
INFO global: VAGRANT_OLD_ENV_ACHE_HOME="/Users/quasiben/anaconda/envs/memex-explorer/lib/python2.7/site-packages/ache/"
INFO global: VAGRANT_OLD_ENV_CONDA_ENV_PATH="/Users/quasiben/anaconda/envs/clusto"
INFO global: VAGRANT_OLD_ENV_PYTHONPATH="/Users/quasiben/Research/ContinuumDev/GitRepo/conda-cluster/::/Users/quasiben/Research/GitClones/spark/python"
INFO global: VAGRANT_OLD_ENV_PATH="/Users/quasiben/anaconda/envs/clusto/bin:/usr/local/bin:/usr/local/heroku/bin:/Users/quasiben/google-cloud-sdk/bin:/usr/local/sbin:/Users/quasiben/.cabal/bin/:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/texbin:/Users/quasiben/Research/ContinuumDev/GitRepo/libdynd/build"
INFO global: VAGRANT_OLD_ENV_PWD="/Users/quasiben"
INFO global: VAGRANT_OLD_ENV_ITERM_PROFILE="Default"
INFO global: VAGRANT_OLD_ENV_JDK_HOME="/Library/Java/JavaVirtualMachines/jdk1.7.0_45.jdk/Contents/Home/"
INFO global: VAGRANT_OLD_ENV_COLORFGBG="7;0"
INFO global: VAGRANT_OLD_ENV_CONDA_DEFAULT_ENV="clusto"
INFO global: VAGRANT_INSTALLER_ENV="1"
INFO global: VAGRANT_EXECUTABLE="/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/bin/vagrant"
INFO global: VAGRANT_INSTALLER_EMBEDDED_DIR="/opt/vagrant/embedded"
INFO global: VAGRANT_OLD_ENV_COMMAND_MODE="unix2003"
INFO global: VAGRANT_OLD_ENV_SSH_AUTH_SOCK="/private/tmp/com.apple.launchd.CSjdOMPkpG/Listeners"
INFO global: VAGRANT_OLD_ENV_LANG="en_US.UTF-8"
INFO global: VAGRANT_OLD_ENV_TERM_PROGRAM="iTerm.app"
INFO global: VAGRANT_OLD_ENV_XPC_SERVICE_NAME="0"
INFO global: VAGRANT_OLD_ENV_SHLVL="1"
INFO global: VAGRANT_OLD_ENV_SECURITYSESSIONID="186a5"
INFO global: VAGRANT_OLD_ENV_TERM="xterm-color"
INFO global: VAGRANT_OLD_ENV_USER="quasiben"
INFO global: VAGRANT_OLD_ENV___CF_USER_TEXT_ENCODING="0x1F7:0x0:0x0"
INFO global: VAGRANT_OLD_ENV_ITERM_SESSION_ID="w0t1p0"
INFO global: VAGRANT_OLD_ENV_SHELL="/bin/bash"
INFO global: VAGRANT_OLD_ENV_PS1="(clusto)\\[\\033[01;32m\\]\\u@\\h\\[\\033[00m\\]:\\[\\033[01;36m\\]\\w\\[\\033[00m\\]\\$ "
INFO global: VAGRANT_OLD_ENV_OLDPWD="/Users/quasiben/Research/ContinuumDev/AC_AS_Vagrant/Head+Compute/test"
INFO global: VAGRANT_OLD_ENV_JRE_HOME="/Library/Java/JavaVirtualMachines/jdk1.7.0_45.jdk/Contents/Home/jre/"
INFO global: VAGRANT_OLD_ENV_LOGNAME="quasiben"
INFO global: VAGRANT_INTERNAL_BUNDLERIZED="1"
INFO global: Plugins:
DEBUG subprocess: stderr: INFO global: - bundler = 1.10.5
INFO global: - mime-types = 1.25.1
INFO global: - rest-client = 1.6.9
INFO global: - vagrant-share = 1.1.4
INFO global: - vagrant-vmware-fusion = 4.0.2
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/box/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: box command
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/destroy/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: destroy command
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/global-status/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: global-status command
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/halt/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: halt command
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/help/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: help command
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/init/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: init command
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/list-commands/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: list-commands command
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/login/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: vagrant-login
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/package/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: package command
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/plugin/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: plugin command
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/provision/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: provision command
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/push/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: push command
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/rdp/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: rdp command
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/reload/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: reload command
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/resume/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: resume command
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/ssh/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: ssh command
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/ssh_config/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: ssh-config command
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/status/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: status command
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/suspend/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: suspend command
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/up/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: up command
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/version/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: version command
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/communicators/ssh/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: ssh communicator
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/communicators/winrm/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: winrm communicator
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/arch/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: Arch guest
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/atomic/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: Atomic Host guest
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/coreos/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: CoreOS guest
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/darwin/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: Darwin guest
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/debian/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: Debian guest
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/debian8/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: Debian Jessie guest
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/esxi/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: ESXi guest.
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/fedora/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: Fedora guest
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/freebsd/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: FreeBSD guest
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/funtoo/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: Funtoo guest
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/gentoo/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: Gentoo guest
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/linux/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: Linux guest.
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/mint/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: Mint guest
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/netbsd/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: NetBSD guest
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/nixos/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: NixOS guest
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/omnios/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: OmniOS guest.
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/openbsd/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: OpenBSD guest
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/photon/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: VMware Photon guest
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/pld/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: PLD Linux guest
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/redhat/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: Red Hat Enterprise Linux guest
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/smartos/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: SmartOS guest.
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/solaris/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: Solaris guest.
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/solaris11/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: Solaris 11 guest.
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/suse/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: SUSE guest
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/tinycore/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: TinyCore Linux guest.
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/ubuntu/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: Ubuntu guest
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/windows/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: Windows guest.
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/arch/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: Arch host
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/bsd/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: BSD host
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/darwin/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: Mac OS X host
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/freebsd/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: FreeBSD host
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/gentoo/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: Gentoo host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/linux/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: Linux host
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/null/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: null host
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/redhat/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: Red Hat Enterprise Linux host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/slackware/plugin.rb
INFO manager: Registered plugin: Slackware host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/suse/plugin.rb
INFO manager: Registered plugin: SUSE host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/windows/plugin.rb
INFO manager: Registered plugin: Windows host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/kernel_v1/plugin.rb
INFO manager: Registered plugin: kernel
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/kernel_v2/plugin.rb
INFO manager: Registered plugin: kernel
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/providers/docker/plugin.rb
INFO manager: Registered plugin: docker-provider
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/providers/hyperv/plugin.rb
INFO manager: Registered plugin: Hyper-V provider
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/providers/virtualbox/plugin.rb
INFO manager: Registered plugin: VirtualBox provider
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/ansible/plugin.rb
INFO manager: Registered plugin: ansible
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/cfengine/plugin.rb
INFO manager: Registered plugin: CFEngine Provisioner
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/chef/plugin.rb
INFO manager: Registered plugin: chef
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/docker/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: docker
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/file/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: file
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/puppet/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: puppet
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/salt/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: salt
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/shell/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: shell
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/pushes/atlas/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: atlas
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/pushes/ftp/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: ftp
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/pushes/heroku/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: heroku
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/pushes/local-exec/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: local-exec
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/pushes/noop/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: noop
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/synced_folders/nfs/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: NFS synced folders
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/synced_folders/rsync/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: RSync synced folders
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/synced_folders/smb/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: SMB synced folders
DEBUG subprocess: stderr: INFO manager: Registered plugin: VMware Fusion Provider
DEBUG subprocess: stderr: INFO vmware_driver: VMX file:
INFO vmware_driver: Looking for VMware Fusion: /Applications/VMware Fusion.app
DEBUG subprocess: stderr: INFO vmware_driver: VMware Fusion path: #<Pathname:/Applications/VMware Fusion.app>
DEBUG subprocess: stderr: DEBUG vmware_driver: Attempting to read VMware version...
DEBUG subprocess: stderr: INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmware-vmx", "-v"]
DEBUG subprocess: stderr: DEBUG subprocess: Command not in installer, not touching env vars.
DEBUG subprocess: stderr: INFO subprocess: Command is setuid/setgid, clearing DYLD_LIBRARY_PATH
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: stderr: DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: DEBUG subprocess: stderr:
VMware Fusion Information:
VMware Fusion 7.1.0 build-2314774 Release
DEBUG subprocess: stderr: DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
DEBUG subprocess: stderr: INFO vmware_driver: Detected VMware version: 7.1.0
DEBUG subprocess: stderr: DEBUG vmware_driver: service starter path: /Applications/VMware Fusion.app/Contents/Library/services/Open VMware Fusion Services
DEBUG vmware_driver: vmnet-cli path: /Applications/VMware Fusion.app/Contents/Library/vmnet-cli
DEBUG subprocess: stderr: INFO vmware:sudo_helper: Calling command: verify-vmnet
INFO vmware_driver: Starting services starter and waiting for them to start...
DEBUG subprocess: stderr: INFO vmware_driver: Killing vmnet-natd if it is alive...
DEBUG subprocess: stderr: INFO subprocess: Starting process: ["/usr/bin/pkill", "vmnet-natd"]
DEBUG subprocess: stderr: DEBUG subprocess: Command not in installer, not touching env vars.
DEBUG subprocess: stderr: INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: stderr: DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
DEBUG subprocess: stderr: INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--start"]
DEBUG subprocess: stderr: DEBUG subprocess: Command not in installer, not touching env vars.
DEBUG subprocess: stderr: INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: stderr: DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: DEBUG subprocess: stdout: Enabled hostonly virtual adapter on vmnet1
Started DHCP service on vmnet1
Enabled hostonly virtual adapter on vmnet2
Started DHCP service on vmnet2
Enabled hostonly virtual adapter on vmnet3
Started DHCP service on vmnet3
Enabled hostonly virtual adapter on vmnet4
Started DHCP service on vmnet4
Enabled hostonly virtual adapter on vmnet5
Started DHCP service on vmnet5
Started NAT service on vmnet8
Enabled hostonly virtual adapter on vmnet8
Started DHCP service on vmnet8
Started all configured services on all networks
DEBUG subprocess: stderr: DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 31999
DEBUG subprocess: stderr: DEBUG subprocess: Exit status: 0
DEBUG subprocess: stderr: INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"]
DEBUG subprocess: stderr: DEBUG subprocess: Command not in installer, not touching env vars.
DEBUG subprocess: stderr: INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: stderr: DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: DEBUG subprocess: stdout: DHCP service on vmnet1 is running
Hostonly virtual adapter on vmnet1 is enabled
DHCP service on vmnet2 is running
Hostonly virtual adapter on vmnet2 is enabled
DHCP service on vmnet3 is running
Hostonly virtual adapter on vmnet3 is enabled
DHCP service on vmnet4 is running
Hostonly virtual adapter on vmnet4 is enabled
DHCP service on vmnet5 is running
Hostonly virtual adapter on vmnet5 is enabled
DHCP service on vmnet8 is running
NAT service on vmnet8 is running
Hostonly virtual adapter on vmnet8 is enabled
All the services configured on all the networks are running
DEBUG subprocess: stderr: DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
DEBUG subprocess: stderr: INFO vmware_driver: Stopping services starter...
DEBUG subprocess: stderr: INFO vmware_driver: vmnet devices appear healthy!
DEBUG vmware_driver: Beginning to verify routing of devices...
DEBUG subprocess: stderr: INFO vmware_driver: Starting services starter and waiting for them to start...
DEBUG subprocess: stderr: INFO vmware_driver: Killing vmnet-natd if it is alive...
DEBUG subprocess: stderr: INFO subprocess: Starting process: ["/usr/bin/pkill", "vmnet-natd"]
DEBUG subprocess: stderr: DEBUG subprocess: Command not in installer, not touching env vars.
DEBUG subprocess: stderr: INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: stderr: DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
DEBUG subprocess: stderr: INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--start"]
DEBUG subprocess: stderr: DEBUG subprocess: Command not in installer, not touching env vars.
DEBUG subprocess: stderr: INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: stderr: DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: DEBUG subprocess: stdout: Enabled hostonly virtual adapter on vmnet1
Started DHCP service on vmnet1
Enabled hostonly virtual adapter on vmnet2
Started DHCP service on vmnet2
Enabled hostonly virtual adapter on vmnet3
Started DHCP service on vmnet3
Enabled hostonly virtual adapter on vmnet4
Started DHCP service on vmnet4
Enabled hostonly virtual adapter on vmnet5
Started DHCP service on vmnet5
Started NAT service on vmnet8
Enabled hostonly virtual adapter on vmnet8
Started DHCP service on vmnet8
Started all configured services on all networks
DEBUG subprocess: stderr: DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
DEBUG subprocess: stderr: INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"]
DEBUG subprocess: stderr: DEBUG subprocess: Command not in installer, not touching env vars.
DEBUG subprocess: stderr: INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: stderr: DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: DEBUG subprocess: stdout: DHCP service on vmnet1 is running
Hostonly virtual adapter on vmnet1 is enabled
DHCP service on vmnet2 is running
Hostonly virtual adapter on vmnet2 is enabled
DHCP service on vmnet3 is running
Hostonly virtual adapter on vmnet3 is enabled
DHCP service on vmnet4 is running
Hostonly virtual adapter on vmnet4 is enabled
DHCP service on vmnet5 is running
Hostonly virtual adapter on vmnet5 is enabled
DHCP service on vmnet8 is running
NAT service on vmnet8 is running
Hostonly virtual adapter on vmnet8 is enabled
All the services configured on all the networks are running
DEBUG subprocess: stderr: DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
DEBUG subprocess: stderr: INFO subprocess: Starting process: ["/usr/sbin/netstat", "-nr", "-f", "inet"]
DEBUG subprocess: stderr: DEBUG subprocess: Command not in installer, not touching env vars.
DEBUG subprocess: stderr: INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: stderr: DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: DEBUG subprocess: stdout: Routing tables
Internet:
Destination Gateway Flags Refs Use Netif Expire
default 192.168.1.1 UGSc 43 0 en0
10.10.10/24 link#12 UC 1 0 vmnet2
127 127.0.0.1 UCS 0 0 lo0
127.0.0.1 127.0.0.1 UH 24 252630 lo0
169.254 link#4 UCS 0 0 en0
172.16.48/24 link#14 UC 1 0 vmnet4
192.168.1 link#4 UCS 1 0 en0
192.168.1.1/32 link#4 UCS 1 0 en0
192.168.1.1 28:c6:8e:8f:75:b2 UHLWIir 45 5771 en0 1084
192.168.1.2 0:22:58:9c:58:df UHLWI 0 925 en0 1085
192.168.1.13/32 link#4 UCS 0 0 en0
192.168.18 link#13 UC 1 0 vmnet3
192.168.27 link#11 UC 1 0 vmnet1
192.168.111 link#15 UC 1 0 vmnet5
192.168.186 link#16 UC 1 0 vmnet8
DEBUG subprocess: stderr: DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
DEBUG subprocess: stderr: INFO networking_file: Reading adapters from networking file...
DEBUG subprocess: stderr: DEBUG networking_file: VNET: 1. KEY: 'DHCP' = 'yes'
DEBUG networking_file: VNET: 1. KEY: 'DHCP_CFG_HASH' = 'D80210FE873BE2813B8C769A8E72B64979061717'
DEBUG subprocess: stderr: DEBUG networking_file: VNET: 1. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG networking_file: VNET: 1. KEY: 'HOSTONLY_SUBNET' = '192.168.27.0'
DEBUG networking_file: VNET: 1. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG networking_file: VNET: 2. KEY: 'DHCP' = 'yes'
DEBUG subprocess: stderr: DEBUG networking_file: VNET: 2. KEY: 'DHCP_CFG_HASH' = '87768080D35EC28F8A98E2922D0D6FE5E5C18A59'
DEBUG networking_file: VNET: 2. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG subprocess: stderr: DEBUG networking_file: VNET: 2. KEY: 'HOSTONLY_SUBNET' = '10.10.10.0'
DEBUG subprocess: stderr: DEBUG networking_file: VNET: 2. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG networking_file: VNET: 3. KEY: 'DHCP' = 'yes'
DEBUG subprocess: stderr: DEBUG networking_file: VNET: 3. KEY: 'DHCP_CFG_HASH' = '3EC4C96155C7AA76726042C1D3C8D9C208404144'
DEBUG networking_file: VNET: 3. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG subprocess: stderr: DEBUG networking_file: VNET: 3. KEY: 'HOSTONLY_SUBNET' = '192.168.18.0'
DEBUG networking_file: VNET: 3. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG subprocess: stderr: DEBUG networking_file: VNET: 4. KEY: 'DHCP' = 'yes'
DEBUG subprocess: stderr: DEBUG networking_file: VNET: 4. KEY: 'DHCP_CFG_HASH' = '6F6696B0E161F81ED0E3CE9F08794F4DD8D794EB'
DEBUG networking_file: VNET: 4. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG subprocess: stderr: DEBUG networking_file: VNET: 4. KEY: 'HOSTONLY_SUBNET' = '172.16.48.0'
DEBUG networking_file: VNET: 4. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG networking_file: VNET: 5. KEY: 'DHCP' = 'yes'
DEBUG subprocess: stderr: DEBUG networking_file: VNET: 5. KEY: 'DHCP_CFG_HASH' = '9B81D6F11FF984546E1C4E2B438F14AC3B559373'
DEBUG networking_file: VNET: 5. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG networking_file: VNET: 5. KEY: 'HOSTONLY_SUBNET' = '192.168.111.0'
DEBUG networking_file: VNET: 5. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG subprocess: stderr: DEBUG networking_file: VNET: 8. KEY: 'DHCP' = 'yes'
DEBUG networking_file: VNET: 8. KEY: 'DHCP_CFG_HASH' = '1BDC60FCCCD2EEB9E6AA5D403BE51F90BF3ACC00'
DEBUG networking_file: VNET: 8. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG subprocess: stderr: DEBUG networking_file: VNET: 8. KEY: 'HOSTONLY_SUBNET' = '192.168.186.0'
DEBUG subprocess: stderr: DEBUG networking_file: VNET: 8. KEY: 'NAT' = 'yes'
DEBUG networking_file: VNET: 8. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG subprocess: stderr: DEBUG networking_file: Pruning adapters that aren't actually active...
DEBUG subprocess: stderr: DEBUG vmware_driver: Testing route: 192.168.27.0 expects {:name=>"vmnet1", :number=>1, :dhcp=>"yes", :hostonly_netmask=>"255.255.255.0", :hostonly_subnet=>"192.168.27.0", :nat=>nil, :virtual_adapter=>"yes"}
DEBUG subprocess: stderr: DEBUG vmware_driver: Testing route: 10.10.10.0 expects {:name=>"vmnet2", :number=>2, :dhcp=>"yes", :hostonly_netmask=>"255.255.255.0", :hostonly_subnet=>"10.10.10.0", :nat=>nil, :virtual_adapter=>"yes"}
DEBUG subprocess: stderr: DEBUG vmware_driver: Testing route: 192.168.18.0 expects {:name=>"vmnet3", :number=>3, :dhcp=>"yes", :hostonly_netmask=>"255.255.255.0", :hostonly_subnet=>"192.168.18.0", :nat=>nil, :virtual_adapter=>"yes"}
DEBUG subprocess: stderr: DEBUG vmware_driver: Testing route: 172.16.48.0 expects {:name=>"vmnet4", :number=>4, :dhcp=>"yes", :hostonly_netmask=>"255.255.255.0", :hostonly_subnet=>"172.16.48.0", :nat=>nil, :virtual_adapter=>"yes"}
DEBUG subprocess: stderr: DEBUG vmware_driver: Testing route: 192.168.111.0 expects {:name=>"vmnet5", :number=>5, :dhcp=>"yes", :hostonly_netmask=>"255.255.255.0", :hostonly_subnet=>"192.168.111.0", :nat=>nil, :virtual_adapter=>"yes"}
DEBUG subprocess: stderr: DEBUG vmware_driver: Testing route: 192.168.186.0 expects {:name=>"vmnet8", :number=>8, :dhcp=>"yes", :hostonly_netmask=>"255.255.255.0", :hostonly_subnet=>"192.168.186.0", :nat=>"yes", :virtual_adapter=>"yes"}
DEBUG subprocess: stderr: INFO vmware_driver: Stopping services starter...
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 31996
DEBUG subprocess: Exit status: 0
INFO environment: Released process lock: vmware-network
DEBUG environment: Attempting to acquire process-lock: dotlock
INFO environment: Acquired process lock: dotlock
INFO environment: Released process lock: dotlock
INFO warden: Calling IN action: #<Vagrant::Action::Builtin::Call:0x00000102a409b8>
INFO runner: Preparing hooks for middleware sequence...
INFO runner: 1 hooks defined.
INFO runner: Running action: machine_action_up #<Vagrant::Action::Builder:0x00000100a6e1a8>
INFO warden: Calling IN action: VMware Middleware: Suspended
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmrun", "list"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stdout: Total running VMs: 0
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 31999
DEBUG subprocess: Exit status: 0
DEBUG vmware: VM state requested. Current state: not_running
DEBUG suspended: result: false
INFO warden: Calling OUT action: VMware Middleware: Suspended
INFO runner: Preparing hooks for middleware sequence...
INFO runner: 1 hooks defined.
INFO runner: Running action: machine_action_up #<Vagrant::Action::Warden:0x00000100ae69a0>
INFO warden: Calling IN action: #<Proc:0x00000100ad4728@/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:94 (lambda)>
INFO warden: Calling IN action: #<Vagrant::Action::Builtin::Provision:0x00000100ae68b0>
INFO provision: Checking provisioner sentinel file...
INFO warden: Calling IN action: VMware Middleware: PrepareSyncedFolderCleanup
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmrun", "list"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stdout: Total running VMs: 0
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO warden: Calling IN action: #<VagrantPlugins::SyncedFolderNFS::ActionCleanup:0x00000101c079c8>
DEBUG host: Searching for cap: nfs_prune
DEBUG host: Checking in: darwin
DEBUG host: Checking in: bsd
DEBUG host: Found cap: nfs_prune in bsd
INFO nfs: NFS pruning. Valid IDs: []
DEBUG host: Searching for cap: nfs_prune
DEBUG host: Checking in: darwin
DEBUG host: Checking in: bsd
DEBUG host: Found cap: nfs_prune in bsd
INFO host: Execute capability: nfs_prune [#<Vagrant::Environment: /Users/quasiben>, #<Vagrant::UI::Prefixed:0x00000102adae28 @logger=#<Log4r::Logger:0x00000102adadd8 @fullname="vagrant::ui::interface", @outputters=[], @additive=true, @name="interface", @path="vagrant::ui", @parent=#<Log4r::Logger:0x000001009da520 @fullname="vagrant", @outputters=[#<Log4r::StderrOutputter:0x00000100864b00 @mon_owner=nil, @mon_count=0, @mon_mutex=#<Mutex:0x00000100864920>, @name="stderr", @level=0, @formatter=#<Log4r::DefaultFormatter:0x0000010087f8b0 @depth=7>, @out=#<IO:<STDERR>>>], @additive=true, @name="vagrant", @path="", @parent=#<Log4r::RootLogger:0x000001009da3b8 @level=0, @outputters=[]>, @level=1, @trace=false>, @level=1, @trace=false>, @opts={}, @stdin=#<IO:<STDIN>>, @stdout=#<IO:<STDOUT>>, @stderr=#<IO:<STDERR>>, @prefix=:dev, @ui=#<Vagrant::UI::Colored:0x00000101a988a8 @logger=#<Log4r::Logger:0x00000101a98858 @fullname="vagrant::ui::interface", @outputters=[], @additive=true, @name="interface", @path="vagrant::ui", @parent=#<Log4r::Logger:0x000001009da520 @fullname="vagrant", @outputters=[#<Log4r::StderrOutputter:0x00000100864b00 @mon_owner=nil, @mon_count=0, @mon_mutex=#<Mutex:0x00000100864920>, @name="stderr", @level=0, @formatter=#<Log4r::DefaultFormatter:0x0000010087f8b0 @depth=7>, @out=#<IO:<STDERR>>>], @additive=true, @name="vagrant", @path="", @parent=#<Log4r::RootLogger:0x000001009da3b8 @level=0, @outputters=[]>, @level=1, @trace=false>, @level=1, @trace=false>, @opts={:color=>:default}, @stdin=#<IO:<STDIN>>, @stdout=#<IO:<STDOUT>>, @stderr=#<IO:<STDERR>>, @lock=#<Mutex:0x00000101aab0e8>>>, []] (darwin)
INFO warden: Calling IN action: #<Vagrant::Action::Builtin::SyncedFolderCleanup:0x00000101c5fcb8>
INFO warden: Calling IN action: #<Vagrant::Action::Builtin::SyncedFolders:0x00000101c9f9d0>
INFO warden: Calling IN action: VMware Middleware: PrepareNFSSettings
INFO warden: Calling IN action: VMware Middleware: Network
DEBUG network: Available slots for high-level adapters: #<Set: {1, 2, 3, 4, 5, 6, 7, 8}>
INFO network: Determining network adapters required for high-level configuration...
INFO network: -- Slot 1: hostonly
INFO network: Determining adapters and compiling network configuration...
INFO network: Slot 0. Type: nat
DEBUG network: Normalized configuration: {:auto_config=>false, :type=>:dhcp}
DEBUG network: Adapter configuration: {:type=>:nat, :slot=>0}
DEBUG network: Network configuration: {:type=>:dhcp, :auto_config=>false}
INFO network: Slot 1. Type: hostonly
DEBUG network: Normalized configuration: {:auto_config=>true, :netmask=>"255.255.255.0", :type=>:static, :ip=>"192.168.222.100", :protocol=>"tcp", :id=>"597e51cb-d4d7-4b5c-8ba2-905d1963220c", :subnet_ip=>"192.168.222.0", :adapter_ip=>"192.168.222.1"}
DEBUG vmware_driver: Reading VMware vmnet devices...
INFO networking_file: Reading adapters from networking file...
DEBUG networking_file: VNET: 1. KEY: 'DHCP' = 'yes'
DEBUG networking_file: VNET: 1. KEY: 'DHCP_CFG_HASH' = 'D80210FE873BE2813B8C769A8E72B64979061717'
DEBUG networking_file: VNET: 1. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG networking_file: VNET: 1. KEY: 'HOSTONLY_SUBNET' = '192.168.27.0'
DEBUG networking_file: VNET: 1. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG networking_file: VNET: 2. KEY: 'DHCP' = 'yes'
DEBUG networking_file: VNET: 2. KEY: 'DHCP_CFG_HASH' = '87768080D35EC28F8A98E2922D0D6FE5E5C18A59'
DEBUG networking_file: VNET: 2. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG networking_file: VNET: 2. KEY: 'HOSTONLY_SUBNET' = '10.10.10.0'
DEBUG networking_file: VNET: 2. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG networking_file: VNET: 3. KEY: 'DHCP' = 'yes'
DEBUG networking_file: VNET: 3. KEY: 'DHCP_CFG_HASH' = '3EC4C96155C7AA76726042C1D3C8D9C208404144'
DEBUG networking_file: VNET: 3. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG networking_file: VNET: 3. KEY: 'HOSTONLY_SUBNET' = '192.168.18.0'
DEBUG networking_file: VNET: 3. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG networking_file: VNET: 4. KEY: 'DHCP' = 'yes'
DEBUG networking_file: VNET: 4. KEY: 'DHCP_CFG_HASH' = '6F6696B0E161F81ED0E3CE9F08794F4DD8D794EB'
DEBUG networking_file: VNET: 4. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG networking_file: VNET: 4. KEY: 'HOSTONLY_SUBNET' = '172.16.48.0'
DEBUG networking_file: VNET: 4. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG networking_file: VNET: 5. KEY: 'DHCP' = 'yes'
DEBUG networking_file: VNET: 5. KEY: 'DHCP_CFG_HASH' = '9B81D6F11FF984546E1C4E2B438F14AC3B559373'
DEBUG networking_file: VNET: 5. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG networking_file: VNET: 5. KEY: 'HOSTONLY_SUBNET' = '192.168.111.0'
DEBUG networking_file: VNET: 5. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG networking_file: VNET: 8. KEY: 'DHCP' = 'yes'
DEBUG networking_file: VNET: 8. KEY: 'DHCP_CFG_HASH' = '1BDC60FCCCD2EEB9E6AA5D403BE51F90BF3ACC00'
DEBUG networking_file: VNET: 8. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG networking_file: VNET: 8. KEY: 'HOSTONLY_SUBNET' = '192.168.186.0'
DEBUG networking_file: VNET: 8. KEY: 'NAT' = 'yes'
DEBUG networking_file: VNET: 8. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG networking_file: Pruning adapters that aren't actually active...
INFO network: Checking for hostonly network collisions...
INFO subprocess: Starting process: ["/usr/sbin/netstat", "-nr", "-f", "inet"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stdout: Routing tables
Internet:
Destination Gateway Flags Refs Use Netif Expire
default 192.168.1.1 UGSc 43 0 en0
10.10.10/24 link#12 UC 1 0 vmnet2
127 127.0.0.1 UCS 0 0 lo0
127.0.0.1 127.0.0.1 UH 24 252630 lo0
169.254 link#4 UCS 0 0 en0
172.16.48/24 link#14 UC 1 0 vmnet4
192.168.1 link#4 UCS 1 0 en0
192.168.1.1/32 link#4 UCS 1 0 en0
192.168.1.1 28:c6:8e:8f:75:b2 UHLWIir 45 5771 en0 1083
192.168.1.2 0:22:58:9c:58:df UHLWI 0 925 en0 1084
192.168.1.13/32 link#4 UCS 0 0 en0
192.168.18 link#13 UC 1 0 vmnet3
192.168.27 link#11 UC 1 0 vmnet1
192.168.111 link#15 UC 1 0 vmnet5
192.168.186 link#16 UC 1 0 vmnet8
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO network: No collisions detected, creating new vmnet device.
INFO vmware_driver: Creating a vmnet device...
INFO subprocess: Starting process: ["/Users/quasiben/.vagrant.d/gems/gems/vagrant-vmware-fusion-4.0.2/bin/vagrant_vmware_desktop_sudo_helper_wrapper_darwin_amd64", "create-vmnet-device", "/var/folders/1t/t94brwgx7sjcn8jgz4gr3_c00000gq/T/vagrant-sudo-helper20151111-6218-1hxvszq"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command is setuid/setgid, clearing DYLD_LIBRARY_PATH
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: INFO global: Vagrant version: 1.7.4
INFO global: Ruby version: 2.0.0
INFO global: RubyGems version: 2.0.14
DEBUG subprocess: stderr: INFO global: VAGRANT_LOG="debug"
INFO global: VAGRANT_OLD_ENV_SPARK_HOME="/Users/quasiben/Research/GitClones/spark"
INFO global: VAGRANT_OLD_ENV_HOME="/Users/quasiben"
INFO global: VAGRANT_OLD_ENV__="/usr/local/bin/vagrant"
INFO global: VAGRANT_OLD_ENV_XPC_FLAGS="0x0"
INFO global: VAGRANT_INSTALLER_VERSION="2"
INFO global: VAGRANT_OLD_ENV_VAGRANT_LOG="debug"
INFO global: VAGRANT_OLD_ENV_TMPDIR="/var/folders/1t/t94brwgx7sjcn8jgz4gr3_c00000gq/T/"
INFO global: VAGRANT_OLD_ENV_Apple_PubSub_Socket_Render="/private/tmp/com.apple.launchd.KW13obTzd8/Render"
INFO global: VAGRANT_OLD_ENV_JAVA_HOME="/Library/Java/JavaVirtualMachines/jdk1.7.0_45.jdk/Contents/Home"
INFO global: VAGRANT_OLD_ENV_ACHE_HOME="/Users/quasiben/anaconda/envs/memex-explorer/lib/python2.7/site-packages/ache/"
INFO global: VAGRANT_OLD_ENV_CONDA_ENV_PATH="/Users/quasiben/anaconda/envs/clusto"
INFO global: VAGRANT_OLD_ENV_PYTHONPATH="/Users/quasiben/Research/ContinuumDev/GitRepo/conda-cluster/::/Users/quasiben/Research/GitClones/spark/python"
INFO global: VAGRANT_OLD_ENV_PATH="/Users/quasiben/anaconda/envs/clusto/bin:/usr/local/bin:/usr/local/heroku/bin:/Users/quasiben/google-cloud-sdk/bin:/usr/local/sbin:/Users/quasiben/.cabal/bin/:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/texbin:/Users/quasiben/Research/ContinuumDev/GitRepo/libdynd/build"
INFO global: VAGRANT_OLD_ENV_PWD="/Users/quasiben"
INFO global: VAGRANT_OLD_ENV_ITERM_PROFILE="Default"
INFO global: VAGRANT_OLD_ENV_JDK_HOME="/Library/Java/JavaVirtualMachines/jdk1.7.0_45.jdk/Contents/Home/"
INFO global: VAGRANT_OLD_ENV_COLORFGBG="7;0"
INFO global: VAGRANT_OLD_ENV_CONDA_DEFAULT_ENV="clusto"
INFO global: VAGRANT_INSTALLER_ENV="1"
INFO global: VAGRANT_EXECUTABLE="/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/bin/vagrant"
INFO global: VAGRANT_INSTALLER_EMBEDDED_DIR="/opt/vagrant/embedded"
INFO global: VAGRANT_OLD_ENV_COMMAND_MODE="unix2003"
INFO global: VAGRANT_OLD_ENV_SSH_AUTH_SOCK="/private/tmp/com.apple.launchd.CSjdOMPkpG/Listeners"
INFO global: VAGRANT_OLD_ENV_LANG="en_US.UTF-8"
INFO global: VAGRANT_OLD_ENV_TERM_PROGRAM="iTerm.app"
INFO global: VAGRANT_OLD_ENV_XPC_SERVICE_NAME="0"
INFO global: VAGRANT_OLD_ENV_SHLVL="1"
INFO global: VAGRANT_OLD_ENV_SECURITYSESSIONID="186a5"
INFO global: VAGRANT_OLD_ENV_TERM="xterm-color"
INFO global: VAGRANT_OLD_ENV_USER="quasiben"
INFO global: VAGRANT_OLD_ENV___CF_USER_TEXT_ENCODING="0x1F7:0x0:0x0"
INFO global: VAGRANT_OLD_ENV_ITERM_SESSION_ID="w0t1p0"
INFO global: VAGRANT_OLD_ENV_SHELL="/bin/bash"
INFO global: VAGRANT_OLD_ENV_PS1="(clusto)\\[\\033[01;32m\\]\\u@\\h\\[\\033[00m\\]:\\[\\033[01;36m\\]\\w\\[\\033[00m\\]\\$ "
INFO global: VAGRANT_OLD_ENV_OLDPWD="/Users/quasiben/Research/ContinuumDev/AC_AS_Vagrant/Head+Compute/test"
INFO global: VAGRANT_OLD_ENV_JRE_HOME="/Library/Java/JavaVirtualMachines/jdk1.7.0_45.jdk/Contents/Home/jre/"
INFO global: VAGRANT_OLD_ENV_LOGNAME="quasiben"
INFO global: VAGRANT_INTERNAL_BUNDLERIZED="1"
INFO global: Plugins:
DEBUG subprocess: stderr: INFO global: - bundler = 1.10.5
INFO global: - mime-types = 1.25.1
INFO global: - rest-client = 1.6.9
DEBUG subprocess: stderr: INFO global: - vagrant-share = 1.1.4
INFO global: - vagrant-vmware-fusion = 4.0.2
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/box/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: box command
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/destroy/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: destroy command
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/global-status/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: global-status command
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/halt/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: halt command
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/help/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: help command
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/init/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: init command
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/list-commands/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: list-commands command
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/login/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: vagrant-login
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/package/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: package command
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/plugin/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: plugin command
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/provision/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: provision command
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/push/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: push command
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/rdp/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: rdp command
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/reload/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: reload command
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/resume/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: resume command
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/ssh/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: ssh command
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/ssh_config/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: ssh-config command
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/status/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: status command
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/suspend/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: suspend command
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/up/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: up command
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/version/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: version command
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/communicators/ssh/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: ssh communicator
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/communicators/winrm/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: winrm communicator
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/arch/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: Arch guest
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/atomic/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: Atomic Host guest
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/coreos/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: CoreOS guest
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/darwin/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: Darwin guest
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/debian/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: Debian guest
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/debian8/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: Debian Jessie guest
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/esxi/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: ESXi guest.
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/fedora/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: Fedora guest
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/freebsd/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: FreeBSD guest
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/funtoo/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: Funtoo guest
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/gentoo/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: Gentoo guest
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/linux/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: Linux guest.
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/mint/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: Mint guest
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/netbsd/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: NetBSD guest
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/nixos/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: NixOS guest
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/omnios/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: OmniOS guest.
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/openbsd/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: OpenBSD guest
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/photon/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: VMware Photon guest
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/pld/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: PLD Linux guest
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/redhat/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: Red Hat Enterprise Linux guest
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/smartos/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: SmartOS guest.
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/solaris/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: Solaris guest.
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/solaris11/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: Solaris 11 guest.
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/suse/plugin.rb
INFO manager: Registered plugin: SUSE guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/tinycore/plugin.rb
INFO manager: Registered plugin: TinyCore Linux guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/ubuntu/plugin.rb
INFO manager: Registered plugin: Ubuntu guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/windows/plugin.rb
INFO manager: Registered plugin: Windows guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/arch/plugin.rb
INFO manager: Registered plugin: Arch host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/bsd/plugin.rb
INFO manager: Registered plugin: BSD host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/darwin/plugin.rb
INFO manager: Registered plugin: Mac OS X host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/freebsd/plugin.rb
INFO manager: Registered plugin: FreeBSD host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/gentoo/plugin.rb
INFO manager: Registered plugin: Gentoo host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/linux/plugin.rb
INFO manager: Registered plugin: Linux host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/null/plugin.rb
INFO manager: Registered plugin: null host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/redhat/plugin.rb
INFO manager: Registered plugin: Red Hat Enterprise Linux host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/slackware/plugin.rb
INFO manager: Registered plugin: Slackware host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/suse/plugin.rb
INFO manager: Registered plugin: SUSE host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/windows/plugin.rb
INFO manager: Registered plugin: Windows host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/kernel_v1/plugin.rb
INFO manager: Registered plugin: kernel
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/kernel_v2/plugin.rb
INFO manager: Registered plugin: kernel
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/providers/docker/plugin.rb
INFO manager: Registered plugin: docker-provider
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/providers/hyperv/plugin.rb
INFO manager: Registered plugin: Hyper-V provider
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/providers/virtualbox/plugin.rb
INFO manager: Registered plugin: VirtualBox provider
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/ansible/plugin.rb
INFO manager: Registered plugin: ansible
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/cfengine/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: CFEngine Provisioner
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/chef/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: chef
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/docker/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: docker
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/file/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: file
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/puppet/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: puppet
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/salt/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: salt
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/shell/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: shell
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/pushes/atlas/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: atlas
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/pushes/ftp/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: ftp
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/pushes/heroku/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: heroku
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/pushes/local-exec/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: local-exec
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/pushes/noop/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: noop
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/synced_folders/nfs/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: NFS synced folders
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/synced_folders/rsync/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: RSync synced folders
DEBUG subprocess: stderr: DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/synced_folders/smb/plugin.rb
DEBUG subprocess: stderr: INFO manager: Registered plugin: SMB synced folders
DEBUG subprocess: stderr: INFO manager: Registered plugin: VMware Fusion Provider
DEBUG subprocess: stderr: INFO vmware_driver: VMX path is a directory. Finding VMX file...
DEBUG subprocess: stderr: INFO vmware_driver: VMX file: /Users/quasiben/.vagrant/machines/dev/vmware_fusion/7890b8d8-98e2-4cd5-a989-d65c4e0279ae/trusty64.vmx
INFO vmware_driver: Looking for VMware Fusion: /Applications/VMware Fusion.app
DEBUG subprocess: stderr: INFO vmware_driver: VMware Fusion path: #<Pathname:/Applications/VMware Fusion.app>
DEBUG subprocess: stderr: DEBUG vmware_driver: Attempting to read VMware version...
DEBUG subprocess: stderr: INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmware-vmx", "-v"]
DEBUG subprocess: stderr: DEBUG subprocess: Command not in installer, not touching env vars.
DEBUG subprocess: stderr: INFO subprocess: Command is setuid/setgid, clearing DYLD_LIBRARY_PATH
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: stderr: DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: DEBUG subprocess: stderr:
VMware Fusion Information:
VMware Fusion 7.1.0 build-2314774 Release
DEBUG subprocess: stderr: DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: stderr: DEBUG subprocess: Exit status: 0
DEBUG subprocess: stderr: INFO vmware_driver: Detected VMware version: 7.1.0
DEBUG subprocess: stderr: DEBUG vmware_driver: service starter path: /Applications/VMware Fusion.app/Contents/Library/services/Open VMware Fusion Services
DEBUG vmware_driver: vmnet-cli path: /Applications/VMware Fusion.app/Contents/Library/vmnet-cli
DEBUG subprocess: stderr: INFO vmware:sudo_helper: Calling command: create-vmnet-device
DEBUG subprocess: stderr: INFO networking_file: Reading adapters from networking file...
DEBUG subprocess: stderr: DEBUG networking_file: VNET: 1. KEY: 'DHCP' = 'yes'
DEBUG subprocess: stderr: DEBUG networking_file: VNET: 1. KEY: 'DHCP_CFG_HASH' = 'D80210FE873BE2813B8C769A8E72B64979061717'
DEBUG networking_file: VNET: 1. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG networking_file: VNET: 1. KEY: 'HOSTONLY_SUBNET' = '192.168.27.0'
DEBUG networking_file: VNET: 1. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG subprocess: stderr: DEBUG networking_file: VNET: 2. KEY: 'DHCP' = 'yes'
DEBUG networking_file: VNET: 2. KEY: 'DHCP_CFG_HASH' = '87768080D35EC28F8A98E2922D0D6FE5E5C18A59'
DEBUG subprocess: stderr: DEBUG networking_file: VNET: 2. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG networking_file: VNET: 2. KEY: 'HOSTONLY_SUBNET' = '10.10.10.0'
DEBUG subprocess: stderr: DEBUG networking_file: VNET: 2. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG networking_file: VNET: 3. KEY: 'DHCP' = 'yes'
DEBUG networking_file: VNET: 3. KEY: 'DHCP_CFG_HASH' = '3EC4C96155C7AA76726042C1D3C8D9C208404144'
DEBUG subprocess: stderr: DEBUG networking_file: VNET: 3. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG networking_file: VNET: 3. KEY: 'HOSTONLY_SUBNET' = '192.168.18.0'
DEBUG networking_file: VNET: 3. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG subprocess: stderr: DEBUG networking_file: VNET: 4. KEY: 'DHCP' = 'yes'
DEBUG networking_file: VNET: 4. KEY: 'DHCP_CFG_HASH' = '6F6696B0E161F81ED0E3CE9F08794F4DD8D794EB'
DEBUG networking_file: VNET: 4. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG subprocess: stderr: DEBUG networking_file: VNET: 4. KEY: 'HOSTONLY_SUBNET' = '172.16.48.0'
DEBUG networking_file: VNET: 4. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG subprocess: stderr: DEBUG networking_file: VNET: 5. KEY: 'DHCP' = 'yes'
DEBUG networking_file: VNET: 5. KEY: 'DHCP_CFG_HASH' = '9B81D6F11FF984546E1C4E2B438F14AC3B559373'
DEBUG networking_file: VNET: 5. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG subprocess: stderr: DEBUG networking_file: VNET: 5. KEY: 'HOSTONLY_SUBNET' = '192.168.111.0'
DEBUG networking_file: VNET: 5. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG networking_file: VNET: 8. KEY: 'DHCP' = 'yes'
DEBUG subprocess: stderr: DEBUG networking_file: VNET: 8. KEY: 'DHCP_CFG_HASH' = '1BDC60FCCCD2EEB9E6AA5D403BE51F90BF3ACC00'
DEBUG networking_file: VNET: 8. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG subprocess: stderr: DEBUG networking_file: VNET: 8. KEY: 'HOSTONLY_SUBNET' = '192.168.186.0'
DEBUG networking_file: VNET: 8. KEY: 'NAT' = 'yes'
DEBUG networking_file: VNET: 8. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG subprocess: stderr: DEBUG networking_file: Pruning adapters that aren't actually active...
DEBUG subprocess: stderr: INFO vmware_driver: Starting services starter and waiting for them to start...
DEBUG subprocess: stderr: INFO vmware_driver: Killing vmnet-natd if it is alive...
DEBUG subprocess: stderr: INFO subprocess: Starting process: ["/usr/bin/pkill", "vmnet-natd"]
DEBUG subprocess: stderr: DEBUG subprocess: Command not in installer, not touching env vars.
DEBUG subprocess: stderr: INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: stderr: DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: stderr: DEBUG subprocess: Exit status: 0
DEBUG subprocess: stderr: INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--start"]
DEBUG subprocess: stderr: DEBUG subprocess: Command not in installer, not touching env vars.
DEBUG subprocess: stderr: INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: stderr: DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: DEBUG subprocess: stderr: Failed to start DHCP service on vmnet6
DEBUG subprocess: stderr: DEBUG subprocess: stderr: Failed to start some/all services
DEBUG subprocess: stdout: Enabled hostonly virtual adapter on vmnet1
Started DHCP service on vmnet1
Enabled hostonly virtual adapter on vmnet2
Started DHCP service on vmnet2
Enabled hostonly virtual adapter on vmnet3
Started DHCP service on vmnet3
Enabled hostonly virtual adapter on vmnet4
Started DHCP service on vmnet4
Enabled hostonly virtual adapter on vmnet5
Started DHCP service on vmnet5
Enabled hostonly virtual adapter on vmnet6
Started NAT service on vmnet8
Enabled hostonly virtual adapter on vmnet8
Started DHCP service on vmnet8
DEBUG subprocess: stderr: DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
DEBUG subprocess: stderr: INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"]
DEBUG subprocess: stderr: DEBUG subprocess: Command not in installer, not touching env vars.
DEBUG subprocess: stderr: INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: stderr: DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: DEBUG subprocess: stderr: Some/All of the configured services are not running
DEBUG subprocess: stdout: DHCP service on vmnet1 is running
Hostonly virtual adapter on vmnet1 is enabled
DHCP service on vmnet2 is running
Hostonly virtual adapter on vmnet2 is enabled
DHCP service on vmnet3 is running
Hostonly virtual adapter on vmnet3 is enabled
DHCP service on vmnet4 is running
Hostonly virtual adapter on vmnet4 is enabled
DHCP service on vmnet5 is running
Hostonly virtual adapter on vmnet5 is enabled
DHCP service on vmnet6 is not running
Hostonly virtual adapter on vmnet6 is enabled
DHCP service on vmnet8 is running
NAT service on vmnet8 is running
Hostonly virtual adapter on vmnet8 is enabled
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
DEBUG subprocess: stderr: INFO retryable: Retryable exception raised: #<HashiCorp::VagrantVMwarefusion::Errors::VMNetDevicesWontStart: The VMware "vmnet" devices are failing to start. The most common
reason for this is collisions with existing network services. For
example, if a hostonly network space collides with another hostonly
network (such as with VirtualBox), it will fail to start. Likewise,
if forwarded ports collide with other listening ports, it will
fail to start.
Vagrant does its best to fix these issues, but in some cases it
cannot determine the root cause of these failures.
Please verify you have no other colliding network services running.
As a last resort, restarting your computer often fixes this issue.>
DEBUG subprocess: stderr: INFO vmware_driver: Killing vmnet-natd if it is alive...
DEBUG subprocess: stderr: INFO subprocess: Starting process: ["/usr/bin/pkill", "vmnet-natd"]
DEBUG subprocess: stderr: DEBUG subprocess: Command not in installer, not touching env vars.
DEBUG subprocess: stderr: INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: stderr: DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: stderr: DEBUG subprocess: Exit status: 0
DEBUG subprocess: stderr: INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--start"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: stderr: DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: DEBUG subprocess: stderr: Failed to start DHCP service on vmnet6
DEBUG subprocess: stderr: DEBUG subprocess: stderr: Failed to start some/all services
DEBUG subprocess: stderr: DEBUG subprocess: stdout: Enabled hostonly virtual adapter on vmnet1
Started DHCP service on vmnet1
Enabled hostonly virtual adapter on vmnet2
Started DHCP service on vmnet2
Enabled hostonly virtual adapter on vmnet3
Started DHCP service on vmnet3
Enabled hostonly virtual adapter on vmnet4
Started DHCP service on vmnet4
Enabled hostonly virtual adapter on vmnet5
Started DHCP service on vmnet5
Enabled hostonly virtual adapter on vmnet6
Started NAT service on vmnet8
Enabled hostonly virtual adapter on vmnet8
Started DHCP service on vmnet8
DEBUG subprocess: stderr: DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: stderr: DEBUG subprocess: Exit status: 1
DEBUG subprocess: stderr: INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"]
DEBUG subprocess: stderr: DEBUG subprocess: Command not in installer, not touching env vars.
DEBUG subprocess: stderr: INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: stderr: DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: DEBUG subprocess: stderr: Some/All of the configured services are not running
DEBUG subprocess: stdout: DHCP service on vmnet1 is running
Hostonly virtual adapter on vmnet1 is enabled
DHCP service on vmnet2 is running
Hostonly virtual adapter on vmnet2 is enabled
DHCP service on vmnet3 is running
Hostonly virtual adapter on vmnet3 is enabled
DHCP service on vmnet4 is running
Hostonly virtual adapter on vmnet4 is enabled
DHCP service on vmnet5 is running
Hostonly virtual adapter on vmnet5 is enabled
DHCP service on vmnet6 is not running
Hostonly virtual adapter on vmnet6 is enabled
DHCP service on vmnet8 is running
NAT service on vmnet8 is running
Hostonly virtual adapter on vmnet8 is enabled
DEBUG subprocess: stderr: DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: stderr: DEBUG subprocess: Exit status: 1
DEBUG subprocess: stderr: INFO retryable: Retryable exception raised: #<HashiCorp::VagrantVMwarefusion::Errors::VMNetDevicesWontStart: The VMware "vmnet" devices are failing to start. The most common
reason for this is collisions with existing network services. For
example, if a hostonly network space collides with another hostonly
network (such as with VirtualBox), it will fail to start. Likewise,
if forwarded ports collide with other listening ports, it will
fail to start.
Vagrant does its best to fix these issues, but in some cases it
cannot determine the root cause of these failures.
Please verify you have no other colliding network services running.
As a last resort, restarting your computer often fixes this issue.>
DEBUG subprocess: stderr: INFO vmware_driver: Killing vmnet-natd if it is alive...
DEBUG subprocess: stderr: INFO subprocess: Starting process: ["/usr/bin/pkill", "vmnet-natd"]
DEBUG subprocess: stderr: DEBUG subprocess: Command not in installer, not touching env vars.
DEBUG subprocess: stderr: INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: stderr: DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
DEBUG subprocess: stderr: INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--start"]
DEBUG subprocess: stderr: DEBUG subprocess: Command not in installer, not touching env vars.
DEBUG subprocess: stderr: INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: stderr: DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: DEBUG subprocess: stderr: Failed to start DHCP service on vmnet6
DEBUG subprocess: stderr: DEBUG subprocess: stderr: Failed to start some/all services
DEBUG subprocess: stdout: Enabled hostonly virtual adapter on vmnet1
Started DHCP service on vmnet1
Enabled hostonly virtual adapter on vmnet2
Started DHCP service on vmnet2
Enabled hostonly virtual adapter on vmnet3
Started DHCP service on vmnet3
Enabled hostonly virtual adapter on vmnet4
Started DHCP service on vmnet4
Enabled hostonly virtual adapter on vmnet5
Started DHCP service on vmnet5
Enabled hostonly virtual adapter on vmnet6
Started NAT service on vmnet8
Enabled hostonly virtual adapter on vmnet8
Started DHCP service on vmnet8
DEBUG subprocess: stderr: DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 31999
DEBUG subprocess: Exit status: 1
DEBUG subprocess: stderr: INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"]
DEBUG subprocess: stderr: DEBUG subprocess: Command not in installer, not touching env vars.
DEBUG subprocess: stderr: INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: stderr: DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: DEBUG subprocess: stderr: Some/All of the configured services are not running
DEBUG subprocess: stderr: DEBUG subprocess: stdout: DHCP service on vmnet1 is running
Hostonly virtual adapter on vmnet1 is enabled
DHCP service on vmnet2 is running
Hostonly virtual adapter on vmnet2 is enabled
DHCP service on vmnet3 is running
Hostonly virtual adapter on vmnet3 is enabled
DHCP service on vmnet4 is running
Hostonly virtual adapter on vmnet4 is enabled
DHCP service on vmnet5 is running
Hostonly virtual adapter on vmnet5 is enabled
DHCP service on vmnet6 is not running
Hostonly virtual adapter on vmnet6 is enabled
DHCP service on vmnet8 is running
NAT service on vmnet8 is running
Hostonly virtual adapter on vmnet8 is enabled
DEBUG subprocess: stderr: DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
DEBUG subprocess: stderr: INFO retryable: Retryable exception raised: #<HashiCorp::VagrantVMwarefusion::Errors::VMNetDevicesWontStart: The VMware "vmnet" devices are failing to start. The most common
reason for this is collisions with existing network services. For
example, if a hostonly network space collides with another hostonly
network (such as with VirtualBox), it will fail to start. Likewise,
if forwarded ports collide with other listening ports, it will
fail to start.
Vagrant does its best to fix these issues, but in some cases it
cannot determine the root cause of these failures.
Please verify you have no other colliding network services running.
As a last resort, restarting your computer often fixes this issue.>
DEBUG subprocess: stderr: INFO vmware_driver: Killing vmnet-natd if it is alive...
DEBUG subprocess: stderr: INFO subprocess: Starting process: ["/usr/bin/pkill", "vmnet-natd"]
DEBUG subprocess: stderr: DEBUG subprocess: Command not in installer, not touching env vars.
DEBUG subprocess: stderr: INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: stderr: DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
DEBUG subprocess: stderr: INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--start"]
DEBUG subprocess: stderr: DEBUG subprocess: Command not in installer, not touching env vars.
DEBUG subprocess: stderr: INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: stderr: DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: DEBUG subprocess: stderr: Failed to start DHCP service on vmnet6
DEBUG subprocess: stderr: DEBUG subprocess: stderr: Failed to start some/all services
DEBUG subprocess: stdout: Enabled hostonly virtual adapter on vmnet1
Started DHCP service on vmnet1
Enabled hostonly virtual adapter on vmnet2
Started DHCP service on vmnet2
Enabled hostonly virtual adapter on vmnet3
Started DHCP service on vmnet3
Enabled hostonly virtual adapter on vmnet4
Started DHCP service on vmnet4
Enabled hostonly virtual adapter on vmnet5
Started DHCP service on vmnet5
Enabled hostonly virtual adapter on vmnet6
Started NAT service on vmnet8
Enabled hostonly virtual adapter on vmnet8
Started DHCP service on vmnet8
DEBUG subprocess: stderr: DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
DEBUG subprocess: stderr: INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"]
DEBUG subprocess: stderr: DEBUG subprocess: Command not in installer, not touching env vars.
DEBUG subprocess: stderr: INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: stderr: DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: DEBUG subprocess: stderr: Some/All of the configured services are not running
DEBUG subprocess: stderr: DEBUG subprocess: stdout: DHCP service on vmnet1 is running
Hostonly virtual adapter on vmnet1 is enabled
DHCP service on vmnet2 is running
Hostonly virtual adapter on vmnet2 is enabled
DHCP service on vmnet3 is running
Hostonly virtual adapter on vmnet3 is enabled
DHCP service on vmnet4 is running
Hostonly virtual adapter on vmnet4 is enabled
DHCP service on vmnet5 is running
Hostonly virtual adapter on vmnet5 is enabled
DHCP service on vmnet6 is not running
Hostonly virtual adapter on vmnet6 is enabled
DHCP service on vmnet8 is running
NAT service on vmnet8 is running
Hostonly virtual adapter on vmnet8 is enabled
DEBUG subprocess: stderr: DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
DEBUG subprocess: stderr: INFO retryable: Retryable exception raised: #<HashiCorp::VagrantVMwarefusion::Errors::VMNetDevicesWontStart: The VMware "vmnet" devices are failing to start. The most common
reason for this is collisions with existing network services. For
example, if a hostonly network space collides with another hostonly
network (such as with VirtualBox), it will fail to start. Likewise,
if forwarded ports collide with other listening ports, it will
fail to start.
Vagrant does its best to fix these issues, but in some cases it
cannot determine the root cause of these failures.
Please verify you have no other colliding network services running.
As a last resort, restarting your computer often fixes this issue.>
DEBUG subprocess: stderr: INFO vmware_driver: Killing vmnet-natd if it is alive...
DEBUG subprocess: stderr: INFO subprocess: Starting process: ["/usr/bin/pkill", "vmnet-natd"]
DEBUG subprocess: stderr: DEBUG subprocess: Command not in installer, not touching env vars.
DEBUG subprocess: stderr: INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: stderr: DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
DEBUG subprocess: stderr: INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--start"]
DEBUG subprocess: stderr: DEBUG subprocess: Command not in installer, not touching env vars.
DEBUG subprocess: stderr: INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: stderr: DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: DEBUG subprocess: stderr: Failed to start DHCP service on vmnet6
DEBUG subprocess: stderr: DEBUG subprocess: stderr: Failed to start some/all services
DEBUG subprocess: stdout: Enabled hostonly virtual adapter on vmnet1
Started DHCP service on vmnet1
Enabled hostonly virtual adapter on vmnet2
Started DHCP service on vmnet2
Enabled hostonly virtual adapter on vmnet3
Started DHCP service on vmnet3
Enabled hostonly virtual adapter on vmnet4
Started DHCP service on vmnet4
Enabled hostonly virtual adapter on vmnet5
Started DHCP service on vmnet5
Enabled hostonly virtual adapter on vmnet6
Started NAT service on vmnet8
Enabled hostonly virtual adapter on vmnet8
Started DHCP service on vmnet8
DEBUG subprocess: stderr: DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 31999
DEBUG subprocess: Exit status: 1
DEBUG subprocess: stderr: INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"]
DEBUG subprocess: stderr: DEBUG subprocess: Command not in installer, not touching env vars.
DEBUG subprocess: stderr: INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: stderr: DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: DEBUG subprocess: stderr: Some/All of the configured services are not running
DEBUG subprocess: stderr: DEBUG subprocess: stdout: DHCP service on vmnet1 is running
Hostonly virtual adapter on vmnet1 is enabled
DHCP service on vmnet2 is running
Hostonly virtual adapter on vmnet2 is enabled
DHCP service on vmnet3 is running
Hostonly virtual adapter on vmnet3 is enabled
DHCP service on vmnet4 is running
Hostonly virtual adapter on vmnet4 is enabled
DHCP service on vmnet5 is running
Hostonly virtual adapter on vmnet5 is enabled
DHCP service on vmnet6 is not running
Hostonly virtual adapter on vmnet6 is enabled
DHCP service on vmnet8 is running
NAT service on vmnet8 is running
Hostonly virtual adapter on vmnet8 is enabled
DEBUG subprocess: stderr: DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: stderr: DEBUG subprocess: Exit status: 1
DEBUG subprocess: stderr: INFO vmware_driver: Stopping services starter...
DEBUG subprocess: stderr: The VMware "vmnet" devices are failing to start. The most common
reason for this is collisions with existing network services. For
example, if a hostonly network space collides with another hostonly
network (such as with VirtualBox), it will fail to start. Likewise,
if forwarded ports collide with other listening ports, it will
fail to start.
Vagrant does its best to fix these issues, but in some cases it
cannot determine the root cause of these failures.
Please verify you have no other colliding network services running.
As a last resort, restarting your computer often fixes this issue.
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 31987
DEBUG subprocess: Exit status: 1
ERROR warden: Error occurred: INFO global: Vagrant version: 1.7.4
INFO global: Ruby version: 2.0.0
INFO global: RubyGems version: 2.0.14
INFO global: VAGRANT_LOG="debug"
INFO global: VAGRANT_OLD_ENV_SPARK_HOME="/Users/quasiben/Research/GitClones/spark"
INFO global: VAGRANT_OLD_ENV_HOME="/Users/quasiben"
INFO global: VAGRANT_OLD_ENV__="/usr/local/bin/vagrant"
INFO global: VAGRANT_OLD_ENV_XPC_FLAGS="0x0"
INFO global: VAGRANT_INSTALLER_VERSION="2"
INFO global: VAGRANT_OLD_ENV_VAGRANT_LOG="debug"
INFO global: VAGRANT_OLD_ENV_TMPDIR="/var/folders/1t/t94brwgx7sjcn8jgz4gr3_c00000gq/T/"
INFO global: VAGRANT_OLD_ENV_Apple_PubSub_Socket_Render="/private/tmp/com.apple.launchd.KW13obTzd8/Render"
INFO global: VAGRANT_OLD_ENV_JAVA_HOME="/Library/Java/JavaVirtualMachines/jdk1.7.0_45.jdk/Contents/Home"
INFO global: VAGRANT_OLD_ENV_ACHE_HOME="/Users/quasiben/anaconda/envs/memex-explorer/lib/python2.7/site-packages/ache/"
INFO global: VAGRANT_OLD_ENV_CONDA_ENV_PATH="/Users/quasiben/anaconda/envs/clusto"
INFO global: VAGRANT_OLD_ENV_PYTHONPATH="/Users/quasiben/Research/ContinuumDev/GitRepo/conda-cluster/::/Users/quasiben/Research/GitClones/spark/python"
INFO global: VAGRANT_OLD_ENV_PATH="/Users/quasiben/anaconda/envs/clusto/bin:/usr/local/bin:/usr/local/heroku/bin:/Users/quasiben/google-cloud-sdk/bin:/usr/local/sbin:/Users/quasiben/.cabal/bin/:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/texbin:/Users/quasiben/Research/ContinuumDev/GitRepo/libdynd/build"
INFO global: VAGRANT_OLD_ENV_PWD="/Users/quasiben"
INFO global: VAGRANT_OLD_ENV_ITERM_PROFILE="Default"
INFO global: VAGRANT_OLD_ENV_JDK_HOME="/Library/Java/JavaVirtualMachines/jdk1.7.0_45.jdk/Contents/Home/"
INFO global: VAGRANT_OLD_ENV_COLORFGBG="7;0"
INFO global: VAGRANT_OLD_ENV_CONDA_DEFAULT_ENV="clusto"
INFO global: VAGRANT_INSTALLER_ENV="1"
INFO global: VAGRANT_EXECUTABLE="/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/bin/vagrant"
INFO global: VAGRANT_INSTALLER_EMBEDDED_DIR="/opt/vagrant/embedded"
INFO global: VAGRANT_OLD_ENV_COMMAND_MODE="unix2003"
INFO global: VAGRANT_OLD_ENV_SSH_AUTH_SOCK="/private/tmp/com.apple.launchd.CSjdOMPkpG/Listeners"
INFO global: VAGRANT_OLD_ENV_LANG="en_US.UTF-8"
INFO global: VAGRANT_OLD_ENV_TERM_PROGRAM="iTerm.app"
INFO global: VAGRANT_OLD_ENV_XPC_SERVICE_NAME="0"
INFO global: VAGRANT_OLD_ENV_SHLVL="1"
INFO global: VAGRANT_OLD_ENV_SECURITYSESSIONID="186a5"
INFO global: VAGRANT_OLD_ENV_TERM="xterm-color"
INFO global: VAGRANT_OLD_ENV_USER="quasiben"
INFO global: VAGRANT_OLD_ENV___CF_USER_TEXT_ENCODING="0x1F7:0x0:0x0"
INFO global: VAGRANT_OLD_ENV_ITERM_SESSION_ID="w0t1p0"
INFO global: VAGRANT_OLD_ENV_SHELL="/bin/bash"
INFO global: VAGRANT_OLD_ENV_PS1="(clusto)\\[\\033[01;32m\\]\\u@\\h\\[\\033[00m\\]:\\[\\033[01;36m\\]\\w\\[\\033[00m\\]\\$ "
INFO global: VAGRANT_OLD_ENV_OLDPWD="/Users/quasiben/Research/ContinuumDev/AC_AS_Vagrant/Head+Compute/test"
INFO global: VAGRANT_OLD_ENV_JRE_HOME="/Library/Java/JavaVirtualMachines/jdk1.7.0_45.jdk/Contents/Home/jre/"
INFO global: VAGRANT_OLD_ENV_LOGNAME="quasiben"
INFO global: VAGRANT_INTERNAL_BUNDLERIZED="1"
INFO global: Plugins:
INFO global: - bundler = 1.10.5
INFO global: - mime-types = 1.25.1
INFO global: - rest-client = 1.6.9
INFO global: - vagrant-share = 1.1.4
INFO global: - vagrant-vmware-fusion = 4.0.2
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/box/plugin.rb
INFO manager: Registered plugin: box command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/destroy/plugin.rb
INFO manager: Registered plugin: destroy command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/global-status/plugin.rb
INFO manager: Registered plugin: global-status command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/halt/plugin.rb
INFO manager: Registered plugin: halt command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/help/plugin.rb
INFO manager: Registered plugin: help command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/init/plugin.rb
INFO manager: Registered plugin: init command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/list-commands/plugin.rb
INFO manager: Registered plugin: list-commands command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/login/plugin.rb
INFO manager: Registered plugin: vagrant-login
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/package/plugin.rb
INFO manager: Registered plugin: package command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/plugin/plugin.rb
INFO manager: Registered plugin: plugin command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/provision/plugin.rb
INFO manager: Registered plugin: provision command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/push/plugin.rb
INFO manager: Registered plugin: push command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/rdp/plugin.rb
INFO manager: Registered plugin: rdp command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/reload/plugin.rb
INFO manager: Registered plugin: reload command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/resume/plugin.rb
INFO manager: Registered plugin: resume command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/ssh/plugin.rb
INFO manager: Registered plugin: ssh command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/ssh_config/plugin.rb
INFO manager: Registered plugin: ssh-config command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/status/plugin.rb
INFO manager: Registered plugin: status command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/suspend/plugin.rb
INFO manager: Registered plugin: suspend command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/up/plugin.rb
INFO manager: Registered plugin: up command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/version/plugin.rb
INFO manager: Registered plugin: version command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/communicators/ssh/plugin.rb
INFO manager: Registered plugin: ssh communicator
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/communicators/winrm/plugin.rb
INFO manager: Registered plugin: winrm communicator
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/arch/plugin.rb
INFO manager: Registered plugin: Arch guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/atomic/plugin.rb
INFO manager: Registered plugin: Atomic Host guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/coreos/plugin.rb
INFO manager: Registered plugin: CoreOS guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/darwin/plugin.rb
INFO manager: Registered plugin: Darwin guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/debian/plugin.rb
INFO manager: Registered plugin: Debian guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/debian8/plugin.rb
INFO manager: Registered plugin: Debian Jessie guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/esxi/plugin.rb
INFO manager: Registered plugin: ESXi guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/fedora/plugin.rb
INFO manager: Registered plugin: Fedora guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/freebsd/plugin.rb
INFO manager: Registered plugin: FreeBSD guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/funtoo/plugin.rb
INFO manager: Registered plugin: Funtoo guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/gentoo/plugin.rb
INFO manager: Registered plugin: Gentoo guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/linux/plugin.rb
INFO manager: Registered plugin: Linux guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/mint/plugin.rb
INFO manager: Registered plugin: Mint guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/netbsd/plugin.rb
INFO manager: Registered plugin: NetBSD guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/nixos/plugin.rb
INFO manager: Registered plugin: NixOS guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/omnios/plugin.rb
INFO manager: Registered plugin: OmniOS guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/openbsd/plugin.rb
INFO manager: Registered plugin: OpenBSD guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/photon/plugin.rb
INFO manager: Registered plugin: VMware Photon guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/pld/plugin.rb
INFO manager: Registered plugin: PLD Linux guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/redhat/plugin.rb
INFO manager: Registered plugin: Red Hat Enterprise Linux guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/smartos/plugin.rb
INFO manager: Registered plugin: SmartOS guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/solaris/plugin.rb
INFO manager: Registered plugin: Solaris guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/solaris11/plugin.rb
INFO manager: Registered plugin: Solaris 11 guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/suse/plugin.rb
INFO manager: Registered plugin: SUSE guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/tinycore/plugin.rb
INFO manager: Registered plugin: TinyCore Linux guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/ubuntu/plugin.rb
INFO manager: Registered plugin: Ubuntu guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/windows/plugin.rb
INFO manager: Registered plugin: Windows guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/arch/plugin.rb
INFO manager: Registered plugin: Arch host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/bsd/plugin.rb
INFO manager: Registered plugin: BSD host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/darwin/plugin.rb
INFO manager: Registered plugin: Mac OS X host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/freebsd/plugin.rb
INFO manager: Registered plugin: FreeBSD host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/gentoo/plugin.rb
INFO manager: Registered plugin: Gentoo host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/linux/plugin.rb
INFO manager: Registered plugin: Linux host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/null/plugin.rb
INFO manager: Registered plugin: null host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/redhat/plugin.rb
INFO manager: Registered plugin: Red Hat Enterprise Linux host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/slackware/plugin.rb
INFO manager: Registered plugin: Slackware host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/suse/plugin.rb
INFO manager: Registered plugin: SUSE host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/windows/plugin.rb
INFO manager: Registered plugin: Windows host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/kernel_v1/plugin.rb
INFO manager: Registered plugin: kernel
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/kernel_v2/plugin.rb
INFO manager: Registered plugin: kernel
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/providers/docker/plugin.rb
INFO manager: Registered plugin: docker-provider
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/providers/hyperv/plugin.rb
INFO manager: Registered plugin: Hyper-V provider
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/providers/virtualbox/plugin.rb
INFO manager: Registered plugin: VirtualBox provider
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/ansible/plugin.rb
INFO manager: Registered plugin: ansible
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/cfengine/plugin.rb
INFO manager: Registered plugin: CFEngine Provisioner
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/chef/plugin.rb
INFO manager: Registered plugin: chef
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/docker/plugin.rb
INFO manager: Registered plugin: docker
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/file/plugin.rb
INFO manager: Registered plugin: file
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/puppet/plugin.rb
INFO manager: Registered plugin: puppet
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/salt/plugin.rb
INFO manager: Registered plugin: salt
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/shell/plugin.rb
INFO manager: Registered plugin: shell
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/pushes/atlas/plugin.rb
INFO manager: Registered plugin: atlas
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/pushes/ftp/plugin.rb
INFO manager: Registered plugin: ftp
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/pushes/heroku/plugin.rb
INFO manager: Registered plugin: heroku
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/pushes/local-exec/plugin.rb
INFO manager: Registered plugin: local-exec
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/pushes/noop/plugin.rb
INFO manager: Registered plugin: noop
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/synced_folders/nfs/plugin.rb
INFO manager: Registered plugin: NFS synced folders
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/synced_folders/rsync/plugin.rb
INFO manager: Registered plugin: RSync synced folders
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/synced_folders/smb/plugin.rb
INFO manager: Registered plugin: SMB synced folders
INFO manager: Registered plugin: VMware Fusion Provider
INFO vmware_driver: VMX path is a directory. Finding VMX file...
INFO vmware_driver: VMX file: /Users/quasiben/.vagrant/machines/dev/vmware_fusion/7890b8d8-98e2-4cd5-a989-d65c4e0279ae/trusty64.vmx
INFO vmware_driver: Looking for VMware Fusion: /Applications/VMware Fusion.app
INFO vmware_driver: VMware Fusion path: #<Pathname:/Applications/VMware Fusion.app>
DEBUG vmware_driver: Attempting to read VMware version...
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmware-vmx", "-v"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command is setuid/setgid, clearing DYLD_LIBRARY_PATH
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr:
VMware Fusion Information:
VMware Fusion 7.1.0 build-2314774 Release
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO vmware_driver: Detected VMware version: 7.1.0
DEBUG vmware_driver: service starter path: /Applications/VMware Fusion.app/Contents/Library/services/Open VMware Fusion Services
DEBUG vmware_driver: vmnet-cli path: /Applications/VMware Fusion.app/Contents/Library/vmnet-cli
INFO vmware:sudo_helper: Calling command: create-vmnet-device
INFO networking_file: Reading adapters from networking file...
DEBUG networking_file: VNET: 1. KEY: 'DHCP' = 'yes'
DEBUG networking_file: VNET: 1. KEY: 'DHCP_CFG_HASH' = 'D80210FE873BE2813B8C769A8E72B64979061717'
DEBUG networking_file: VNET: 1. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG networking_file: VNET: 1. KEY: 'HOSTONLY_SUBNET' = '192.168.27.0'
DEBUG networking_file: VNET: 1. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG networking_file: VNET: 2. KEY: 'DHCP' = 'yes'
DEBUG networking_file: VNET: 2. KEY: 'DHCP_CFG_HASH' = '87768080D35EC28F8A98E2922D0D6FE5E5C18A59'
DEBUG networking_file: VNET: 2. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG networking_file: VNET: 2. KEY: 'HOSTONLY_SUBNET' = '10.10.10.0'
DEBUG networking_file: VNET: 2. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG networking_file: VNET: 3. KEY: 'DHCP' = 'yes'
DEBUG networking_file: VNET: 3. KEY: 'DHCP_CFG_HASH' = '3EC4C96155C7AA76726042C1D3C8D9C208404144'
DEBUG networking_file: VNET: 3. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG networking_file: VNET: 3. KEY: 'HOSTONLY_SUBNET' = '192.168.18.0'
DEBUG networking_file: VNET: 3. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG networking_file: VNET: 4. KEY: 'DHCP' = 'yes'
DEBUG networking_file: VNET: 4. KEY: 'DHCP_CFG_HASH' = '6F6696B0E161F81ED0E3CE9F08794F4DD8D794EB'
DEBUG networking_file: VNET: 4. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG networking_file: VNET: 4. KEY: 'HOSTONLY_SUBNET' = '172.16.48.0'
DEBUG networking_file: VNET: 4. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG networking_file: VNET: 5. KEY: 'DHCP' = 'yes'
DEBUG networking_file: VNET: 5. KEY: 'DHCP_CFG_HASH' = '9B81D6F11FF984546E1C4E2B438F14AC3B559373'
DEBUG networking_file: VNET: 5. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG networking_file: VNET: 5. KEY: 'HOSTONLY_SUBNET' = '192.168.111.0'
DEBUG networking_file: VNET: 5. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG networking_file: VNET: 8. KEY: 'DHCP' = 'yes'
DEBUG networking_file: VNET: 8. KEY: 'DHCP_CFG_HASH' = '1BDC60FCCCD2EEB9E6AA5D403BE51F90BF3ACC00'
DEBUG networking_file: VNET: 8. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG networking_file: VNET: 8. KEY: 'HOSTONLY_SUBNET' = '192.168.186.0'
DEBUG networking_file: VNET: 8. KEY: 'NAT' = 'yes'
DEBUG networking_file: VNET: 8. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG networking_file: Pruning adapters that aren't actually active...
INFO vmware_driver: Starting services starter and waiting for them to start...
INFO vmware_driver: Killing vmnet-natd if it is alive...
INFO subprocess: Starting process: ["/usr/bin/pkill", "vmnet-natd"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--start"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Failed to start DHCP service on vmnet6
DEBUG subprocess: stderr: Failed to start some/all services
DEBUG subprocess: stdout: Enabled hostonly virtual adapter on vmnet1
Started DHCP service on vmnet1
Enabled hostonly virtual adapter on vmnet2
Started DHCP service on vmnet2
Enabled hostonly virtual adapter on vmnet3
Started DHCP service on vmnet3
Enabled hostonly virtual adapter on vmnet4
Started DHCP service on vmnet4
Enabled hostonly virtual adapter on vmnet5
Started DHCP service on vmnet5
Enabled hostonly virtual adapter on vmnet6
Started NAT service on vmnet8
Enabled hostonly virtual adapter on vmnet8
Started DHCP service on vmnet8
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Some/All of the configured services are not running
DEBUG subprocess: stdout: DHCP service on vmnet1 is running
Hostonly virtual adapter on vmnet1 is enabled
DHCP service on vmnet2 is running
Hostonly virtual adapter on vmnet2 is enabled
DHCP service on vmnet3 is running
Hostonly virtual adapter on vmnet3 is enabled
DHCP service on vmnet4 is running
Hostonly virtual adapter on vmnet4 is enabled
DHCP service on vmnet5 is running
Hostonly virtual adapter on vmnet5 is enabled
DHCP service on vmnet6 is not running
Hostonly virtual adapter on vmnet6 is enabled
DHCP service on vmnet8 is running
NAT service on vmnet8 is running
Hostonly virtual adapter on vmnet8 is enabled
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO retryable: Retryable exception raised: #<HashiCorp::VagrantVMwarefusion::Errors::VMNetDevicesWontStart: The VMware "vmnet" devices are failing to start. The most common
reason for this is collisions with existing network services. For
example, if a hostonly network space collides with another hostonly
network (such as with VirtualBox), it will fail to start. Likewise,
if forwarded ports collide with other listening ports, it will
fail to start.
Vagrant does its best to fix these issues, but in some cases it
cannot determine the root cause of these failures.
Please verify you have no other colliding network services running.
As a last resort, restarting your computer often fixes this issue.>
INFO vmware_driver: Killing vmnet-natd if it is alive...
INFO subprocess: Starting process: ["/usr/bin/pkill", "vmnet-natd"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--start"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Failed to start DHCP service on vmnet6
DEBUG subprocess: stderr: Failed to start some/all services
DEBUG subprocess: stdout: Enabled hostonly virtual adapter on vmnet1
Started DHCP service on vmnet1
Enabled hostonly virtual adapter on vmnet2
Started DHCP service on vmnet2
Enabled hostonly virtual adapter on vmnet3
Started DHCP service on vmnet3
Enabled hostonly virtual adapter on vmnet4
Started DHCP service on vmnet4
Enabled hostonly virtual adapter on vmnet5
Started DHCP service on vmnet5
Enabled hostonly virtual adapter on vmnet6
Started NAT service on vmnet8
Enabled hostonly virtual adapter on vmnet8
Started DHCP service on vmnet8
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Some/All of the configured services are not running
DEBUG subprocess: stdout: DHCP service on vmnet1 is running
Hostonly virtual adapter on vmnet1 is enabled
DHCP service on vmnet2 is running
Hostonly virtual adapter on vmnet2 is enabled
DHCP service on vmnet3 is running
Hostonly virtual adapter on vmnet3 is enabled
DHCP service on vmnet4 is running
Hostonly virtual adapter on vmnet4 is enabled
DHCP service on vmnet5 is running
Hostonly virtual adapter on vmnet5 is enabled
DHCP service on vmnet6 is not running
Hostonly virtual adapter on vmnet6 is enabled
DHCP service on vmnet8 is running
NAT service on vmnet8 is running
Hostonly virtual adapter on vmnet8 is enabled
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO retryable: Retryable exception raised: #<HashiCorp::VagrantVMwarefusion::Errors::VMNetDevicesWontStart: The VMware "vmnet" devices are failing to start. The most common
reason for this is collisions with existing network services. For
example, if a hostonly network space collides with another hostonly
network (such as with VirtualBox), it will fail to start. Likewise,
if forwarded ports collide with other listening ports, it will
fail to start.
Vagrant does its best to fix these issues, but in some cases it
cannot determine the root cause of these failures.
Please verify you have no other colliding network services running.
As a last resort, restarting your computer often fixes this issue.>
INFO vmware_driver: Killing vmnet-natd if it is alive...
INFO subprocess: Starting process: ["/usr/bin/pkill", "vmnet-natd"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--start"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Failed to start DHCP service on vmnet6
DEBUG subprocess: stderr: Failed to start some/all services
DEBUG subprocess: stdout: Enabled hostonly virtual adapter on vmnet1
Started DHCP service on vmnet1
Enabled hostonly virtual adapter on vmnet2
Started DHCP service on vmnet2
Enabled hostonly virtual adapter on vmnet3
Started DHCP service on vmnet3
Enabled hostonly virtual adapter on vmnet4
Started DHCP service on vmnet4
Enabled hostonly virtual adapter on vmnet5
Started DHCP service on vmnet5
Enabled hostonly virtual adapter on vmnet6
Started NAT service on vmnet8
Enabled hostonly virtual adapter on vmnet8
Started DHCP service on vmnet8
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 31999
DEBUG subprocess: Exit status: 1
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Some/All of the configured services are not running
DEBUG subprocess: stdout: DHCP service on vmnet1 is running
Hostonly virtual adapter on vmnet1 is enabled
DHCP service on vmnet2 is running
Hostonly virtual adapter on vmnet2 is enabled
DHCP service on vmnet3 is running
Hostonly virtual adapter on vmnet3 is enabled
DHCP service on vmnet4 is running
Hostonly virtual adapter on vmnet4 is enabled
DHCP service on vmnet5 is running
Hostonly virtual adapter on vmnet5 is enabled
DHCP service on vmnet6 is not running
Hostonly virtual adapter on vmnet6 is enabled
DHCP service on vmnet8 is running
NAT service on vmnet8 is running
Hostonly virtual adapter on vmnet8 is enabled
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO retryable: Retryable exception raised: #<HashiCorp::VagrantVMwarefusion::Errors::VMNetDevicesWontStart: The VMware "vmnet" devices are failing to start. The most common
reason for this is collisions with existing network services. For
example, if a hostonly network space collides with another hostonly
network (such as with VirtualBox), it will fail to start. Likewise,
if forwarded ports collide with other listening ports, it will
fail to start.
Vagrant does its best to fix these issues, but in some cases it
cannot determine the root cause of these failures.
Please verify you have no other colliding network services running.
As a last resort, restarting your computer often fixes this issue.>
INFO vmware_driver: Killing vmnet-natd if it is alive...
INFO subprocess: Starting process: ["/usr/bin/pkill", "vmnet-natd"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--start"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Failed to start DHCP service on vmnet6
DEBUG subprocess: stderr: Failed to start some/all services
DEBUG subprocess: stdout: Enabled hostonly virtual adapter on vmnet1
Started DHCP service on vmnet1
Enabled hostonly virtual adapter on vmnet2
Started DHCP service on vmnet2
Enabled hostonly virtual adapter on vmnet3
Started DHCP service on vmnet3
Enabled hostonly virtual adapter on vmnet4
Started DHCP service on vmnet4
Enabled hostonly virtual adapter on vmnet5
Started DHCP service on vmnet5
Enabled hostonly virtual adapter on vmnet6
Started NAT service on vmnet8
Enabled hostonly virtual adapter on vmnet8
Started DHCP service on vmnet8
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Some/All of the configured services are not running
DEBUG subprocess: stdout: DHCP service on vmnet1 is running
Hostonly virtual adapter on vmnet1 is enabled
DHCP service on vmnet2 is running
Hostonly virtual adapter on vmnet2 is enabled
DHCP service on vmnet3 is running
Hostonly virtual adapter on vmnet3 is enabled
DHCP service on vmnet4 is running
Hostonly virtual adapter on vmnet4 is enabled
DHCP service on vmnet5 is running
Hostonly virtual adapter on vmnet5 is enabled
DHCP service on vmnet6 is not running
Hostonly virtual adapter on vmnet6 is enabled
DHCP service on vmnet8 is running
NAT service on vmnet8 is running
Hostonly virtual adapter on vmnet8 is enabled
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO retryable: Retryable exception raised: #<HashiCorp::VagrantVMwarefusion::Errors::VMNetDevicesWontStart: The VMware "vmnet" devices are failing to start. The most common
reason for this is collisions with existing network services. For
example, if a hostonly network space collides with another hostonly
network (such as with VirtualBox), it will fail to start. Likewise,
if forwarded ports collide with other listening ports, it will
fail to start.
Vagrant does its best to fix these issues, but in some cases it
cannot determine the root cause of these failures.
Please verify you have no other colliding network services running.
As a last resort, restarting your computer often fixes this issue.>
INFO vmware_driver: Killing vmnet-natd if it is alive...
INFO subprocess: Starting process: ["/usr/bin/pkill", "vmnet-natd"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--start"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Failed to start DHCP service on vmnet6
DEBUG subprocess: stderr: Failed to start some/all services
DEBUG subprocess: stdout: Enabled hostonly virtual adapter on vmnet1
Started DHCP service on vmnet1
Enabled hostonly virtual adapter on vmnet2
Started DHCP service on vmnet2
Enabled hostonly virtual adapter on vmnet3
Started DHCP service on vmnet3
Enabled hostonly virtual adapter on vmnet4
Started DHCP service on vmnet4
Enabled hostonly virtual adapter on vmnet5
Started DHCP service on vmnet5
Enabled hostonly virtual adapter on vmnet6
Started NAT service on vmnet8
Enabled hostonly virtual adapter on vmnet8
Started DHCP service on vmnet8
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 31999
DEBUG subprocess: Exit status: 1
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Some/All of the configured services are not running
DEBUG subprocess: stdout: DHCP service on vmnet1 is running
Hostonly virtual adapter on vmnet1 is enabled
DHCP service on vmnet2 is running
Hostonly virtual adapter on vmnet2 is enabled
DHCP service on vmnet3 is running
Hostonly virtual adapter on vmnet3 is enabled
DHCP service on vmnet4 is running
Hostonly virtual adapter on vmnet4 is enabled
DHCP service on vmnet5 is running
Hostonly virtual adapter on vmnet5 is enabled
DHCP service on vmnet6 is not running
Hostonly virtual adapter on vmnet6 is enabled
DHCP service on vmnet8 is running
NAT service on vmnet8 is running
Hostonly virtual adapter on vmnet8 is enabled
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO vmware_driver: Stopping services starter...
The VMware "vmnet" devices are failing to start. The most common
reason for this is collisions with existing network services. For
example, if a hostonly network space collides with another hostonly
network (such as with VirtualBox), it will fail to start. Likewise,
if forwarded ports collide with other listening ports, it will
fail to start.
Vagrant does its best to fix these issues, but in some cases it
cannot determine the root cause of these failures.
Please verify you have no other colliding network services running.
As a last resort, restarting your computer often fixes this issue.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
ERROR warden: Error occurred: INFO global: Vagrant version: 1.7.4
INFO global: Ruby version: 2.0.0
INFO global: RubyGems version: 2.0.14
INFO global: VAGRANT_LOG="debug"
INFO global: VAGRANT_OLD_ENV_SPARK_HOME="/Users/quasiben/Research/GitClones/spark"
INFO global: VAGRANT_OLD_ENV_HOME="/Users/quasiben"
INFO global: VAGRANT_OLD_ENV__="/usr/local/bin/vagrant"
INFO global: VAGRANT_OLD_ENV_XPC_FLAGS="0x0"
INFO global: VAGRANT_INSTALLER_VERSION="2"
INFO global: VAGRANT_OLD_ENV_VAGRANT_LOG="debug"
INFO global: VAGRANT_OLD_ENV_TMPDIR="/var/folders/1t/t94brwgx7sjcn8jgz4gr3_c00000gq/T/"
INFO global: VAGRANT_OLD_ENV_Apple_PubSub_Socket_Render="/private/tmp/com.apple.launchd.KW13obTzd8/Render"
INFO global: VAGRANT_OLD_ENV_JAVA_HOME="/Library/Java/JavaVirtualMachines/jdk1.7.0_45.jdk/Contents/Home"
INFO global: VAGRANT_OLD_ENV_ACHE_HOME="/Users/quasiben/anaconda/envs/memex-explorer/lib/python2.7/site-packages/ache/"
INFO global: VAGRANT_OLD_ENV_CONDA_ENV_PATH="/Users/quasiben/anaconda/envs/clusto"
INFO global: VAGRANT_OLD_ENV_PYTHONPATH="/Users/quasiben/Research/ContinuumDev/GitRepo/conda-cluster/::/Users/quasiben/Research/GitClones/spark/python"
INFO global: VAGRANT_OLD_ENV_PATH="/Users/quasiben/anaconda/envs/clusto/bin:/usr/local/bin:/usr/local/heroku/bin:/Users/quasiben/google-cloud-sdk/bin:/usr/local/sbin:/Users/quasiben/.cabal/bin/:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/texbin:/Users/quasiben/Research/ContinuumDev/GitRepo/libdynd/build"
INFO global: VAGRANT_OLD_ENV_PWD="/Users/quasiben"
INFO global: VAGRANT_OLD_ENV_ITERM_PROFILE="Default"
INFO global: VAGRANT_OLD_ENV_JDK_HOME="/Library/Java/JavaVirtualMachines/jdk1.7.0_45.jdk/Contents/Home/"
INFO global: VAGRANT_OLD_ENV_COLORFGBG="7;0"
INFO global: VAGRANT_OLD_ENV_CONDA_DEFAULT_ENV="clusto"
INFO global: VAGRANT_INSTALLER_ENV="1"
INFO global: VAGRANT_EXECUTABLE="/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/bin/vagrant"
INFO global: VAGRANT_INSTALLER_EMBEDDED_DIR="/opt/vagrant/embedded"
INFO global: VAGRANT_OLD_ENV_COMMAND_MODE="unix2003"
INFO global: VAGRANT_OLD_ENV_SSH_AUTH_SOCK="/private/tmp/com.apple.launchd.CSjdOMPkpG/Listeners"
INFO global: VAGRANT_OLD_ENV_LANG="en_US.UTF-8"
INFO global: VAGRANT_OLD_ENV_TERM_PROGRAM="iTerm.app"
INFO global: VAGRANT_OLD_ENV_XPC_SERVICE_NAME="0"
INFO global: VAGRANT_OLD_ENV_SHLVL="1"
INFO global: VAGRANT_OLD_ENV_SECURITYSESSIONID="186a5"
INFO global: VAGRANT_OLD_ENV_TERM="xterm-color"
INFO global: VAGRANT_OLD_ENV_USER="quasiben"
INFO global: VAGRANT_OLD_ENV___CF_USER_TEXT_ENCODING="0x1F7:0x0:0x0"
INFO global: VAGRANT_OLD_ENV_ITERM_SESSION_ID="w0t1p0"
INFO global: VAGRANT_OLD_ENV_SHELL="/bin/bash"
INFO global: VAGRANT_OLD_ENV_PS1="(clusto)\\[\\033[01;32m\\]\\u@\\h\\[\\033[00m\\]:\\[\\033[01;36m\\]\\w\\[\\033[00m\\]\\$ "
INFO global: VAGRANT_OLD_ENV_OLDPWD="/Users/quasiben/Research/ContinuumDev/AC_AS_Vagrant/Head+Compute/test"
INFO global: VAGRANT_OLD_ENV_JRE_HOME="/Library/Java/JavaVirtualMachines/jdk1.7.0_45.jdk/Contents/Home/jre/"
INFO global: VAGRANT_OLD_ENV_LOGNAME="quasiben"
INFO global: VAGRANT_INTERNAL_BUNDLERIZED="1"
INFO global: Plugins:
INFO global: - bundler = 1.10.5
INFO global: - mime-types = 1.25.1
INFO global: - rest-client = 1.6.9
INFO global: - vagrant-share = 1.1.4
INFO global: - vagrant-vmware-fusion = 4.0.2
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/box/plugin.rb
INFO manager: Registered plugin: box command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/destroy/plugin.rb
INFO manager: Registered plugin: destroy command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/global-status/plugin.rb
INFO manager: Registered plugin: global-status command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/halt/plugin.rb
INFO manager: Registered plugin: halt command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/help/plugin.rb
INFO manager: Registered plugin: help command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/init/plugin.rb
INFO manager: Registered plugin: init command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/list-commands/plugin.rb
INFO manager: Registered plugin: list-commands command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/login/plugin.rb
INFO manager: Registered plugin: vagrant-login
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/package/plugin.rb
INFO manager: Registered plugin: package command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/plugin/plugin.rb
INFO manager: Registered plugin: plugin command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/provision/plugin.rb
INFO manager: Registered plugin: provision command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/push/plugin.rb
INFO manager: Registered plugin: push command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/rdp/plugin.rb
INFO manager: Registered plugin: rdp command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/reload/plugin.rb
INFO manager: Registered plugin: reload command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/resume/plugin.rb
INFO manager: Registered plugin: resume command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/ssh/plugin.rb
INFO manager: Registered plugin: ssh command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/ssh_config/plugin.rb
INFO manager: Registered plugin: ssh-config command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/status/plugin.rb
INFO manager: Registered plugin: status command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/suspend/plugin.rb
INFO manager: Registered plugin: suspend command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/up/plugin.rb
INFO manager: Registered plugin: up command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/version/plugin.rb
INFO manager: Registered plugin: version command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/communicators/ssh/plugin.rb
INFO manager: Registered plugin: ssh communicator
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/communicators/winrm/plugin.rb
INFO manager: Registered plugin: winrm communicator
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/arch/plugin.rb
INFO manager: Registered plugin: Arch guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/atomic/plugin.rb
INFO manager: Registered plugin: Atomic Host guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/coreos/plugin.rb
INFO manager: Registered plugin: CoreOS guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/darwin/plugin.rb
INFO manager: Registered plugin: Darwin guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/debian/plugin.rb
INFO manager: Registered plugin: Debian guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/debian8/plugin.rb
INFO manager: Registered plugin: Debian Jessie guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/esxi/plugin.rb
INFO manager: Registered plugin: ESXi guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/fedora/plugin.rb
INFO manager: Registered plugin: Fedora guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/freebsd/plugin.rb
INFO manager: Registered plugin: FreeBSD guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/funtoo/plugin.rb
INFO manager: Registered plugin: Funtoo guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/gentoo/plugin.rb
INFO manager: Registered plugin: Gentoo guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/linux/plugin.rb
INFO manager: Registered plugin: Linux guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/mint/plugin.rb
INFO manager: Registered plugin: Mint guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/netbsd/plugin.rb
INFO manager: Registered plugin: NetBSD guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/nixos/plugin.rb
INFO manager: Registered plugin: NixOS guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/omnios/plugin.rb
INFO manager: Registered plugin: OmniOS guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/openbsd/plugin.rb
INFO manager: Registered plugin: OpenBSD guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/photon/plugin.rb
INFO manager: Registered plugin: VMware Photon guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/pld/plugin.rb
INFO manager: Registered plugin: PLD Linux guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/redhat/plugin.rb
INFO manager: Registered plugin: Red Hat Enterprise Linux guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/smartos/plugin.rb
INFO manager: Registered plugin: SmartOS guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/solaris/plugin.rb
INFO manager: Registered plugin: Solaris guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/solaris11/plugin.rb
INFO manager: Registered plugin: Solaris 11 guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/suse/plugin.rb
INFO manager: Registered plugin: SUSE guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/tinycore/plugin.rb
INFO manager: Registered plugin: TinyCore Linux guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/ubuntu/plugin.rb
INFO manager: Registered plugin: Ubuntu guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/windows/plugin.rb
INFO manager: Registered plugin: Windows guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/arch/plugin.rb
INFO manager: Registered plugin: Arch host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/bsd/plugin.rb
INFO manager: Registered plugin: BSD host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/darwin/plugin.rb
INFO manager: Registered plugin: Mac OS X host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/freebsd/plugin.rb
INFO manager: Registered plugin: FreeBSD host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/gentoo/plugin.rb
INFO manager: Registered plugin: Gentoo host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/linux/plugin.rb
INFO manager: Registered plugin: Linux host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/null/plugin.rb
INFO manager: Registered plugin: null host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/redhat/plugin.rb
INFO manager: Registered plugin: Red Hat Enterprise Linux host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/slackware/plugin.rb
INFO manager: Registered plugin: Slackware host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/suse/plugin.rb
INFO manager: Registered plugin: SUSE host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/windows/plugin.rb
INFO manager: Registered plugin: Windows host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/kernel_v1/plugin.rb
INFO manager: Registered plugin: kernel
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/kernel_v2/plugin.rb
INFO manager: Registered plugin: kernel
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/providers/docker/plugin.rb
INFO manager: Registered plugin: docker-provider
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/providers/hyperv/plugin.rb
INFO manager: Registered plugin: Hyper-V provider
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/providers/virtualbox/plugin.rb
INFO manager: Registered plugin: VirtualBox provider
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/ansible/plugin.rb
INFO manager: Registered plugin: ansible
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/cfengine/plugin.rb
INFO manager: Registered plugin: CFEngine Provisioner
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/chef/plugin.rb
INFO manager: Registered plugin: chef
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/docker/plugin.rb
INFO manager: Registered plugin: docker
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/file/plugin.rb
INFO manager: Registered plugin: file
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/puppet/plugin.rb
INFO manager: Registered plugin: puppet
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/salt/plugin.rb
INFO manager: Registered plugin: salt
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/shell/plugin.rb
INFO manager: Registered plugin: shell
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/pushes/atlas/plugin.rb
INFO manager: Registered plugin: atlas
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/pushes/ftp/plugin.rb
INFO manager: Registered plugin: ftp
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/pushes/heroku/plugin.rb
INFO manager: Registered plugin: heroku
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/pushes/local-exec/plugin.rb
INFO manager: Registered plugin: local-exec
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/pushes/noop/plugin.rb
INFO manager: Registered plugin: noop
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/synced_folders/nfs/plugin.rb
INFO manager: Registered plugin: NFS synced folders
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/synced_folders/rsync/plugin.rb
INFO manager: Registered plugin: RSync synced folders
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/synced_folders/smb/plugin.rb
INFO manager: Registered plugin: SMB synced folders
INFO manager: Registered plugin: VMware Fusion Provider
INFO vmware_driver: VMX path is a directory. Finding VMX file...
INFO vmware_driver: VMX file: /Users/quasiben/.vagrant/machines/dev/vmware_fusion/7890b8d8-98e2-4cd5-a989-d65c4e0279ae/trusty64.vmx
INFO vmware_driver: Looking for VMware Fusion: /Applications/VMware Fusion.app
INFO vmware_driver: VMware Fusion path: #<Pathname:/Applications/VMware Fusion.app>
DEBUG vmware_driver: Attempting to read VMware version...
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmware-vmx", "-v"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command is setuid/setgid, clearing DYLD_LIBRARY_PATH
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr:
VMware Fusion Information:
VMware Fusion 7.1.0 build-2314774 Release
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO vmware_driver: Detected VMware version: 7.1.0
DEBUG vmware_driver: service starter path: /Applications/VMware Fusion.app/Contents/Library/services/Open VMware Fusion Services
DEBUG vmware_driver: vmnet-cli path: /Applications/VMware Fusion.app/Contents/Library/vmnet-cli
INFO vmware:sudo_helper: Calling command: create-vmnet-device
INFO networking_file: Reading adapters from networking file...
DEBUG networking_file: VNET: 1. KEY: 'DHCP' = 'yes'
DEBUG networking_file: VNET: 1. KEY: 'DHCP_CFG_HASH' = 'D80210FE873BE2813B8C769A8E72B64979061717'
DEBUG networking_file: VNET: 1. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG networking_file: VNET: 1. KEY: 'HOSTONLY_SUBNET' = '192.168.27.0'
DEBUG networking_file: VNET: 1. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG networking_file: VNET: 2. KEY: 'DHCP' = 'yes'
DEBUG networking_file: VNET: 2. KEY: 'DHCP_CFG_HASH' = '87768080D35EC28F8A98E2922D0D6FE5E5C18A59'
DEBUG networking_file: VNET: 2. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG networking_file: VNET: 2. KEY: 'HOSTONLY_SUBNET' = '10.10.10.0'
DEBUG networking_file: VNET: 2. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG networking_file: VNET: 3. KEY: 'DHCP' = 'yes'
DEBUG networking_file: VNET: 3. KEY: 'DHCP_CFG_HASH' = '3EC4C96155C7AA76726042C1D3C8D9C208404144'
DEBUG networking_file: VNET: 3. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG networking_file: VNET: 3. KEY: 'HOSTONLY_SUBNET' = '192.168.18.0'
DEBUG networking_file: VNET: 3. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG networking_file: VNET: 4. KEY: 'DHCP' = 'yes'
DEBUG networking_file: VNET: 4. KEY: 'DHCP_CFG_HASH' = '6F6696B0E161F81ED0E3CE9F08794F4DD8D794EB'
DEBUG networking_file: VNET: 4. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG networking_file: VNET: 4. KEY: 'HOSTONLY_SUBNET' = '172.16.48.0'
DEBUG networking_file: VNET: 4. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG networking_file: VNET: 5. KEY: 'DHCP' = 'yes'
DEBUG networking_file: VNET: 5. KEY: 'DHCP_CFG_HASH' = '9B81D6F11FF984546E1C4E2B438F14AC3B559373'
DEBUG networking_file: VNET: 5. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG networking_file: VNET: 5. KEY: 'HOSTONLY_SUBNET' = '192.168.111.0'
DEBUG networking_file: VNET: 5. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG networking_file: VNET: 8. KEY: 'DHCP' = 'yes'
DEBUG networking_file: VNET: 8. KEY: 'DHCP_CFG_HASH' = '1BDC60FCCCD2EEB9E6AA5D403BE51F90BF3ACC00'
DEBUG networking_file: VNET: 8. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG networking_file: VNET: 8. KEY: 'HOSTONLY_SUBNET' = '192.168.186.0'
DEBUG networking_file: VNET: 8. KEY: 'NAT' = 'yes'
DEBUG networking_file: VNET: 8. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG networking_file: Pruning adapters that aren't actually active...
INFO vmware_driver: Starting services starter and waiting for them to start...
INFO vmware_driver: Killing vmnet-natd if it is alive...
INFO subprocess: Starting process: ["/usr/bin/pkill", "vmnet-natd"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--start"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Failed to start DHCP service on vmnet6
DEBUG subprocess: stderr: Failed to start some/all services
DEBUG subprocess: stdout: Enabled hostonly virtual adapter on vmnet1
Started DHCP service on vmnet1
Enabled hostonly virtual adapter on vmnet2
Started DHCP service on vmnet2
Enabled hostonly virtual adapter on vmnet3
Started DHCP service on vmnet3
Enabled hostonly virtual adapter on vmnet4
Started DHCP service on vmnet4
Enabled hostonly virtual adapter on vmnet5
Started DHCP service on vmnet5
Enabled hostonly virtual adapter on vmnet6
Started NAT service on vmnet8
Enabled hostonly virtual adapter on vmnet8
Started DHCP service on vmnet8
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Some/All of the configured services are not running
DEBUG subprocess: stdout: DHCP service on vmnet1 is running
Hostonly virtual adapter on vmnet1 is enabled
DHCP service on vmnet2 is running
Hostonly virtual adapter on vmnet2 is enabled
DHCP service on vmnet3 is running
Hostonly virtual adapter on vmnet3 is enabled
DHCP service on vmnet4 is running
Hostonly virtual adapter on vmnet4 is enabled
DHCP service on vmnet5 is running
Hostonly virtual adapter on vmnet5 is enabled
DHCP service on vmnet6 is not running
Hostonly virtual adapter on vmnet6 is enabled
DHCP service on vmnet8 is running
NAT service on vmnet8 is running
Hostonly virtual adapter on vmnet8 is enabled
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO retryable: Retryable exception raised: #<HashiCorp::VagrantVMwarefusion::Errors::VMNetDevicesWontStart: The VMware "vmnet" devices are failing to start. The most common
reason for this is collisions with existing network services. For
example, if a hostonly network space collides with another hostonly
network (such as with VirtualBox), it will fail to start. Likewise,
if forwarded ports collide with other listening ports, it will
fail to start.
Vagrant does its best to fix these issues, but in some cases it
cannot determine the root cause of these failures.
Please verify you have no other colliding network services running.
As a last resort, restarting your computer often fixes this issue.>
INFO vmware_driver: Killing vmnet-natd if it is alive...
INFO subprocess: Starting process: ["/usr/bin/pkill", "vmnet-natd"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--start"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Failed to start DHCP service on vmnet6
DEBUG subprocess: stderr: Failed to start some/all services
DEBUG subprocess: stdout: Enabled hostonly virtual adapter on vmnet1
Started DHCP service on vmnet1
Enabled hostonly virtual adapter on vmnet2
Started DHCP service on vmnet2
Enabled hostonly virtual adapter on vmnet3
Started DHCP service on vmnet3
Enabled hostonly virtual adapter on vmnet4
Started DHCP service on vmnet4
Enabled hostonly virtual adapter on vmnet5
Started DHCP service on vmnet5
Enabled hostonly virtual adapter on vmnet6
Started NAT service on vmnet8
Enabled hostonly virtual adapter on vmnet8
Started DHCP service on vmnet8
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Some/All of the configured services are not running
DEBUG subprocess: stdout: DHCP service on vmnet1 is running
Hostonly virtual adapter on vmnet1 is enabled
DHCP service on vmnet2 is running
Hostonly virtual adapter on vmnet2 is enabled
DHCP service on vmnet3 is running
Hostonly virtual adapter on vmnet3 is enabled
DHCP service on vmnet4 is running
Hostonly virtual adapter on vmnet4 is enabled
DHCP service on vmnet5 is running
Hostonly virtual adapter on vmnet5 is enabled
DHCP service on vmnet6 is not running
Hostonly virtual adapter on vmnet6 is enabled
DHCP service on vmnet8 is running
NAT service on vmnet8 is running
Hostonly virtual adapter on vmnet8 is enabled
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO retryable: Retryable exception raised: #<HashiCorp::VagrantVMwarefusion::Errors::VMNetDevicesWontStart: The VMware "vmnet" devices are failing to start. The most common
reason for this is collisions with existing network services. For
example, if a hostonly network space collides with another hostonly
network (such as with VirtualBox), it will fail to start. Likewise,
if forwarded ports collide with other listening ports, it will
fail to start.
Vagrant does its best to fix these issues, but in some cases it
cannot determine the root cause of these failures.
Please verify you have no other colliding network services running.
As a last resort, restarting your computer often fixes this issue.>
INFO vmware_driver: Killing vmnet-natd if it is alive...
INFO subprocess: Starting process: ["/usr/bin/pkill", "vmnet-natd"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--start"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Failed to start DHCP service on vmnet6
DEBUG subprocess: stderr: Failed to start some/all services
DEBUG subprocess: stdout: Enabled hostonly virtual adapter on vmnet1
Started DHCP service on vmnet1
Enabled hostonly virtual adapter on vmnet2
Started DHCP service on vmnet2
Enabled hostonly virtual adapter on vmnet3
Started DHCP service on vmnet3
Enabled hostonly virtual adapter on vmnet4
Started DHCP service on vmnet4
Enabled hostonly virtual adapter on vmnet5
Started DHCP service on vmnet5
Enabled hostonly virtual adapter on vmnet6
Started NAT service on vmnet8
Enabled hostonly virtual adapter on vmnet8
Started DHCP service on vmnet8
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 31999
DEBUG subprocess: Exit status: 1
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Some/All of the configured services are not running
DEBUG subprocess: stdout: DHCP service on vmnet1 is running
Hostonly virtual adapter on vmnet1 is enabled
DHCP service on vmnet2 is running
Hostonly virtual adapter on vmnet2 is enabled
DHCP service on vmnet3 is running
Hostonly virtual adapter on vmnet3 is enabled
DHCP service on vmnet4 is running
Hostonly virtual adapter on vmnet4 is enabled
DHCP service on vmnet5 is running
Hostonly virtual adapter on vmnet5 is enabled
DHCP service on vmnet6 is not running
Hostonly virtual adapter on vmnet6 is enabled
DHCP service on vmnet8 is running
NAT service on vmnet8 is running
Hostonly virtual adapter on vmnet8 is enabled
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO retryable: Retryable exception raised: #<HashiCorp::VagrantVMwarefusion::Errors::VMNetDevicesWontStart: The VMware "vmnet" devices are failing to start. The most common
reason for this is collisions with existing network services. For
example, if a hostonly network space collides with another hostonly
network (such as with VirtualBox), it will fail to start. Likewise,
if forwarded ports collide with other listening ports, it will
fail to start.
Vagrant does its best to fix these issues, but in some cases it
cannot determine the root cause of these failures.
Please verify you have no other colliding network services running.
As a last resort, restarting your computer often fixes this issue.>
INFO vmware_driver: Killing vmnet-natd if it is alive...
INFO subprocess: Starting process: ["/usr/bin/pkill", "vmnet-natd"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--start"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Failed to start DHCP service on vmnet6
DEBUG subprocess: stderr: Failed to start some/all services
DEBUG subprocess: stdout: Enabled hostonly virtual adapter on vmnet1
Started DHCP service on vmnet1
Enabled hostonly virtual adapter on vmnet2
Started DHCP service on vmnet2
Enabled hostonly virtual adapter on vmnet3
Started DHCP service on vmnet3
Enabled hostonly virtual adapter on vmnet4
Started DHCP service on vmnet4
Enabled hostonly virtual adapter on vmnet5
Started DHCP service on vmnet5
Enabled hostonly virtual adapter on vmnet6
Started NAT service on vmnet8
Enabled hostonly virtual adapter on vmnet8
Started DHCP service on vmnet8
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Some/All of the configured services are not running
DEBUG subprocess: stdout: DHCP service on vmnet1 is running
Hostonly virtual adapter on vmnet1 is enabled
DHCP service on vmnet2 is running
Hostonly virtual adapter on vmnet2 is enabled
DHCP service on vmnet3 is running
Hostonly virtual adapter on vmnet3 is enabled
DHCP service on vmnet4 is running
Hostonly virtual adapter on vmnet4 is enabled
DHCP service on vmnet5 is running
Hostonly virtual adapter on vmnet5 is enabled
DHCP service on vmnet6 is not running
Hostonly virtual adapter on vmnet6 is enabled
DHCP service on vmnet8 is running
NAT service on vmnet8 is running
Hostonly virtual adapter on vmnet8 is enabled
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO retryable: Retryable exception raised: #<HashiCorp::VagrantVMwarefusion::Errors::VMNetDevicesWontStart: The VMware "vmnet" devices are failing to start. The most common
reason for this is collisions with existing network services. For
example, if a hostonly network space collides with another hostonly
network (such as with VirtualBox), it will fail to start. Likewise,
if forwarded ports collide with other listening ports, it will
fail to start.
Vagrant does its best to fix these issues, but in some cases it
cannot determine the root cause of these failures.
Please verify you have no other colliding network services running.
As a last resort, restarting your computer often fixes this issue.>
INFO vmware_driver: Killing vmnet-natd if it is alive...
INFO subprocess: Starting process: ["/usr/bin/pkill", "vmnet-natd"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--start"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Failed to start DHCP service on vmnet6
DEBUG subprocess: stderr: Failed to start some/all services
DEBUG subprocess: stdout: Enabled hostonly virtual adapter on vmnet1
Started DHCP service on vmnet1
Enabled hostonly virtual adapter on vmnet2
Started DHCP service on vmnet2
Enabled hostonly virtual adapter on vmnet3
Started DHCP service on vmnet3
Enabled hostonly virtual adapter on vmnet4
Started DHCP service on vmnet4
Enabled hostonly virtual adapter on vmnet5
Started DHCP service on vmnet5
Enabled hostonly virtual adapter on vmnet6
Started NAT service on vmnet8
Enabled hostonly virtual adapter on vmnet8
Started DHCP service on vmnet8
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 31999
DEBUG subprocess: Exit status: 1
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Some/All of the configured services are not running
DEBUG subprocess: stdout: DHCP service on vmnet1 is running
Hostonly virtual adapter on vmnet1 is enabled
DHCP service on vmnet2 is running
Hostonly virtual adapter on vmnet2 is enabled
DHCP service on vmnet3 is running
Hostonly virtual adapter on vmnet3 is enabled
DHCP service on vmnet4 is running
Hostonly virtual adapter on vmnet4 is enabled
DHCP service on vmnet5 is running
Hostonly virtual adapter on vmnet5 is enabled
DHCP service on vmnet6 is not running
Hostonly virtual adapter on vmnet6 is enabled
DHCP service on vmnet8 is running
NAT service on vmnet8 is running
Hostonly virtual adapter on vmnet8 is enabled
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO vmware_driver: Stopping services starter...
The VMware "vmnet" devices are failing to start. The most common
reason for this is collisions with existing network services. For
example, if a hostonly network space collides with another hostonly
network (such as with VirtualBox), it will fail to start. Likewise,
if forwarded ports collide with other listening ports, it will
fail to start.
Vagrant does its best to fix these issues, but in some cases it
cannot determine the root cause of these failures.
Please verify you have no other colliding network services running.
As a last resort, restarting your computer often fixes this issue.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
ERROR warden: Error occurred: INFO global: Vagrant version: 1.7.4
INFO global: Ruby version: 2.0.0
INFO global: RubyGems version: 2.0.14
INFO global: VAGRANT_LOG="debug"
INFO global: VAGRANT_OLD_ENV_SPARK_HOME="/Users/quasiben/Research/GitClones/spark"
INFO global: VAGRANT_OLD_ENV_HOME="/Users/quasiben"
INFO global: VAGRANT_OLD_ENV__="/usr/local/bin/vagrant"
INFO global: VAGRANT_OLD_ENV_XPC_FLAGS="0x0"
INFO global: VAGRANT_INSTALLER_VERSION="2"
INFO global: VAGRANT_OLD_ENV_VAGRANT_LOG="debug"
INFO global: VAGRANT_OLD_ENV_TMPDIR="/var/folders/1t/t94brwgx7sjcn8jgz4gr3_c00000gq/T/"
INFO global: VAGRANT_OLD_ENV_Apple_PubSub_Socket_Render="/private/tmp/com.apple.launchd.KW13obTzd8/Render"
INFO global: VAGRANT_OLD_ENV_JAVA_HOME="/Library/Java/JavaVirtualMachines/jdk1.7.0_45.jdk/Contents/Home"
INFO global: VAGRANT_OLD_ENV_ACHE_HOME="/Users/quasiben/anaconda/envs/memex-explorer/lib/python2.7/site-packages/ache/"
INFO global: VAGRANT_OLD_ENV_CONDA_ENV_PATH="/Users/quasiben/anaconda/envs/clusto"
INFO global: VAGRANT_OLD_ENV_PYTHONPATH="/Users/quasiben/Research/ContinuumDev/GitRepo/conda-cluster/::/Users/quasiben/Research/GitClones/spark/python"
INFO global: VAGRANT_OLD_ENV_PATH="/Users/quasiben/anaconda/envs/clusto/bin:/usr/local/bin:/usr/local/heroku/bin:/Users/quasiben/google-cloud-sdk/bin:/usr/local/sbin:/Users/quasiben/.cabal/bin/:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/texbin:/Users/quasiben/Research/ContinuumDev/GitRepo/libdynd/build"
INFO global: VAGRANT_OLD_ENV_PWD="/Users/quasiben"
INFO global: VAGRANT_OLD_ENV_ITERM_PROFILE="Default"
INFO global: VAGRANT_OLD_ENV_JDK_HOME="/Library/Java/JavaVirtualMachines/jdk1.7.0_45.jdk/Contents/Home/"
INFO global: VAGRANT_OLD_ENV_COLORFGBG="7;0"
INFO global: VAGRANT_OLD_ENV_CONDA_DEFAULT_ENV="clusto"
INFO global: VAGRANT_INSTALLER_ENV="1"
INFO global: VAGRANT_EXECUTABLE="/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/bin/vagrant"
INFO global: VAGRANT_INSTALLER_EMBEDDED_DIR="/opt/vagrant/embedded"
INFO global: VAGRANT_OLD_ENV_COMMAND_MODE="unix2003"
INFO global: VAGRANT_OLD_ENV_SSH_AUTH_SOCK="/private/tmp/com.apple.launchd.CSjdOMPkpG/Listeners"
INFO global: VAGRANT_OLD_ENV_LANG="en_US.UTF-8"
INFO global: VAGRANT_OLD_ENV_TERM_PROGRAM="iTerm.app"
INFO global: VAGRANT_OLD_ENV_XPC_SERVICE_NAME="0"
INFO global: VAGRANT_OLD_ENV_SHLVL="1"
INFO global: VAGRANT_OLD_ENV_SECURITYSESSIONID="186a5"
INFO global: VAGRANT_OLD_ENV_TERM="xterm-color"
INFO global: VAGRANT_OLD_ENV_USER="quasiben"
INFO global: VAGRANT_OLD_ENV___CF_USER_TEXT_ENCODING="0x1F7:0x0:0x0"
INFO global: VAGRANT_OLD_ENV_ITERM_SESSION_ID="w0t1p0"
INFO global: VAGRANT_OLD_ENV_SHELL="/bin/bash"
INFO global: VAGRANT_OLD_ENV_PS1="(clusto)\\[\\033[01;32m\\]\\u@\\h\\[\\033[00m\\]:\\[\\033[01;36m\\]\\w\\[\\033[00m\\]\\$ "
INFO global: VAGRANT_OLD_ENV_OLDPWD="/Users/quasiben/Research/ContinuumDev/AC_AS_Vagrant/Head+Compute/test"
INFO global: VAGRANT_OLD_ENV_JRE_HOME="/Library/Java/JavaVirtualMachines/jdk1.7.0_45.jdk/Contents/Home/jre/"
INFO global: VAGRANT_OLD_ENV_LOGNAME="quasiben"
INFO global: VAGRANT_INTERNAL_BUNDLERIZED="1"
INFO global: Plugins:
INFO global: - bundler = 1.10.5
INFO global: - mime-types = 1.25.1
INFO global: - rest-client = 1.6.9
INFO global: - vagrant-share = 1.1.4
INFO global: - vagrant-vmware-fusion = 4.0.2
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/box/plugin.rb
INFO manager: Registered plugin: box command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/destroy/plugin.rb
INFO manager: Registered plugin: destroy command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/global-status/plugin.rb
INFO manager: Registered plugin: global-status command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/halt/plugin.rb
INFO manager: Registered plugin: halt command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/help/plugin.rb
INFO manager: Registered plugin: help command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/init/plugin.rb
INFO manager: Registered plugin: init command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/list-commands/plugin.rb
INFO manager: Registered plugin: list-commands command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/login/plugin.rb
INFO manager: Registered plugin: vagrant-login
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/package/plugin.rb
INFO manager: Registered plugin: package command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/plugin/plugin.rb
INFO manager: Registered plugin: plugin command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/provision/plugin.rb
INFO manager: Registered plugin: provision command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/push/plugin.rb
INFO manager: Registered plugin: push command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/rdp/plugin.rb
INFO manager: Registered plugin: rdp command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/reload/plugin.rb
INFO manager: Registered plugin: reload command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/resume/plugin.rb
INFO manager: Registered plugin: resume command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/ssh/plugin.rb
INFO manager: Registered plugin: ssh command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/ssh_config/plugin.rb
INFO manager: Registered plugin: ssh-config command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/status/plugin.rb
INFO manager: Registered plugin: status command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/suspend/plugin.rb
INFO manager: Registered plugin: suspend command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/up/plugin.rb
INFO manager: Registered plugin: up command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/version/plugin.rb
INFO manager: Registered plugin: version command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/communicators/ssh/plugin.rb
INFO manager: Registered plugin: ssh communicator
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/communicators/winrm/plugin.rb
INFO manager: Registered plugin: winrm communicator
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/arch/plugin.rb
INFO manager: Registered plugin: Arch guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/atomic/plugin.rb
INFO manager: Registered plugin: Atomic Host guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/coreos/plugin.rb
INFO manager: Registered plugin: CoreOS guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/darwin/plugin.rb
INFO manager: Registered plugin: Darwin guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/debian/plugin.rb
INFO manager: Registered plugin: Debian guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/debian8/plugin.rb
INFO manager: Registered plugin: Debian Jessie guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/esxi/plugin.rb
INFO manager: Registered plugin: ESXi guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/fedora/plugin.rb
INFO manager: Registered plugin: Fedora guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/freebsd/plugin.rb
INFO manager: Registered plugin: FreeBSD guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/funtoo/plugin.rb
INFO manager: Registered plugin: Funtoo guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/gentoo/plugin.rb
INFO manager: Registered plugin: Gentoo guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/linux/plugin.rb
INFO manager: Registered plugin: Linux guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/mint/plugin.rb
INFO manager: Registered plugin: Mint guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/netbsd/plugin.rb
INFO manager: Registered plugin: NetBSD guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/nixos/plugin.rb
INFO manager: Registered plugin: NixOS guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/omnios/plugin.rb
INFO manager: Registered plugin: OmniOS guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/openbsd/plugin.rb
INFO manager: Registered plugin: OpenBSD guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/photon/plugin.rb
INFO manager: Registered plugin: VMware Photon guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/pld/plugin.rb
INFO manager: Registered plugin: PLD Linux guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/redhat/plugin.rb
INFO manager: Registered plugin: Red Hat Enterprise Linux guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/smartos/plugin.rb
INFO manager: Registered plugin: SmartOS guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/solaris/plugin.rb
INFO manager: Registered plugin: Solaris guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/solaris11/plugin.rb
INFO manager: Registered plugin: Solaris 11 guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/suse/plugin.rb
INFO manager: Registered plugin: SUSE guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/tinycore/plugin.rb
INFO manager: Registered plugin: TinyCore Linux guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/ubuntu/plugin.rb
INFO manager: Registered plugin: Ubuntu guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/windows/plugin.rb
INFO manager: Registered plugin: Windows guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/arch/plugin.rb
INFO manager: Registered plugin: Arch host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/bsd/plugin.rb
INFO manager: Registered plugin: BSD host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/darwin/plugin.rb
INFO manager: Registered plugin: Mac OS X host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/freebsd/plugin.rb
INFO manager: Registered plugin: FreeBSD host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/gentoo/plugin.rb
INFO manager: Registered plugin: Gentoo host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/linux/plugin.rb
INFO manager: Registered plugin: Linux host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/null/plugin.rb
INFO manager: Registered plugin: null host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/redhat/plugin.rb
INFO manager: Registered plugin: Red Hat Enterprise Linux host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/slackware/plugin.rb
INFO manager: Registered plugin: Slackware host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/suse/plugin.rb
INFO manager: Registered plugin: SUSE host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/windows/plugin.rb
INFO manager: Registered plugin: Windows host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/kernel_v1/plugin.rb
INFO manager: Registered plugin: kernel
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/kernel_v2/plugin.rb
INFO manager: Registered plugin: kernel
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/providers/docker/plugin.rb
INFO manager: Registered plugin: docker-provider
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/providers/hyperv/plugin.rb
INFO manager: Registered plugin: Hyper-V provider
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/providers/virtualbox/plugin.rb
INFO manager: Registered plugin: VirtualBox provider
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/ansible/plugin.rb
INFO manager: Registered plugin: ansible
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/cfengine/plugin.rb
INFO manager: Registered plugin: CFEngine Provisioner
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/chef/plugin.rb
INFO manager: Registered plugin: chef
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/docker/plugin.rb
INFO manager: Registered plugin: docker
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/file/plugin.rb
INFO manager: Registered plugin: file
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/puppet/plugin.rb
INFO manager: Registered plugin: puppet
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/salt/plugin.rb
INFO manager: Registered plugin: salt
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/shell/plugin.rb
INFO manager: Registered plugin: shell
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/pushes/atlas/plugin.rb
INFO manager: Registered plugin: atlas
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/pushes/ftp/plugin.rb
INFO manager: Registered plugin: ftp
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/pushes/heroku/plugin.rb
INFO manager: Registered plugin: heroku
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/pushes/local-exec/plugin.rb
INFO manager: Registered plugin: local-exec
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/pushes/noop/plugin.rb
INFO manager: Registered plugin: noop
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/synced_folders/nfs/plugin.rb
INFO manager: Registered plugin: NFS synced folders
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/synced_folders/rsync/plugin.rb
INFO manager: Registered plugin: RSync synced folders
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/synced_folders/smb/plugin.rb
INFO manager: Registered plugin: SMB synced folders
INFO manager: Registered plugin: VMware Fusion Provider
INFO vmware_driver: VMX path is a directory. Finding VMX file...
INFO vmware_driver: VMX file: /Users/quasiben/.vagrant/machines/dev/vmware_fusion/7890b8d8-98e2-4cd5-a989-d65c4e0279ae/trusty64.vmx
INFO vmware_driver: Looking for VMware Fusion: /Applications/VMware Fusion.app
INFO vmware_driver: VMware Fusion path: #<Pathname:/Applications/VMware Fusion.app>
DEBUG vmware_driver: Attempting to read VMware version...
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmware-vmx", "-v"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command is setuid/setgid, clearing DYLD_LIBRARY_PATH
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr:
VMware Fusion Information:
VMware Fusion 7.1.0 build-2314774 Release
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO vmware_driver: Detected VMware version: 7.1.0
DEBUG vmware_driver: service starter path: /Applications/VMware Fusion.app/Contents/Library/services/Open VMware Fusion Services
DEBUG vmware_driver: vmnet-cli path: /Applications/VMware Fusion.app/Contents/Library/vmnet-cli
INFO vmware:sudo_helper: Calling command: create-vmnet-device
INFO networking_file: Reading adapters from networking file...
DEBUG networking_file: VNET: 1. KEY: 'DHCP' = 'yes'
DEBUG networking_file: VNET: 1. KEY: 'DHCP_CFG_HASH' = 'D80210FE873BE2813B8C769A8E72B64979061717'
DEBUG networking_file: VNET: 1. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG networking_file: VNET: 1. KEY: 'HOSTONLY_SUBNET' = '192.168.27.0'
DEBUG networking_file: VNET: 1. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG networking_file: VNET: 2. KEY: 'DHCP' = 'yes'
DEBUG networking_file: VNET: 2. KEY: 'DHCP_CFG_HASH' = '87768080D35EC28F8A98E2922D0D6FE5E5C18A59'
DEBUG networking_file: VNET: 2. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG networking_file: VNET: 2. KEY: 'HOSTONLY_SUBNET' = '10.10.10.0'
DEBUG networking_file: VNET: 2. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG networking_file: VNET: 3. KEY: 'DHCP' = 'yes'
DEBUG networking_file: VNET: 3. KEY: 'DHCP_CFG_HASH' = '3EC4C96155C7AA76726042C1D3C8D9C208404144'
DEBUG networking_file: VNET: 3. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG networking_file: VNET: 3. KEY: 'HOSTONLY_SUBNET' = '192.168.18.0'
DEBUG networking_file: VNET: 3. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG networking_file: VNET: 4. KEY: 'DHCP' = 'yes'
DEBUG networking_file: VNET: 4. KEY: 'DHCP_CFG_HASH' = '6F6696B0E161F81ED0E3CE9F08794F4DD8D794EB'
DEBUG networking_file: VNET: 4. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG networking_file: VNET: 4. KEY: 'HOSTONLY_SUBNET' = '172.16.48.0'
DEBUG networking_file: VNET: 4. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG networking_file: VNET: 5. KEY: 'DHCP' = 'yes'
DEBUG networking_file: VNET: 5. KEY: 'DHCP_CFG_HASH' = '9B81D6F11FF984546E1C4E2B438F14AC3B559373'
DEBUG networking_file: VNET: 5. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG networking_file: VNET: 5. KEY: 'HOSTONLY_SUBNET' = '192.168.111.0'
DEBUG networking_file: VNET: 5. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG networking_file: VNET: 8. KEY: 'DHCP' = 'yes'
DEBUG networking_file: VNET: 8. KEY: 'DHCP_CFG_HASH' = '1BDC60FCCCD2EEB9E6AA5D403BE51F90BF3ACC00'
DEBUG networking_file: VNET: 8. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG networking_file: VNET: 8. KEY: 'HOSTONLY_SUBNET' = '192.168.186.0'
DEBUG networking_file: VNET: 8. KEY: 'NAT' = 'yes'
DEBUG networking_file: VNET: 8. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG networking_file: Pruning adapters that aren't actually active...
INFO vmware_driver: Starting services starter and waiting for them to start...
INFO vmware_driver: Killing vmnet-natd if it is alive...
INFO subprocess: Starting process: ["/usr/bin/pkill", "vmnet-natd"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--start"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Failed to start DHCP service on vmnet6
DEBUG subprocess: stderr: Failed to start some/all services
DEBUG subprocess: stdout: Enabled hostonly virtual adapter on vmnet1
Started DHCP service on vmnet1
Enabled hostonly virtual adapter on vmnet2
Started DHCP service on vmnet2
Enabled hostonly virtual adapter on vmnet3
Started DHCP service on vmnet3
Enabled hostonly virtual adapter on vmnet4
Started DHCP service on vmnet4
Enabled hostonly virtual adapter on vmnet5
Started DHCP service on vmnet5
Enabled hostonly virtual adapter on vmnet6
Started NAT service on vmnet8
Enabled hostonly virtual adapter on vmnet8
Started DHCP service on vmnet8
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Some/All of the configured services are not running
DEBUG subprocess: stdout: DHCP service on vmnet1 is running
Hostonly virtual adapter on vmnet1 is enabled
DHCP service on vmnet2 is running
Hostonly virtual adapter on vmnet2 is enabled
DHCP service on vmnet3 is running
Hostonly virtual adapter on vmnet3 is enabled
DHCP service on vmnet4 is running
Hostonly virtual adapter on vmnet4 is enabled
DHCP service on vmnet5 is running
Hostonly virtual adapter on vmnet5 is enabled
DHCP service on vmnet6 is not running
Hostonly virtual adapter on vmnet6 is enabled
DHCP service on vmnet8 is running
NAT service on vmnet8 is running
Hostonly virtual adapter on vmnet8 is enabled
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO retryable: Retryable exception raised: #<HashiCorp::VagrantVMwarefusion::Errors::VMNetDevicesWontStart: The VMware "vmnet" devices are failing to start. The most common
reason for this is collisions with existing network services. For
example, if a hostonly network space collides with another hostonly
network (such as with VirtualBox), it will fail to start. Likewise,
if forwarded ports collide with other listening ports, it will
fail to start.
Vagrant does its best to fix these issues, but in some cases it
cannot determine the root cause of these failures.
Please verify you have no other colliding network services running.
As a last resort, restarting your computer often fixes this issue.>
INFO vmware_driver: Killing vmnet-natd if it is alive...
INFO subprocess: Starting process: ["/usr/bin/pkill", "vmnet-natd"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--start"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Failed to start DHCP service on vmnet6
DEBUG subprocess: stderr: Failed to start some/all services
DEBUG subprocess: stdout: Enabled hostonly virtual adapter on vmnet1
Started DHCP service on vmnet1
Enabled hostonly virtual adapter on vmnet2
Started DHCP service on vmnet2
Enabled hostonly virtual adapter on vmnet3
Started DHCP service on vmnet3
Enabled hostonly virtual adapter on vmnet4
Started DHCP service on vmnet4
Enabled hostonly virtual adapter on vmnet5
Started DHCP service on vmnet5
Enabled hostonly virtual adapter on vmnet6
Started NAT service on vmnet8
Enabled hostonly virtual adapter on vmnet8
Started DHCP service on vmnet8
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Some/All of the configured services are not running
DEBUG subprocess: stdout: DHCP service on vmnet1 is running
Hostonly virtual adapter on vmnet1 is enabled
DHCP service on vmnet2 is running
Hostonly virtual adapter on vmnet2 is enabled
DHCP service on vmnet3 is running
Hostonly virtual adapter on vmnet3 is enabled
DHCP service on vmnet4 is running
Hostonly virtual adapter on vmnet4 is enabled
DHCP service on vmnet5 is running
Hostonly virtual adapter on vmnet5 is enabled
DHCP service on vmnet6 is not running
Hostonly virtual adapter on vmnet6 is enabled
DHCP service on vmnet8 is running
NAT service on vmnet8 is running
Hostonly virtual adapter on vmnet8 is enabled
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO retryable: Retryable exception raised: #<HashiCorp::VagrantVMwarefusion::Errors::VMNetDevicesWontStart: The VMware "vmnet" devices are failing to start. The most common
reason for this is collisions with existing network services. For
example, if a hostonly network space collides with another hostonly
network (such as with VirtualBox), it will fail to start. Likewise,
if forwarded ports collide with other listening ports, it will
fail to start.
Vagrant does its best to fix these issues, but in some cases it
cannot determine the root cause of these failures.
Please verify you have no other colliding network services running.
As a last resort, restarting your computer often fixes this issue.>
INFO vmware_driver: Killing vmnet-natd if it is alive...
INFO subprocess: Starting process: ["/usr/bin/pkill", "vmnet-natd"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--start"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Failed to start DHCP service on vmnet6
DEBUG subprocess: stderr: Failed to start some/all services
DEBUG subprocess: stdout: Enabled hostonly virtual adapter on vmnet1
Started DHCP service on vmnet1
Enabled hostonly virtual adapter on vmnet2
Started DHCP service on vmnet2
Enabled hostonly virtual adapter on vmnet3
Started DHCP service on vmnet3
Enabled hostonly virtual adapter on vmnet4
Started DHCP service on vmnet4
Enabled hostonly virtual adapter on vmnet5
Started DHCP service on vmnet5
Enabled hostonly virtual adapter on vmnet6
Started NAT service on vmnet8
Enabled hostonly virtual adapter on vmnet8
Started DHCP service on vmnet8
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 31999
DEBUG subprocess: Exit status: 1
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Some/All of the configured services are not running
DEBUG subprocess: stdout: DHCP service on vmnet1 is running
Hostonly virtual adapter on vmnet1 is enabled
DHCP service on vmnet2 is running
Hostonly virtual adapter on vmnet2 is enabled
DHCP service on vmnet3 is running
Hostonly virtual adapter on vmnet3 is enabled
DHCP service on vmnet4 is running
Hostonly virtual adapter on vmnet4 is enabled
DHCP service on vmnet5 is running
Hostonly virtual adapter on vmnet5 is enabled
DHCP service on vmnet6 is not running
Hostonly virtual adapter on vmnet6 is enabled
DHCP service on vmnet8 is running
NAT service on vmnet8 is running
Hostonly virtual adapter on vmnet8 is enabled
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO retryable: Retryable exception raised: #<HashiCorp::VagrantVMwarefusion::Errors::VMNetDevicesWontStart: The VMware "vmnet" devices are failing to start. The most common
reason for this is collisions with existing network services. For
example, if a hostonly network space collides with another hostonly
network (such as with VirtualBox), it will fail to start. Likewise,
if forwarded ports collide with other listening ports, it will
fail to start.
Vagrant does its best to fix these issues, but in some cases it
cannot determine the root cause of these failures.
Please verify you have no other colliding network services running.
As a last resort, restarting your computer often fixes this issue.>
INFO vmware_driver: Killing vmnet-natd if it is alive...
INFO subprocess: Starting process: ["/usr/bin/pkill", "vmnet-natd"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--start"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Failed to start DHCP service on vmnet6
DEBUG subprocess: stderr: Failed to start some/all services
DEBUG subprocess: stdout: Enabled hostonly virtual adapter on vmnet1
Started DHCP service on vmnet1
Enabled hostonly virtual adapter on vmnet2
Started DHCP service on vmnet2
Enabled hostonly virtual adapter on vmnet3
Started DHCP service on vmnet3
Enabled hostonly virtual adapter on vmnet4
Started DHCP service on vmnet4
Enabled hostonly virtual adapter on vmnet5
Started DHCP service on vmnet5
Enabled hostonly virtual adapter on vmnet6
Started NAT service on vmnet8
Enabled hostonly virtual adapter on vmnet8
Started DHCP service on vmnet8
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Some/All of the configured services are not running
DEBUG subprocess: stdout: DHCP service on vmnet1 is running
Hostonly virtual adapter on vmnet1 is enabled
DHCP service on vmnet2 is running
Hostonly virtual adapter on vmnet2 is enabled
DHCP service on vmnet3 is running
Hostonly virtual adapter on vmnet3 is enabled
DHCP service on vmnet4 is running
Hostonly virtual adapter on vmnet4 is enabled
DHCP service on vmnet5 is running
Hostonly virtual adapter on vmnet5 is enabled
DHCP service on vmnet6 is not running
Hostonly virtual adapter on vmnet6 is enabled
DHCP service on vmnet8 is running
NAT service on vmnet8 is running
Hostonly virtual adapter on vmnet8 is enabled
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO retryable: Retryable exception raised: #<HashiCorp::VagrantVMwarefusion::Errors::VMNetDevicesWontStart: The VMware "vmnet" devices are failing to start. The most common
reason for this is collisions with existing network services. For
example, if a hostonly network space collides with another hostonly
network (such as with VirtualBox), it will fail to start. Likewise,
if forwarded ports collide with other listening ports, it will
fail to start.
Vagrant does its best to fix these issues, but in some cases it
cannot determine the root cause of these failures.
Please verify you have no other colliding network services running.
As a last resort, restarting your computer often fixes this issue.>
INFO vmware_driver: Killing vmnet-natd if it is alive...
INFO subprocess: Starting process: ["/usr/bin/pkill", "vmnet-natd"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--start"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Failed to start DHCP service on vmnet6
DEBUG subprocess: stderr: Failed to start some/all services
DEBUG subprocess: stdout: Enabled hostonly virtual adapter on vmnet1
Started DHCP service on vmnet1
Enabled hostonly virtual adapter on vmnet2
Started DHCP service on vmnet2
Enabled hostonly virtual adapter on vmnet3
Started DHCP service on vmnet3
Enabled hostonly virtual adapter on vmnet4
Started DHCP service on vmnet4
Enabled hostonly virtual adapter on vmnet5
Started DHCP service on vmnet5
Enabled hostonly virtual adapter on vmnet6
Started NAT service on vmnet8
Enabled hostonly virtual adapter on vmnet8
Started DHCP service on vmnet8
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 31999
DEBUG subprocess: Exit status: 1
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Some/All of the configured services are not running
DEBUG subprocess: stdout: DHCP service on vmnet1 is running
Hostonly virtual adapter on vmnet1 is enabled
DHCP service on vmnet2 is running
Hostonly virtual adapter on vmnet2 is enabled
DHCP service on vmnet3 is running
Hostonly virtual adapter on vmnet3 is enabled
DHCP service on vmnet4 is running
Hostonly virtual adapter on vmnet4 is enabled
DHCP service on vmnet5 is running
Hostonly virtual adapter on vmnet5 is enabled
DHCP service on vmnet6 is not running
Hostonly virtual adapter on vmnet6 is enabled
DHCP service on vmnet8 is running
NAT service on vmnet8 is running
Hostonly virtual adapter on vmnet8 is enabled
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO vmware_driver: Stopping services starter...
The VMware "vmnet" devices are failing to start. The most common
reason for this is collisions with existing network services. For
example, if a hostonly network space collides with another hostonly
network (such as with VirtualBox), it will fail to start. Likewise,
if forwarded ports collide with other listening ports, it will
fail to start.
Vagrant does its best to fix these issues, but in some cases it
cannot determine the root cause of these failures.
Please verify you have no other colliding network services running.
As a last resort, restarting your computer often fixes this issue.
INFO warden: Beginning recovery process...
INFO warden: Calling recover: #<Vagrant::Action::Builtin::Call:0x00000102a409b8>
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
ERROR warden: Error occurred: INFO global: Vagrant version: 1.7.4
INFO global: Ruby version: 2.0.0
INFO global: RubyGems version: 2.0.14
INFO global: VAGRANT_LOG="debug"
INFO global: VAGRANT_OLD_ENV_SPARK_HOME="/Users/quasiben/Research/GitClones/spark"
INFO global: VAGRANT_OLD_ENV_HOME="/Users/quasiben"
INFO global: VAGRANT_OLD_ENV__="/usr/local/bin/vagrant"
INFO global: VAGRANT_OLD_ENV_XPC_FLAGS="0x0"
INFO global: VAGRANT_INSTALLER_VERSION="2"
INFO global: VAGRANT_OLD_ENV_VAGRANT_LOG="debug"
INFO global: VAGRANT_OLD_ENV_TMPDIR="/var/folders/1t/t94brwgx7sjcn8jgz4gr3_c00000gq/T/"
INFO global: VAGRANT_OLD_ENV_Apple_PubSub_Socket_Render="/private/tmp/com.apple.launchd.KW13obTzd8/Render"
INFO global: VAGRANT_OLD_ENV_JAVA_HOME="/Library/Java/JavaVirtualMachines/jdk1.7.0_45.jdk/Contents/Home"
INFO global: VAGRANT_OLD_ENV_ACHE_HOME="/Users/quasiben/anaconda/envs/memex-explorer/lib/python2.7/site-packages/ache/"
INFO global: VAGRANT_OLD_ENV_CONDA_ENV_PATH="/Users/quasiben/anaconda/envs/clusto"
INFO global: VAGRANT_OLD_ENV_PYTHONPATH="/Users/quasiben/Research/ContinuumDev/GitRepo/conda-cluster/::/Users/quasiben/Research/GitClones/spark/python"
INFO global: VAGRANT_OLD_ENV_PATH="/Users/quasiben/anaconda/envs/clusto/bin:/usr/local/bin:/usr/local/heroku/bin:/Users/quasiben/google-cloud-sdk/bin:/usr/local/sbin:/Users/quasiben/.cabal/bin/:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/texbin:/Users/quasiben/Research/ContinuumDev/GitRepo/libdynd/build"
INFO global: VAGRANT_OLD_ENV_PWD="/Users/quasiben"
INFO global: VAGRANT_OLD_ENV_ITERM_PROFILE="Default"
INFO global: VAGRANT_OLD_ENV_JDK_HOME="/Library/Java/JavaVirtualMachines/jdk1.7.0_45.jdk/Contents/Home/"
INFO global: VAGRANT_OLD_ENV_COLORFGBG="7;0"
INFO global: VAGRANT_OLD_ENV_CONDA_DEFAULT_ENV="clusto"
INFO global: VAGRANT_INSTALLER_ENV="1"
INFO global: VAGRANT_EXECUTABLE="/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/bin/vagrant"
INFO global: VAGRANT_INSTALLER_EMBEDDED_DIR="/opt/vagrant/embedded"
INFO global: VAGRANT_OLD_ENV_COMMAND_MODE="unix2003"
INFO global: VAGRANT_OLD_ENV_SSH_AUTH_SOCK="/private/tmp/com.apple.launchd.CSjdOMPkpG/Listeners"
INFO global: VAGRANT_OLD_ENV_LANG="en_US.UTF-8"
INFO global: VAGRANT_OLD_ENV_TERM_PROGRAM="iTerm.app"
INFO global: VAGRANT_OLD_ENV_XPC_SERVICE_NAME="0"
INFO global: VAGRANT_OLD_ENV_SHLVL="1"
INFO global: VAGRANT_OLD_ENV_SECURITYSESSIONID="186a5"
INFO global: VAGRANT_OLD_ENV_TERM="xterm-color"
INFO global: VAGRANT_OLD_ENV_USER="quasiben"
INFO global: VAGRANT_OLD_ENV___CF_USER_TEXT_ENCODING="0x1F7:0x0:0x0"
INFO global: VAGRANT_OLD_ENV_ITERM_SESSION_ID="w0t1p0"
INFO global: VAGRANT_OLD_ENV_SHELL="/bin/bash"
INFO global: VAGRANT_OLD_ENV_PS1="(clusto)\\[\\033[01;32m\\]\\u@\\h\\[\\033[00m\\]:\\[\\033[01;36m\\]\\w\\[\\033[00m\\]\\$ "
INFO global: VAGRANT_OLD_ENV_OLDPWD="/Users/quasiben/Research/ContinuumDev/AC_AS_Vagrant/Head+Compute/test"
INFO global: VAGRANT_OLD_ENV_JRE_HOME="/Library/Java/JavaVirtualMachines/jdk1.7.0_45.jdk/Contents/Home/jre/"
INFO global: VAGRANT_OLD_ENV_LOGNAME="quasiben"
INFO global: VAGRANT_INTERNAL_BUNDLERIZED="1"
INFO global: Plugins:
INFO global: - bundler = 1.10.5
INFO global: - mime-types = 1.25.1
INFO global: - rest-client = 1.6.9
INFO global: - vagrant-share = 1.1.4
INFO global: - vagrant-vmware-fusion = 4.0.2
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/box/plugin.rb
INFO manager: Registered plugin: box command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/destroy/plugin.rb
INFO manager: Registered plugin: destroy command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/global-status/plugin.rb
INFO manager: Registered plugin: global-status command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/halt/plugin.rb
INFO manager: Registered plugin: halt command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/help/plugin.rb
INFO manager: Registered plugin: help command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/init/plugin.rb
INFO manager: Registered plugin: init command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/list-commands/plugin.rb
INFO manager: Registered plugin: list-commands command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/login/plugin.rb
INFO manager: Registered plugin: vagrant-login
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/package/plugin.rb
INFO manager: Registered plugin: package command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/plugin/plugin.rb
INFO manager: Registered plugin: plugin command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/provision/plugin.rb
INFO manager: Registered plugin: provision command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/push/plugin.rb
INFO manager: Registered plugin: push command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/rdp/plugin.rb
INFO manager: Registered plugin: rdp command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/reload/plugin.rb
INFO manager: Registered plugin: reload command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/resume/plugin.rb
INFO manager: Registered plugin: resume command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/ssh/plugin.rb
INFO manager: Registered plugin: ssh command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/ssh_config/plugin.rb
INFO manager: Registered plugin: ssh-config command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/status/plugin.rb
INFO manager: Registered plugin: status command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/suspend/plugin.rb
INFO manager: Registered plugin: suspend command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/up/plugin.rb
INFO manager: Registered plugin: up command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/version/plugin.rb
INFO manager: Registered plugin: version command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/communicators/ssh/plugin.rb
INFO manager: Registered plugin: ssh communicator
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/communicators/winrm/plugin.rb
INFO manager: Registered plugin: winrm communicator
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/arch/plugin.rb
INFO manager: Registered plugin: Arch guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/atomic/plugin.rb
INFO manager: Registered plugin: Atomic Host guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/coreos/plugin.rb
INFO manager: Registered plugin: CoreOS guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/darwin/plugin.rb
INFO manager: Registered plugin: Darwin guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/debian/plugin.rb
INFO manager: Registered plugin: Debian guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/debian8/plugin.rb
INFO manager: Registered plugin: Debian Jessie guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/esxi/plugin.rb
INFO manager: Registered plugin: ESXi guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/fedora/plugin.rb
INFO manager: Registered plugin: Fedora guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/freebsd/plugin.rb
INFO manager: Registered plugin: FreeBSD guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/funtoo/plugin.rb
INFO manager: Registered plugin: Funtoo guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/gentoo/plugin.rb
INFO manager: Registered plugin: Gentoo guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/linux/plugin.rb
INFO manager: Registered plugin: Linux guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/mint/plugin.rb
INFO manager: Registered plugin: Mint guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/netbsd/plugin.rb
INFO manager: Registered plugin: NetBSD guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/nixos/plugin.rb
INFO manager: Registered plugin: NixOS guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/omnios/plugin.rb
INFO manager: Registered plugin: OmniOS guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/openbsd/plugin.rb
INFO manager: Registered plugin: OpenBSD guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/photon/plugin.rb
INFO manager: Registered plugin: VMware Photon guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/pld/plugin.rb
INFO manager: Registered plugin: PLD Linux guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/redhat/plugin.rb
INFO manager: Registered plugin: Red Hat Enterprise Linux guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/smartos/plugin.rb
INFO manager: Registered plugin: SmartOS guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/solaris/plugin.rb
INFO manager: Registered plugin: Solaris guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/solaris11/plugin.rb
INFO manager: Registered plugin: Solaris 11 guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/suse/plugin.rb
INFO manager: Registered plugin: SUSE guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/tinycore/plugin.rb
INFO manager: Registered plugin: TinyCore Linux guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/ubuntu/plugin.rb
INFO manager: Registered plugin: Ubuntu guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/windows/plugin.rb
INFO manager: Registered plugin: Windows guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/arch/plugin.rb
INFO manager: Registered plugin: Arch host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/bsd/plugin.rb
INFO manager: Registered plugin: BSD host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/darwin/plugin.rb
INFO manager: Registered plugin: Mac OS X host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/freebsd/plugin.rb
INFO manager: Registered plugin: FreeBSD host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/gentoo/plugin.rb
INFO manager: Registered plugin: Gentoo host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/linux/plugin.rb
INFO manager: Registered plugin: Linux host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/null/plugin.rb
INFO manager: Registered plugin: null host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/redhat/plugin.rb
INFO manager: Registered plugin: Red Hat Enterprise Linux host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/slackware/plugin.rb
INFO manager: Registered plugin: Slackware host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/suse/plugin.rb
INFO manager: Registered plugin: SUSE host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/windows/plugin.rb
INFO manager: Registered plugin: Windows host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/kernel_v1/plugin.rb
INFO manager: Registered plugin: kernel
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/kernel_v2/plugin.rb
INFO manager: Registered plugin: kernel
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/providers/docker/plugin.rb
INFO manager: Registered plugin: docker-provider
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/providers/hyperv/plugin.rb
INFO manager: Registered plugin: Hyper-V provider
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/providers/virtualbox/plugin.rb
INFO manager: Registered plugin: VirtualBox provider
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/ansible/plugin.rb
INFO manager: Registered plugin: ansible
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/cfengine/plugin.rb
INFO manager: Registered plugin: CFEngine Provisioner
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/chef/plugin.rb
INFO manager: Registered plugin: chef
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/docker/plugin.rb
INFO manager: Registered plugin: docker
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/file/plugin.rb
INFO manager: Registered plugin: file
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/puppet/plugin.rb
INFO manager: Registered plugin: puppet
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/salt/plugin.rb
INFO manager: Registered plugin: salt
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/shell/plugin.rb
INFO manager: Registered plugin: shell
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/pushes/atlas/plugin.rb
INFO manager: Registered plugin: atlas
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/pushes/ftp/plugin.rb
INFO manager: Registered plugin: ftp
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/pushes/heroku/plugin.rb
INFO manager: Registered plugin: heroku
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/pushes/local-exec/plugin.rb
INFO manager: Registered plugin: local-exec
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/pushes/noop/plugin.rb
INFO manager: Registered plugin: noop
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/synced_folders/nfs/plugin.rb
INFO manager: Registered plugin: NFS synced folders
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/synced_folders/rsync/plugin.rb
INFO manager: Registered plugin: RSync synced folders
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/synced_folders/smb/plugin.rb
INFO manager: Registered plugin: SMB synced folders
INFO manager: Registered plugin: VMware Fusion Provider
INFO vmware_driver: VMX path is a directory. Finding VMX file...
INFO vmware_driver: VMX file: /Users/quasiben/.vagrant/machines/dev/vmware_fusion/7890b8d8-98e2-4cd5-a989-d65c4e0279ae/trusty64.vmx
INFO vmware_driver: Looking for VMware Fusion: /Applications/VMware Fusion.app
INFO vmware_driver: VMware Fusion path: #<Pathname:/Applications/VMware Fusion.app>
DEBUG vmware_driver: Attempting to read VMware version...
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmware-vmx", "-v"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command is setuid/setgid, clearing DYLD_LIBRARY_PATH
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr:
VMware Fusion Information:
VMware Fusion 7.1.0 build-2314774 Release
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO vmware_driver: Detected VMware version: 7.1.0
DEBUG vmware_driver: service starter path: /Applications/VMware Fusion.app/Contents/Library/services/Open VMware Fusion Services
DEBUG vmware_driver: vmnet-cli path: /Applications/VMware Fusion.app/Contents/Library/vmnet-cli
INFO vmware:sudo_helper: Calling command: create-vmnet-device
INFO networking_file: Reading adapters from networking file...
DEBUG networking_file: VNET: 1. KEY: 'DHCP' = 'yes'
DEBUG networking_file: VNET: 1. KEY: 'DHCP_CFG_HASH' = 'D80210FE873BE2813B8C769A8E72B64979061717'
DEBUG networking_file: VNET: 1. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG networking_file: VNET: 1. KEY: 'HOSTONLY_SUBNET' = '192.168.27.0'
DEBUG networking_file: VNET: 1. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG networking_file: VNET: 2. KEY: 'DHCP' = 'yes'
DEBUG networking_file: VNET: 2. KEY: 'DHCP_CFG_HASH' = '87768080D35EC28F8A98E2922D0D6FE5E5C18A59'
DEBUG networking_file: VNET: 2. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG networking_file: VNET: 2. KEY: 'HOSTONLY_SUBNET' = '10.10.10.0'
DEBUG networking_file: VNET: 2. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG networking_file: VNET: 3. KEY: 'DHCP' = 'yes'
DEBUG networking_file: VNET: 3. KEY: 'DHCP_CFG_HASH' = '3EC4C96155C7AA76726042C1D3C8D9C208404144'
DEBUG networking_file: VNET: 3. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG networking_file: VNET: 3. KEY: 'HOSTONLY_SUBNET' = '192.168.18.0'
DEBUG networking_file: VNET: 3. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG networking_file: VNET: 4. KEY: 'DHCP' = 'yes'
DEBUG networking_file: VNET: 4. KEY: 'DHCP_CFG_HASH' = '6F6696B0E161F81ED0E3CE9F08794F4DD8D794EB'
DEBUG networking_file: VNET: 4. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG networking_file: VNET: 4. KEY: 'HOSTONLY_SUBNET' = '172.16.48.0'
DEBUG networking_file: VNET: 4. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG networking_file: VNET: 5. KEY: 'DHCP' = 'yes'
DEBUG networking_file: VNET: 5. KEY: 'DHCP_CFG_HASH' = '9B81D6F11FF984546E1C4E2B438F14AC3B559373'
DEBUG networking_file: VNET: 5. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG networking_file: VNET: 5. KEY: 'HOSTONLY_SUBNET' = '192.168.111.0'
DEBUG networking_file: VNET: 5. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG networking_file: VNET: 8. KEY: 'DHCP' = 'yes'
DEBUG networking_file: VNET: 8. KEY: 'DHCP_CFG_HASH' = '1BDC60FCCCD2EEB9E6AA5D403BE51F90BF3ACC00'
DEBUG networking_file: VNET: 8. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG networking_file: VNET: 8. KEY: 'HOSTONLY_SUBNET' = '192.168.186.0'
DEBUG networking_file: VNET: 8. KEY: 'NAT' = 'yes'
DEBUG networking_file: VNET: 8. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG networking_file: Pruning adapters that aren't actually active...
INFO vmware_driver: Starting services starter and waiting for them to start...
INFO vmware_driver: Killing vmnet-natd if it is alive...
INFO subprocess: Starting process: ["/usr/bin/pkill", "vmnet-natd"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--start"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Failed to start DHCP service on vmnet6
DEBUG subprocess: stderr: Failed to start some/all services
DEBUG subprocess: stdout: Enabled hostonly virtual adapter on vmnet1
Started DHCP service on vmnet1
Enabled hostonly virtual adapter on vmnet2
Started DHCP service on vmnet2
Enabled hostonly virtual adapter on vmnet3
Started DHCP service on vmnet3
Enabled hostonly virtual adapter on vmnet4
Started DHCP service on vmnet4
Enabled hostonly virtual adapter on vmnet5
Started DHCP service on vmnet5
Enabled hostonly virtual adapter on vmnet6
Started NAT service on vmnet8
Enabled hostonly virtual adapter on vmnet8
Started DHCP service on vmnet8
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Some/All of the configured services are not running
DEBUG subprocess: stdout: DHCP service on vmnet1 is running
Hostonly virtual adapter on vmnet1 is enabled
DHCP service on vmnet2 is running
Hostonly virtual adapter on vmnet2 is enabled
DHCP service on vmnet3 is running
Hostonly virtual adapter on vmnet3 is enabled
DHCP service on vmnet4 is running
Hostonly virtual adapter on vmnet4 is enabled
DHCP service on vmnet5 is running
Hostonly virtual adapter on vmnet5 is enabled
DHCP service on vmnet6 is not running
Hostonly virtual adapter on vmnet6 is enabled
DHCP service on vmnet8 is running
NAT service on vmnet8 is running
Hostonly virtual adapter on vmnet8 is enabled
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO retryable: Retryable exception raised: #<HashiCorp::VagrantVMwarefusion::Errors::VMNetDevicesWontStart: The VMware "vmnet" devices are failing to start. The most common
reason for this is collisions with existing network services. For
example, if a hostonly network space collides with another hostonly
network (such as with VirtualBox), it will fail to start. Likewise,
if forwarded ports collide with other listening ports, it will
fail to start.
Vagrant does its best to fix these issues, but in some cases it
cannot determine the root cause of these failures.
Please verify you have no other colliding network services running.
As a last resort, restarting your computer often fixes this issue.>
INFO vmware_driver: Killing vmnet-natd if it is alive...
INFO subprocess: Starting process: ["/usr/bin/pkill", "vmnet-natd"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--start"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Failed to start DHCP service on vmnet6
DEBUG subprocess: stderr: Failed to start some/all services
DEBUG subprocess: stdout: Enabled hostonly virtual adapter on vmnet1
Started DHCP service on vmnet1
Enabled hostonly virtual adapter on vmnet2
Started DHCP service on vmnet2
Enabled hostonly virtual adapter on vmnet3
Started DHCP service on vmnet3
Enabled hostonly virtual adapter on vmnet4
Started DHCP service on vmnet4
Enabled hostonly virtual adapter on vmnet5
Started DHCP service on vmnet5
Enabled hostonly virtual adapter on vmnet6
Started NAT service on vmnet8
Enabled hostonly virtual adapter on vmnet8
Started DHCP service on vmnet8
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Some/All of the configured services are not running
DEBUG subprocess: stdout: DHCP service on vmnet1 is running
Hostonly virtual adapter on vmnet1 is enabled
DHCP service on vmnet2 is running
Hostonly virtual adapter on vmnet2 is enabled
DHCP service on vmnet3 is running
Hostonly virtual adapter on vmnet3 is enabled
DHCP service on vmnet4 is running
Hostonly virtual adapter on vmnet4 is enabled
DHCP service on vmnet5 is running
Hostonly virtual adapter on vmnet5 is enabled
DHCP service on vmnet6 is not running
Hostonly virtual adapter on vmnet6 is enabled
DHCP service on vmnet8 is running
NAT service on vmnet8 is running
Hostonly virtual adapter on vmnet8 is enabled
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO retryable: Retryable exception raised: #<HashiCorp::VagrantVMwarefusion::Errors::VMNetDevicesWontStart: The VMware "vmnet" devices are failing to start. The most common
reason for this is collisions with existing network services. For
example, if a hostonly network space collides with another hostonly
network (such as with VirtualBox), it will fail to start. Likewise,
if forwarded ports collide with other listening ports, it will
fail to start.
Vagrant does its best to fix these issues, but in some cases it
cannot determine the root cause of these failures.
Please verify you have no other colliding network services running.
As a last resort, restarting your computer often fixes this issue.>
INFO vmware_driver: Killing vmnet-natd if it is alive...
INFO subprocess: Starting process: ["/usr/bin/pkill", "vmnet-natd"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--start"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Failed to start DHCP service on vmnet6
DEBUG subprocess: stderr: Failed to start some/all services
DEBUG subprocess: stdout: Enabled hostonly virtual adapter on vmnet1
Started DHCP service on vmnet1
Enabled hostonly virtual adapter on vmnet2
Started DHCP service on vmnet2
Enabled hostonly virtual adapter on vmnet3
Started DHCP service on vmnet3
Enabled hostonly virtual adapter on vmnet4
Started DHCP service on vmnet4
Enabled hostonly virtual adapter on vmnet5
Started DHCP service on vmnet5
Enabled hostonly virtual adapter on vmnet6
Started NAT service on vmnet8
Enabled hostonly virtual adapter on vmnet8
Started DHCP service on vmnet8
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 31999
DEBUG subprocess: Exit status: 1
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Some/All of the configured services are not running
DEBUG subprocess: stdout: DHCP service on vmnet1 is running
Hostonly virtual adapter on vmnet1 is enabled
DHCP service on vmnet2 is running
Hostonly virtual adapter on vmnet2 is enabled
DHCP service on vmnet3 is running
Hostonly virtual adapter on vmnet3 is enabled
DHCP service on vmnet4 is running
Hostonly virtual adapter on vmnet4 is enabled
DHCP service on vmnet5 is running
Hostonly virtual adapter on vmnet5 is enabled
DHCP service on vmnet6 is not running
Hostonly virtual adapter on vmnet6 is enabled
DHCP service on vmnet8 is running
NAT service on vmnet8 is running
Hostonly virtual adapter on vmnet8 is enabled
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO retryable: Retryable exception raised: #<HashiCorp::VagrantVMwarefusion::Errors::VMNetDevicesWontStart: The VMware "vmnet" devices are failing to start. The most common
reason for this is collisions with existing network services. For
example, if a hostonly network space collides with another hostonly
network (such as with VirtualBox), it will fail to start. Likewise,
if forwarded ports collide with other listening ports, it will
fail to start.
Vagrant does its best to fix these issues, but in some cases it
cannot determine the root cause of these failures.
Please verify you have no other colliding network services running.
As a last resort, restarting your computer often fixes this issue.>
INFO vmware_driver: Killing vmnet-natd if it is alive...
INFO subprocess: Starting process: ["/usr/bin/pkill", "vmnet-natd"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--start"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Failed to start DHCP service on vmnet6
DEBUG subprocess: stderr: Failed to start some/all services
DEBUG subprocess: stdout: Enabled hostonly virtual adapter on vmnet1
Started DHCP service on vmnet1
Enabled hostonly virtual adapter on vmnet2
Started DHCP service on vmnet2
Enabled hostonly virtual adapter on vmnet3
Started DHCP service on vmnet3
Enabled hostonly virtual adapter on vmnet4
Started DHCP service on vmnet4
Enabled hostonly virtual adapter on vmnet5
Started DHCP service on vmnet5
Enabled hostonly virtual adapter on vmnet6
Started NAT service on vmnet8
Enabled hostonly virtual adapter on vmnet8
Started DHCP service on vmnet8
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Some/All of the configured services are not running
DEBUG subprocess: stdout: DHCP service on vmnet1 is running
Hostonly virtual adapter on vmnet1 is enabled
DHCP service on vmnet2 is running
Hostonly virtual adapter on vmnet2 is enabled
DHCP service on vmnet3 is running
Hostonly virtual adapter on vmnet3 is enabled
DHCP service on vmnet4 is running
Hostonly virtual adapter on vmnet4 is enabled
DHCP service on vmnet5 is running
Hostonly virtual adapter on vmnet5 is enabled
DHCP service on vmnet6 is not running
Hostonly virtual adapter on vmnet6 is enabled
DHCP service on vmnet8 is running
NAT service on vmnet8 is running
Hostonly virtual adapter on vmnet8 is enabled
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO retryable: Retryable exception raised: #<HashiCorp::VagrantVMwarefusion::Errors::VMNetDevicesWontStart: The VMware "vmnet" devices are failing to start. The most common
reason for this is collisions with existing network services. For
example, if a hostonly network space collides with another hostonly
network (such as with VirtualBox), it will fail to start. Likewise,
if forwarded ports collide with other listening ports, it will
fail to start.
Vagrant does its best to fix these issues, but in some cases it
cannot determine the root cause of these failures.
Please verify you have no other colliding network services running.
As a last resort, restarting your computer often fixes this issue.>
INFO vmware_driver: Killing vmnet-natd if it is alive...
INFO subprocess: Starting process: ["/usr/bin/pkill", "vmnet-natd"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--start"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Failed to start DHCP service on vmnet6
DEBUG subprocess: stderr: Failed to start some/all services
DEBUG subprocess: stdout: Enabled hostonly virtual adapter on vmnet1
Started DHCP service on vmnet1
Enabled hostonly virtual adapter on vmnet2
Started DHCP service on vmnet2
Enabled hostonly virtual adapter on vmnet3
Started DHCP service on vmnet3
Enabled hostonly virtual adapter on vmnet4
Started DHCP service on vmnet4
Enabled hostonly virtual adapter on vmnet5
Started DHCP service on vmnet5
Enabled hostonly virtual adapter on vmnet6
Started NAT service on vmnet8
Enabled hostonly virtual adapter on vmnet8
Started DHCP service on vmnet8
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 31999
DEBUG subprocess: Exit status: 1
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Some/All of the configured services are not running
DEBUG subprocess: stdout: DHCP service on vmnet1 is running
Hostonly virtual adapter on vmnet1 is enabled
DHCP service on vmnet2 is running
Hostonly virtual adapter on vmnet2 is enabled
DHCP service on vmnet3 is running
Hostonly virtual adapter on vmnet3 is enabled
DHCP service on vmnet4 is running
Hostonly virtual adapter on vmnet4 is enabled
DHCP service on vmnet5 is running
Hostonly virtual adapter on vmnet5 is enabled
DHCP service on vmnet6 is not running
Hostonly virtual adapter on vmnet6 is enabled
DHCP service on vmnet8 is running
NAT service on vmnet8 is running
Hostonly virtual adapter on vmnet8 is enabled
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO vmware_driver: Stopping services starter...
The VMware "vmnet" devices are failing to start. The most common
reason for this is collisions with existing network services. For
example, if a hostonly network space collides with another hostonly
network (such as with VirtualBox), it will fail to start. Likewise,
if forwarded ports collide with other listening ports, it will
fail to start.
Vagrant does its best to fix these issues, but in some cases it
cannot determine the root cause of these failures.
Please verify you have no other colliding network services running.
As a last resort, restarting your computer often fixes this issue.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
ERROR warden: Error occurred: INFO global: Vagrant version: 1.7.4
INFO global: Ruby version: 2.0.0
INFO global: RubyGems version: 2.0.14
INFO global: VAGRANT_LOG="debug"
INFO global: VAGRANT_OLD_ENV_SPARK_HOME="/Users/quasiben/Research/GitClones/spark"
INFO global: VAGRANT_OLD_ENV_HOME="/Users/quasiben"
INFO global: VAGRANT_OLD_ENV__="/usr/local/bin/vagrant"
INFO global: VAGRANT_OLD_ENV_XPC_FLAGS="0x0"
INFO global: VAGRANT_INSTALLER_VERSION="2"
INFO global: VAGRANT_OLD_ENV_VAGRANT_LOG="debug"
INFO global: VAGRANT_OLD_ENV_TMPDIR="/var/folders/1t/t94brwgx7sjcn8jgz4gr3_c00000gq/T/"
INFO global: VAGRANT_OLD_ENV_Apple_PubSub_Socket_Render="/private/tmp/com.apple.launchd.KW13obTzd8/Render"
INFO global: VAGRANT_OLD_ENV_JAVA_HOME="/Library/Java/JavaVirtualMachines/jdk1.7.0_45.jdk/Contents/Home"
INFO global: VAGRANT_OLD_ENV_ACHE_HOME="/Users/quasiben/anaconda/envs/memex-explorer/lib/python2.7/site-packages/ache/"
INFO global: VAGRANT_OLD_ENV_CONDA_ENV_PATH="/Users/quasiben/anaconda/envs/clusto"
INFO global: VAGRANT_OLD_ENV_PYTHONPATH="/Users/quasiben/Research/ContinuumDev/GitRepo/conda-cluster/::/Users/quasiben/Research/GitClones/spark/python"
INFO global: VAGRANT_OLD_ENV_PATH="/Users/quasiben/anaconda/envs/clusto/bin:/usr/local/bin:/usr/local/heroku/bin:/Users/quasiben/google-cloud-sdk/bin:/usr/local/sbin:/Users/quasiben/.cabal/bin/:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/texbin:/Users/quasiben/Research/ContinuumDev/GitRepo/libdynd/build"
INFO global: VAGRANT_OLD_ENV_PWD="/Users/quasiben"
INFO global: VAGRANT_OLD_ENV_ITERM_PROFILE="Default"
INFO global: VAGRANT_OLD_ENV_JDK_HOME="/Library/Java/JavaVirtualMachines/jdk1.7.0_45.jdk/Contents/Home/"
INFO global: VAGRANT_OLD_ENV_COLORFGBG="7;0"
INFO global: VAGRANT_OLD_ENV_CONDA_DEFAULT_ENV="clusto"
INFO global: VAGRANT_INSTALLER_ENV="1"
INFO global: VAGRANT_EXECUTABLE="/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/bin/vagrant"
INFO global: VAGRANT_INSTALLER_EMBEDDED_DIR="/opt/vagrant/embedded"
INFO global: VAGRANT_OLD_ENV_COMMAND_MODE="unix2003"
INFO global: VAGRANT_OLD_ENV_SSH_AUTH_SOCK="/private/tmp/com.apple.launchd.CSjdOMPkpG/Listeners"
INFO global: VAGRANT_OLD_ENV_LANG="en_US.UTF-8"
INFO global: VAGRANT_OLD_ENV_TERM_PROGRAM="iTerm.app"
INFO global: VAGRANT_OLD_ENV_XPC_SERVICE_NAME="0"
INFO global: VAGRANT_OLD_ENV_SHLVL="1"
INFO global: VAGRANT_OLD_ENV_SECURITYSESSIONID="186a5"
INFO global: VAGRANT_OLD_ENV_TERM="xterm-color"
INFO global: VAGRANT_OLD_ENV_USER="quasiben"
INFO global: VAGRANT_OLD_ENV___CF_USER_TEXT_ENCODING="0x1F7:0x0:0x0"
INFO global: VAGRANT_OLD_ENV_ITERM_SESSION_ID="w0t1p0"
INFO global: VAGRANT_OLD_ENV_SHELL="/bin/bash"
INFO global: VAGRANT_OLD_ENV_PS1="(clusto)\\[\\033[01;32m\\]\\u@\\h\\[\\033[00m\\]:\\[\\033[01;36m\\]\\w\\[\\033[00m\\]\\$ "
INFO global: VAGRANT_OLD_ENV_OLDPWD="/Users/quasiben/Research/ContinuumDev/AC_AS_Vagrant/Head+Compute/test"
INFO global: VAGRANT_OLD_ENV_JRE_HOME="/Library/Java/JavaVirtualMachines/jdk1.7.0_45.jdk/Contents/Home/jre/"
INFO global: VAGRANT_OLD_ENV_LOGNAME="quasiben"
INFO global: VAGRANT_INTERNAL_BUNDLERIZED="1"
INFO global: Plugins:
INFO global: - bundler = 1.10.5
INFO global: - mime-types = 1.25.1
INFO global: - rest-client = 1.6.9
INFO global: - vagrant-share = 1.1.4
INFO global: - vagrant-vmware-fusion = 4.0.2
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/box/plugin.rb
INFO manager: Registered plugin: box command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/destroy/plugin.rb
INFO manager: Registered plugin: destroy command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/global-status/plugin.rb
INFO manager: Registered plugin: global-status command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/halt/plugin.rb
INFO manager: Registered plugin: halt command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/help/plugin.rb
INFO manager: Registered plugin: help command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/init/plugin.rb
INFO manager: Registered plugin: init command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/list-commands/plugin.rb
INFO manager: Registered plugin: list-commands command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/login/plugin.rb
INFO manager: Registered plugin: vagrant-login
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/package/plugin.rb
INFO manager: Registered plugin: package command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/plugin/plugin.rb
INFO manager: Registered plugin: plugin command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/provision/plugin.rb
INFO manager: Registered plugin: provision command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/push/plugin.rb
INFO manager: Registered plugin: push command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/rdp/plugin.rb
INFO manager: Registered plugin: rdp command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/reload/plugin.rb
INFO manager: Registered plugin: reload command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/resume/plugin.rb
INFO manager: Registered plugin: resume command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/ssh/plugin.rb
INFO manager: Registered plugin: ssh command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/ssh_config/plugin.rb
INFO manager: Registered plugin: ssh-config command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/status/plugin.rb
INFO manager: Registered plugin: status command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/suspend/plugin.rb
INFO manager: Registered plugin: suspend command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/up/plugin.rb
INFO manager: Registered plugin: up command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/version/plugin.rb
INFO manager: Registered plugin: version command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/communicators/ssh/plugin.rb
INFO manager: Registered plugin: ssh communicator
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/communicators/winrm/plugin.rb
INFO manager: Registered plugin: winrm communicator
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/arch/plugin.rb
INFO manager: Registered plugin: Arch guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/atomic/plugin.rb
INFO manager: Registered plugin: Atomic Host guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/coreos/plugin.rb
INFO manager: Registered plugin: CoreOS guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/darwin/plugin.rb
INFO manager: Registered plugin: Darwin guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/debian/plugin.rb
INFO manager: Registered plugin: Debian guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/debian8/plugin.rb
INFO manager: Registered plugin: Debian Jessie guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/esxi/plugin.rb
INFO manager: Registered plugin: ESXi guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/fedora/plugin.rb
INFO manager: Registered plugin: Fedora guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/freebsd/plugin.rb
INFO manager: Registered plugin: FreeBSD guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/funtoo/plugin.rb
INFO manager: Registered plugin: Funtoo guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/gentoo/plugin.rb
INFO manager: Registered plugin: Gentoo guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/linux/plugin.rb
INFO manager: Registered plugin: Linux guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/mint/plugin.rb
INFO manager: Registered plugin: Mint guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/netbsd/plugin.rb
INFO manager: Registered plugin: NetBSD guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/nixos/plugin.rb
INFO manager: Registered plugin: NixOS guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/omnios/plugin.rb
INFO manager: Registered plugin: OmniOS guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/openbsd/plugin.rb
INFO manager: Registered plugin: OpenBSD guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/photon/plugin.rb
INFO manager: Registered plugin: VMware Photon guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/pld/plugin.rb
INFO manager: Registered plugin: PLD Linux guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/redhat/plugin.rb
INFO manager: Registered plugin: Red Hat Enterprise Linux guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/smartos/plugin.rb
INFO manager: Registered plugin: SmartOS guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/solaris/plugin.rb
INFO manager: Registered plugin: Solaris guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/solaris11/plugin.rb
INFO manager: Registered plugin: Solaris 11 guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/suse/plugin.rb
INFO manager: Registered plugin: SUSE guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/tinycore/plugin.rb
INFO manager: Registered plugin: TinyCore Linux guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/ubuntu/plugin.rb
INFO manager: Registered plugin: Ubuntu guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/windows/plugin.rb
INFO manager: Registered plugin: Windows guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/arch/plugin.rb
INFO manager: Registered plugin: Arch host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/bsd/plugin.rb
INFO manager: Registered plugin: BSD host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/darwin/plugin.rb
INFO manager: Registered plugin: Mac OS X host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/freebsd/plugin.rb
INFO manager: Registered plugin: FreeBSD host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/gentoo/plugin.rb
INFO manager: Registered plugin: Gentoo host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/linux/plugin.rb
INFO manager: Registered plugin: Linux host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/null/plugin.rb
INFO manager: Registered plugin: null host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/redhat/plugin.rb
INFO manager: Registered plugin: Red Hat Enterprise Linux host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/slackware/plugin.rb
INFO manager: Registered plugin: Slackware host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/suse/plugin.rb
INFO manager: Registered plugin: SUSE host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/windows/plugin.rb
INFO manager: Registered plugin: Windows host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/kernel_v1/plugin.rb
INFO manager: Registered plugin: kernel
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/kernel_v2/plugin.rb
INFO manager: Registered plugin: kernel
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/providers/docker/plugin.rb
INFO manager: Registered plugin: docker-provider
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/providers/hyperv/plugin.rb
INFO manager: Registered plugin: Hyper-V provider
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/providers/virtualbox/plugin.rb
INFO manager: Registered plugin: VirtualBox provider
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/ansible/plugin.rb
INFO manager: Registered plugin: ansible
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/cfengine/plugin.rb
INFO manager: Registered plugin: CFEngine Provisioner
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/chef/plugin.rb
INFO manager: Registered plugin: chef
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/docker/plugin.rb
INFO manager: Registered plugin: docker
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/file/plugin.rb
INFO manager: Registered plugin: file
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/puppet/plugin.rb
INFO manager: Registered plugin: puppet
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/salt/plugin.rb
INFO manager: Registered plugin: salt
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/shell/plugin.rb
INFO manager: Registered plugin: shell
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/pushes/atlas/plugin.rb
INFO manager: Registered plugin: atlas
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/pushes/ftp/plugin.rb
INFO manager: Registered plugin: ftp
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/pushes/heroku/plugin.rb
INFO manager: Registered plugin: heroku
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/pushes/local-exec/plugin.rb
INFO manager: Registered plugin: local-exec
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/pushes/noop/plugin.rb
INFO manager: Registered plugin: noop
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/synced_folders/nfs/plugin.rb
INFO manager: Registered plugin: NFS synced folders
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/synced_folders/rsync/plugin.rb
INFO manager: Registered plugin: RSync synced folders
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/synced_folders/smb/plugin.rb
INFO manager: Registered plugin: SMB synced folders
INFO manager: Registered plugin: VMware Fusion Provider
INFO vmware_driver: VMX path is a directory. Finding VMX file...
INFO vmware_driver: VMX file: /Users/quasiben/.vagrant/machines/dev/vmware_fusion/7890b8d8-98e2-4cd5-a989-d65c4e0279ae/trusty64.vmx
INFO vmware_driver: Looking for VMware Fusion: /Applications/VMware Fusion.app
INFO vmware_driver: VMware Fusion path: #<Pathname:/Applications/VMware Fusion.app>
DEBUG vmware_driver: Attempting to read VMware version...
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmware-vmx", "-v"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command is setuid/setgid, clearing DYLD_LIBRARY_PATH
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr:
VMware Fusion Information:
VMware Fusion 7.1.0 build-2314774 Release
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO vmware_driver: Detected VMware version: 7.1.0
DEBUG vmware_driver: service starter path: /Applications/VMware Fusion.app/Contents/Library/services/Open VMware Fusion Services
DEBUG vmware_driver: vmnet-cli path: /Applications/VMware Fusion.app/Contents/Library/vmnet-cli
INFO vmware:sudo_helper: Calling command: create-vmnet-device
INFO networking_file: Reading adapters from networking file...
DEBUG networking_file: VNET: 1. KEY: 'DHCP' = 'yes'
DEBUG networking_file: VNET: 1. KEY: 'DHCP_CFG_HASH' = 'D80210FE873BE2813B8C769A8E72B64979061717'
DEBUG networking_file: VNET: 1. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG networking_file: VNET: 1. KEY: 'HOSTONLY_SUBNET' = '192.168.27.0'
DEBUG networking_file: VNET: 1. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG networking_file: VNET: 2. KEY: 'DHCP' = 'yes'
DEBUG networking_file: VNET: 2. KEY: 'DHCP_CFG_HASH' = '87768080D35EC28F8A98E2922D0D6FE5E5C18A59'
DEBUG networking_file: VNET: 2. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG networking_file: VNET: 2. KEY: 'HOSTONLY_SUBNET' = '10.10.10.0'
DEBUG networking_file: VNET: 2. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG networking_file: VNET: 3. KEY: 'DHCP' = 'yes'
DEBUG networking_file: VNET: 3. KEY: 'DHCP_CFG_HASH' = '3EC4C96155C7AA76726042C1D3C8D9C208404144'
DEBUG networking_file: VNET: 3. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG networking_file: VNET: 3. KEY: 'HOSTONLY_SUBNET' = '192.168.18.0'
DEBUG networking_file: VNET: 3. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG networking_file: VNET: 4. KEY: 'DHCP' = 'yes'
DEBUG networking_file: VNET: 4. KEY: 'DHCP_CFG_HASH' = '6F6696B0E161F81ED0E3CE9F08794F4DD8D794EB'
DEBUG networking_file: VNET: 4. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG networking_file: VNET: 4. KEY: 'HOSTONLY_SUBNET' = '172.16.48.0'
DEBUG networking_file: VNET: 4. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG networking_file: VNET: 5. KEY: 'DHCP' = 'yes'
DEBUG networking_file: VNET: 5. KEY: 'DHCP_CFG_HASH' = '9B81D6F11FF984546E1C4E2B438F14AC3B559373'
DEBUG networking_file: VNET: 5. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG networking_file: VNET: 5. KEY: 'HOSTONLY_SUBNET' = '192.168.111.0'
DEBUG networking_file: VNET: 5. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG networking_file: VNET: 8. KEY: 'DHCP' = 'yes'
DEBUG networking_file: VNET: 8. KEY: 'DHCP_CFG_HASH' = '1BDC60FCCCD2EEB9E6AA5D403BE51F90BF3ACC00'
DEBUG networking_file: VNET: 8. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG networking_file: VNET: 8. KEY: 'HOSTONLY_SUBNET' = '192.168.186.0'
DEBUG networking_file: VNET: 8. KEY: 'NAT' = 'yes'
DEBUG networking_file: VNET: 8. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG networking_file: Pruning adapters that aren't actually active...
INFO vmware_driver: Starting services starter and waiting for them to start...
INFO vmware_driver: Killing vmnet-natd if it is alive...
INFO subprocess: Starting process: ["/usr/bin/pkill", "vmnet-natd"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--start"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Failed to start DHCP service on vmnet6
DEBUG subprocess: stderr: Failed to start some/all services
DEBUG subprocess: stdout: Enabled hostonly virtual adapter on vmnet1
Started DHCP service on vmnet1
Enabled hostonly virtual adapter on vmnet2
Started DHCP service on vmnet2
Enabled hostonly virtual adapter on vmnet3
Started DHCP service on vmnet3
Enabled hostonly virtual adapter on vmnet4
Started DHCP service on vmnet4
Enabled hostonly virtual adapter on vmnet5
Started DHCP service on vmnet5
Enabled hostonly virtual adapter on vmnet6
Started NAT service on vmnet8
Enabled hostonly virtual adapter on vmnet8
Started DHCP service on vmnet8
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Some/All of the configured services are not running
DEBUG subprocess: stdout: DHCP service on vmnet1 is running
Hostonly virtual adapter on vmnet1 is enabled
DHCP service on vmnet2 is running
Hostonly virtual adapter on vmnet2 is enabled
DHCP service on vmnet3 is running
Hostonly virtual adapter on vmnet3 is enabled
DHCP service on vmnet4 is running
Hostonly virtual adapter on vmnet4 is enabled
DHCP service on vmnet5 is running
Hostonly virtual adapter on vmnet5 is enabled
DHCP service on vmnet6 is not running
Hostonly virtual adapter on vmnet6 is enabled
DHCP service on vmnet8 is running
NAT service on vmnet8 is running
Hostonly virtual adapter on vmnet8 is enabled
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO retryable: Retryable exception raised: #<HashiCorp::VagrantVMwarefusion::Errors::VMNetDevicesWontStart: The VMware "vmnet" devices are failing to start. The most common
reason for this is collisions with existing network services. For
example, if a hostonly network space collides with another hostonly
network (such as with VirtualBox), it will fail to start. Likewise,
if forwarded ports collide with other listening ports, it will
fail to start.
Vagrant does its best to fix these issues, but in some cases it
cannot determine the root cause of these failures.
Please verify you have no other colliding network services running.
As a last resort, restarting your computer often fixes this issue.>
INFO vmware_driver: Killing vmnet-natd if it is alive...
INFO subprocess: Starting process: ["/usr/bin/pkill", "vmnet-natd"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--start"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Failed to start DHCP service on vmnet6
DEBUG subprocess: stderr: Failed to start some/all services
DEBUG subprocess: stdout: Enabled hostonly virtual adapter on vmnet1
Started DHCP service on vmnet1
Enabled hostonly virtual adapter on vmnet2
Started DHCP service on vmnet2
Enabled hostonly virtual adapter on vmnet3
Started DHCP service on vmnet3
Enabled hostonly virtual adapter on vmnet4
Started DHCP service on vmnet4
Enabled hostonly virtual adapter on vmnet5
Started DHCP service on vmnet5
Enabled hostonly virtual adapter on vmnet6
Started NAT service on vmnet8
Enabled hostonly virtual adapter on vmnet8
Started DHCP service on vmnet8
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Some/All of the configured services are not running
DEBUG subprocess: stdout: DHCP service on vmnet1 is running
Hostonly virtual adapter on vmnet1 is enabled
DHCP service on vmnet2 is running
Hostonly virtual adapter on vmnet2 is enabled
DHCP service on vmnet3 is running
Hostonly virtual adapter on vmnet3 is enabled
DHCP service on vmnet4 is running
Hostonly virtual adapter on vmnet4 is enabled
DHCP service on vmnet5 is running
Hostonly virtual adapter on vmnet5 is enabled
DHCP service on vmnet6 is not running
Hostonly virtual adapter on vmnet6 is enabled
DHCP service on vmnet8 is running
NAT service on vmnet8 is running
Hostonly virtual adapter on vmnet8 is enabled
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO retryable: Retryable exception raised: #<HashiCorp::VagrantVMwarefusion::Errors::VMNetDevicesWontStart: The VMware "vmnet" devices are failing to start. The most common
reason for this is collisions with existing network services. For
example, if a hostonly network space collides with another hostonly
network (such as with VirtualBox), it will fail to start. Likewise,
if forwarded ports collide with other listening ports, it will
fail to start.
Vagrant does its best to fix these issues, but in some cases it
cannot determine the root cause of these failures.
Please verify you have no other colliding network services running.
As a last resort, restarting your computer often fixes this issue.>
INFO vmware_driver: Killing vmnet-natd if it is alive...
INFO subprocess: Starting process: ["/usr/bin/pkill", "vmnet-natd"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--start"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Failed to start DHCP service on vmnet6
DEBUG subprocess: stderr: Failed to start some/all services
DEBUG subprocess: stdout: Enabled hostonly virtual adapter on vmnet1
Started DHCP service on vmnet1
Enabled hostonly virtual adapter on vmnet2
Started DHCP service on vmnet2
Enabled hostonly virtual adapter on vmnet3
Started DHCP service on vmnet3
Enabled hostonly virtual adapter on vmnet4
Started DHCP service on vmnet4
Enabled hostonly virtual adapter on vmnet5
Started DHCP service on vmnet5
Enabled hostonly virtual adapter on vmnet6
Started NAT service on vmnet8
Enabled hostonly virtual adapter on vmnet8
Started DHCP service on vmnet8
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 31999
DEBUG subprocess: Exit status: 1
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Some/All of the configured services are not running
DEBUG subprocess: stdout: DHCP service on vmnet1 is running
Hostonly virtual adapter on vmnet1 is enabled
DHCP service on vmnet2 is running
Hostonly virtual adapter on vmnet2 is enabled
DHCP service on vmnet3 is running
Hostonly virtual adapter on vmnet3 is enabled
DHCP service on vmnet4 is running
Hostonly virtual adapter on vmnet4 is enabled
DHCP service on vmnet5 is running
Hostonly virtual adapter on vmnet5 is enabled
DHCP service on vmnet6 is not running
Hostonly virtual adapter on vmnet6 is enabled
DHCP service on vmnet8 is running
NAT service on vmnet8 is running
Hostonly virtual adapter on vmnet8 is enabled
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO retryable: Retryable exception raised: #<HashiCorp::VagrantVMwarefusion::Errors::VMNetDevicesWontStart: The VMware "vmnet" devices are failing to start. The most common
reason for this is collisions with existing network services. For
example, if a hostonly network space collides with another hostonly
network (such as with VirtualBox), it will fail to start. Likewise,
if forwarded ports collide with other listening ports, it will
fail to start.
Vagrant does its best to fix these issues, but in some cases it
cannot determine the root cause of these failures.
Please verify you have no other colliding network services running.
As a last resort, restarting your computer often fixes this issue.>
INFO vmware_driver: Killing vmnet-natd if it is alive...
INFO subprocess: Starting process: ["/usr/bin/pkill", "vmnet-natd"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--start"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Failed to start DHCP service on vmnet6
DEBUG subprocess: stderr: Failed to start some/all services
DEBUG subprocess: stdout: Enabled hostonly virtual adapter on vmnet1
Started DHCP service on vmnet1
Enabled hostonly virtual adapter on vmnet2
Started DHCP service on vmnet2
Enabled hostonly virtual adapter on vmnet3
Started DHCP service on vmnet3
Enabled hostonly virtual adapter on vmnet4
Started DHCP service on vmnet4
Enabled hostonly virtual adapter on vmnet5
Started DHCP service on vmnet5
Enabled hostonly virtual adapter on vmnet6
Started NAT service on vmnet8
Enabled hostonly virtual adapter on vmnet8
Started DHCP service on vmnet8
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Some/All of the configured services are not running
DEBUG subprocess: stdout: DHCP service on vmnet1 is running
Hostonly virtual adapter on vmnet1 is enabled
DHCP service on vmnet2 is running
Hostonly virtual adapter on vmnet2 is enabled
DHCP service on vmnet3 is running
Hostonly virtual adapter on vmnet3 is enabled
DHCP service on vmnet4 is running
Hostonly virtual adapter on vmnet4 is enabled
DHCP service on vmnet5 is running
Hostonly virtual adapter on vmnet5 is enabled
DHCP service on vmnet6 is not running
Hostonly virtual adapter on vmnet6 is enabled
DHCP service on vmnet8 is running
NAT service on vmnet8 is running
Hostonly virtual adapter on vmnet8 is enabled
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO retryable: Retryable exception raised: #<HashiCorp::VagrantVMwarefusion::Errors::VMNetDevicesWontStart: The VMware "vmnet" devices are failing to start. The most common
reason for this is collisions with existing network services. For
example, if a hostonly network space collides with another hostonly
network (such as with VirtualBox), it will fail to start. Likewise,
if forwarded ports collide with other listening ports, it will
fail to start.
Vagrant does its best to fix these issues, but in some cases it
cannot determine the root cause of these failures.
Please verify you have no other colliding network services running.
As a last resort, restarting your computer often fixes this issue.>
INFO vmware_driver: Killing vmnet-natd if it is alive...
INFO subprocess: Starting process: ["/usr/bin/pkill", "vmnet-natd"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--start"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Failed to start DHCP service on vmnet6
DEBUG subprocess: stderr: Failed to start some/all services
DEBUG subprocess: stdout: Enabled hostonly virtual adapter on vmnet1
Started DHCP service on vmnet1
Enabled hostonly virtual adapter on vmnet2
Started DHCP service on vmnet2
Enabled hostonly virtual adapter on vmnet3
Started DHCP service on vmnet3
Enabled hostonly virtual adapter on vmnet4
Started DHCP service on vmnet4
Enabled hostonly virtual adapter on vmnet5
Started DHCP service on vmnet5
Enabled hostonly virtual adapter on vmnet6
Started NAT service on vmnet8
Enabled hostonly virtual adapter on vmnet8
Started DHCP service on vmnet8
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 31999
DEBUG subprocess: Exit status: 1
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Some/All of the configured services are not running
DEBUG subprocess: stdout: DHCP service on vmnet1 is running
Hostonly virtual adapter on vmnet1 is enabled
DHCP service on vmnet2 is running
Hostonly virtual adapter on vmnet2 is enabled
DHCP service on vmnet3 is running
Hostonly virtual adapter on vmnet3 is enabled
DHCP service on vmnet4 is running
Hostonly virtual adapter on vmnet4 is enabled
DHCP service on vmnet5 is running
Hostonly virtual adapter on vmnet5 is enabled
DHCP service on vmnet6 is not running
Hostonly virtual adapter on vmnet6 is enabled
DHCP service on vmnet8 is running
NAT service on vmnet8 is running
Hostonly virtual adapter on vmnet8 is enabled
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO vmware_driver: Stopping services starter...
The VMware "vmnet" devices are failing to start. The most common
reason for this is collisions with existing network services. For
example, if a hostonly network space collides with another hostonly
network (such as with VirtualBox), it will fail to start. Likewise,
if forwarded ports collide with other listening ports, it will
fail to start.
Vagrant does its best to fix these issues, but in some cases it
cannot determine the root cause of these failures.
Please verify you have no other colliding network services running.
As a last resort, restarting your computer often fixes this issue.
INFO warden: Beginning recovery process...
INFO warden: Calling recover: #<Vagrant::Action::Builtin::Call:0x000001029aaee0>
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Calling recover: VMware Middleware: Import
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmrun", "list"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stdout: Total running VMs: 0
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
DEBUG vmware: VM state requested. Current state: not_running
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
ERROR warden: Error occurred: INFO global: Vagrant version: 1.7.4
INFO global: Ruby version: 2.0.0
INFO global: RubyGems version: 2.0.14
INFO global: VAGRANT_LOG="debug"
INFO global: VAGRANT_OLD_ENV_SPARK_HOME="/Users/quasiben/Research/GitClones/spark"
INFO global: VAGRANT_OLD_ENV_HOME="/Users/quasiben"
INFO global: VAGRANT_OLD_ENV__="/usr/local/bin/vagrant"
INFO global: VAGRANT_OLD_ENV_XPC_FLAGS="0x0"
INFO global: VAGRANT_INSTALLER_VERSION="2"
INFO global: VAGRANT_OLD_ENV_VAGRANT_LOG="debug"
INFO global: VAGRANT_OLD_ENV_TMPDIR="/var/folders/1t/t94brwgx7sjcn8jgz4gr3_c00000gq/T/"
INFO global: VAGRANT_OLD_ENV_Apple_PubSub_Socket_Render="/private/tmp/com.apple.launchd.KW13obTzd8/Render"
INFO global: VAGRANT_OLD_ENV_JAVA_HOME="/Library/Java/JavaVirtualMachines/jdk1.7.0_45.jdk/Contents/Home"
INFO global: VAGRANT_OLD_ENV_ACHE_HOME="/Users/quasiben/anaconda/envs/memex-explorer/lib/python2.7/site-packages/ache/"
INFO global: VAGRANT_OLD_ENV_CONDA_ENV_PATH="/Users/quasiben/anaconda/envs/clusto"
INFO global: VAGRANT_OLD_ENV_PYTHONPATH="/Users/quasiben/Research/ContinuumDev/GitRepo/conda-cluster/::/Users/quasiben/Research/GitClones/spark/python"
INFO global: VAGRANT_OLD_ENV_PATH="/Users/quasiben/anaconda/envs/clusto/bin:/usr/local/bin:/usr/local/heroku/bin:/Users/quasiben/google-cloud-sdk/bin:/usr/local/sbin:/Users/quasiben/.cabal/bin/:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/texbin:/Users/quasiben/Research/ContinuumDev/GitRepo/libdynd/build"
INFO global: VAGRANT_OLD_ENV_PWD="/Users/quasiben"
INFO global: VAGRANT_OLD_ENV_ITERM_PROFILE="Default"
INFO global: VAGRANT_OLD_ENV_JDK_HOME="/Library/Java/JavaVirtualMachines/jdk1.7.0_45.jdk/Contents/Home/"
INFO global: VAGRANT_OLD_ENV_COLORFGBG="7;0"
INFO global: VAGRANT_OLD_ENV_CONDA_DEFAULT_ENV="clusto"
INFO global: VAGRANT_INSTALLER_ENV="1"
INFO global: VAGRANT_EXECUTABLE="/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/bin/vagrant"
INFO global: VAGRANT_INSTALLER_EMBEDDED_DIR="/opt/vagrant/embedded"
INFO global: VAGRANT_OLD_ENV_COMMAND_MODE="unix2003"
INFO global: VAGRANT_OLD_ENV_SSH_AUTH_SOCK="/private/tmp/com.apple.launchd.CSjdOMPkpG/Listeners"
INFO global: VAGRANT_OLD_ENV_LANG="en_US.UTF-8"
INFO global: VAGRANT_OLD_ENV_TERM_PROGRAM="iTerm.app"
INFO global: VAGRANT_OLD_ENV_XPC_SERVICE_NAME="0"
INFO global: VAGRANT_OLD_ENV_SHLVL="1"
INFO global: VAGRANT_OLD_ENV_SECURITYSESSIONID="186a5"
INFO global: VAGRANT_OLD_ENV_TERM="xterm-color"
INFO global: VAGRANT_OLD_ENV_USER="quasiben"
INFO global: VAGRANT_OLD_ENV___CF_USER_TEXT_ENCODING="0x1F7:0x0:0x0"
INFO global: VAGRANT_OLD_ENV_ITERM_SESSION_ID="w0t1p0"
INFO global: VAGRANT_OLD_ENV_SHELL="/bin/bash"
INFO global: VAGRANT_OLD_ENV_PS1="(clusto)\\[\\033[01;32m\\]\\u@\\h\\[\\033[00m\\]:\\[\\033[01;36m\\]\\w\\[\\033[00m\\]\\$ "
INFO global: VAGRANT_OLD_ENV_OLDPWD="/Users/quasiben/Research/ContinuumDev/AC_AS_Vagrant/Head+Compute/test"
INFO global: VAGRANT_OLD_ENV_JRE_HOME="/Library/Java/JavaVirtualMachines/jdk1.7.0_45.jdk/Contents/Home/jre/"
INFO global: VAGRANT_OLD_ENV_LOGNAME="quasiben"
INFO global: VAGRANT_INTERNAL_BUNDLERIZED="1"
INFO global: Plugins:
INFO global: - bundler = 1.10.5
INFO global: - mime-types = 1.25.1
INFO global: - rest-client = 1.6.9
INFO global: - vagrant-share = 1.1.4
INFO global: - vagrant-vmware-fusion = 4.0.2
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/box/plugin.rb
INFO manager: Registered plugin: box command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/destroy/plugin.rb
INFO manager: Registered plugin: destroy command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/global-status/plugin.rb
INFO manager: Registered plugin: global-status command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/halt/plugin.rb
INFO manager: Registered plugin: halt command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/help/plugin.rb
INFO manager: Registered plugin: help command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/init/plugin.rb
INFO manager: Registered plugin: init command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/list-commands/plugin.rb
INFO manager: Registered plugin: list-commands command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/login/plugin.rb
INFO manager: Registered plugin: vagrant-login
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/package/plugin.rb
INFO manager: Registered plugin: package command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/plugin/plugin.rb
INFO manager: Registered plugin: plugin command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/provision/plugin.rb
INFO manager: Registered plugin: provision command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/push/plugin.rb
INFO manager: Registered plugin: push command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/rdp/plugin.rb
INFO manager: Registered plugin: rdp command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/reload/plugin.rb
INFO manager: Registered plugin: reload command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/resume/plugin.rb
INFO manager: Registered plugin: resume command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/ssh/plugin.rb
INFO manager: Registered plugin: ssh command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/ssh_config/plugin.rb
INFO manager: Registered plugin: ssh-config command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/status/plugin.rb
INFO manager: Registered plugin: status command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/suspend/plugin.rb
INFO manager: Registered plugin: suspend command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/up/plugin.rb
INFO manager: Registered plugin: up command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/version/plugin.rb
INFO manager: Registered plugin: version command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/communicators/ssh/plugin.rb
INFO manager: Registered plugin: ssh communicator
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/communicators/winrm/plugin.rb
INFO manager: Registered plugin: winrm communicator
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/arch/plugin.rb
INFO manager: Registered plugin: Arch guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/atomic/plugin.rb
INFO manager: Registered plugin: Atomic Host guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/coreos/plugin.rb
INFO manager: Registered plugin: CoreOS guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/darwin/plugin.rb
INFO manager: Registered plugin: Darwin guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/debian/plugin.rb
INFO manager: Registered plugin: Debian guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/debian8/plugin.rb
INFO manager: Registered plugin: Debian Jessie guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/esxi/plugin.rb
INFO manager: Registered plugin: ESXi guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/fedora/plugin.rb
INFO manager: Registered plugin: Fedora guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/freebsd/plugin.rb
INFO manager: Registered plugin: FreeBSD guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/funtoo/plugin.rb
INFO manager: Registered plugin: Funtoo guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/gentoo/plugin.rb
INFO manager: Registered plugin: Gentoo guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/linux/plugin.rb
INFO manager: Registered plugin: Linux guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/mint/plugin.rb
INFO manager: Registered plugin: Mint guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/netbsd/plugin.rb
INFO manager: Registered plugin: NetBSD guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/nixos/plugin.rb
INFO manager: Registered plugin: NixOS guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/omnios/plugin.rb
INFO manager: Registered plugin: OmniOS guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/openbsd/plugin.rb
INFO manager: Registered plugin: OpenBSD guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/photon/plugin.rb
INFO manager: Registered plugin: VMware Photon guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/pld/plugin.rb
INFO manager: Registered plugin: PLD Linux guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/redhat/plugin.rb
INFO manager: Registered plugin: Red Hat Enterprise Linux guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/smartos/plugin.rb
INFO manager: Registered plugin: SmartOS guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/solaris/plugin.rb
INFO manager: Registered plugin: Solaris guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/solaris11/plugin.rb
INFO manager: Registered plugin: Solaris 11 guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/suse/plugin.rb
INFO manager: Registered plugin: SUSE guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/tinycore/plugin.rb
INFO manager: Registered plugin: TinyCore Linux guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/ubuntu/plugin.rb
INFO manager: Registered plugin: Ubuntu guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/windows/plugin.rb
INFO manager: Registered plugin: Windows guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/arch/plugin.rb
INFO manager: Registered plugin: Arch host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/bsd/plugin.rb
INFO manager: Registered plugin: BSD host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/darwin/plugin.rb
INFO manager: Registered plugin: Mac OS X host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/freebsd/plugin.rb
INFO manager: Registered plugin: FreeBSD host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/gentoo/plugin.rb
INFO manager: Registered plugin: Gentoo host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/linux/plugin.rb
INFO manager: Registered plugin: Linux host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/null/plugin.rb
INFO manager: Registered plugin: null host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/redhat/plugin.rb
INFO manager: Registered plugin: Red Hat Enterprise Linux host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/slackware/plugin.rb
INFO manager: Registered plugin: Slackware host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/suse/plugin.rb
INFO manager: Registered plugin: SUSE host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/windows/plugin.rb
INFO manager: Registered plugin: Windows host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/kernel_v1/plugin.rb
INFO manager: Registered plugin: kernel
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/kernel_v2/plugin.rb
INFO manager: Registered plugin: kernel
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/providers/docker/plugin.rb
INFO manager: Registered plugin: docker-provider
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/providers/hyperv/plugin.rb
INFO manager: Registered plugin: Hyper-V provider
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/providers/virtualbox/plugin.rb
INFO manager: Registered plugin: VirtualBox provider
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/ansible/plugin.rb
INFO manager: Registered plugin: ansible
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/cfengine/plugin.rb
INFO manager: Registered plugin: CFEngine Provisioner
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/chef/plugin.rb
INFO manager: Registered plugin: chef
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/docker/plugin.rb
INFO manager: Registered plugin: docker
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/file/plugin.rb
INFO manager: Registered plugin: file
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/puppet/plugin.rb
INFO manager: Registered plugin: puppet
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/salt/plugin.rb
INFO manager: Registered plugin: salt
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/shell/plugin.rb
INFO manager: Registered plugin: shell
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/pushes/atlas/plugin.rb
INFO manager: Registered plugin: atlas
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/pushes/ftp/plugin.rb
INFO manager: Registered plugin: ftp
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/pushes/heroku/plugin.rb
INFO manager: Registered plugin: heroku
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/pushes/local-exec/plugin.rb
INFO manager: Registered plugin: local-exec
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/pushes/noop/plugin.rb
INFO manager: Registered plugin: noop
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/synced_folders/nfs/plugin.rb
INFO manager: Registered plugin: NFS synced folders
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/synced_folders/rsync/plugin.rb
INFO manager: Registered plugin: RSync synced folders
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/synced_folders/smb/plugin.rb
INFO manager: Registered plugin: SMB synced folders
INFO manager: Registered plugin: VMware Fusion Provider
INFO vmware_driver: VMX path is a directory. Finding VMX file...
INFO vmware_driver: VMX file: /Users/quasiben/.vagrant/machines/dev/vmware_fusion/7890b8d8-98e2-4cd5-a989-d65c4e0279ae/trusty64.vmx
INFO vmware_driver: Looking for VMware Fusion: /Applications/VMware Fusion.app
INFO vmware_driver: VMware Fusion path: #<Pathname:/Applications/VMware Fusion.app>
DEBUG vmware_driver: Attempting to read VMware version...
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmware-vmx", "-v"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command is setuid/setgid, clearing DYLD_LIBRARY_PATH
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr:
VMware Fusion Information:
VMware Fusion 7.1.0 build-2314774 Release
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO vmware_driver: Detected VMware version: 7.1.0
DEBUG vmware_driver: service starter path: /Applications/VMware Fusion.app/Contents/Library/services/Open VMware Fusion Services
DEBUG vmware_driver: vmnet-cli path: /Applications/VMware Fusion.app/Contents/Library/vmnet-cli
INFO vmware:sudo_helper: Calling command: create-vmnet-device
INFO networking_file: Reading adapters from networking file...
DEBUG networking_file: VNET: 1. KEY: 'DHCP' = 'yes'
DEBUG networking_file: VNET: 1. KEY: 'DHCP_CFG_HASH' = 'D80210FE873BE2813B8C769A8E72B64979061717'
DEBUG networking_file: VNET: 1. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG networking_file: VNET: 1. KEY: 'HOSTONLY_SUBNET' = '192.168.27.0'
DEBUG networking_file: VNET: 1. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG networking_file: VNET: 2. KEY: 'DHCP' = 'yes'
DEBUG networking_file: VNET: 2. KEY: 'DHCP_CFG_HASH' = '87768080D35EC28F8A98E2922D0D6FE5E5C18A59'
DEBUG networking_file: VNET: 2. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG networking_file: VNET: 2. KEY: 'HOSTONLY_SUBNET' = '10.10.10.0'
DEBUG networking_file: VNET: 2. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG networking_file: VNET: 3. KEY: 'DHCP' = 'yes'
DEBUG networking_file: VNET: 3. KEY: 'DHCP_CFG_HASH' = '3EC4C96155C7AA76726042C1D3C8D9C208404144'
DEBUG networking_file: VNET: 3. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG networking_file: VNET: 3. KEY: 'HOSTONLY_SUBNET' = '192.168.18.0'
DEBUG networking_file: VNET: 3. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG networking_file: VNET: 4. KEY: 'DHCP' = 'yes'
DEBUG networking_file: VNET: 4. KEY: 'DHCP_CFG_HASH' = '6F6696B0E161F81ED0E3CE9F08794F4DD8D794EB'
DEBUG networking_file: VNET: 4. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG networking_file: VNET: 4. KEY: 'HOSTONLY_SUBNET' = '172.16.48.0'
DEBUG networking_file: VNET: 4. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG networking_file: VNET: 5. KEY: 'DHCP' = 'yes'
DEBUG networking_file: VNET: 5. KEY: 'DHCP_CFG_HASH' = '9B81D6F11FF984546E1C4E2B438F14AC3B559373'
DEBUG networking_file: VNET: 5. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG networking_file: VNET: 5. KEY: 'HOSTONLY_SUBNET' = '192.168.111.0'
DEBUG networking_file: VNET: 5. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG networking_file: VNET: 8. KEY: 'DHCP' = 'yes'
DEBUG networking_file: VNET: 8. KEY: 'DHCP_CFG_HASH' = '1BDC60FCCCD2EEB9E6AA5D403BE51F90BF3ACC00'
DEBUG networking_file: VNET: 8. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG networking_file: VNET: 8. KEY: 'HOSTONLY_SUBNET' = '192.168.186.0'
DEBUG networking_file: VNET: 8. KEY: 'NAT' = 'yes'
DEBUG networking_file: VNET: 8. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG networking_file: Pruning adapters that aren't actually active...
INFO vmware_driver: Starting services starter and waiting for them to start...
INFO vmware_driver: Killing vmnet-natd if it is alive...
INFO subprocess: Starting process: ["/usr/bin/pkill", "vmnet-natd"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--start"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Failed to start DHCP service on vmnet6
DEBUG subprocess: stderr: Failed to start some/all services
DEBUG subprocess: stdout: Enabled hostonly virtual adapter on vmnet1
Started DHCP service on vmnet1
Enabled hostonly virtual adapter on vmnet2
Started DHCP service on vmnet2
Enabled hostonly virtual adapter on vmnet3
Started DHCP service on vmnet3
Enabled hostonly virtual adapter on vmnet4
Started DHCP service on vmnet4
Enabled hostonly virtual adapter on vmnet5
Started DHCP service on vmnet5
Enabled hostonly virtual adapter on vmnet6
Started NAT service on vmnet8
Enabled hostonly virtual adapter on vmnet8
Started DHCP service on vmnet8
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Some/All of the configured services are not running
DEBUG subprocess: stdout: DHCP service on vmnet1 is running
Hostonly virtual adapter on vmnet1 is enabled
DHCP service on vmnet2 is running
Hostonly virtual adapter on vmnet2 is enabled
DHCP service on vmnet3 is running
Hostonly virtual adapter on vmnet3 is enabled
DHCP service on vmnet4 is running
Hostonly virtual adapter on vmnet4 is enabled
DHCP service on vmnet5 is running
Hostonly virtual adapter on vmnet5 is enabled
DHCP service on vmnet6 is not running
Hostonly virtual adapter on vmnet6 is enabled
DHCP service on vmnet8 is running
NAT service on vmnet8 is running
Hostonly virtual adapter on vmnet8 is enabled
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO retryable: Retryable exception raised: #<HashiCorp::VagrantVMwarefusion::Errors::VMNetDevicesWontStart: The VMware "vmnet" devices are failing to start. The most common
reason for this is collisions with existing network services. For
example, if a hostonly network space collides with another hostonly
network (such as with VirtualBox), it will fail to start. Likewise,
if forwarded ports collide with other listening ports, it will
fail to start.
Vagrant does its best to fix these issues, but in some cases it
cannot determine the root cause of these failures.
Please verify you have no other colliding network services running.
As a last resort, restarting your computer often fixes this issue.>
INFO vmware_driver: Killing vmnet-natd if it is alive...
INFO subprocess: Starting process: ["/usr/bin/pkill", "vmnet-natd"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--start"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Failed to start DHCP service on vmnet6
DEBUG subprocess: stderr: Failed to start some/all services
DEBUG subprocess: stdout: Enabled hostonly virtual adapter on vmnet1
Started DHCP service on vmnet1
Enabled hostonly virtual adapter on vmnet2
Started DHCP service on vmnet2
Enabled hostonly virtual adapter on vmnet3
Started DHCP service on vmnet3
Enabled hostonly virtual adapter on vmnet4
Started DHCP service on vmnet4
Enabled hostonly virtual adapter on vmnet5
Started DHCP service on vmnet5
Enabled hostonly virtual adapter on vmnet6
Started NAT service on vmnet8
Enabled hostonly virtual adapter on vmnet8
Started DHCP service on vmnet8
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Some/All of the configured services are not running
DEBUG subprocess: stdout: DHCP service on vmnet1 is running
Hostonly virtual adapter on vmnet1 is enabled
DHCP service on vmnet2 is running
Hostonly virtual adapter on vmnet2 is enabled
DHCP service on vmnet3 is running
Hostonly virtual adapter on vmnet3 is enabled
DHCP service on vmnet4 is running
Hostonly virtual adapter on vmnet4 is enabled
DHCP service on vmnet5 is running
Hostonly virtual adapter on vmnet5 is enabled
DHCP service on vmnet6 is not running
Hostonly virtual adapter on vmnet6 is enabled
DHCP service on vmnet8 is running
NAT service on vmnet8 is running
Hostonly virtual adapter on vmnet8 is enabled
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO retryable: Retryable exception raised: #<HashiCorp::VagrantVMwarefusion::Errors::VMNetDevicesWontStart: The VMware "vmnet" devices are failing to start. The most common
reason for this is collisions with existing network services. For
example, if a hostonly network space collides with another hostonly
network (such as with VirtualBox), it will fail to start. Likewise,
if forwarded ports collide with other listening ports, it will
fail to start.
Vagrant does its best to fix these issues, but in some cases it
cannot determine the root cause of these failures.
Please verify you have no other colliding network services running.
As a last resort, restarting your computer often fixes this issue.>
INFO vmware_driver: Killing vmnet-natd if it is alive...
INFO subprocess: Starting process: ["/usr/bin/pkill", "vmnet-natd"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--start"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Failed to start DHCP service on vmnet6
DEBUG subprocess: stderr: Failed to start some/all services
DEBUG subprocess: stdout: Enabled hostonly virtual adapter on vmnet1
Started DHCP service on vmnet1
Enabled hostonly virtual adapter on vmnet2
Started DHCP service on vmnet2
Enabled hostonly virtual adapter on vmnet3
Started DHCP service on vmnet3
Enabled hostonly virtual adapter on vmnet4
Started DHCP service on vmnet4
Enabled hostonly virtual adapter on vmnet5
Started DHCP service on vmnet5
Enabled hostonly virtual adapter on vmnet6
Started NAT service on vmnet8
Enabled hostonly virtual adapter on vmnet8
Started DHCP service on vmnet8
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 31999
DEBUG subprocess: Exit status: 1
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Some/All of the configured services are not running
DEBUG subprocess: stdout: DHCP service on vmnet1 is running
Hostonly virtual adapter on vmnet1 is enabled
DHCP service on vmnet2 is running
Hostonly virtual adapter on vmnet2 is enabled
DHCP service on vmnet3 is running
Hostonly virtual adapter on vmnet3 is enabled
DHCP service on vmnet4 is running
Hostonly virtual adapter on vmnet4 is enabled
DHCP service on vmnet5 is running
Hostonly virtual adapter on vmnet5 is enabled
DHCP service on vmnet6 is not running
Hostonly virtual adapter on vmnet6 is enabled
DHCP service on vmnet8 is running
NAT service on vmnet8 is running
Hostonly virtual adapter on vmnet8 is enabled
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO retryable: Retryable exception raised: #<HashiCorp::VagrantVMwarefusion::Errors::VMNetDevicesWontStart: The VMware "vmnet" devices are failing to start. The most common
reason for this is collisions with existing network services. For
example, if a hostonly network space collides with another hostonly
network (such as with VirtualBox), it will fail to start. Likewise,
if forwarded ports collide with other listening ports, it will
fail to start.
Vagrant does its best to fix these issues, but in some cases it
cannot determine the root cause of these failures.
Please verify you have no other colliding network services running.
As a last resort, restarting your computer often fixes this issue.>
INFO vmware_driver: Killing vmnet-natd if it is alive...
INFO subprocess: Starting process: ["/usr/bin/pkill", "vmnet-natd"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--start"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Failed to start DHCP service on vmnet6
DEBUG subprocess: stderr: Failed to start some/all services
DEBUG subprocess: stdout: Enabled hostonly virtual adapter on vmnet1
Started DHCP service on vmnet1
Enabled hostonly virtual adapter on vmnet2
Started DHCP service on vmnet2
Enabled hostonly virtual adapter on vmnet3
Started DHCP service on vmnet3
Enabled hostonly virtual adapter on vmnet4
Started DHCP service on vmnet4
Enabled hostonly virtual adapter on vmnet5
Started DHCP service on vmnet5
Enabled hostonly virtual adapter on vmnet6
Started NAT service on vmnet8
Enabled hostonly virtual adapter on vmnet8
Started DHCP service on vmnet8
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Some/All of the configured services are not running
DEBUG subprocess: stdout: DHCP service on vmnet1 is running
Hostonly virtual adapter on vmnet1 is enabled
DHCP service on vmnet2 is running
Hostonly virtual adapter on vmnet2 is enabled
DHCP service on vmnet3 is running
Hostonly virtual adapter on vmnet3 is enabled
DHCP service on vmnet4 is running
Hostonly virtual adapter on vmnet4 is enabled
DHCP service on vmnet5 is running
Hostonly virtual adapter on vmnet5 is enabled
DHCP service on vmnet6 is not running
Hostonly virtual adapter on vmnet6 is enabled
DHCP service on vmnet8 is running
NAT service on vmnet8 is running
Hostonly virtual adapter on vmnet8 is enabled
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO retryable: Retryable exception raised: #<HashiCorp::VagrantVMwarefusion::Errors::VMNetDevicesWontStart: The VMware "vmnet" devices are failing to start. The most common
reason for this is collisions with existing network services. For
example, if a hostonly network space collides with another hostonly
network (such as with VirtualBox), it will fail to start. Likewise,
if forwarded ports collide with other listening ports, it will
fail to start.
Vagrant does its best to fix these issues, but in some cases it
cannot determine the root cause of these failures.
Please verify you have no other colliding network services running.
As a last resort, restarting your computer often fixes this issue.>
INFO vmware_driver: Killing vmnet-natd if it is alive...
INFO subprocess: Starting process: ["/usr/bin/pkill", "vmnet-natd"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--start"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Failed to start DHCP service on vmnet6
DEBUG subprocess: stderr: Failed to start some/all services
DEBUG subprocess: stdout: Enabled hostonly virtual adapter on vmnet1
Started DHCP service on vmnet1
Enabled hostonly virtual adapter on vmnet2
Started DHCP service on vmnet2
Enabled hostonly virtual adapter on vmnet3
Started DHCP service on vmnet3
Enabled hostonly virtual adapter on vmnet4
Started DHCP service on vmnet4
Enabled hostonly virtual adapter on vmnet5
Started DHCP service on vmnet5
Enabled hostonly virtual adapter on vmnet6
Started NAT service on vmnet8
Enabled hostonly virtual adapter on vmnet8
Started DHCP service on vmnet8
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 31999
DEBUG subprocess: Exit status: 1
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Some/All of the configured services are not running
DEBUG subprocess: stdout: DHCP service on vmnet1 is running
Hostonly virtual adapter on vmnet1 is enabled
DHCP service on vmnet2 is running
Hostonly virtual adapter on vmnet2 is enabled
DHCP service on vmnet3 is running
Hostonly virtual adapter on vmnet3 is enabled
DHCP service on vmnet4 is running
Hostonly virtual adapter on vmnet4 is enabled
DHCP service on vmnet5 is running
Hostonly virtual adapter on vmnet5 is enabled
DHCP service on vmnet6 is not running
Hostonly virtual adapter on vmnet6 is enabled
DHCP service on vmnet8 is running
NAT service on vmnet8 is running
Hostonly virtual adapter on vmnet8 is enabled
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO vmware_driver: Stopping services starter...
The VMware "vmnet" devices are failing to start. The most common
reason for this is collisions with existing network services. For
example, if a hostonly network space collides with another hostonly
network (such as with VirtualBox), it will fail to start. Likewise,
if forwarded ports collide with other listening ports, it will
fail to start.
Vagrant does its best to fix these issues, but in some cases it
cannot determine the root cause of these failures.
Please verify you have no other colliding network services running.
As a last resort, restarting your computer often fixes this issue.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
ERROR warden: Error occurred: INFO global: Vagrant version: 1.7.4
INFO global: Ruby version: 2.0.0
INFO global: RubyGems version: 2.0.14
INFO global: VAGRANT_LOG="debug"
INFO global: VAGRANT_OLD_ENV_SPARK_HOME="/Users/quasiben/Research/GitClones/spark"
INFO global: VAGRANT_OLD_ENV_HOME="/Users/quasiben"
INFO global: VAGRANT_OLD_ENV__="/usr/local/bin/vagrant"
INFO global: VAGRANT_OLD_ENV_XPC_FLAGS="0x0"
INFO global: VAGRANT_INSTALLER_VERSION="2"
INFO global: VAGRANT_OLD_ENV_VAGRANT_LOG="debug"
INFO global: VAGRANT_OLD_ENV_TMPDIR="/var/folders/1t/t94brwgx7sjcn8jgz4gr3_c00000gq/T/"
INFO global: VAGRANT_OLD_ENV_Apple_PubSub_Socket_Render="/private/tmp/com.apple.launchd.KW13obTzd8/Render"
INFO global: VAGRANT_OLD_ENV_JAVA_HOME="/Library/Java/JavaVirtualMachines/jdk1.7.0_45.jdk/Contents/Home"
INFO global: VAGRANT_OLD_ENV_ACHE_HOME="/Users/quasiben/anaconda/envs/memex-explorer/lib/python2.7/site-packages/ache/"
INFO global: VAGRANT_OLD_ENV_CONDA_ENV_PATH="/Users/quasiben/anaconda/envs/clusto"
INFO global: VAGRANT_OLD_ENV_PYTHONPATH="/Users/quasiben/Research/ContinuumDev/GitRepo/conda-cluster/::/Users/quasiben/Research/GitClones/spark/python"
INFO global: VAGRANT_OLD_ENV_PATH="/Users/quasiben/anaconda/envs/clusto/bin:/usr/local/bin:/usr/local/heroku/bin:/Users/quasiben/google-cloud-sdk/bin:/usr/local/sbin:/Users/quasiben/.cabal/bin/:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/texbin:/Users/quasiben/Research/ContinuumDev/GitRepo/libdynd/build"
INFO global: VAGRANT_OLD_ENV_PWD="/Users/quasiben"
INFO global: VAGRANT_OLD_ENV_ITERM_PROFILE="Default"
INFO global: VAGRANT_OLD_ENV_JDK_HOME="/Library/Java/JavaVirtualMachines/jdk1.7.0_45.jdk/Contents/Home/"
INFO global: VAGRANT_OLD_ENV_COLORFGBG="7;0"
INFO global: VAGRANT_OLD_ENV_CONDA_DEFAULT_ENV="clusto"
INFO global: VAGRANT_INSTALLER_ENV="1"
INFO global: VAGRANT_EXECUTABLE="/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/bin/vagrant"
INFO global: VAGRANT_INSTALLER_EMBEDDED_DIR="/opt/vagrant/embedded"
INFO global: VAGRANT_OLD_ENV_COMMAND_MODE="unix2003"
INFO global: VAGRANT_OLD_ENV_SSH_AUTH_SOCK="/private/tmp/com.apple.launchd.CSjdOMPkpG/Listeners"
INFO global: VAGRANT_OLD_ENV_LANG="en_US.UTF-8"
INFO global: VAGRANT_OLD_ENV_TERM_PROGRAM="iTerm.app"
INFO global: VAGRANT_OLD_ENV_XPC_SERVICE_NAME="0"
INFO global: VAGRANT_OLD_ENV_SHLVL="1"
INFO global: VAGRANT_OLD_ENV_SECURITYSESSIONID="186a5"
INFO global: VAGRANT_OLD_ENV_TERM="xterm-color"
INFO global: VAGRANT_OLD_ENV_USER="quasiben"
INFO global: VAGRANT_OLD_ENV___CF_USER_TEXT_ENCODING="0x1F7:0x0:0x0"
INFO global: VAGRANT_OLD_ENV_ITERM_SESSION_ID="w0t1p0"
INFO global: VAGRANT_OLD_ENV_SHELL="/bin/bash"
INFO global: VAGRANT_OLD_ENV_PS1="(clusto)\\[\\033[01;32m\\]\\u@\\h\\[\\033[00m\\]:\\[\\033[01;36m\\]\\w\\[\\033[00m\\]\\$ "
INFO global: VAGRANT_OLD_ENV_OLDPWD="/Users/quasiben/Research/ContinuumDev/AC_AS_Vagrant/Head+Compute/test"
INFO global: VAGRANT_OLD_ENV_JRE_HOME="/Library/Java/JavaVirtualMachines/jdk1.7.0_45.jdk/Contents/Home/jre/"
INFO global: VAGRANT_OLD_ENV_LOGNAME="quasiben"
INFO global: VAGRANT_INTERNAL_BUNDLERIZED="1"
INFO global: Plugins:
INFO global: - bundler = 1.10.5
INFO global: - mime-types = 1.25.1
INFO global: - rest-client = 1.6.9
INFO global: - vagrant-share = 1.1.4
INFO global: - vagrant-vmware-fusion = 4.0.2
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/box/plugin.rb
INFO manager: Registered plugin: box command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/destroy/plugin.rb
INFO manager: Registered plugin: destroy command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/global-status/plugin.rb
INFO manager: Registered plugin: global-status command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/halt/plugin.rb
INFO manager: Registered plugin: halt command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/help/plugin.rb
INFO manager: Registered plugin: help command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/init/plugin.rb
INFO manager: Registered plugin: init command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/list-commands/plugin.rb
INFO manager: Registered plugin: list-commands command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/login/plugin.rb
INFO manager: Registered plugin: vagrant-login
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/package/plugin.rb
INFO manager: Registered plugin: package command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/plugin/plugin.rb
INFO manager: Registered plugin: plugin command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/provision/plugin.rb
INFO manager: Registered plugin: provision command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/push/plugin.rb
INFO manager: Registered plugin: push command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/rdp/plugin.rb
INFO manager: Registered plugin: rdp command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/reload/plugin.rb
INFO manager: Registered plugin: reload command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/resume/plugin.rb
INFO manager: Registered plugin: resume command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/ssh/plugin.rb
INFO manager: Registered plugin: ssh command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/ssh_config/plugin.rb
INFO manager: Registered plugin: ssh-config command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/status/plugin.rb
INFO manager: Registered plugin: status command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/suspend/plugin.rb
INFO manager: Registered plugin: suspend command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/up/plugin.rb
INFO manager: Registered plugin: up command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/version/plugin.rb
INFO manager: Registered plugin: version command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/communicators/ssh/plugin.rb
INFO manager: Registered plugin: ssh communicator
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/communicators/winrm/plugin.rb
INFO manager: Registered plugin: winrm communicator
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/arch/plugin.rb
INFO manager: Registered plugin: Arch guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/atomic/plugin.rb
INFO manager: Registered plugin: Atomic Host guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/coreos/plugin.rb
INFO manager: Registered plugin: CoreOS guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/darwin/plugin.rb
INFO manager: Registered plugin: Darwin guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/debian/plugin.rb
INFO manager: Registered plugin: Debian guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/debian8/plugin.rb
INFO manager: Registered plugin: Debian Jessie guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/esxi/plugin.rb
INFO manager: Registered plugin: ESXi guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/fedora/plugin.rb
INFO manager: Registered plugin: Fedora guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/freebsd/plugin.rb
INFO manager: Registered plugin: FreeBSD guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/funtoo/plugin.rb
INFO manager: Registered plugin: Funtoo guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/gentoo/plugin.rb
INFO manager: Registered plugin: Gentoo guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/linux/plugin.rb
INFO manager: Registered plugin: Linux guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/mint/plugin.rb
INFO manager: Registered plugin: Mint guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/netbsd/plugin.rb
INFO manager: Registered plugin: NetBSD guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/nixos/plugin.rb
INFO manager: Registered plugin: NixOS guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/omnios/plugin.rb
INFO manager: Registered plugin: OmniOS guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/openbsd/plugin.rb
INFO manager: Registered plugin: OpenBSD guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/photon/plugin.rb
INFO manager: Registered plugin: VMware Photon guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/pld/plugin.rb
INFO manager: Registered plugin: PLD Linux guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/redhat/plugin.rb
INFO manager: Registered plugin: Red Hat Enterprise Linux guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/smartos/plugin.rb
INFO manager: Registered plugin: SmartOS guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/solaris/plugin.rb
INFO manager: Registered plugin: Solaris guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/solaris11/plugin.rb
INFO manager: Registered plugin: Solaris 11 guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/suse/plugin.rb
INFO manager: Registered plugin: SUSE guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/tinycore/plugin.rb
INFO manager: Registered plugin: TinyCore Linux guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/ubuntu/plugin.rb
INFO manager: Registered plugin: Ubuntu guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/windows/plugin.rb
INFO manager: Registered plugin: Windows guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/arch/plugin.rb
INFO manager: Registered plugin: Arch host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/bsd/plugin.rb
INFO manager: Registered plugin: BSD host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/darwin/plugin.rb
INFO manager: Registered plugin: Mac OS X host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/freebsd/plugin.rb
INFO manager: Registered plugin: FreeBSD host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/gentoo/plugin.rb
INFO manager: Registered plugin: Gentoo host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/linux/plugin.rb
INFO manager: Registered plugin: Linux host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/null/plugin.rb
INFO manager: Registered plugin: null host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/redhat/plugin.rb
INFO manager: Registered plugin: Red Hat Enterprise Linux host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/slackware/plugin.rb
INFO manager: Registered plugin: Slackware host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/suse/plugin.rb
INFO manager: Registered plugin: SUSE host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/windows/plugin.rb
INFO manager: Registered plugin: Windows host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/kernel_v1/plugin.rb
INFO manager: Registered plugin: kernel
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/kernel_v2/plugin.rb
INFO manager: Registered plugin: kernel
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/providers/docker/plugin.rb
INFO manager: Registered plugin: docker-provider
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/providers/hyperv/plugin.rb
INFO manager: Registered plugin: Hyper-V provider
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/providers/virtualbox/plugin.rb
INFO manager: Registered plugin: VirtualBox provider
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/ansible/plugin.rb
INFO manager: Registered plugin: ansible
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/cfengine/plugin.rb
INFO manager: Registered plugin: CFEngine Provisioner
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/chef/plugin.rb
INFO manager: Registered plugin: chef
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/docker/plugin.rb
INFO manager: Registered plugin: docker
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/file/plugin.rb
INFO manager: Registered plugin: file
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/puppet/plugin.rb
INFO manager: Registered plugin: puppet
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/salt/plugin.rb
INFO manager: Registered plugin: salt
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/shell/plugin.rb
INFO manager: Registered plugin: shell
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/pushes/atlas/plugin.rb
INFO manager: Registered plugin: atlas
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/pushes/ftp/plugin.rb
INFO manager: Registered plugin: ftp
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/pushes/heroku/plugin.rb
INFO manager: Registered plugin: heroku
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/pushes/local-exec/plugin.rb
INFO manager: Registered plugin: local-exec
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/pushes/noop/plugin.rb
INFO manager: Registered plugin: noop
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/synced_folders/nfs/plugin.rb
INFO manager: Registered plugin: NFS synced folders
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/synced_folders/rsync/plugin.rb
INFO manager: Registered plugin: RSync synced folders
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/synced_folders/smb/plugin.rb
INFO manager: Registered plugin: SMB synced folders
INFO manager: Registered plugin: VMware Fusion Provider
INFO vmware_driver: VMX path is a directory. Finding VMX file...
INFO vmware_driver: VMX file: /Users/quasiben/.vagrant/machines/dev/vmware_fusion/7890b8d8-98e2-4cd5-a989-d65c4e0279ae/trusty64.vmx
INFO vmware_driver: Looking for VMware Fusion: /Applications/VMware Fusion.app
INFO vmware_driver: VMware Fusion path: #<Pathname:/Applications/VMware Fusion.app>
DEBUG vmware_driver: Attempting to read VMware version...
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmware-vmx", "-v"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command is setuid/setgid, clearing DYLD_LIBRARY_PATH
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr:
VMware Fusion Information:
VMware Fusion 7.1.0 build-2314774 Release
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO vmware_driver: Detected VMware version: 7.1.0
DEBUG vmware_driver: service starter path: /Applications/VMware Fusion.app/Contents/Library/services/Open VMware Fusion Services
DEBUG vmware_driver: vmnet-cli path: /Applications/VMware Fusion.app/Contents/Library/vmnet-cli
INFO vmware:sudo_helper: Calling command: create-vmnet-device
INFO networking_file: Reading adapters from networking file...
DEBUG networking_file: VNET: 1. KEY: 'DHCP' = 'yes'
DEBUG networking_file: VNET: 1. KEY: 'DHCP_CFG_HASH' = 'D80210FE873BE2813B8C769A8E72B64979061717'
DEBUG networking_file: VNET: 1. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG networking_file: VNET: 1. KEY: 'HOSTONLY_SUBNET' = '192.168.27.0'
DEBUG networking_file: VNET: 1. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG networking_file: VNET: 2. KEY: 'DHCP' = 'yes'
DEBUG networking_file: VNET: 2. KEY: 'DHCP_CFG_HASH' = '87768080D35EC28F8A98E2922D0D6FE5E5C18A59'
DEBUG networking_file: VNET: 2. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG networking_file: VNET: 2. KEY: 'HOSTONLY_SUBNET' = '10.10.10.0'
DEBUG networking_file: VNET: 2. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG networking_file: VNET: 3. KEY: 'DHCP' = 'yes'
DEBUG networking_file: VNET: 3. KEY: 'DHCP_CFG_HASH' = '3EC4C96155C7AA76726042C1D3C8D9C208404144'
DEBUG networking_file: VNET: 3. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG networking_file: VNET: 3. KEY: 'HOSTONLY_SUBNET' = '192.168.18.0'
DEBUG networking_file: VNET: 3. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG networking_file: VNET: 4. KEY: 'DHCP' = 'yes'
DEBUG networking_file: VNET: 4. KEY: 'DHCP_CFG_HASH' = '6F6696B0E161F81ED0E3CE9F08794F4DD8D794EB'
DEBUG networking_file: VNET: 4. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG networking_file: VNET: 4. KEY: 'HOSTONLY_SUBNET' = '172.16.48.0'
DEBUG networking_file: VNET: 4. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG networking_file: VNET: 5. KEY: 'DHCP' = 'yes'
DEBUG networking_file: VNET: 5. KEY: 'DHCP_CFG_HASH' = '9B81D6F11FF984546E1C4E2B438F14AC3B559373'
DEBUG networking_file: VNET: 5. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG networking_file: VNET: 5. KEY: 'HOSTONLY_SUBNET' = '192.168.111.0'
DEBUG networking_file: VNET: 5. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG networking_file: VNET: 8. KEY: 'DHCP' = 'yes'
DEBUG networking_file: VNET: 8. KEY: 'DHCP_CFG_HASH' = '1BDC60FCCCD2EEB9E6AA5D403BE51F90BF3ACC00'
DEBUG networking_file: VNET: 8. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG networking_file: VNET: 8. KEY: 'HOSTONLY_SUBNET' = '192.168.186.0'
DEBUG networking_file: VNET: 8. KEY: 'NAT' = 'yes'
DEBUG networking_file: VNET: 8. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG networking_file: Pruning adapters that aren't actually active...
INFO vmware_driver: Starting services starter and waiting for them to start...
INFO vmware_driver: Killing vmnet-natd if it is alive...
INFO subprocess: Starting process: ["/usr/bin/pkill", "vmnet-natd"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--start"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Failed to start DHCP service on vmnet6
DEBUG subprocess: stderr: Failed to start some/all services
DEBUG subprocess: stdout: Enabled hostonly virtual adapter on vmnet1
Started DHCP service on vmnet1
Enabled hostonly virtual adapter on vmnet2
Started DHCP service on vmnet2
Enabled hostonly virtual adapter on vmnet3
Started DHCP service on vmnet3
Enabled hostonly virtual adapter on vmnet4
Started DHCP service on vmnet4
Enabled hostonly virtual adapter on vmnet5
Started DHCP service on vmnet5
Enabled hostonly virtual adapter on vmnet6
Started NAT service on vmnet8
Enabled hostonly virtual adapter on vmnet8
Started DHCP service on vmnet8
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Some/All of the configured services are not running
DEBUG subprocess: stdout: DHCP service on vmnet1 is running
Hostonly virtual adapter on vmnet1 is enabled
DHCP service on vmnet2 is running
Hostonly virtual adapter on vmnet2 is enabled
DHCP service on vmnet3 is running
Hostonly virtual adapter on vmnet3 is enabled
DHCP service on vmnet4 is running
Hostonly virtual adapter on vmnet4 is enabled
DHCP service on vmnet5 is running
Hostonly virtual adapter on vmnet5 is enabled
DHCP service on vmnet6 is not running
Hostonly virtual adapter on vmnet6 is enabled
DHCP service on vmnet8 is running
NAT service on vmnet8 is running
Hostonly virtual adapter on vmnet8 is enabled
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO retryable: Retryable exception raised: #<HashiCorp::VagrantVMwarefusion::Errors::VMNetDevicesWontStart: The VMware "vmnet" devices are failing to start. The most common
reason for this is collisions with existing network services. For
example, if a hostonly network space collides with another hostonly
network (such as with VirtualBox), it will fail to start. Likewise,
if forwarded ports collide with other listening ports, it will
fail to start.
Vagrant does its best to fix these issues, but in some cases it
cannot determine the root cause of these failures.
Please verify you have no other colliding network services running.
As a last resort, restarting your computer often fixes this issue.>
INFO vmware_driver: Killing vmnet-natd if it is alive...
INFO subprocess: Starting process: ["/usr/bin/pkill", "vmnet-natd"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--start"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Failed to start DHCP service on vmnet6
DEBUG subprocess: stderr: Failed to start some/all services
DEBUG subprocess: stdout: Enabled hostonly virtual adapter on vmnet1
Started DHCP service on vmnet1
Enabled hostonly virtual adapter on vmnet2
Started DHCP service on vmnet2
Enabled hostonly virtual adapter on vmnet3
Started DHCP service on vmnet3
Enabled hostonly virtual adapter on vmnet4
Started DHCP service on vmnet4
Enabled hostonly virtual adapter on vmnet5
Started DHCP service on vmnet5
Enabled hostonly virtual adapter on vmnet6
Started NAT service on vmnet8
Enabled hostonly virtual adapter on vmnet8
Started DHCP service on vmnet8
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Some/All of the configured services are not running
DEBUG subprocess: stdout: DHCP service on vmnet1 is running
Hostonly virtual adapter on vmnet1 is enabled
DHCP service on vmnet2 is running
Hostonly virtual adapter on vmnet2 is enabled
DHCP service on vmnet3 is running
Hostonly virtual adapter on vmnet3 is enabled
DHCP service on vmnet4 is running
Hostonly virtual adapter on vmnet4 is enabled
DHCP service on vmnet5 is running
Hostonly virtual adapter on vmnet5 is enabled
DHCP service on vmnet6 is not running
Hostonly virtual adapter on vmnet6 is enabled
DHCP service on vmnet8 is running
NAT service on vmnet8 is running
Hostonly virtual adapter on vmnet8 is enabled
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO retryable: Retryable exception raised: #<HashiCorp::VagrantVMwarefusion::Errors::VMNetDevicesWontStart: The VMware "vmnet" devices are failing to start. The most common
reason for this is collisions with existing network services. For
example, if a hostonly network space collides with another hostonly
network (such as with VirtualBox), it will fail to start. Likewise,
if forwarded ports collide with other listening ports, it will
fail to start.
Vagrant does its best to fix these issues, but in some cases it
cannot determine the root cause of these failures.
Please verify you have no other colliding network services running.
As a last resort, restarting your computer often fixes this issue.>
INFO vmware_driver: Killing vmnet-natd if it is alive...
INFO subprocess: Starting process: ["/usr/bin/pkill", "vmnet-natd"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--start"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Failed to start DHCP service on vmnet6
DEBUG subprocess: stderr: Failed to start some/all services
DEBUG subprocess: stdout: Enabled hostonly virtual adapter on vmnet1
Started DHCP service on vmnet1
Enabled hostonly virtual adapter on vmnet2
Started DHCP service on vmnet2
Enabled hostonly virtual adapter on vmnet3
Started DHCP service on vmnet3
Enabled hostonly virtual adapter on vmnet4
Started DHCP service on vmnet4
Enabled hostonly virtual adapter on vmnet5
Started DHCP service on vmnet5
Enabled hostonly virtual adapter on vmnet6
Started NAT service on vmnet8
Enabled hostonly virtual adapter on vmnet8
Started DHCP service on vmnet8
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 31999
DEBUG subprocess: Exit status: 1
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Some/All of the configured services are not running
DEBUG subprocess: stdout: DHCP service on vmnet1 is running
Hostonly virtual adapter on vmnet1 is enabled
DHCP service on vmnet2 is running
Hostonly virtual adapter on vmnet2 is enabled
DHCP service on vmnet3 is running
Hostonly virtual adapter on vmnet3 is enabled
DHCP service on vmnet4 is running
Hostonly virtual adapter on vmnet4 is enabled
DHCP service on vmnet5 is running
Hostonly virtual adapter on vmnet5 is enabled
DHCP service on vmnet6 is not running
Hostonly virtual adapter on vmnet6 is enabled
DHCP service on vmnet8 is running
NAT service on vmnet8 is running
Hostonly virtual adapter on vmnet8 is enabled
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO retryable: Retryable exception raised: #<HashiCorp::VagrantVMwarefusion::Errors::VMNetDevicesWontStart: The VMware "vmnet" devices are failing to start. The most common
reason for this is collisions with existing network services. For
example, if a hostonly network space collides with another hostonly
network (such as with VirtualBox), it will fail to start. Likewise,
if forwarded ports collide with other listening ports, it will
fail to start.
Vagrant does its best to fix these issues, but in some cases it
cannot determine the root cause of these failures.
Please verify you have no other colliding network services running.
As a last resort, restarting your computer often fixes this issue.>
INFO vmware_driver: Killing vmnet-natd if it is alive...
INFO subprocess: Starting process: ["/usr/bin/pkill", "vmnet-natd"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--start"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Failed to start DHCP service on vmnet6
DEBUG subprocess: stderr: Failed to start some/all services
DEBUG subprocess: stdout: Enabled hostonly virtual adapter on vmnet1
Started DHCP service on vmnet1
Enabled hostonly virtual adapter on vmnet2
Started DHCP service on vmnet2
Enabled hostonly virtual adapter on vmnet3
Started DHCP service on vmnet3
Enabled hostonly virtual adapter on vmnet4
Started DHCP service on vmnet4
Enabled hostonly virtual adapter on vmnet5
Started DHCP service on vmnet5
Enabled hostonly virtual adapter on vmnet6
Started NAT service on vmnet8
Enabled hostonly virtual adapter on vmnet8
Started DHCP service on vmnet8
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Some/All of the configured services are not running
DEBUG subprocess: stdout: DHCP service on vmnet1 is running
Hostonly virtual adapter on vmnet1 is enabled
DHCP service on vmnet2 is running
Hostonly virtual adapter on vmnet2 is enabled
DHCP service on vmnet3 is running
Hostonly virtual adapter on vmnet3 is enabled
DHCP service on vmnet4 is running
Hostonly virtual adapter on vmnet4 is enabled
DHCP service on vmnet5 is running
Hostonly virtual adapter on vmnet5 is enabled
DHCP service on vmnet6 is not running
Hostonly virtual adapter on vmnet6 is enabled
DHCP service on vmnet8 is running
NAT service on vmnet8 is running
Hostonly virtual adapter on vmnet8 is enabled
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO retryable: Retryable exception raised: #<HashiCorp::VagrantVMwarefusion::Errors::VMNetDevicesWontStart: The VMware "vmnet" devices are failing to start. The most common
reason for this is collisions with existing network services. For
example, if a hostonly network space collides with another hostonly
network (such as with VirtualBox), it will fail to start. Likewise,
if forwarded ports collide with other listening ports, it will
fail to start.
Vagrant does its best to fix these issues, but in some cases it
cannot determine the root cause of these failures.
Please verify you have no other colliding network services running.
As a last resort, restarting your computer often fixes this issue.>
INFO vmware_driver: Killing vmnet-natd if it is alive...
INFO subprocess: Starting process: ["/usr/bin/pkill", "vmnet-natd"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--start"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Failed to start DHCP service on vmnet6
DEBUG subprocess: stderr: Failed to start some/all services
DEBUG subprocess: stdout: Enabled hostonly virtual adapter on vmnet1
Started DHCP service on vmnet1
Enabled hostonly virtual adapter on vmnet2
Started DHCP service on vmnet2
Enabled hostonly virtual adapter on vmnet3
Started DHCP service on vmnet3
Enabled hostonly virtual adapter on vmnet4
Started DHCP service on vmnet4
Enabled hostonly virtual adapter on vmnet5
Started DHCP service on vmnet5
Enabled hostonly virtual adapter on vmnet6
Started NAT service on vmnet8
Enabled hostonly virtual adapter on vmnet8
Started DHCP service on vmnet8
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 31999
DEBUG subprocess: Exit status: 1
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Some/All of the configured services are not running
DEBUG subprocess: stdout: DHCP service on vmnet1 is running
Hostonly virtual adapter on vmnet1 is enabled
DHCP service on vmnet2 is running
Hostonly virtual adapter on vmnet2 is enabled
DHCP service on vmnet3 is running
Hostonly virtual adapter on vmnet3 is enabled
DHCP service on vmnet4 is running
Hostonly virtual adapter on vmnet4 is enabled
DHCP service on vmnet5 is running
Hostonly virtual adapter on vmnet5 is enabled
DHCP service on vmnet6 is not running
Hostonly virtual adapter on vmnet6 is enabled
DHCP service on vmnet8 is running
NAT service on vmnet8 is running
Hostonly virtual adapter on vmnet8 is enabled
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO vmware_driver: Stopping services starter...
The VMware "vmnet" devices are failing to start. The most common
reason for this is collisions with existing network services. For
example, if a hostonly network space collides with another hostonly
network (such as with VirtualBox), it will fail to start. Likewise,
if forwarded ports collide with other listening ports, it will
fail to start.
Vagrant does its best to fix these issues, but in some cases it
cannot determine the root cause of these failures.
Please verify you have no other colliding network services running.
As a last resort, restarting your computer often fixes this issue.
INFO warden: Beginning recovery process...
INFO warden: Calling recover: #<Vagrant::Action::Builtin::Call:0x000001011ccda0>
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO environment: Released process lock: machine-action-5af8e8d0e46bf4726d0a29fe0f7ac441
INFO environment: Running hook: environment_unload
INFO runner: Preparing hooks for middleware sequence...
INFO runner: 2 hooks defined.
INFO runner: Running action: environment_unload #<Vagrant::Action::Builder:0x00000100a189d8>
INFO warden: Calling IN action: HashiCorp Background Check: End
INFO logger: Cleaning up background activation thread...
INFO warden: Calling OUT action: HashiCorp Background Check: End
ERROR vagrant: Vagrant experienced an error! Details:
ERROR vagrant: #<HashiCorp::VagrantVMwarefusion::Errors::HelperFailed: INFO global: Vagrant version: 1.7.4
INFO global: Ruby version: 2.0.0
INFO global: RubyGems version: 2.0.14
INFO global: VAGRANT_LOG="debug"
INFO global: VAGRANT_OLD_ENV_SPARK_HOME="/Users/quasiben/Research/GitClones/spark"
INFO global: VAGRANT_OLD_ENV_HOME="/Users/quasiben"
INFO global: VAGRANT_OLD_ENV__="/usr/local/bin/vagrant"
INFO global: VAGRANT_OLD_ENV_XPC_FLAGS="0x0"
INFO global: VAGRANT_INSTALLER_VERSION="2"
INFO global: VAGRANT_OLD_ENV_VAGRANT_LOG="debug"
INFO global: VAGRANT_OLD_ENV_TMPDIR="/var/folders/1t/t94brwgx7sjcn8jgz4gr3_c00000gq/T/"
INFO global: VAGRANT_OLD_ENV_Apple_PubSub_Socket_Render="/private/tmp/com.apple.launchd.KW13obTzd8/Render"
INFO global: VAGRANT_OLD_ENV_JAVA_HOME="/Library/Java/JavaVirtualMachines/jdk1.7.0_45.jdk/Contents/Home"
INFO global: VAGRANT_OLD_ENV_ACHE_HOME="/Users/quasiben/anaconda/envs/memex-explorer/lib/python2.7/site-packages/ache/"
INFO global: VAGRANT_OLD_ENV_CONDA_ENV_PATH="/Users/quasiben/anaconda/envs/clusto"
INFO global: VAGRANT_OLD_ENV_PYTHONPATH="/Users/quasiben/Research/ContinuumDev/GitRepo/conda-cluster/::/Users/quasiben/Research/GitClones/spark/python"
INFO global: VAGRANT_OLD_ENV_PATH="/Users/quasiben/anaconda/envs/clusto/bin:/usr/local/bin:/usr/local/heroku/bin:/Users/quasiben/google-cloud-sdk/bin:/usr/local/sbin:/Users/quasiben/.cabal/bin/:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/texbin:/Users/quasiben/Research/ContinuumDev/GitRepo/libdynd/build"
INFO global: VAGRANT_OLD_ENV_PWD="/Users/quasiben"
INFO global: VAGRANT_OLD_ENV_ITERM_PROFILE="Default"
INFO global: VAGRANT_OLD_ENV_JDK_HOME="/Library/Java/JavaVirtualMachines/jdk1.7.0_45.jdk/Contents/Home/"
INFO global: VAGRANT_OLD_ENV_COLORFGBG="7;0"
INFO global: VAGRANT_OLD_ENV_CONDA_DEFAULT_ENV="clusto"
INFO global: VAGRANT_INSTALLER_ENV="1"
INFO global: VAGRANT_EXECUTABLE="/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/bin/vagrant"
INFO global: VAGRANT_INSTALLER_EMBEDDED_DIR="/opt/vagrant/embedded"
INFO global: VAGRANT_OLD_ENV_COMMAND_MODE="unix2003"
INFO global: VAGRANT_OLD_ENV_SSH_AUTH_SOCK="/private/tmp/com.apple.launchd.CSjdOMPkpG/Listeners"
INFO global: VAGRANT_OLD_ENV_LANG="en_US.UTF-8"
INFO global: VAGRANT_OLD_ENV_TERM_PROGRAM="iTerm.app"
INFO global: VAGRANT_OLD_ENV_XPC_SERVICE_NAME="0"
INFO global: VAGRANT_OLD_ENV_SHLVL="1"
INFO global: VAGRANT_OLD_ENV_SECURITYSESSIONID="186a5"
INFO global: VAGRANT_OLD_ENV_TERM="xterm-color"
INFO global: VAGRANT_OLD_ENV_USER="quasiben"
INFO global: VAGRANT_OLD_ENV___CF_USER_TEXT_ENCODING="0x1F7:0x0:0x0"
INFO global: VAGRANT_OLD_ENV_ITERM_SESSION_ID="w0t1p0"
INFO global: VAGRANT_OLD_ENV_SHELL="/bin/bash"
INFO global: VAGRANT_OLD_ENV_PS1="(clusto)\\[\\033[01;32m\\]\\u@\\h\\[\\033[00m\\]:\\[\\033[01;36m\\]\\w\\[\\033[00m\\]\\$ "
INFO global: VAGRANT_OLD_ENV_OLDPWD="/Users/quasiben/Research/ContinuumDev/AC_AS_Vagrant/Head+Compute/test"
INFO global: VAGRANT_OLD_ENV_JRE_HOME="/Library/Java/JavaVirtualMachines/jdk1.7.0_45.jdk/Contents/Home/jre/"
INFO global: VAGRANT_OLD_ENV_LOGNAME="quasiben"
INFO global: VAGRANT_INTERNAL_BUNDLERIZED="1"
INFO global: Plugins:
INFO global: - bundler = 1.10.5
INFO global: - mime-types = 1.25.1
INFO global: - rest-client = 1.6.9
INFO global: - vagrant-share = 1.1.4
INFO global: - vagrant-vmware-fusion = 4.0.2
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/box/plugin.rb
INFO manager: Registered plugin: box command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/destroy/plugin.rb
INFO manager: Registered plugin: destroy command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/global-status/plugin.rb
INFO manager: Registered plugin: global-status command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/halt/plugin.rb
INFO manager: Registered plugin: halt command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/help/plugin.rb
INFO manager: Registered plugin: help command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/init/plugin.rb
INFO manager: Registered plugin: init command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/list-commands/plugin.rb
INFO manager: Registered plugin: list-commands command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/login/plugin.rb
INFO manager: Registered plugin: vagrant-login
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/package/plugin.rb
INFO manager: Registered plugin: package command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/plugin/plugin.rb
INFO manager: Registered plugin: plugin command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/provision/plugin.rb
INFO manager: Registered plugin: provision command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/push/plugin.rb
INFO manager: Registered plugin: push command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/rdp/plugin.rb
INFO manager: Registered plugin: rdp command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/reload/plugin.rb
INFO manager: Registered plugin: reload command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/resume/plugin.rb
INFO manager: Registered plugin: resume command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/ssh/plugin.rb
INFO manager: Registered plugin: ssh command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/ssh_config/plugin.rb
INFO manager: Registered plugin: ssh-config command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/status/plugin.rb
INFO manager: Registered plugin: status command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/suspend/plugin.rb
INFO manager: Registered plugin: suspend command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/up/plugin.rb
INFO manager: Registered plugin: up command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/version/plugin.rb
INFO manager: Registered plugin: version command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/communicators/ssh/plugin.rb
INFO manager: Registered plugin: ssh communicator
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/communicators/winrm/plugin.rb
INFO manager: Registered plugin: winrm communicator
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/arch/plugin.rb
INFO manager: Registered plugin: Arch guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/atomic/plugin.rb
INFO manager: Registered plugin: Atomic Host guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/coreos/plugin.rb
INFO manager: Registered plugin: CoreOS guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/darwin/plugin.rb
INFO manager: Registered plugin: Darwin guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/debian/plugin.rb
INFO manager: Registered plugin: Debian guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/debian8/plugin.rb
INFO manager: Registered plugin: Debian Jessie guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/esxi/plugin.rb
INFO manager: Registered plugin: ESXi guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/fedora/plugin.rb
INFO manager: Registered plugin: Fedora guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/freebsd/plugin.rb
INFO manager: Registered plugin: FreeBSD guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/funtoo/plugin.rb
INFO manager: Registered plugin: Funtoo guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/gentoo/plugin.rb
INFO manager: Registered plugin: Gentoo guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/linux/plugin.rb
INFO manager: Registered plugin: Linux guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/mint/plugin.rb
INFO manager: Registered plugin: Mint guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/netbsd/plugin.rb
INFO manager: Registered plugin: NetBSD guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/nixos/plugin.rb
INFO manager: Registered plugin: NixOS guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/omnios/plugin.rb
INFO manager: Registered plugin: OmniOS guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/openbsd/plugin.rb
INFO manager: Registered plugin: OpenBSD guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/photon/plugin.rb
INFO manager: Registered plugin: VMware Photon guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/pld/plugin.rb
INFO manager: Registered plugin: PLD Linux guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/redhat/plugin.rb
INFO manager: Registered plugin: Red Hat Enterprise Linux guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/smartos/plugin.rb
INFO manager: Registered plugin: SmartOS guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/solaris/plugin.rb
INFO manager: Registered plugin: Solaris guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/solaris11/plugin.rb
INFO manager: Registered plugin: Solaris 11 guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/suse/plugin.rb
INFO manager: Registered plugin: SUSE guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/tinycore/plugin.rb
INFO manager: Registered plugin: TinyCore Linux guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/ubuntu/plugin.rb
INFO manager: Registered plugin: Ubuntu guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/windows/plugin.rb
INFO manager: Registered plugin: Windows guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/arch/plugin.rb
INFO manager: Registered plugin: Arch host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/bsd/plugin.rb
INFO manager: Registered plugin: BSD host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/darwin/plugin.rb
INFO manager: Registered plugin: Mac OS X host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/freebsd/plugin.rb
INFO manager: Registered plugin: FreeBSD host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/gentoo/plugin.rb
INFO manager: Registered plugin: Gentoo host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/linux/plugin.rb
INFO manager: Registered plugin: Linux host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/null/plugin.rb
INFO manager: Registered plugin: null host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/redhat/plugin.rb
INFO manager: Registered plugin: Red Hat Enterprise Linux host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/slackware/plugin.rb
INFO manager: Registered plugin: Slackware host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/suse/plugin.rb
INFO manager: Registered plugin: SUSE host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/windows/plugin.rb
INFO manager: Registered plugin: Windows host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/kernel_v1/plugin.rb
INFO manager: Registered plugin: kernel
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/kernel_v2/plugin.rb
INFO manager: Registered plugin: kernel
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/providers/docker/plugin.rb
INFO manager: Registered plugin: docker-provider
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/providers/hyperv/plugin.rb
INFO manager: Registered plugin: Hyper-V provider
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/providers/virtualbox/plugin.rb
INFO manager: Registered plugin: VirtualBox provider
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/ansible/plugin.rb
INFO manager: Registered plugin: ansible
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/cfengine/plugin.rb
INFO manager: Registered plugin: CFEngine Provisioner
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/chef/plugin.rb
INFO manager: Registered plugin: chef
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/docker/plugin.rb
INFO manager: Registered plugin: docker
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/file/plugin.rb
INFO manager: Registered plugin: file
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/puppet/plugin.rb
INFO manager: Registered plugin: puppet
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/salt/plugin.rb
INFO manager: Registered plugin: salt
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/shell/plugin.rb
INFO manager: Registered plugin: shell
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/pushes/atlas/plugin.rb
INFO manager: Registered plugin: atlas
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/pushes/ftp/plugin.rb
INFO manager: Registered plugin: ftp
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/pushes/heroku/plugin.rb
INFO manager: Registered plugin: heroku
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/pushes/local-exec/plugin.rb
INFO manager: Registered plugin: local-exec
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/pushes/noop/plugin.rb
INFO manager: Registered plugin: noop
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/synced_folders/nfs/plugin.rb
INFO manager: Registered plugin: NFS synced folders
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/synced_folders/rsync/plugin.rb
INFO manager: Registered plugin: RSync synced folders
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/synced_folders/smb/plugin.rb
INFO manager: Registered plugin: SMB synced folders
INFO manager: Registered plugin: VMware Fusion Provider
INFO vmware_driver: VMX path is a directory. Finding VMX file...
INFO vmware_driver: VMX file: /Users/quasiben/.vagrant/machines/dev/vmware_fusion/7890b8d8-98e2-4cd5-a989-d65c4e0279ae/trusty64.vmx
INFO vmware_driver: Looking for VMware Fusion: /Applications/VMware Fusion.app
INFO vmware_driver: VMware Fusion path: #<Pathname:/Applications/VMware Fusion.app>
DEBUG vmware_driver: Attempting to read VMware version...
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmware-vmx", "-v"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command is setuid/setgid, clearing DYLD_LIBRARY_PATH
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr:
VMware Fusion Information:
VMware Fusion 7.1.0 build-2314774 Release
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO vmware_driver: Detected VMware version: 7.1.0
DEBUG vmware_driver: service starter path: /Applications/VMware Fusion.app/Contents/Library/services/Open VMware Fusion Services
DEBUG vmware_driver: vmnet-cli path: /Applications/VMware Fusion.app/Contents/Library/vmnet-cli
INFO vmware:sudo_helper: Calling command: create-vmnet-device
INFO networking_file: Reading adapters from networking file...
DEBUG networking_file: VNET: 1. KEY: 'DHCP' = 'yes'
DEBUG networking_file: VNET: 1. KEY: 'DHCP_CFG_HASH' = 'D80210FE873BE2813B8C769A8E72B64979061717'
DEBUG networking_file: VNET: 1. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG networking_file: VNET: 1. KEY: 'HOSTONLY_SUBNET' = '192.168.27.0'
DEBUG networking_file: VNET: 1. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG networking_file: VNET: 2. KEY: 'DHCP' = 'yes'
DEBUG networking_file: VNET: 2. KEY: 'DHCP_CFG_HASH' = '87768080D35EC28F8A98E2922D0D6FE5E5C18A59'
DEBUG networking_file: VNET: 2. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG networking_file: VNET: 2. KEY: 'HOSTONLY_SUBNET' = '10.10.10.0'
DEBUG networking_file: VNET: 2. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG networking_file: VNET: 3. KEY: 'DHCP' = 'yes'
DEBUG networking_file: VNET: 3. KEY: 'DHCP_CFG_HASH' = '3EC4C96155C7AA76726042C1D3C8D9C208404144'
DEBUG networking_file: VNET: 3. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG networking_file: VNET: 3. KEY: 'HOSTONLY_SUBNET' = '192.168.18.0'
DEBUG networking_file: VNET: 3. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG networking_file: VNET: 4. KEY: 'DHCP' = 'yes'
DEBUG networking_file: VNET: 4. KEY: 'DHCP_CFG_HASH' = '6F6696B0E161F81ED0E3CE9F08794F4DD8D794EB'
DEBUG networking_file: VNET: 4. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG networking_file: VNET: 4. KEY: 'HOSTONLY_SUBNET' = '172.16.48.0'
DEBUG networking_file: VNET: 4. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG networking_file: VNET: 5. KEY: 'DHCP' = 'yes'
DEBUG networking_file: VNET: 5. KEY: 'DHCP_CFG_HASH' = '9B81D6F11FF984546E1C4E2B438F14AC3B559373'
DEBUG networking_file: VNET: 5. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG networking_file: VNET: 5. KEY: 'HOSTONLY_SUBNET' = '192.168.111.0'
DEBUG networking_file: VNET: 5. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG networking_file: VNET: 8. KEY: 'DHCP' = 'yes'
DEBUG networking_file: VNET: 8. KEY: 'DHCP_CFG_HASH' = '1BDC60FCCCD2EEB9E6AA5D403BE51F90BF3ACC00'
DEBUG networking_file: VNET: 8. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG networking_file: VNET: 8. KEY: 'HOSTONLY_SUBNET' = '192.168.186.0'
DEBUG networking_file: VNET: 8. KEY: 'NAT' = 'yes'
DEBUG networking_file: VNET: 8. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG networking_file: Pruning adapters that aren't actually active...
INFO vmware_driver: Starting services starter and waiting for them to start...
INFO vmware_driver: Killing vmnet-natd if it is alive...
INFO subprocess: Starting process: ["/usr/bin/pkill", "vmnet-natd"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--start"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Failed to start DHCP service on vmnet6
DEBUG subprocess: stderr: Failed to start some/all services
DEBUG subprocess: stdout: Enabled hostonly virtual adapter on vmnet1
Started DHCP service on vmnet1
Enabled hostonly virtual adapter on vmnet2
Started DHCP service on vmnet2
Enabled hostonly virtual adapter on vmnet3
Started DHCP service on vmnet3
Enabled hostonly virtual adapter on vmnet4
Started DHCP service on vmnet4
Enabled hostonly virtual adapter on vmnet5
Started DHCP service on vmnet5
Enabled hostonly virtual adapter on vmnet6
Started NAT service on vmnet8
Enabled hostonly virtual adapter on vmnet8
Started DHCP service on vmnet8
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Some/All of the configured services are not running
DEBUG subprocess: stdout: DHCP service on vmnet1 is running
Hostonly virtual adapter on vmnet1 is enabled
DHCP service on vmnet2 is running
Hostonly virtual adapter on vmnet2 is enabled
DHCP service on vmnet3 is running
Hostonly virtual adapter on vmnet3 is enabled
DHCP service on vmnet4 is running
Hostonly virtual adapter on vmnet4 is enabled
DHCP service on vmnet5 is running
Hostonly virtual adapter on vmnet5 is enabled
DHCP service on vmnet6 is not running
Hostonly virtual adapter on vmnet6 is enabled
DHCP service on vmnet8 is running
NAT service on vmnet8 is running
Hostonly virtual adapter on vmnet8 is enabled
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO retryable: Retryable exception raised: #<HashiCorp::VagrantVMwarefusion::Errors::VMNetDevicesWontStart: The VMware "vmnet" devices are failing to start. The most common
reason for this is collisions with existing network services. For
example, if a hostonly network space collides with another hostonly
network (such as with VirtualBox), it will fail to start. Likewise,
if forwarded ports collide with other listening ports, it will
fail to start.
Vagrant does its best to fix these issues, but in some cases it
cannot determine the root cause of these failures.
Please verify you have no other colliding network services running.
As a last resort, restarting your computer often fixes this issue.>
INFO vmware_driver: Killing vmnet-natd if it is alive...
INFO subprocess: Starting process: ["/usr/bin/pkill", "vmnet-natd"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--start"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Failed to start DHCP service on vmnet6
DEBUG subprocess: stderr: Failed to start some/all services
DEBUG subprocess: stdout: Enabled hostonly virtual adapter on vmnet1
Started DHCP service on vmnet1
Enabled hostonly virtual adapter on vmnet2
Started DHCP service on vmnet2
Enabled hostonly virtual adapter on vmnet3
Started DHCP service on vmnet3
Enabled hostonly virtual adapter on vmnet4
Started DHCP service on vmnet4
Enabled hostonly virtual adapter on vmnet5
Started DHCP service on vmnet5
Enabled hostonly virtual adapter on vmnet6
Started NAT service on vmnet8
Enabled hostonly virtual adapter on vmnet8
Started DHCP service on vmnet8
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Some/All of the configured services are not running
DEBUG subprocess: stdout: DHCP service on vmnet1 is running
Hostonly virtual adapter on vmnet1 is enabled
DHCP service on vmnet2 is running
Hostonly virtual adapter on vmnet2 is enabled
DHCP service on vmnet3 is running
Hostonly virtual adapter on vmnet3 is enabled
DHCP service on vmnet4 is running
Hostonly virtual adapter on vmnet4 is enabled
DHCP service on vmnet5 is running
Hostonly virtual adapter on vmnet5 is enabled
DHCP service on vmnet6 is not running
Hostonly virtual adapter on vmnet6 is enabled
DHCP service on vmnet8 is running
NAT service on vmnet8 is running
Hostonly virtual adapter on vmnet8 is enabled
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO retryable: Retryable exception raised: #<HashiCorp::VagrantVMwarefusion::Errors::VMNetDevicesWontStart: The VMware "vmnet" devices are failing to start. The most common
reason for this is collisions with existing network services. For
example, if a hostonly network space collides with another hostonly
network (such as with VirtualBox), it will fail to start. Likewise,
if forwarded ports collide with other listening ports, it will
fail to start.
Vagrant does its best to fix these issues, but in some cases it
cannot determine the root cause of these failures.
Please verify you have no other colliding network services running.
As a last resort, restarting your computer often fixes this issue.>
INFO vmware_driver: Killing vmnet-natd if it is alive...
INFO subprocess: Starting process: ["/usr/bin/pkill", "vmnet-natd"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--start"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Failed to start DHCP service on vmnet6
DEBUG subprocess: stderr: Failed to start some/all services
DEBUG subprocess: stdout: Enabled hostonly virtual adapter on vmnet1
Started DHCP service on vmnet1
Enabled hostonly virtual adapter on vmnet2
Started DHCP service on vmnet2
Enabled hostonly virtual adapter on vmnet3
Started DHCP service on vmnet3
Enabled hostonly virtual adapter on vmnet4
Started DHCP service on vmnet4
Enabled hostonly virtual adapter on vmnet5
Started DHCP service on vmnet5
Enabled hostonly virtual adapter on vmnet6
Started NAT service on vmnet8
Enabled hostonly virtual adapter on vmnet8
Started DHCP service on vmnet8
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 31999
DEBUG subprocess: Exit status: 1
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Some/All of the configured services are not running
DEBUG subprocess: stdout: DHCP service on vmnet1 is running
Hostonly virtual adapter on vmnet1 is enabled
DHCP service on vmnet2 is running
Hostonly virtual adapter on vmnet2 is enabled
DHCP service on vmnet3 is running
Hostonly virtual adapter on vmnet3 is enabled
DHCP service on vmnet4 is running
Hostonly virtual adapter on vmnet4 is enabled
DHCP service on vmnet5 is running
Hostonly virtual adapter on vmnet5 is enabled
DHCP service on vmnet6 is not running
Hostonly virtual adapter on vmnet6 is enabled
DHCP service on vmnet8 is running
NAT service on vmnet8 is running
Hostonly virtual adapter on vmnet8 is enabled
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO retryable: Retryable exception raised: #<HashiCorp::VagrantVMwarefusion::Errors::VMNetDevicesWontStart: The VMware "vmnet" devices are failing to start. The most common
reason for this is collisions with existing network services. For
example, if a hostonly network space collides with another hostonly
network (such as with VirtualBox), it will fail to start. Likewise,
if forwarded ports collide with other listening ports, it will
fail to start.
Vagrant does its best to fix these issues, but in some cases it
cannot determine the root cause of these failures.
Please verify you have no other colliding network services running.
As a last resort, restarting your computer often fixes this issue.>
INFO vmware_driver: Killing vmnet-natd if it is alive...
INFO subprocess: Starting process: ["/usr/bin/pkill", "vmnet-natd"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--start"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Failed to start DHCP service on vmnet6
DEBUG subprocess: stderr: Failed to start some/all services
DEBUG subprocess: stdout: Enabled hostonly virtual adapter on vmnet1
Started DHCP service on vmnet1
Enabled hostonly virtual adapter on vmnet2
Started DHCP service on vmnet2
Enabled hostonly virtual adapter on vmnet3
Started DHCP service on vmnet3
Enabled hostonly virtual adapter on vmnet4
Started DHCP service on vmnet4
Enabled hostonly virtual adapter on vmnet5
Started DHCP service on vmnet5
Enabled hostonly virtual adapter on vmnet6
Started NAT service on vmnet8
Enabled hostonly virtual adapter on vmnet8
Started DHCP service on vmnet8
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Some/All of the configured services are not running
DEBUG subprocess: stdout: DHCP service on vmnet1 is running
Hostonly virtual adapter on vmnet1 is enabled
DHCP service on vmnet2 is running
Hostonly virtual adapter on vmnet2 is enabled
DHCP service on vmnet3 is running
Hostonly virtual adapter on vmnet3 is enabled
DHCP service on vmnet4 is running
Hostonly virtual adapter on vmnet4 is enabled
DHCP service on vmnet5 is running
Hostonly virtual adapter on vmnet5 is enabled
DHCP service on vmnet6 is not running
Hostonly virtual adapter on vmnet6 is enabled
DHCP service on vmnet8 is running
NAT service on vmnet8 is running
Hostonly virtual adapter on vmnet8 is enabled
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO retryable: Retryable exception raised: #<HashiCorp::VagrantVMwarefusion::Errors::VMNetDevicesWontStart: The VMware "vmnet" devices are failing to start. The most common
reason for this is collisions with existing network services. For
example, if a hostonly network space collides with another hostonly
network (such as with VirtualBox), it will fail to start. Likewise,
if forwarded ports collide with other listening ports, it will
fail to start.
Vagrant does its best to fix these issues, but in some cases it
cannot determine the root cause of these failures.
Please verify you have no other colliding network services running.
As a last resort, restarting your computer often fixes this issue.>
INFO vmware_driver: Killing vmnet-natd if it is alive...
INFO subprocess: Starting process: ["/usr/bin/pkill", "vmnet-natd"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--start"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Failed to start DHCP service on vmnet6
DEBUG subprocess: stderr: Failed to start some/all services
DEBUG subprocess: stdout: Enabled hostonly virtual adapter on vmnet1
Started DHCP service on vmnet1
Enabled hostonly virtual adapter on vmnet2
Started DHCP service on vmnet2
Enabled hostonly virtual adapter on vmnet3
Started DHCP service on vmnet3
Enabled hostonly virtual adapter on vmnet4
Started DHCP service on vmnet4
Enabled hostonly virtual adapter on vmnet5
Started DHCP service on vmnet5
Enabled hostonly virtual adapter on vmnet6
Started NAT service on vmnet8
Enabled hostonly virtual adapter on vmnet8
Started DHCP service on vmnet8
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 31999
DEBUG subprocess: Exit status: 1
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Some/All of the configured services are not running
DEBUG subprocess: stdout: DHCP service on vmnet1 is running
Hostonly virtual adapter on vmnet1 is enabled
DHCP service on vmnet2 is running
Hostonly virtual adapter on vmnet2 is enabled
DHCP service on vmnet3 is running
Hostonly virtual adapter on vmnet3 is enabled
DHCP service on vmnet4 is running
Hostonly virtual adapter on vmnet4 is enabled
DHCP service on vmnet5 is running
Hostonly virtual adapter on vmnet5 is enabled
DHCP service on vmnet6 is not running
Hostonly virtual adapter on vmnet6 is enabled
DHCP service on vmnet8 is running
NAT service on vmnet8 is running
Hostonly virtual adapter on vmnet8 is enabled
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO vmware_driver: Stopping services starter...
The VMware "vmnet" devices are failing to start. The most common
reason for this is collisions with existing network services. For
example, if a hostonly network space collides with another hostonly
network (such as with VirtualBox), it will fail to start. Likewise,
if forwarded ports collide with other listening ports, it will
fail to start.
Vagrant does its best to fix these issues, but in some cases it
cannot determine the root cause of these failures.
Please verify you have no other colliding network services running.
As a last resort, restarting your computer often fixes this issue.>
ERROR vagrant: INFO global: Vagrant version: 1.7.4
INFO global: Ruby version: 2.0.0
INFO global: RubyGems version: 2.0.14
INFO global: VAGRANT_LOG="debug"
INFO global: VAGRANT_OLD_ENV_SPARK_HOME="/Users/quasiben/Research/GitClones/spark"
INFO global: VAGRANT_OLD_ENV_HOME="/Users/quasiben"
INFO global: VAGRANT_OLD_ENV__="/usr/local/bin/vagrant"
INFO global: VAGRANT_OLD_ENV_XPC_FLAGS="0x0"
INFO global: VAGRANT_INSTALLER_VERSION="2"
INFO global: VAGRANT_OLD_ENV_VAGRANT_LOG="debug"
INFO global: VAGRANT_OLD_ENV_TMPDIR="/var/folders/1t/t94brwgx7sjcn8jgz4gr3_c00000gq/T/"
INFO global: VAGRANT_OLD_ENV_Apple_PubSub_Socket_Render="/private/tmp/com.apple.launchd.KW13obTzd8/Render"
INFO global: VAGRANT_OLD_ENV_JAVA_HOME="/Library/Java/JavaVirtualMachines/jdk1.7.0_45.jdk/Contents/Home"
INFO global: VAGRANT_OLD_ENV_ACHE_HOME="/Users/quasiben/anaconda/envs/memex-explorer/lib/python2.7/site-packages/ache/"
INFO global: VAGRANT_OLD_ENV_CONDA_ENV_PATH="/Users/quasiben/anaconda/envs/clusto"
INFO global: VAGRANT_OLD_ENV_PYTHONPATH="/Users/quasiben/Research/ContinuumDev/GitRepo/conda-cluster/::/Users/quasiben/Research/GitClones/spark/python"
INFO global: VAGRANT_OLD_ENV_PATH="/Users/quasiben/anaconda/envs/clusto/bin:/usr/local/bin:/usr/local/heroku/bin:/Users/quasiben/google-cloud-sdk/bin:/usr/local/sbin:/Users/quasiben/.cabal/bin/:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/texbin:/Users/quasiben/Research/ContinuumDev/GitRepo/libdynd/build"
INFO global: VAGRANT_OLD_ENV_PWD="/Users/quasiben"
INFO global: VAGRANT_OLD_ENV_ITERM_PROFILE="Default"
INFO global: VAGRANT_OLD_ENV_JDK_HOME="/Library/Java/JavaVirtualMachines/jdk1.7.0_45.jdk/Contents/Home/"
INFO global: VAGRANT_OLD_ENV_COLORFGBG="7;0"
INFO global: VAGRANT_OLD_ENV_CONDA_DEFAULT_ENV="clusto"
INFO global: VAGRANT_INSTALLER_ENV="1"
INFO global: VAGRANT_EXECUTABLE="/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/bin/vagrant"
INFO global: VAGRANT_INSTALLER_EMBEDDED_DIR="/opt/vagrant/embedded"
INFO global: VAGRANT_OLD_ENV_COMMAND_MODE="unix2003"
INFO global: VAGRANT_OLD_ENV_SSH_AUTH_SOCK="/private/tmp/com.apple.launchd.CSjdOMPkpG/Listeners"
INFO global: VAGRANT_OLD_ENV_LANG="en_US.UTF-8"
INFO global: VAGRANT_OLD_ENV_TERM_PROGRAM="iTerm.app"
INFO global: VAGRANT_OLD_ENV_XPC_SERVICE_NAME="0"
INFO global: VAGRANT_OLD_ENV_SHLVL="1"
INFO global: VAGRANT_OLD_ENV_SECURITYSESSIONID="186a5"
INFO global: VAGRANT_OLD_ENV_TERM="xterm-color"
INFO global: VAGRANT_OLD_ENV_USER="quasiben"
INFO global: VAGRANT_OLD_ENV___CF_USER_TEXT_ENCODING="0x1F7:0x0:0x0"
INFO global: VAGRANT_OLD_ENV_ITERM_SESSION_ID="w0t1p0"
INFO global: VAGRANT_OLD_ENV_SHELL="/bin/bash"
INFO global: VAGRANT_OLD_ENV_PS1="(clusto)\\[\\033[01;32m\\]\\u@\\h\\[\\033[00m\\]:\\[\\033[01;36m\\]\\w\\[\\033[00m\\]\\$ "
INFO global: VAGRANT_OLD_ENV_OLDPWD="/Users/quasiben/Research/ContinuumDev/AC_AS_Vagrant/Head+Compute/test"
INFO global: VAGRANT_OLD_ENV_JRE_HOME="/Library/Java/JavaVirtualMachines/jdk1.7.0_45.jdk/Contents/Home/jre/"
INFO global: VAGRANT_OLD_ENV_LOGNAME="quasiben"
INFO global: VAGRANT_INTERNAL_BUNDLERIZED="1"
INFO global: Plugins:
INFO global: - bundler = 1.10.5
INFO global: - mime-types = 1.25.1
INFO global: - rest-client = 1.6.9
INFO global: - vagrant-share = 1.1.4
INFO global: - vagrant-vmware-fusion = 4.0.2
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/box/plugin.rb
INFO manager: Registered plugin: box command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/destroy/plugin.rb
INFO manager: Registered plugin: destroy command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/global-status/plugin.rb
INFO manager: Registered plugin: global-status command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/halt/plugin.rb
INFO manager: Registered plugin: halt command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/help/plugin.rb
INFO manager: Registered plugin: help command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/init/plugin.rb
INFO manager: Registered plugin: init command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/list-commands/plugin.rb
INFO manager: Registered plugin: list-commands command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/login/plugin.rb
INFO manager: Registered plugin: vagrant-login
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/package/plugin.rb
INFO manager: Registered plugin: package command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/plugin/plugin.rb
INFO manager: Registered plugin: plugin command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/provision/plugin.rb
INFO manager: Registered plugin: provision command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/push/plugin.rb
INFO manager: Registered plugin: push command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/rdp/plugin.rb
INFO manager: Registered plugin: rdp command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/reload/plugin.rb
INFO manager: Registered plugin: reload command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/resume/plugin.rb
INFO manager: Registered plugin: resume command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/ssh/plugin.rb
INFO manager: Registered plugin: ssh command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/ssh_config/plugin.rb
INFO manager: Registered plugin: ssh-config command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/status/plugin.rb
INFO manager: Registered plugin: status command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/suspend/plugin.rb
INFO manager: Registered plugin: suspend command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/up/plugin.rb
INFO manager: Registered plugin: up command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/version/plugin.rb
INFO manager: Registered plugin: version command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/communicators/ssh/plugin.rb
INFO manager: Registered plugin: ssh communicator
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/communicators/winrm/plugin.rb
INFO manager: Registered plugin: winrm communicator
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/arch/plugin.rb
INFO manager: Registered plugin: Arch guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/atomic/plugin.rb
INFO manager: Registered plugin: Atomic Host guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/coreos/plugin.rb
INFO manager: Registered plugin: CoreOS guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/darwin/plugin.rb
INFO manager: Registered plugin: Darwin guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/debian/plugin.rb
INFO manager: Registered plugin: Debian guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/debian8/plugin.rb
INFO manager: Registered plugin: Debian Jessie guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/esxi/plugin.rb
INFO manager: Registered plugin: ESXi guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/fedora/plugin.rb
INFO manager: Registered plugin: Fedora guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/freebsd/plugin.rb
INFO manager: Registered plugin: FreeBSD guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/funtoo/plugin.rb
INFO manager: Registered plugin: Funtoo guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/gentoo/plugin.rb
INFO manager: Registered plugin: Gentoo guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/linux/plugin.rb
INFO manager: Registered plugin: Linux guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/mint/plugin.rb
INFO manager: Registered plugin: Mint guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/netbsd/plugin.rb
INFO manager: Registered plugin: NetBSD guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/nixos/plugin.rb
INFO manager: Registered plugin: NixOS guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/omnios/plugin.rb
INFO manager: Registered plugin: OmniOS guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/openbsd/plugin.rb
INFO manager: Registered plugin: OpenBSD guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/photon/plugin.rb
INFO manager: Registered plugin: VMware Photon guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/pld/plugin.rb
INFO manager: Registered plugin: PLD Linux guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/redhat/plugin.rb
INFO manager: Registered plugin: Red Hat Enterprise Linux guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/smartos/plugin.rb
INFO manager: Registered plugin: SmartOS guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/solaris/plugin.rb
INFO manager: Registered plugin: Solaris guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/solaris11/plugin.rb
INFO manager: Registered plugin: Solaris 11 guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/suse/plugin.rb
INFO manager: Registered plugin: SUSE guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/tinycore/plugin.rb
INFO manager: Registered plugin: TinyCore Linux guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/ubuntu/plugin.rb
INFO manager: Registered plugin: Ubuntu guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/windows/plugin.rb
INFO manager: Registered plugin: Windows guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/arch/plugin.rb
INFO manager: Registered plugin: Arch host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/bsd/plugin.rb
INFO manager: Registered plugin: BSD host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/darwin/plugin.rb
INFO manager: Registered plugin: Mac OS X host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/freebsd/plugin.rb
INFO manager: Registered plugin: FreeBSD host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/gentoo/plugin.rb
INFO manager: Registered plugin: Gentoo host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/linux/plugin.rb
INFO manager: Registered plugin: Linux host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/null/plugin.rb
INFO manager: Registered plugin: null host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/redhat/plugin.rb
INFO manager: Registered plugin: Red Hat Enterprise Linux host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/slackware/plugin.rb
INFO manager: Registered plugin: Slackware host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/suse/plugin.rb
INFO manager: Registered plugin: SUSE host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/windows/plugin.rb
INFO manager: Registered plugin: Windows host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/kernel_v1/plugin.rb
INFO manager: Registered plugin: kernel
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/kernel_v2/plugin.rb
INFO manager: Registered plugin: kernel
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/providers/docker/plugin.rb
INFO manager: Registered plugin: docker-provider
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/providers/hyperv/plugin.rb
INFO manager: Registered plugin: Hyper-V provider
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/providers/virtualbox/plugin.rb
INFO manager: Registered plugin: VirtualBox provider
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/ansible/plugin.rb
INFO manager: Registered plugin: ansible
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/cfengine/plugin.rb
INFO manager: Registered plugin: CFEngine Provisioner
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/chef/plugin.rb
INFO manager: Registered plugin: chef
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/docker/plugin.rb
INFO manager: Registered plugin: docker
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/file/plugin.rb
INFO manager: Registered plugin: file
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/puppet/plugin.rb
INFO manager: Registered plugin: puppet
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/salt/plugin.rb
INFO manager: Registered plugin: salt
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/shell/plugin.rb
INFO manager: Registered plugin: shell
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/pushes/atlas/plugin.rb
INFO manager: Registered plugin: atlas
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/pushes/ftp/plugin.rb
INFO manager: Registered plugin: ftp
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/pushes/heroku/plugin.rb
INFO manager: Registered plugin: heroku
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/pushes/local-exec/plugin.rb
INFO manager: Registered plugin: local-exec
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/pushes/noop/plugin.rb
INFO manager: Registered plugin: noop
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/synced_folders/nfs/plugin.rb
INFO manager: Registered plugin: NFS synced folders
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/synced_folders/rsync/plugin.rb
INFO manager: Registered plugin: RSync synced folders
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/synced_folders/smb/plugin.rb
INFO manager: Registered plugin: SMB synced folders
INFO manager: Registered plugin: VMware Fusion Provider
INFO vmware_driver: VMX path is a directory. Finding VMX file...
INFO vmware_driver: VMX file: /Users/quasiben/.vagrant/machines/dev/vmware_fusion/7890b8d8-98e2-4cd5-a989-d65c4e0279ae/trusty64.vmx
INFO vmware_driver: Looking for VMware Fusion: /Applications/VMware Fusion.app
INFO vmware_driver: VMware Fusion path: #<Pathname:/Applications/VMware Fusion.app>
DEBUG vmware_driver: Attempting to read VMware version...
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmware-vmx", "-v"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command is setuid/setgid, clearing DYLD_LIBRARY_PATH
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr:
VMware Fusion Information:
VMware Fusion 7.1.0 build-2314774 Release
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO vmware_driver: Detected VMware version: 7.1.0
DEBUG vmware_driver: service starter path: /Applications/VMware Fusion.app/Contents/Library/services/Open VMware Fusion Services
DEBUG vmware_driver: vmnet-cli path: /Applications/VMware Fusion.app/Contents/Library/vmnet-cli
INFO vmware:sudo_helper: Calling command: create-vmnet-device
INFO networking_file: Reading adapters from networking file...
DEBUG networking_file: VNET: 1. KEY: 'DHCP' = 'yes'
DEBUG networking_file: VNET: 1. KEY: 'DHCP_CFG_HASH' = 'D80210FE873BE2813B8C769A8E72B64979061717'
DEBUG networking_file: VNET: 1. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG networking_file: VNET: 1. KEY: 'HOSTONLY_SUBNET' = '192.168.27.0'
DEBUG networking_file: VNET: 1. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG networking_file: VNET: 2. KEY: 'DHCP' = 'yes'
DEBUG networking_file: VNET: 2. KEY: 'DHCP_CFG_HASH' = '87768080D35EC28F8A98E2922D0D6FE5E5C18A59'
DEBUG networking_file: VNET: 2. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG networking_file: VNET: 2. KEY: 'HOSTONLY_SUBNET' = '10.10.10.0'
DEBUG networking_file: VNET: 2. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG networking_file: VNET: 3. KEY: 'DHCP' = 'yes'
DEBUG networking_file: VNET: 3. KEY: 'DHCP_CFG_HASH' = '3EC4C96155C7AA76726042C1D3C8D9C208404144'
DEBUG networking_file: VNET: 3. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG networking_file: VNET: 3. KEY: 'HOSTONLY_SUBNET' = '192.168.18.0'
DEBUG networking_file: VNET: 3. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG networking_file: VNET: 4. KEY: 'DHCP' = 'yes'
DEBUG networking_file: VNET: 4. KEY: 'DHCP_CFG_HASH' = '6F6696B0E161F81ED0E3CE9F08794F4DD8D794EB'
DEBUG networking_file: VNET: 4. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG networking_file: VNET: 4. KEY: 'HOSTONLY_SUBNET' = '172.16.48.0'
DEBUG networking_file: VNET: 4. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG networking_file: VNET: 5. KEY: 'DHCP' = 'yes'
DEBUG networking_file: VNET: 5. KEY: 'DHCP_CFG_HASH' = '9B81D6F11FF984546E1C4E2B438F14AC3B559373'
DEBUG networking_file: VNET: 5. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG networking_file: VNET: 5. KEY: 'HOSTONLY_SUBNET' = '192.168.111.0'
DEBUG networking_file: VNET: 5. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG networking_file: VNET: 8. KEY: 'DHCP' = 'yes'
DEBUG networking_file: VNET: 8. KEY: 'DHCP_CFG_HASH' = '1BDC60FCCCD2EEB9E6AA5D403BE51F90BF3ACC00'
DEBUG networking_file: VNET: 8. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG networking_file: VNET: 8. KEY: 'HOSTONLY_SUBNET' = '192.168.186.0'
DEBUG networking_file: VNET: 8. KEY: 'NAT' = 'yes'
DEBUG networking_file: VNET: 8. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG networking_file: Pruning adapters that aren't actually active...
INFO vmware_driver: Starting services starter and waiting for them to start...
INFO vmware_driver: Killing vmnet-natd if it is alive...
INFO subprocess: Starting process: ["/usr/bin/pkill", "vmnet-natd"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--start"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Failed to start DHCP service on vmnet6
DEBUG subprocess: stderr: Failed to start some/all services
DEBUG subprocess: stdout: Enabled hostonly virtual adapter on vmnet1
Started DHCP service on vmnet1
Enabled hostonly virtual adapter on vmnet2
Started DHCP service on vmnet2
Enabled hostonly virtual adapter on vmnet3
Started DHCP service on vmnet3
Enabled hostonly virtual adapter on vmnet4
Started DHCP service on vmnet4
Enabled hostonly virtual adapter on vmnet5
Started DHCP service on vmnet5
Enabled hostonly virtual adapter on vmnet6
Started NAT service on vmnet8
Enabled hostonly virtual adapter on vmnet8
Started DHCP service on vmnet8
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Some/All of the configured services are not running
DEBUG subprocess: stdout: DHCP service on vmnet1 is running
Hostonly virtual adapter on vmnet1 is enabled
DHCP service on vmnet2 is running
Hostonly virtual adapter on vmnet2 is enabled
DHCP service on vmnet3 is running
Hostonly virtual adapter on vmnet3 is enabled
DHCP service on vmnet4 is running
Hostonly virtual adapter on vmnet4 is enabled
DHCP service on vmnet5 is running
Hostonly virtual adapter on vmnet5 is enabled
DHCP service on vmnet6 is not running
Hostonly virtual adapter on vmnet6 is enabled
DHCP service on vmnet8 is running
NAT service on vmnet8 is running
Hostonly virtual adapter on vmnet8 is enabled
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO retryable: Retryable exception raised: #<HashiCorp::VagrantVMwarefusion::Errors::VMNetDevicesWontStart: The VMware "vmnet" devices are failing to start. The most common
reason for this is collisions with existing network services. For
example, if a hostonly network space collides with another hostonly
network (such as with VirtualBox), it will fail to start. Likewise,
if forwarded ports collide with other listening ports, it will
fail to start.
Vagrant does its best to fix these issues, but in some cases it
cannot determine the root cause of these failures.
Please verify you have no other colliding network services running.
As a last resort, restarting your computer often fixes this issue.>
INFO vmware_driver: Killing vmnet-natd if it is alive...
INFO subprocess: Starting process: ["/usr/bin/pkill", "vmnet-natd"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--start"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Failed to start DHCP service on vmnet6
DEBUG subprocess: stderr: Failed to start some/all services
DEBUG subprocess: stdout: Enabled hostonly virtual adapter on vmnet1
Started DHCP service on vmnet1
Enabled hostonly virtual adapter on vmnet2
Started DHCP service on vmnet2
Enabled hostonly virtual adapter on vmnet3
Started DHCP service on vmnet3
Enabled hostonly virtual adapter on vmnet4
Started DHCP service on vmnet4
Enabled hostonly virtual adapter on vmnet5
Started DHCP service on vmnet5
Enabled hostonly virtual adapter on vmnet6
Started NAT service on vmnet8
Enabled hostonly virtual adapter on vmnet8
Started DHCP service on vmnet8
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Some/All of the configured services are not running
DEBUG subprocess: stdout: DHCP service on vmnet1 is running
Hostonly virtual adapter on vmnet1 is enabled
DHCP service on vmnet2 is running
Hostonly virtual adapter on vmnet2 is enabled
DHCP service on vmnet3 is running
Hostonly virtual adapter on vmnet3 is enabled
DHCP service on vmnet4 is running
Hostonly virtual adapter on vmnet4 is enabled
DHCP service on vmnet5 is running
Hostonly virtual adapter on vmnet5 is enabled
DHCP service on vmnet6 is not running
Hostonly virtual adapter on vmnet6 is enabled
DHCP service on vmnet8 is running
NAT service on vmnet8 is running
Hostonly virtual adapter on vmnet8 is enabled
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO retryable: Retryable exception raised: #<HashiCorp::VagrantVMwarefusion::Errors::VMNetDevicesWontStart: The VMware "vmnet" devices are failing to start. The most common
reason for this is collisions with existing network services. For
example, if a hostonly network space collides with another hostonly
network (such as with VirtualBox), it will fail to start. Likewise,
if forwarded ports collide with other listening ports, it will
fail to start.
Vagrant does its best to fix these issues, but in some cases it
cannot determine the root cause of these failures.
Please verify you have no other colliding network services running.
As a last resort, restarting your computer often fixes this issue.>
INFO vmware_driver: Killing vmnet-natd if it is alive...
INFO subprocess: Starting process: ["/usr/bin/pkill", "vmnet-natd"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--start"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Failed to start DHCP service on vmnet6
DEBUG subprocess: stderr: Failed to start some/all services
DEBUG subprocess: stdout: Enabled hostonly virtual adapter on vmnet1
Started DHCP service on vmnet1
Enabled hostonly virtual adapter on vmnet2
Started DHCP service on vmnet2
Enabled hostonly virtual adapter on vmnet3
Started DHCP service on vmnet3
Enabled hostonly virtual adapter on vmnet4
Started DHCP service on vmnet4
Enabled hostonly virtual adapter on vmnet5
Started DHCP service on vmnet5
Enabled hostonly virtual adapter on vmnet6
Started NAT service on vmnet8
Enabled hostonly virtual adapter on vmnet8
Started DHCP service on vmnet8
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 31999
DEBUG subprocess: Exit status: 1
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Some/All of the configured services are not running
DEBUG subprocess: stdout: DHCP service on vmnet1 is running
Hostonly virtual adapter on vmnet1 is enabled
DHCP service on vmnet2 is running
Hostonly virtual adapter on vmnet2 is enabled
DHCP service on vmnet3 is running
Hostonly virtual adapter on vmnet3 is enabled
DHCP service on vmnet4 is running
Hostonly virtual adapter on vmnet4 is enabled
DHCP service on vmnet5 is running
Hostonly virtual adapter on vmnet5 is enabled
DHCP service on vmnet6 is not running
Hostonly virtual adapter on vmnet6 is enabled
DHCP service on vmnet8 is running
NAT service on vmnet8 is running
Hostonly virtual adapter on vmnet8 is enabled
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO retryable: Retryable exception raised: #<HashiCorp::VagrantVMwarefusion::Errors::VMNetDevicesWontStart: The VMware "vmnet" devices are failing to start. The most common
reason for this is collisions with existing network services. For
example, if a hostonly network space collides with another hostonly
network (such as with VirtualBox), it will fail to start. Likewise,
if forwarded ports collide with other listening ports, it will
fail to start.
Vagrant does its best to fix these issues, but in some cases it
cannot determine the root cause of these failures.
Please verify you have no other colliding network services running.
As a last resort, restarting your computer often fixes this issue.>
INFO vmware_driver: Killing vmnet-natd if it is alive...
INFO subprocess: Starting process: ["/usr/bin/pkill", "vmnet-natd"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--start"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Failed to start DHCP service on vmnet6
DEBUG subprocess: stderr: Failed to start some/all services
DEBUG subprocess: stdout: Enabled hostonly virtual adapter on vmnet1
Started DHCP service on vmnet1
Enabled hostonly virtual adapter on vmnet2
Started DHCP service on vmnet2
Enabled hostonly virtual adapter on vmnet3
Started DHCP service on vmnet3
Enabled hostonly virtual adapter on vmnet4
Started DHCP service on vmnet4
Enabled hostonly virtual adapter on vmnet5
Started DHCP service on vmnet5
Enabled hostonly virtual adapter on vmnet6
Started NAT service on vmnet8
Enabled hostonly virtual adapter on vmnet8
Started DHCP service on vmnet8
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Some/All of the configured services are not running
DEBUG subprocess: stdout: DHCP service on vmnet1 is running
Hostonly virtual adapter on vmnet1 is enabled
DHCP service on vmnet2 is running
Hostonly virtual adapter on vmnet2 is enabled
DHCP service on vmnet3 is running
Hostonly virtual adapter on vmnet3 is enabled
DHCP service on vmnet4 is running
Hostonly virtual adapter on vmnet4 is enabled
DHCP service on vmnet5 is running
Hostonly virtual adapter on vmnet5 is enabled
DHCP service on vmnet6 is not running
Hostonly virtual adapter on vmnet6 is enabled
DHCP service on vmnet8 is running
NAT service on vmnet8 is running
Hostonly virtual adapter on vmnet8 is enabled
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO retryable: Retryable exception raised: #<HashiCorp::VagrantVMwarefusion::Errors::VMNetDevicesWontStart: The VMware "vmnet" devices are failing to start. The most common
reason for this is collisions with existing network services. For
example, if a hostonly network space collides with another hostonly
network (such as with VirtualBox), it will fail to start. Likewise,
if forwarded ports collide with other listening ports, it will
fail to start.
Vagrant does its best to fix these issues, but in some cases it
cannot determine the root cause of these failures.
Please verify you have no other colliding network services running.
As a last resort, restarting your computer often fixes this issue.>
INFO vmware_driver: Killing vmnet-natd if it is alive...
INFO subprocess: Starting process: ["/usr/bin/pkill", "vmnet-natd"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--start"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Failed to start DHCP service on vmnet6
DEBUG subprocess: stderr: Failed to start some/all services
DEBUG subprocess: stdout: Enabled hostonly virtual adapter on vmnet1
Started DHCP service on vmnet1
Enabled hostonly virtual adapter on vmnet2
Started DHCP service on vmnet2
Enabled hostonly virtual adapter on vmnet3
Started DHCP service on vmnet3
Enabled hostonly virtual adapter on vmnet4
Started DHCP service on vmnet4
Enabled hostonly virtual adapter on vmnet5
Started DHCP service on vmnet5
Enabled hostonly virtual adapter on vmnet6
Started NAT service on vmnet8
Enabled hostonly virtual adapter on vmnet8
Started DHCP service on vmnet8
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 31999
DEBUG subprocess: Exit status: 1
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Some/All of the configured services are not running
DEBUG subprocess: stdout: DHCP service on vmnet1 is running
Hostonly virtual adapter on vmnet1 is enabled
DHCP service on vmnet2 is running
Hostonly virtual adapter on vmnet2 is enabled
DHCP service on vmnet3 is running
Hostonly virtual adapter on vmnet3 is enabled
DHCP service on vmnet4 is running
Hostonly virtual adapter on vmnet4 is enabled
DHCP service on vmnet5 is running
Hostonly virtual adapter on vmnet5 is enabled
DHCP service on vmnet6 is not running
Hostonly virtual adapter on vmnet6 is enabled
DHCP service on vmnet8 is running
NAT service on vmnet8 is running
Hostonly virtual adapter on vmnet8 is enabled
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO vmware_driver: Stopping services starter...
The VMware "vmnet" devices are failing to start. The most common
reason for this is collisions with existing network services. For
example, if a hostonly network space collides with another hostonly
network (such as with VirtualBox), it will fail to start. Likewise,
if forwarded ports collide with other listening ports, it will
fail to start.
Vagrant does its best to fix these issues, but in some cases it
cannot determine the root cause of these failures.
Please verify you have no other colliding network services running.
As a last resort, restarting your computer often fixes this issue.
ERROR vagrant: /Users/quasiben/.vagrant.d/gems/gems/vagrant-vmware-fusion-4.0.2/lib/vagrant-vmware-fusion/sudo_helper.rb:53:in `call'
/Users/quasiben/.vagrant.d/gems/gems/vagrant-vmware-fusion-4.0.2/lib/vagrant-vmware-fusion/driver.rb:717:in `create_vmnet_device'
/Users/quasiben/.vagrant.d/gems/gems/vagrant-vmware-fusion-4.0.2/lib/vagrant-vmware-fusion/action_farm.rb:826:in `hostonly_adapter'
/Users/quasiben/.vagrant.d/gems/gems/vagrant-vmware-fusion-4.0.2/lib/vagrant-vmware-fusion/action_farm.rb:705:in `block in call'
/Users/quasiben/.vagrant.d/gems/gems/vagrant-vmware-fusion-4.0.2/lib/vagrant-vmware-fusion/action_farm.rb:694:in `each'
/Users/quasiben/.vagrant.d/gems/gems/vagrant-vmware-fusion-4.0.2/lib/vagrant-vmware-fusion/action_farm.rb:694:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
/Users/quasiben/.vagrant.d/gems/gems/vagrant-vmware-fusion-4.0.2/lib/vagrant-vmware-fusion/action_farm.rb:953:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/builtin/synced_folders.rb:86:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/builtin/synced_folder_cleanup.rb:28:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/synced_folders/nfs/action_cleanup.rb:25:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
/Users/quasiben/.vagrant.d/gems/gems/vagrant-vmware-fusion-4.0.2/lib/vagrant-vmware-fusion/action_farm.rb:1025:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/builtin/provision.rb:80:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/builder.rb:116:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/runner.rb:66:in `block in run'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/util/busy.rb:19:in `busy'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/runner.rb:66:in `run'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/builtin/call.rb:53:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
/Users/quasiben/.vagrant.d/gems/gems/vagrant-vmware-fusion-4.0.2/lib/vagrant-vmware-fusion/action_farm.rb:71:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
/Users/quasiben/.vagrant.d/gems/gems/vagrant-vmware-fusion-4.0.2/lib/vagrant-vmware-fusion/action_farm.rb:1055:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/builder.rb:116:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/runner.rb:66:in `block in run'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/util/busy.rb:19:in `busy'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/runner.rb:66:in `run'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/builtin/call.rb:53:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/builtin/box_check_outdated.rb:68:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
/Users/quasiben/.vagrant.d/gems/gems/vagrant-vmware-fusion-4.0.2/lib/vagrant-vmware-fusion/action_farm.rb:1347:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
/Users/quasiben/.vagrant.d/gems/gems/vagrant-vmware-fusion-4.0.2/lib/vagrant-vmware-fusion/action_farm.rb:273:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
/Users/quasiben/.vagrant.d/gems/gems/vagrant-vmware-fusion-4.0.2/lib/vagrant-vmware-fusion/action_farm.rb:143:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
/Users/quasiben/.vagrant.d/gems/gems/vagrant-vmware-fusion-4.0.2/lib/vagrant-vmware-fusion/action_farm.rb:1134:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
/Users/quasiben/.vagrant.d/gems/gems/vagrant-vmware-fusion-4.0.2/lib/vagrant-vmware-fusion/action_farm.rb:502:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/builtin/handle_box.rb:56:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/builder.rb:116:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/runner.rb:66:in `block in run'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/util/busy.rb:19:in `busy'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/runner.rb:66:in `run'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/builtin/call.rb:53:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
/Users/quasiben/.vagrant.d/gems/gems/vagrant-vmware-fusion-4.0.2/lib/vagrant-vmware-fusion/action_farm.rb:1347:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
/Users/quasiben/.vagrant.d/gems/gems/vagrant-vmware-fusion-4.0.2/lib/vagrant-vmware-fusion/action_farm.rb:99:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
/Users/quasiben/.vagrant.d/gems/gems/vagrant-vmware-fusion-4.0.2/lib/vagrant-vmware-fusion/action_farm.rb:273:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/builtin/config_validate.rb:25:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
/Users/quasiben/.vagrant.d/gems/gems/vagrant-vmware-fusion-4.0.2/lib/vagrant-vmware-fusion/action_farm.rb:160:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/builder.rb:116:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/runner.rb:66:in `block in run'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/util/busy.rb:19:in `busy'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/runner.rb:66:in `run'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/machine.rb:214:in `action_raw'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/machine.rb:191:in `block in action'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/environment.rb:516:in `lock'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/machine.rb:178:in `call'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/machine.rb:178:in `action'
/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/batch_action.rb:82:in `block (2 levels) in run'
INFO interface: error: INFO global: Vagrant version: 1.7.4
INFO global: Ruby version: 2.0.0
INFO global: RubyGems version: 2.0.14
INFO global: VAGRANT_LOG="debug"
INFO global: VAGRANT_OLD_ENV_SPARK_HOME="/Users/quasiben/Research/GitClones/spark"
INFO global: VAGRANT_OLD_ENV_HOME="/Users/quasiben"
INFO global: VAGRANT_OLD_ENV__="/usr/local/bin/vagrant"
INFO global: VAGRANT_OLD_ENV_XPC_FLAGS="0x0"
INFO global: VAGRANT_INSTALLER_VERSION="2"
INFO global: VAGRANT_OLD_ENV_VAGRANT_LOG="debug"
INFO global: VAGRANT_OLD_ENV_TMPDIR="/var/folders/1t/t94brwgx7sjcn8jgz4gr3_c00000gq/T/"
INFO global: VAGRANT_OLD_ENV_Apple_PubSub_Socket_Render="/private/tmp/com.apple.launchd.KW13obTzd8/Render"
INFO global: VAGRANT_OLD_ENV_JAVA_HOME="/Library/Java/JavaVirtualMachines/jdk1.7.0_45.jdk/Contents/Home"
INFO global: VAGRANT_OLD_ENV_ACHE_HOME="/Users/quasiben/anaconda/envs/memex-explorer/lib/python2.7/site-packages/ache/"
INFO global: VAGRANT_OLD_ENV_CONDA_ENV_PATH="/Users/quasiben/anaconda/envs/clusto"
INFO global: VAGRANT_OLD_ENV_PYTHONPATH="/Users/quasiben/Research/ContinuumDev/GitRepo/conda-cluster/::/Users/quasiben/Research/GitClones/spark/python"
INFO global: VAGRANT_OLD_ENV_PATH="/Users/quasiben/anaconda/envs/clusto/bin:/usr/local/bin:/usr/local/heroku/bin:/Users/quasiben/google-cloud-sdk/bin:/usr/local/sbin:/Users/quasiben/.cabal/bin/:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/texbin:/Users/quasiben/Research/ContinuumDev/GitRepo/libdynd/build"
INFO global: VAGRANT_OLD_ENV_PWD="/Users/quasiben"
INFO global: VAGRANT_OLD_ENV_ITERM_PROFILE="Default"
INFO global: VAGRANT_OLD_ENV_JDK_HOME="/Library/Java/JavaVirtualMachines/jdk1.7.0_45.jdk/Contents/Home/"
INFO global: VAGRANT_OLD_ENV_COLORFGBG="7;0"
INFO global: VAGRANT_OLD_ENV_CONDA_DEFAULT_ENV="clusto"
INFO global: VAGRANT_INSTALLER_ENV="1"
INFO global: VAGRANT_EXECUTABLE="/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/bin/vagrant"
INFO global: VAGRANT_INSTALLER_EMBEDDED_DIR="/opt/vagrant/embedded"
INFO global: VAGRANT_OLD_ENV_COMMAND_MODE="unix2003"
INFO global: VAGRANT_OLD_ENV_SSH_AUTH_SOCK="/private/tmp/com.apple.launchd.CSjdOMPkpG/Listeners"
INFO global: VAGRANT_OLD_ENV_LANG="en_US.UTF-8"
INFO global: VAGRANT_OLD_ENV_TERM_PROGRAM="iTerm.app"
INFO global: VAGRANT_OLD_ENV_XPC_SERVICE_NAME="0"
INFO global: VAGRANT_OLD_ENV_SHLVL="1"
INFO global: VAGRANT_OLD_ENV_SECURITYSESSIONID="186a5"
INFO global: VAGRANT_OLD_ENV_TERM="xterm-color"
INFO global: VAGRANT_OLD_ENV_USER="quasiben"
INFO global: VAGRANT_OLD_ENV___CF_USER_TEXT_ENCODING="0x1F7:0x0:0x0"
INFO global: VAGRANT_OLD_ENV_ITERM_SESSION_ID="w0t1p0"
INFO global: VAGRANT_OLD_ENV_SHELL="/bin/bash"
INFO global: VAGRANT_OLD_ENV_PS1="(clusto)\\[\\033[01;32m\\]\\u@\\h\\[\\033[00m\\]:\\[\\033[01;36m\\]\\w\\[\\033[00m\\]\\$ "
INFO global: VAGRANT_OLD_ENV_OLDPWD="/Users/quasiben/Research/ContinuumDev/AC_AS_Vagrant/Head+Compute/test"
INFO global: VAGRANT_OLD_ENV_JRE_HOME="/Library/Java/JavaVirtualMachines/jdk1.7.0_45.jdk/Contents/Home/jre/"
INFO global: VAGRANT_OLD_ENV_LOGNAME="quasiben"
INFO global: VAGRANT_INTERNAL_BUNDLERIZED="1"
INFO global: Plugins:
INFO global: - bundler = 1.10.5
INFO global: - mime-types = 1.25.1
INFO global: - rest-client = 1.6.9
INFO global: - vagrant-share = 1.1.4
INFO global: - vagrant-vmware-fusion = 4.0.2
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/box/plugin.rb
INFO manager: Registered plugin: box command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/destroy/plugin.rb
INFO manager: Registered plugin: destroy command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/global-status/plugin.rb
INFO manager: Registered plugin: global-status command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/halt/plugin.rb
INFO manager: Registered plugin: halt command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/help/plugin.rb
INFO manager: Registered plugin: help command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/init/plugin.rb
INFO manager: Registered plugin: init command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/list-commands/plugin.rb
INFO manager: Registered plugin: list-commands command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/login/plugin.rb
INFO manager: Registered plugin: vagrant-login
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/package/plugin.rb
INFO manager: Registered plugin: package command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/plugin/plugin.rb
INFO manager: Registered plugin: plugin command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/provision/plugin.rb
INFO manager: Registered plugin: provision command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/push/plugin.rb
INFO manager: Registered plugin: push command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/rdp/plugin.rb
INFO manager: Registered plugin: rdp command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/reload/plugin.rb
INFO manager: Registered plugin: reload command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/resume/plugin.rb
INFO manager: Registered plugin: resume command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/ssh/plugin.rb
INFO manager: Registered plugin: ssh command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/ssh_config/plugin.rb
INFO manager: Registered plugin: ssh-config command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/status/plugin.rb
INFO manager: Registered plugin: status command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/suspend/plugin.rb
INFO manager: Registered plugin: suspend command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/up/plugin.rb
INFO manager: Registered plugin: up command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/version/plugin.rb
INFO manager: Registered plugin: version command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/communicators/ssh/plugin.rb
INFO manager: Registered plugin: ssh communicator
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/communicators/winrm/plugin.rb
INFO manager: Registered plugin: winrm communicator
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/arch/plugin.rb
INFO manager: Registered plugin: Arch guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/atomic/plugin.rb
INFO manager: Registered plugin: Atomic Host guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/coreos/plugin.rb
INFO manager: Registered plugin: CoreOS guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/darwin/plugin.rb
INFO manager: Registered plugin: Darwin guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/debian/plugin.rb
INFO manager: Registered plugin: Debian guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/debian8/plugin.rb
INFO manager: Registered plugin: Debian Jessie guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/esxi/plugin.rb
INFO manager: Registered plugin: ESXi guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/fedora/plugin.rb
INFO manager: Registered plugin: Fedora guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/freebsd/plugin.rb
INFO manager: Registered plugin: FreeBSD guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/funtoo/plugin.rb
INFO manager: Registered plugin: Funtoo guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/gentoo/plugin.rb
INFO manager: Registered plugin: Gentoo guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/linux/plugin.rb
INFO manager: Registered plugin: Linux guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/mint/plugin.rb
INFO manager: Registered plugin: Mint guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/netbsd/plugin.rb
INFO manager: Registered plugin: NetBSD guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/nixos/plugin.rb
INFO manager: Registered plugin: NixOS guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/omnios/plugin.rb
INFO manager: Registered plugin: OmniOS guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/openbsd/plugin.rb
INFO manager: Registered plugin: OpenBSD guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/photon/plugin.rb
INFO manager: Registered plugin: VMware Photon guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/pld/plugin.rb
INFO manager: Registered plugin: PLD Linux guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/redhat/plugin.rb
INFO manager: Registered plugin: Red Hat Enterprise Linux guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/smartos/plugin.rb
INFO manager: Registered plugin: SmartOS guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/solaris/plugin.rb
INFO manager: Registered plugin: Solaris guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/solaris11/plugin.rb
INFO manager: Registered plugin: Solaris 11 guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/suse/plugin.rb
INFO manager: Registered plugin: SUSE guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/tinycore/plugin.rb
INFO manager: Registered plugin: TinyCore Linux guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/ubuntu/plugin.rb
INFO manager: Registered plugin: Ubuntu guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/windows/plugin.rb
INFO manager: Registered plugin: Windows guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/arch/plugin.rb
INFO manager: Registered plugin: Arch host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/bsd/plugin.rb
INFO manager: Registered plugin: BSD host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/darwin/plugin.rb
INFO manager: Registered plugin: Mac OS X host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/freebsd/plugin.rb
INFO manager: Registered plugin: FreeBSD host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/gentoo/plugin.rb
INFO manager: Registered plugin: Gentoo host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/linux/plugin.rb
INFO manager: Registered plugin: Linux host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/null/plugin.rb
INFO manager: Registered plugin: null host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/redhat/plugin.rb
INFO manager: Registered plugin: Red Hat Enterprise Linux host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/slackware/plugin.rb
INFO manager: Registered plugin: Slackware host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/suse/plugin.rb
INFO manager: Registered plugin: SUSE host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/windows/plugin.rb
INFO manager: Registered plugin: Windows host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/kernel_v1/plugin.rb
INFO manager: Registered plugin: kernel
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/kernel_v2/plugin.rb
INFO manager: Registered plugin: kernel
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/providers/docker/plugin.rb
INFO manager: Registered plugin: docker-provider
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/providers/hyperv/plugin.rb
INFO manager: Registered plugin: Hyper-V provider
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/providers/virtualbox/plugin.rb
INFO manager: Registered plugin: VirtualBox provider
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/ansible/plugin.rb
INFO manager: Registered plugin: ansible
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/cfengine/plugin.rb
INFO manager: Registered plugin: CFEngine Provisioner
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/chef/plugin.rb
INFO manager: Registered plugin: chef
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/docker/plugin.rb
INFO manager: Registered plugin: docker
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/file/plugin.rb
INFO manager: Registered plugin: file
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/puppet/plugin.rb
INFO manager: Registered plugin: puppet
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/salt/plugin.rb
INFO manager: Registered plugin: salt
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/shell/plugin.rb
INFO manager: Registered plugin: shell
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/pushes/atlas/plugin.rb
INFO manager: Registered plugin: atlas
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/pushes/ftp/plugin.rb
INFO manager: Registered plugin: ftp
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/pushes/heroku/plugin.rb
INFO manager: Registered plugin: heroku
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/pushes/local-exec/plugin.rb
INFO manager: Registered plugin: local-exec
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/pushes/noop/plugin.rb
INFO manager: Registered plugin: noop
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/synced_folders/nfs/plugin.rb
INFO manager: Registered plugin: NFS synced folders
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/synced_folders/rsync/plugin.rb
INFO manager: Registered plugin: RSync synced folders
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/synced_folders/smb/plugin.rb
INFO manager: Registered plugin: SMB synced folders
INFO manager: Registered plugin: VMware Fusion Provider
INFO vmware_driver: VMX path is a directory. Finding VMX file...
INFO vmware_driver: VMX file: /Users/quasiben/.vagrant/machines/dev/vmware_fusion/7890b8d8-98e2-4cd5-a989-d65c4e0279ae/trusty64.vmx
INFO vmware_driver: Looking for VMware Fusion: /Applications/VMware Fusion.app
INFO vmware_driver: VMware Fusion path: #<Pathname:/Applications/VMware Fusion.app>
DEBUG vmware_driver: Attempting to read VMware version...
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmware-vmx", "-v"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command is setuid/setgid, clearing DYLD_LIBRARY_PATH
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr:
VMware Fusion Information:
VMware Fusion 7.1.0 build-2314774 Release
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO vmware_driver: Detected VMware version: 7.1.0
DEBUG vmware_driver: service starter path: /Applications/VMware Fusion.app/Contents/Library/services/Open VMware Fusion Services
DEBUG vmware_driver: vmnet-cli path: /Applications/VMware Fusion.app/Contents/Library/vmnet-cli
INFO vmware:sudo_helper: Calling command: create-vmnet-device
INFO networking_file: Reading adapters from networking file...
DEBUG networking_file: VNET: 1. KEY: 'DHCP' = 'yes'
DEBUG networking_file: VNET: 1. KEY: 'DHCP_CFG_HASH' = 'D80210FE873BE2813B8C769A8E72B64979061717'
DEBUG networking_file: VNET: 1. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG networking_file: VNET: 1. KEY: 'HOSTONLY_SUBNET' = '192.168.27.0'
DEBUG networking_file: VNET: 1. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG networking_file: VNET: 2. KEY: 'DHCP' = 'yes'
DEBUG networking_file: VNET: 2. KEY: 'DHCP_CFG_HASH' = '87768080D35EC28F8A98E2922D0D6FE5E5C18A59'
DEBUG networking_file: VNET: 2. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG networking_file: VNET: 2. KEY: 'HOSTONLY_SUBNET' = '10.10.10.0'
DEBUG networking_file: VNET: 2. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG networking_file: VNET: 3. KEY: 'DHCP' = 'yes'
DEBUG networking_file: VNET: 3. KEY: 'DHCP_CFG_HASH' = '3EC4C96155C7AA76726042C1D3C8D9C208404144'
DEBUG networking_file: VNET: 3. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG networking_file: VNET: 3. KEY: 'HOSTONLY_SUBNET' = '192.168.18.0'
DEBUG networking_file: VNET: 3. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG networking_file: VNET: 4. KEY: 'DHCP' = 'yes'
DEBUG networking_file: VNET: 4. KEY: 'DHCP_CFG_HASH' = '6F6696B0E161F81ED0E3CE9F08794F4DD8D794EB'
DEBUG networking_file: VNET: 4. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG networking_file: VNET: 4. KEY: 'HOSTONLY_SUBNET' = '172.16.48.0'
DEBUG networking_file: VNET: 4. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG networking_file: VNET: 5. KEY: 'DHCP' = 'yes'
DEBUG networking_file: VNET: 5. KEY: 'DHCP_CFG_HASH' = '9B81D6F11FF984546E1C4E2B438F14AC3B559373'
DEBUG networking_file: VNET: 5. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG networking_file: VNET: 5. KEY: 'HOSTONLY_SUBNET' = '192.168.111.0'
DEBUG networking_file: VNET: 5. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG networking_file: VNET: 8. KEY: 'DHCP' = 'yes'
DEBUG networking_file: VNET: 8. KEY: 'DHCP_CFG_HASH' = '1BDC60FCCCD2EEB9E6AA5D403BE51F90BF3ACC00'
DEBUG networking_file: VNET: 8. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG networking_file: VNET: 8. KEY: 'HOSTONLY_SUBNET' = '192.168.186.0'
DEBUG networking_file: VNET: 8. KEY: 'NAT' = 'yes'
DEBUG networking_file: VNET: 8. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG networking_file: Pruning adapters that aren't actually active...
INFO vmware_driver: Starting services starter and waiting for them to start...
INFO vmware_driver: Killing vmnet-natd if it is alive...
INFO subprocess: Starting process: ["/usr/bin/pkill", "vmnet-natd"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--start"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Failed to start DHCP service on vmnet6
DEBUG subprocess: stderr: Failed to start some/all services
DEBUG subprocess: stdout: Enabled hostonly virtual adapter on vmnet1
Started DHCP service on vmnet1
Enabled hostonly virtual adapter on vmnet2
Started DHCP service on vmnet2
Enabled hostonly virtual adapter on vmnet3
Started DHCP service on vmnet3
Enabled hostonly virtual adapter on vmnet4
Started DHCP service on vmnet4
Enabled hostonly virtual adapter on vmnet5
Started DHCP service on vmnet5
Enabled hostonly virtual adapter on vmnet6
Started NAT service on vmnet8
Enabled hostonly virtual adapter on vmnet8
Started DHCP service on vmnet8
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Some/All of the configured services are not running
DEBUG subprocess: stdout: DHCP service on vmnet1 is running
Hostonly virtual adapter on vmnet1 is enabled
DHCP service on vmnet2 is running
Hostonly virtual adapter on vmnet2 is enabled
DHCP service on vmnet3 is running
Hostonly virtual adapter on vmnet3 is enabled
DHCP service on vmnet4 is running
Hostonly virtual adapter on vmnet4 is enabled
DHCP service on vmnet5 is running
Hostonly virtual adapter on vmnet5 is enabled
DHCP service on vmnet6 is not running
Hostonly virtual adapter on vmnet6 is enabled
DHCP service on vmnet8 is running
NAT service on vmnet8 is running
Hostonly virtual adapter on vmnet8 is enabled
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO retryable: Retryable exception raised: #<HashiCorp::VagrantVMwarefusion::Errors::VMNetDevicesWontStart: The VMware "vmnet" devices are failing to start. The most common
reason for this is collisions with existing network services. For
example, if a hostonly network space collides with another hostonly
network (such as with VirtualBox), it will fail to start. Likewise,
if forwarded ports collide with other listening ports, it will
fail to start.
Vagrant does its best to fix these issues, but in some cases it
cannot determine the root cause of these failures.
Please verify you have no other colliding network services running.
As a last resort, restarting your computer often fixes this issue.>
INFO vmware_driver: Killing vmnet-natd if it is alive...
INFO subprocess: Starting process: ["/usr/bin/pkill", "vmnet-natd"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--start"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Failed to start DHCP service on vmnet6
DEBUG subprocess: stderr: Failed to start some/all services
DEBUG subprocess: stdout: Enabled hostonly virtual adapter on vmnet1
Started DHCP service on vmnet1
Enabled hostonly virtual adapter on vmnet2
Started DHCP service on vmnet2
Enabled hostonly virtual adapter on vmnet3
Started DHCP service on vmnet3
Enabled hostonly virtual adapter on vmnet4
Started DHCP service on vmnet4
Enabled hostonly virtual adapter on vmnet5
Started DHCP service on vmnet5
Enabled hostonly virtual adapter on vmnet6
Started NAT service on vmnet8
Enabled hostonly virtual adapter on vmnet8
Started DHCP service on vmnet8
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Some/All of the configured services are not running
DEBUG subprocess: stdout: DHCP service on vmnet1 is running
Hostonly virtual adapter on vmnet1 is enabled
DHCP service on vmnet2 is running
Hostonly virtual adapter on vmnet2 is enabled
DHCP service on vmnet3 is running
Hostonly virtual adapter on vmnet3 is enabled
DHCP service on vmnet4 is running
Hostonly virtual adapter on vmnet4 is enabled
DHCP service on vmnet5 is running
Hostonly virtual adapter on vmnet5 is enabled
DHCP service on vmnet6 is not running
Hostonly virtual adapter on vmnet6 is enabled
DHCP service on vmnet8 is running
NAT service on vmnet8 is running
Hostonly virtual adapter on vmnet8 is enabled
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO retryable: Retryable exception raised: #<HashiCorp::VagrantVMwarefusion::Errors::VMNetDevicesWontStart: The VMware "vmnet" devices are failing to start. The most common
reason for this is collisions with existing network services. For
example, if a hostonly network space collides with another hostonly
network (such as with VirtualBox), it will fail to start. Likewise,
if forwarded ports collide with other listening ports, it will
fail to start.
Vagrant does its best to fix these issues, but in some cases it
cannot determine the root cause of these failures.
Please verify you have no other colliding network services running.
As a last resort, restarting your computer often fixes this issue.>
INFO vmware_driver: Killing vmnet-natd if it is alive...
INFO subprocess: Starting process: ["/usr/bin/pkill", "vmnet-natd"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--start"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Failed to start DHCP service on vmnet6
DEBUG subprocess: stderr: Failed to start some/all services
DEBUG subprocess: stdout: Enabled hostonly virtual adapter on vmnet1
Started DHCP service on vmnet1
Enabled hostonly virtual adapter on vmnet2
Started DHCP service on vmnet2
Enabled hostonly virtual adapter on vmnet3
Started DHCP service on vmnet3
Enabled hostonly virtual adapter on vmnet4
Started DHCP service on vmnet4
Enabled hostonly virtual adapter on vmnet5
Started DHCP service on vmnet5
Enabled hostonly virtual adapter on vmnet6
Started NAT service on vmnet8
Enabled hostonly virtual adapter on vmnet8
Started DHCP service on vmnet8
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 31999
DEBUG subprocess: Exit status: 1
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Some/All of the configured services are not running
DEBUG subprocess: stdout: DHCP service on vmnet1 is running
Hostonly virtual adapter on vmnet1 is enabled
DHCP service on vmnet2 is running
Hostonly virtual adapter on vmnet2 is enabled
DHCP service on vmnet3 is running
Hostonly virtual adapter on vmnet3 is enabled
DHCP service on vmnet4 is running
Hostonly virtual adapter on vmnet4 is enabled
DHCP service on vmnet5 is running
Hostonly virtual adapter on vmnet5 is enabled
DHCP service on vmnet6 is not running
Hostonly virtual adapter on vmnet6 is enabled
DHCP service on vmnet8 is running
NAT service on vmnet8 is running
Hostonly virtual adapter on vmnet8 is enabled
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO retryable: Retryable exception raised: #<HashiCorp::VagrantVMwarefusion::Errors::VMNetDevicesWontStart: The VMware "vmnet" devices are failing to start. The most common
reason for this is collisions with existing network services. For
example, if a hostonly network space collides with another hostonly
network (such as with VirtualBox), it will fail to start. Likewise,
if forwarded ports collide with other listening ports, it will
fail to start.
Vagrant does its best to fix these issues, but in some cases it
cannot determine the root cause of these failures.
Please verify you have no other colliding network services running.
As a last resort, restarting your computer often fixes this issue.>
INFO vmware_driver: Killing vmnet-natd if it is alive...
INFO subprocess: Starting process: ["/usr/bin/pkill", "vmnet-natd"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--start"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Failed to start DHCP service on vmnet6
DEBUG subprocess: stderr: Failed to start some/all services
DEBUG subprocess: stdout: Enabled hostonly virtual adapter on vmnet1
Started DHCP service on vmnet1
Enabled hostonly virtual adapter on vmnet2
Started DHCP service on vmnet2
Enabled hostonly virtual adapter on vmnet3
Started DHCP service on vmnet3
Enabled hostonly virtual adapter on vmnet4
Started DHCP service on vmnet4
Enabled hostonly virtual adapter on vmnet5
Started DHCP service on vmnet5
Enabled hostonly virtual adapter on vmnet6
Started NAT service on vmnet8
Enabled hostonly virtual adapter on vmnet8
Started DHCP service on vmnet8
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Some/All of the configured services are not running
DEBUG subprocess: stdout: DHCP service on vmnet1 is running
Hostonly virtual adapter on vmnet1 is enabled
DHCP service on vmnet2 is running
Hostonly virtual adapter on vmnet2 is enabled
DHCP service on vmnet3 is running
Hostonly virtual adapter on vmnet3 is enabled
DHCP service on vmnet4 is running
Hostonly virtual adapter on vmnet4 is enabled
DHCP service on vmnet5 is running
Hostonly virtual adapter on vmnet5 is enabled
DHCP service on vmnet6 is not running
Hostonly virtual adapter on vmnet6 is enabled
DHCP service on vmnet8 is running
NAT service on vmnet8 is running
Hostonly virtual adapter on vmnet8 is enabled
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO retryable: Retryable exception raised: #<HashiCorp::VagrantVMwarefusion::Errors::VMNetDevicesWontStart: The VMware "vmnet" devices are failing to start. The most common
reason for this is collisions with existing network services. For
example, if a hostonly network space collides with another hostonly
network (such as with VirtualBox), it will fail to start. Likewise,
if forwarded ports collide with other listening ports, it will
fail to start.
Vagrant does its best to fix these issues, but in some cases it
cannot determine the root cause of these failures.
Please verify you have no other colliding network services running.
As a last resort, restarting your computer often fixes this issue.>
INFO vmware_driver: Killing vmnet-natd if it is alive...
INFO subprocess: Starting process: ["/usr/bin/pkill", "vmnet-natd"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--start"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Failed to start DHCP service on vmnet6
DEBUG subprocess: stderr: Failed to start some/all services
DEBUG subprocess: stdout: Enabled hostonly virtual adapter on vmnet1
Started DHCP service on vmnet1
Enabled hostonly virtual adapter on vmnet2
Started DHCP service on vmnet2
Enabled hostonly virtual adapter on vmnet3
Started DHCP service on vmnet3
Enabled hostonly virtual adapter on vmnet4
Started DHCP service on vmnet4
Enabled hostonly virtual adapter on vmnet5
Started DHCP service on vmnet5
Enabled hostonly virtual adapter on vmnet6
Started NAT service on vmnet8
Enabled hostonly virtual adapter on vmnet8
Started DHCP service on vmnet8
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 31999
DEBUG subprocess: Exit status: 1
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Some/All of the configured services are not running
DEBUG subprocess: stdout: DHCP service on vmnet1 is running
Hostonly virtual adapter on vmnet1 is enabled
DHCP service on vmnet2 is running
Hostonly virtual adapter on vmnet2 is enabled
DHCP service on vmnet3 is running
Hostonly virtual adapter on vmnet3 is enabled
DHCP service on vmnet4 is running
Hostonly virtual adapter on vmnet4 is enabled
DHCP service on vmnet5 is running
Hostonly virtual adapter on vmnet5 is enabled
DHCP service on vmnet6 is not running
Hostonly virtual adapter on vmnet6 is enabled
DHCP service on vmnet8 is running
NAT service on vmnet8 is running
Hostonly virtual adapter on vmnet8 is enabled
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO vmware_driver: Stopping services starter...
The VMware "vmnet" devices are failing to start. The most common
reason for this is collisions with existing network services. For
example, if a hostonly network space collides with another hostonly
network (such as with VirtualBox), it will fail to start. Likewise,
if forwarded ports collide with other listening ports, it will
fail to start.
Vagrant does its best to fix these issues, but in some cases it
cannot determine the root cause of these failures.
Please verify you have no other colliding network services running.
As a last resort, restarting your computer often fixes this issue.
 INFO global: Vagrant version: 1.7.4
INFO global: Ruby version: 2.0.0
INFO global: RubyGems version: 2.0.14
INFO global: VAGRANT_LOG="debug"
INFO global: VAGRANT_OLD_ENV_SPARK_HOME="/Users/quasiben/Research/GitClones/spark"
INFO global: VAGRANT_OLD_ENV_HOME="/Users/quasiben"
INFO global: VAGRANT_OLD_ENV__="/usr/local/bin/vagrant"
INFO global: VAGRANT_OLD_ENV_XPC_FLAGS="0x0"
INFO global: VAGRANT_INSTALLER_VERSION="2"
INFO global: VAGRANT_OLD_ENV_VAGRANT_LOG="debug"
INFO global: VAGRANT_OLD_ENV_TMPDIR="/var/folders/1t/t94brwgx7sjcn8jgz4gr3_c00000gq/T/"
INFO global: VAGRANT_OLD_ENV_Apple_PubSub_Socket_Render="/private/tmp/com.apple.launchd.KW13obTzd8/Render"
INFO global: VAGRANT_OLD_ENV_JAVA_HOME="/Library/Java/JavaVirtualMachines/jdk1.7.0_45.jdk/Contents/Home"
INFO global: VAGRANT_OLD_ENV_ACHE_HOME="/Users/quasiben/anaconda/envs/memex-explorer/lib/python2.7/site-packages/ache/"
INFO global: VAGRANT_OLD_ENV_CONDA_ENV_PATH="/Users/quasiben/anaconda/envs/clusto"
INFO global: VAGRANT_OLD_ENV_PYTHONPATH="/Users/quasiben/Research/ContinuumDev/GitRepo/conda-cluster/::/Users/quasiben/Research/GitClones/spark/python"
INFO global: VAGRANT_OLD_ENV_PATH="/Users/quasiben/anaconda/envs/clusto/bin:/usr/local/bin:/usr/local/heroku/bin:/Users/quasiben/google-cloud-sdk/bin:/usr/local/sbin:/Users/quasiben/.cabal/bin/:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/texbin:/Users/quasiben/Research/ContinuumDev/GitRepo/libdynd/build"
INFO global: VAGRANT_OLD_ENV_PWD="/Users/quasiben"
INFO global: VAGRANT_OLD_ENV_ITERM_PROFILE="Default"
INFO global: VAGRANT_OLD_ENV_JDK_HOME="/Library/Java/JavaVirtualMachines/jdk1.7.0_45.jdk/Contents/Home/"
INFO global: VAGRANT_OLD_ENV_COLORFGBG="7;0"
INFO global: VAGRANT_OLD_ENV_CONDA_DEFAULT_ENV="clusto"
INFO global: VAGRANT_INSTALLER_ENV="1"
INFO global: VAGRANT_EXECUTABLE="/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/bin/vagrant"
INFO global: VAGRANT_INSTALLER_EMBEDDED_DIR="/opt/vagrant/embedded"
INFO global: VAGRANT_OLD_ENV_COMMAND_MODE="unix2003"
INFO global: VAGRANT_OLD_ENV_SSH_AUTH_SOCK="/private/tmp/com.apple.launchd.CSjdOMPkpG/Listeners"
INFO global: VAGRANT_OLD_ENV_LANG="en_US.UTF-8"
INFO global: VAGRANT_OLD_ENV_TERM_PROGRAM="iTerm.app"
INFO global: VAGRANT_OLD_ENV_XPC_SERVICE_NAME="0"
INFO global: VAGRANT_OLD_ENV_SHLVL="1"
INFO global: VAGRANT_OLD_ENV_SECURITYSESSIONID="186a5"
INFO global: VAGRANT_OLD_ENV_TERM="xterm-color"
INFO global: VAGRANT_OLD_ENV_USER="quasiben"
INFO global: VAGRANT_OLD_ENV___CF_USER_TEXT_ENCODING="0x1F7:0x0:0x0"
INFO global: VAGRANT_OLD_ENV_ITERM_SESSION_ID="w0t1p0"
INFO global: VAGRANT_OLD_ENV_SHELL="/bin/bash"
INFO global: VAGRANT_OLD_ENV_PS1="(clusto)\\[\\033[01;32m\\]\\u@\\h\\[\\033[00m\\]:\\[\\033[01;36m\\]\\w\\[\\033[00m\\]\\$ "
INFO global: VAGRANT_OLD_ENV_OLDPWD="/Users/quasiben/Research/ContinuumDev/AC_AS_Vagrant/Head+Compute/test"
INFO global: VAGRANT_OLD_ENV_JRE_HOME="/Library/Java/JavaVirtualMachines/jdk1.7.0_45.jdk/Contents/Home/jre/"
INFO global: VAGRANT_OLD_ENV_LOGNAME="quasiben"
INFO global: VAGRANT_INTERNAL_BUNDLERIZED="1"
INFO global: Plugins:
INFO global: - bundler = 1.10.5
INFO global: - mime-types = 1.25.1
INFO global: - rest-client = 1.6.9
INFO global: - vagrant-share = 1.1.4
INFO global: - vagrant-vmware-fusion = 4.0.2
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/box/plugin.rb
INFO manager: Registered plugin: box command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/destroy/plugin.rb
INFO manager: Registered plugin: destroy command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/global-status/plugin.rb
INFO manager: Registered plugin: global-status command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/halt/plugin.rb
INFO manager: Registered plugin: halt command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/help/plugin.rb
INFO manager: Registered plugin: help command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/init/plugin.rb
INFO manager: Registered plugin: init command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/list-commands/plugin.rb
INFO manager: Registered plugin: list-commands command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/login/plugin.rb
INFO manager: Registered plugin: vagrant-login
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/package/plugin.rb
INFO manager: Registered plugin: package command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/plugin/plugin.rb
INFO manager: Registered plugin: plugin command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/provision/plugin.rb
INFO manager: Registered plugin: provision command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/push/plugin.rb
INFO manager: Registered plugin: push command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/rdp/plugin.rb
INFO manager: Registered plugin: rdp command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/reload/plugin.rb
INFO manager: Registered plugin: reload command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/resume/plugin.rb
INFO manager: Registered plugin: resume command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/ssh/plugin.rb
INFO manager: Registered plugin: ssh command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/ssh_config/plugin.rb
INFO manager: Registered plugin: ssh-config command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/status/plugin.rb
INFO manager: Registered plugin: status command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/suspend/plugin.rb
INFO manager: Registered plugin: suspend command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/up/plugin.rb
INFO manager: Registered plugin: up command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/version/plugin.rb
INFO manager: Registered plugin: version command
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/communicators/ssh/plugin.rb
INFO manager: Registered plugin: ssh communicator
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/communicators/winrm/plugin.rb
INFO manager: Registered plugin: winrm communicator
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/arch/plugin.rb
INFO manager: Registered plugin: Arch guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/atomic/plugin.rb
INFO manager: Registered plugin: Atomic Host guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/coreos/plugin.rb
INFO manager: Registered plugin: CoreOS guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/darwin/plugin.rb
INFO manager: Registered plugin: Darwin guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/debian/plugin.rb
INFO manager: Registered plugin: Debian guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/debian8/plugin.rb
INFO manager: Registered plugin: Debian Jessie guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/esxi/plugin.rb
INFO manager: Registered plugin: ESXi guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/fedora/plugin.rb
INFO manager: Registered plugin: Fedora guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/freebsd/plugin.rb
INFO manager: Registered plugin: FreeBSD guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/funtoo/plugin.rb
INFO manager: Registered plugin: Funtoo guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/gentoo/plugin.rb
INFO manager: Registered plugin: Gentoo guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/linux/plugin.rb
INFO manager: Registered plugin: Linux guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/mint/plugin.rb
INFO manager: Registered plugin: Mint guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/netbsd/plugin.rb
INFO manager: Registered plugin: NetBSD guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/nixos/plugin.rb
INFO manager: Registered plugin: NixOS guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/omnios/plugin.rb
INFO manager: Registered plugin: OmniOS guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/openbsd/plugin.rb
INFO manager: Registered plugin: OpenBSD guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/photon/plugin.rb
INFO manager: Registered plugin: VMware Photon guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/pld/plugin.rb
INFO manager: Registered plugin: PLD Linux guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/redhat/plugin.rb
INFO manager: Registered plugin: Red Hat Enterprise Linux guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/smartos/plugin.rb
INFO manager: Registered plugin: SmartOS guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/solaris/plugin.rb
INFO manager: Registered plugin: Solaris guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/solaris11/plugin.rb
INFO manager: Registered plugin: Solaris 11 guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/suse/plugin.rb
INFO manager: Registered plugin: SUSE guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/tinycore/plugin.rb
INFO manager: Registered plugin: TinyCore Linux guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/ubuntu/plugin.rb
INFO manager: Registered plugin: Ubuntu guest
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/windows/plugin.rb
INFO manager: Registered plugin: Windows guest.
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/arch/plugin.rb
INFO manager: Registered plugin: Arch host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/bsd/plugin.rb
INFO manager: Registered plugin: BSD host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/darwin/plugin.rb
INFO manager: Registered plugin: Mac OS X host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/freebsd/plugin.rb
INFO manager: Registered plugin: FreeBSD host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/gentoo/plugin.rb
INFO manager: Registered plugin: Gentoo host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/linux/plugin.rb
INFO manager: Registered plugin: Linux host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/null/plugin.rb
INFO manager: Registered plugin: null host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/redhat/plugin.rb
INFO manager: Registered plugin: Red Hat Enterprise Linux host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/slackware/plugin.rb
INFO manager: Registered plugin: Slackware host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/suse/plugin.rb
INFO manager: Registered plugin: SUSE host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/windows/plugin.rb
INFO manager: Registered plugin: Windows host
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/kernel_v1/plugin.rb
INFO manager: Registered plugin: kernel
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/kernel_v2/plugin.rb
INFO manager: Registered plugin: kernel
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/providers/docker/plugin.rb
INFO manager: Registered plugin: docker-provider
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/providers/hyperv/plugin.rb
INFO manager: Registered plugin: Hyper-V provider
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/providers/virtualbox/plugin.rb
INFO manager: Registered plugin: VirtualBox provider
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/ansible/plugin.rb
INFO manager: Registered plugin: ansible
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/cfengine/plugin.rb
INFO manager: Registered plugin: CFEngine Provisioner
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/chef/plugin.rb
INFO manager: Registered plugin: chef
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/docker/plugin.rb
INFO manager: Registered plugin: docker
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/file/plugin.rb
INFO manager: Registered plugin: file
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/puppet/plugin.rb
INFO manager: Registered plugin: puppet
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/salt/plugin.rb
INFO manager: Registered plugin: salt
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/shell/plugin.rb
INFO manager: Registered plugin: shell
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/pushes/atlas/plugin.rb
INFO manager: Registered plugin: atlas
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/pushes/ftp/plugin.rb
INFO manager: Registered plugin: ftp
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/pushes/heroku/plugin.rb
INFO manager: Registered plugin: heroku
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/pushes/local-exec/plugin.rb
INFO manager: Registered plugin: local-exec
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/pushes/noop/plugin.rb
INFO manager: Registered plugin: noop
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/synced_folders/nfs/plugin.rb
INFO manager: Registered plugin: NFS synced folders
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/synced_folders/rsync/plugin.rb
INFO manager: Registered plugin: RSync synced folders
DEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/synced_folders/smb/plugin.rb
INFO manager: Registered plugin: SMB synced folders
INFO manager: Registered plugin: VMware Fusion Provider
INFO vmware_driver: VMX path is a directory. Finding VMX file...
INFO vmware_driver: VMX file: /Users/quasiben/.vagrant/machines/dev/vmware_fusion/7890b8d8-98e2-4cd5-a989-d65c4e0279ae/trusty64.vmx
INFO vmware_driver: Looking for VMware Fusion: /Applications/VMware Fusion.app
INFO vmware_driver: VMware Fusion path: #<Pathname:/Applications/VMware Fusion.app>
DEBUG vmware_driver: Attempting to read VMware version...
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmware-vmx", "-v"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command is setuid/setgid, clearing DYLD_LIBRARY_PATH
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr:
VMware Fusion Information:
VMware Fusion 7.1.0 build-2314774 Release
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO vmware_driver: Detected VMware version: 7.1.0
DEBUG vmware_driver: service starter path: /Applications/VMware Fusion.app/Contents/Library/services/Open VMware Fusion Services
DEBUG vmware_driver: vmnet-cli path: /Applications/VMware Fusion.app/Contents/Library/vmnet-cli
INFO vmware:sudo_helper: Calling command: create-vmnet-device
INFO networking_file: Reading adapters from networking file...
DEBUG networking_file: VNET: 1. KEY: 'DHCP' = 'yes'
DEBUG networking_file: VNET: 1. KEY: 'DHCP_CFG_HASH' = 'D80210FE873BE2813B8C769A8E72B64979061717'
DEBUG networking_file: VNET: 1. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG networking_file: VNET: 1. KEY: 'HOSTONLY_SUBNET' = '192.168.27.0'
DEBUG networking_file: VNET: 1. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG networking_file: VNET: 2. KEY: 'DHCP' = 'yes'
DEBUG networking_file: VNET: 2. KEY: 'DHCP_CFG_HASH' = '87768080D35EC28F8A98E2922D0D6FE5E5C18A59'
DEBUG networking_file: VNET: 2. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG networking_file: VNET: 2. KEY: 'HOSTONLY_SUBNET' = '10.10.10.0'
DEBUG networking_file: VNET: 2. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG networking_file: VNET: 3. KEY: 'DHCP' = 'yes'
DEBUG networking_file: VNET: 3. KEY: 'DHCP_CFG_HASH' = '3EC4C96155C7AA76726042C1D3C8D9C208404144'
DEBUG networking_file: VNET: 3. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG networking_file: VNET: 3. KEY: 'HOSTONLY_SUBNET' = '192.168.18.0'
DEBUG networking_file: VNET: 3. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG networking_file: VNET: 4. KEY: 'DHCP' = 'yes'
DEBUG networking_file: VNET: 4. KEY: 'DHCP_CFG_HASH' = '6F6696B0E161F81ED0E3CE9F08794F4DD8D794EB'
DEBUG networking_file: VNET: 4. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG networking_file: VNET: 4. KEY: 'HOSTONLY_SUBNET' = '172.16.48.0'
DEBUG networking_file: VNET: 4. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG networking_file: VNET: 5. KEY: 'DHCP' = 'yes'
DEBUG networking_file: VNET: 5. KEY: 'DHCP_CFG_HASH' = '9B81D6F11FF984546E1C4E2B438F14AC3B559373'
DEBUG networking_file: VNET: 5. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG networking_file: VNET: 5. KEY: 'HOSTONLY_SUBNET' = '192.168.111.0'
DEBUG networking_file: VNET: 5. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG networking_file: VNET: 8. KEY: 'DHCP' = 'yes'
DEBUG networking_file: VNET: 8. KEY: 'DHCP_CFG_HASH' = '1BDC60FCCCD2EEB9E6AA5D403BE51F90BF3ACC00'
DEBUG networking_file: VNET: 8. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'
DEBUG networking_file: VNET: 8. KEY: 'HOSTONLY_SUBNET' = '192.168.186.0'
DEBUG networking_file: VNET: 8. KEY: 'NAT' = 'yes'
DEBUG networking_file: VNET: 8. KEY: 'VIRTUAL_ADAPTER' = 'yes'
DEBUG networking_file: Pruning adapters that aren't actually active...
INFO vmware_driver: Starting services starter and waiting for them to start...
INFO vmware_driver: Killing vmnet-natd if it is alive...
INFO subprocess: Starting process: ["/usr/bin/pkill", "vmnet-natd"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--start"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Failed to start DHCP service on vmnet6
DEBUG subprocess: stderr: Failed to start some/all services
DEBUG subprocess: stdout: Enabled hostonly virtual adapter on vmnet1
Started DHCP service on vmnet1
Enabled hostonly virtual adapter on vmnet2
Started DHCP service on vmnet2
Enabled hostonly virtual adapter on vmnet3
Started DHCP service on vmnet3
Enabled hostonly virtual adapter on vmnet4
Started DHCP service on vmnet4
Enabled hostonly virtual adapter on vmnet5
Started DHCP service on vmnet5
Enabled hostonly virtual adapter on vmnet6
Started NAT service on vmnet8
Enabled hostonly virtual adapter on vmnet8
Started DHCP service on vmnet8
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Some/All of the configured services are not running
DEBUG subprocess: stdout: DHCP service on vmnet1 is running
Hostonly virtual adapter on vmnet1 is enabled
DHCP service on vmnet2 is running
Hostonly virtual adapter on vmnet2 is enabled
DHCP service on vmnet3 is running
Hostonly virtual adapter on vmnet3 is enabled
DHCP service on vmnet4 is running
Hostonly virtual adapter on vmnet4 is enabled
DHCP service on vmnet5 is running
Hostonly virtual adapter on vmnet5 is enabled
DHCP service on vmnet6 is not running
Hostonly virtual adapter on vmnet6 is enabled
DHCP service on vmnet8 is running
NAT service on vmnet8 is running
Hostonly virtual adapter on vmnet8 is enabled
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO retryable: Retryable exception raised: #<HashiCorp::VagrantVMwarefusion::Errors::VMNetDevicesWontStart: The VMware "vmnet" devices are failing to start. The most common
reason for this is collisions with existing network services. For
example, if a hostonly network space collides with another hostonly
network (such as with VirtualBox), it will fail to start. Likewise,
if forwarded ports collide with other listening ports, it will
fail to start.
Vagrant does its best to fix these issues, but in some cases it
cannot determine the root cause of these failures.
Please verify you have no other colliding network services running.
As a last resort, restarting your computer often fixes this issue.>
INFO vmware_driver: Killing vmnet-natd if it is alive...
INFO subprocess: Starting process: ["/usr/bin/pkill", "vmnet-natd"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--start"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Failed to start DHCP service on vmnet6
DEBUG subprocess: stderr: Failed to start some/all services
DEBUG subprocess: stdout: Enabled hostonly virtual adapter on vmnet1
Started DHCP service on vmnet1
Enabled hostonly virtual adapter on vmnet2
Started DHCP service on vmnet2
Enabled hostonly virtual adapter on vmnet3
Started DHCP service on vmnet3
Enabled hostonly virtual adapter on vmnet4
Started DHCP service on vmnet4
Enabled hostonly virtual adapter on vmnet5
Started DHCP service on vmnet5
Enabled hostonly virtual adapter on vmnet6
Started NAT service on vmnet8
Enabled hostonly virtual adapter on vmnet8
Started DHCP service on vmnet8
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Some/All of the configured services are not running
DEBUG subprocess: stdout: DHCP service on vmnet1 is running
Hostonly virtual adapter on vmnet1 is enabled
DHCP service on vmnet2 is running
Hostonly virtual adapter on vmnet2 is enabled
DHCP service on vmnet3 is running
Hostonly virtual adapter on vmnet3 is enabled
DHCP service on vmnet4 is running
Hostonly virtual adapter on vmnet4 is enabled
DHCP service on vmnet5 is running
Hostonly virtual adapter on vmnet5 is enabled
DHCP service on vmnet6 is not running
Hostonly virtual adapter on vmnet6 is enabled
DHCP service on vmnet8 is running
NAT service on vmnet8 is running
Hostonly virtual adapter on vmnet8 is enabled
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO retryable: Retryable exception raised: #<HashiCorp::VagrantVMwarefusion::Errors::VMNetDevicesWontStart: The VMware "vmnet" devices are failing to start. The most common
reason for this is collisions with existing network services. For
example, if a hostonly network space collides with another hostonly
network (such as with VirtualBox), it will fail to start. Likewise,
if forwarded ports collide with other listening ports, it will
fail to start.
Vagrant does its best to fix these issues, but in some cases it
cannot determine the root cause of these failures.
Please verify you have no other colliding network services running.
As a last resort, restarting your computer often fixes this issue.>
INFO vmware_driver: Killing vmnet-natd if it is alive...
INFO subprocess: Starting process: ["/usr/bin/pkill", "vmnet-natd"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--start"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Failed to start DHCP service on vmnet6
DEBUG subprocess: stderr: Failed to start some/all services
DEBUG subprocess: stdout: Enabled hostonly virtual adapter on vmnet1
Started DHCP service on vmnet1
Enabled hostonly virtual adapter on vmnet2
Started DHCP service on vmnet2
Enabled hostonly virtual adapter on vmnet3
Started DHCP service on vmnet3
Enabled hostonly virtual adapter on vmnet4
Started DHCP service on vmnet4
Enabled hostonly virtual adapter on vmnet5
Started DHCP service on vmnet5
Enabled hostonly virtual adapter on vmnet6
Started NAT service on vmnet8
Enabled hostonly virtual adapter on vmnet8
Started DHCP service on vmnet8
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 31999
DEBUG subprocess: Exit status: 1
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Some/All of the configured services are not running
DEBUG subprocess: stdout: DHCP service on vmnet1 is running
Hostonly virtual adapter on vmnet1 is enabled
DHCP service on vmnet2 is running
Hostonly virtual adapter on vmnet2 is enabled
DHCP service on vmnet3 is running
Hostonly virtual adapter on vmnet3 is enabled
DHCP service on vmnet4 is running
Hostonly virtual adapter on vmnet4 is enabled
DHCP service on vmnet5 is running
Hostonly virtual adapter on vmnet5 is enabled
DHCP service on vmnet6 is not running
Hostonly virtual adapter on vmnet6 is enabled
DHCP service on vmnet8 is running
NAT service on vmnet8 is running
Hostonly virtual adapter on vmnet8 is enabled
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO retryable: Retryable exception raised: #<HashiCorp::VagrantVMwarefusion::Errors::VMNetDevicesWontStart: The VMware "vmnet" devices are failing to start. The most common
reason for this is collisions with existing network services. For
example, if a hostonly network space collides with another hostonly
network (such as with VirtualBox), it will fail to start. Likewise,
if forwarded ports collide with other listening ports, it will
fail to start.
Vagrant does its best to fix these issues, but in some cases it
cannot determine the root cause of these failures.
Please verify you have no other colliding network services running.
As a last resort, restarting your computer often fixes this issue.>
INFO vmware_driver: Killing vmnet-natd if it is alive...
INFO subprocess: Starting process: ["/usr/bin/pkill", "vmnet-natd"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--start"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Failed to start DHCP service on vmnet6
DEBUG subprocess: stderr: Failed to start some/all services
DEBUG subprocess: stdout: Enabled hostonly virtual adapter on vmnet1
Started DHCP service on vmnet1
Enabled hostonly virtual adapter on vmnet2
Started DHCP service on vmnet2
Enabled hostonly virtual adapter on vmnet3
Started DHCP service on vmnet3
Enabled hostonly virtual adapter on vmnet4
Started DHCP service on vmnet4
Enabled hostonly virtual adapter on vmnet5
Started DHCP service on vmnet5
Enabled hostonly virtual adapter on vmnet6
Started NAT service on vmnet8
Enabled hostonly virtual adapter on vmnet8
Started DHCP service on vmnet8
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Some/All of the configured services are not running
DEBUG subprocess: stdout: DHCP service on vmnet1 is running
Hostonly virtual adapter on vmnet1 is enabled
DHCP service on vmnet2 is running
Hostonly virtual adapter on vmnet2 is enabled
DHCP service on vmnet3 is running
Hostonly virtual adapter on vmnet3 is enabled
DHCP service on vmnet4 is running
Hostonly virtual adapter on vmnet4 is enabled
DHCP service on vmnet5 is running
Hostonly virtual adapter on vmnet5 is enabled
DHCP service on vmnet6 is not running
Hostonly virtual adapter on vmnet6 is enabled
DHCP service on vmnet8 is running
NAT service on vmnet8 is running
Hostonly virtual adapter on vmnet8 is enabled
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO retryable: Retryable exception raised: #<HashiCorp::VagrantVMwarefusion::Errors::VMNetDevicesWontStart: The VMware "vmnet" devices are failing to start. The most common
reason for this is collisions with existing network services. For
example, if a hostonly network space collides with another hostonly
network (such as with VirtualBox), it will fail to start. Likewise,
if forwarded ports collide with other listening ports, it will
fail to start.
Vagrant does its best to fix these issues, but in some cases it
cannot determine the root cause of these failures.
Please verify you have no other colliding network services running.
As a last resort, restarting your computer often fixes this issue.>
INFO vmware_driver: Killing vmnet-natd if it is alive...
INFO subprocess: Starting process: ["/usr/bin/pkill", "vmnet-natd"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--start"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Failed to start DHCP service on vmnet6
DEBUG subprocess: stderr: Failed to start some/all services
DEBUG subprocess: stdout: Enabled hostonly virtual adapter on vmnet1
Started DHCP service on vmnet1
Enabled hostonly virtual adapter on vmnet2
Started DHCP service on vmnet2
Enabled hostonly virtual adapter on vmnet3
Started DHCP service on vmnet3
Enabled hostonly virtual adapter on vmnet4
Started DHCP service on vmnet4
Enabled hostonly virtual adapter on vmnet5
Started DHCP service on vmnet5
Enabled hostonly virtual adapter on vmnet6
Started NAT service on vmnet8
Enabled hostonly virtual adapter on vmnet8
Started DHCP service on vmnet8
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 31999
DEBUG subprocess: Exit status: 1
INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"]
DEBUG subprocess: Command not in installer, not touching env vars.
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Some/All of the configured services are not running
DEBUG subprocess: stdout: DHCP service on vmnet1 is running
Hostonly virtual adapter on vmnet1 is enabled
DHCP service on vmnet2 is running
Hostonly virtual adapter on vmnet2 is enabled
DHCP service on vmnet3 is running
Hostonly virtual adapter on vmnet3 is enabled
DHCP service on vmnet4 is running
Hostonly virtual adapter on vmnet4 is enabled
DHCP service on vmnet5 is running
Hostonly virtual adapter on vmnet5 is enabled
DHCP service on vmnet6 is not running
Hostonly virtual adapter on vmnet6 is enabled
DHCP service on vmnet8 is running
NAT service on vmnet8 is running
Hostonly virtual adapter on vmnet8 is enabled
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 1
INFO vmware_driver: Stopping services starter...
The VMware "vmnet" devices are failing to start. The most common
reason for this is collisions with existing network services. For
example, if a hostonly network space collides with another hostonly
network (such as with VirtualBox), it will fail to start. Likewise,
if forwarded ports collide with other listening ports, it will
fail to start.
Vagrant does its best to fix these issues, but in some cases it
cannot determine the root cause of these failures.
Please verify you have no other colliding network services running.
As a last resort, restarting your computer often fixes this issue.
INFO interface: Machine: error-exit ["HashiCorp::VagrantVMwarefusion::Errors::HelperFailed", " INFO global: Vagrant version: 1.7.4\n INFO global: Ruby version: 2.0.0\n INFO global: RubyGems version: 2.0.14\n INFO global: VAGRANT_LOG=\"debug\"\n INFO global: VAGRANT_OLD_ENV_SPARK_HOME=\"/Users/quasiben/Research/GitClones/spark\"\n INFO global: VAGRANT_OLD_ENV_HOME=\"/Users/quasiben\"\n INFO global: VAGRANT_OLD_ENV__=\"/usr/local/bin/vagrant\"\n INFO global: VAGRANT_OLD_ENV_XPC_FLAGS=\"0x0\"\n INFO global: VAGRANT_INSTALLER_VERSION=\"2\"\n INFO global: VAGRANT_OLD_ENV_VAGRANT_LOG=\"debug\"\n INFO global: VAGRANT_OLD_ENV_TMPDIR=\"/var/folders/1t/t94brwgx7sjcn8jgz4gr3_c00000gq/T/\"\n INFO global: VAGRANT_OLD_ENV_Apple_PubSub_Socket_Render=\"/private/tmp/com.apple.launchd.KW13obTzd8/Render\"\n INFO global: VAGRANT_OLD_ENV_JAVA_HOME=\"/Library/Java/JavaVirtualMachines/jdk1.7.0_45.jdk/Contents/Home\"\n INFO global: VAGRANT_OLD_ENV_ACHE_HOME=\"/Users/quasiben/anaconda/envs/memex-explorer/lib/python2.7/site-packages/ache/\"\n INFO global: VAGRANT_OLD_ENV_CONDA_ENV_PATH=\"/Users/quasiben/anaconda/envs/clusto\"\n INFO global: VAGRANT_OLD_ENV_PYTHONPATH=\"/Users/quasiben/Research/ContinuumDev/GitRepo/conda-cluster/::/Users/quasiben/Research/GitClones/spark/python\"\n INFO global: VAGRANT_OLD_ENV_PATH=\"/Users/quasiben/anaconda/envs/clusto/bin:/usr/local/bin:/usr/local/heroku/bin:/Users/quasiben/google-cloud-sdk/bin:/usr/local/sbin:/Users/quasiben/.cabal/bin/:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/texbin:/Users/quasiben/Research/ContinuumDev/GitRepo/libdynd/build\"\n INFO global: VAGRANT_OLD_ENV_PWD=\"/Users/quasiben\"\n INFO global: VAGRANT_OLD_ENV_ITERM_PROFILE=\"Default\"\n INFO global: VAGRANT_OLD_ENV_JDK_HOME=\"/Library/Java/JavaVirtualMachines/jdk1.7.0_45.jdk/Contents/Home/\"\n INFO global: VAGRANT_OLD_ENV_COLORFGBG=\"7;0\"\n INFO global: VAGRANT_OLD_ENV_CONDA_DEFAULT_ENV=\"clusto\"\n INFO global: VAGRANT_INSTALLER_ENV=\"1\"\n INFO global: VAGRANT_EXECUTABLE=\"/opt/vagrant/embedded/gems/gems/vagrant-1.7.4/bin/vagrant\"\n INFO global: VAGRANT_INSTALLER_EMBEDDED_DIR=\"/opt/vagrant/embedded\"\n INFO global: VAGRANT_OLD_ENV_COMMAND_MODE=\"unix2003\"\n INFO global: VAGRANT_OLD_ENV_SSH_AUTH_SOCK=\"/private/tmp/com.apple.launchd.CSjdOMPkpG/Listeners\"\n INFO global: VAGRANT_OLD_ENV_LANG=\"en_US.UTF-8\"\n INFO global: VAGRANT_OLD_ENV_TERM_PROGRAM=\"iTerm.app\"\n INFO global: VAGRANT_OLD_ENV_XPC_SERVICE_NAME=\"0\"\n INFO global: VAGRANT_OLD_ENV_SHLVL=\"1\"\n INFO global: VAGRANT_OLD_ENV_SECURITYSESSIONID=\"186a5\"\n INFO global: VAGRANT_OLD_ENV_TERM=\"xterm-color\"\n INFO global: VAGRANT_OLD_ENV_USER=\"quasiben\"\n INFO global: VAGRANT_OLD_ENV___CF_USER_TEXT_ENCODING=\"0x1F7:0x0:0x0\"\n INFO global: VAGRANT_OLD_ENV_ITERM_SESSION_ID=\"w0t1p0\"\n INFO global: VAGRANT_OLD_ENV_SHELL=\"/bin/bash\"\n INFO global: VAGRANT_OLD_ENV_PS1=\"(clusto)\\\\[\\\\033[01;32m\\\\]\\\\u@\\\\h\\\\[\\\\033[00m\\\\]:\\\\[\\\\033[01;36m\\\\]\\\\w\\\\[\\\\033[00m\\\\]\\\\$ \"\n INFO global: VAGRANT_OLD_ENV_OLDPWD=\"/Users/quasiben/Research/ContinuumDev/AC_AS_Vagrant/Head+Compute/test\"\n INFO global: VAGRANT_OLD_ENV_JRE_HOME=\"/Library/Java/JavaVirtualMachines/jdk1.7.0_45.jdk/Contents/Home/jre/\"\n INFO global: VAGRANT_OLD_ENV_LOGNAME=\"quasiben\"\n INFO global: VAGRANT_INTERNAL_BUNDLERIZED=\"1\"\n INFO global: Plugins:\n INFO global: - bundler = 1.10.5\n INFO global: - mime-types = 1.25.1\n INFO global: - rest-client = 1.6.9\n INFO global: - vagrant-share = 1.1.4\n INFO global: - vagrant-vmware-fusion = 4.0.2\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/box/plugin.rb\n INFO manager: Registered plugin: box command\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/destroy/plugin.rb\n INFO manager: Registered plugin: destroy command\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/global-status/plugin.rb\n INFO manager: Registered plugin: global-status command\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/halt/plugin.rb\n INFO manager: Registered plugin: halt command\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/help/plugin.rb\n INFO manager: Registered plugin: help command\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/init/plugin.rb\n INFO manager: Registered plugin: init command\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/list-commands/plugin.rb\n INFO manager: Registered plugin: list-commands command\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/login/plugin.rb\n INFO manager: Registered plugin: vagrant-login\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/package/plugin.rb\n INFO manager: Registered plugin: package command\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/plugin/plugin.rb\n INFO manager: Registered plugin: plugin command\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/provision/plugin.rb\n INFO manager: Registered plugin: provision command\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/push/plugin.rb\n INFO manager: Registered plugin: push command\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/rdp/plugin.rb\n INFO manager: Registered plugin: rdp command\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/reload/plugin.rb\n INFO manager: Registered plugin: reload command\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/resume/plugin.rb\n INFO manager: Registered plugin: resume command\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/ssh/plugin.rb\n INFO manager: Registered plugin: ssh command\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/ssh_config/plugin.rb\n INFO manager: Registered plugin: ssh-config command\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/status/plugin.rb\n INFO manager: Registered plugin: status command\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/suspend/plugin.rb\n INFO manager: Registered plugin: suspend command\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/up/plugin.rb\n INFO manager: Registered plugin: up command\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/commands/version/plugin.rb\n INFO manager: Registered plugin: version command\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/communicators/ssh/plugin.rb\n INFO manager: Registered plugin: ssh communicator\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/communicators/winrm/plugin.rb\n INFO manager: Registered plugin: winrm communicator\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/arch/plugin.rb\n INFO manager: Registered plugin: Arch guest\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/atomic/plugin.rb\n INFO manager: Registered plugin: Atomic Host guest\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/coreos/plugin.rb\n INFO manager: Registered plugin: CoreOS guest\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/darwin/plugin.rb\n INFO manager: Registered plugin: Darwin guest\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/debian/plugin.rb\n INFO manager: Registered plugin: Debian guest\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/debian8/plugin.rb\n INFO manager: Registered plugin: Debian Jessie guest\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/esxi/plugin.rb\n INFO manager: Registered plugin: ESXi guest.\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/fedora/plugin.rb\n INFO manager: Registered plugin: Fedora guest\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/freebsd/plugin.rb\n INFO manager: Registered plugin: FreeBSD guest\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/funtoo/plugin.rb\n INFO manager: Registered plugin: Funtoo guest\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/gentoo/plugin.rb\n INFO manager: Registered plugin: Gentoo guest\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/linux/plugin.rb\n INFO manager: Registered plugin: Linux guest.\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/mint/plugin.rb\n INFO manager: Registered plugin: Mint guest\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/netbsd/plugin.rb\n INFO manager: Registered plugin: NetBSD guest\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/nixos/plugin.rb\n INFO manager: Registered plugin: NixOS guest\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/omnios/plugin.rb\n INFO manager: Registered plugin: OmniOS guest.\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/openbsd/plugin.rb\n INFO manager: Registered plugin: OpenBSD guest\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/photon/plugin.rb\n INFO manager: Registered plugin: VMware Photon guest\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/pld/plugin.rb\n INFO manager: Registered plugin: PLD Linux guest\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/redhat/plugin.rb\n INFO manager: Registered plugin: Red Hat Enterprise Linux guest\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/smartos/plugin.rb\n INFO manager: Registered plugin: SmartOS guest.\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/solaris/plugin.rb\n INFO manager: Registered plugin: Solaris guest.\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/solaris11/plugin.rb\n INFO manager: Registered plugin: Solaris 11 guest.\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/suse/plugin.rb\n INFO manager: Registered plugin: SUSE guest\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/tinycore/plugin.rb\n INFO manager: Registered plugin: TinyCore Linux guest.\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/ubuntu/plugin.rb\n INFO manager: Registered plugin: Ubuntu guest\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/guests/windows/plugin.rb\n INFO manager: Registered plugin: Windows guest.\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/arch/plugin.rb\n INFO manager: Registered plugin: Arch host\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/bsd/plugin.rb\n INFO manager: Registered plugin: BSD host\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/darwin/plugin.rb\n INFO manager: Registered plugin: Mac OS X host\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/freebsd/plugin.rb\n INFO manager: Registered plugin: FreeBSD host\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/gentoo/plugin.rb\n INFO manager: Registered plugin: Gentoo host\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/linux/plugin.rb\n INFO manager: Registered plugin: Linux host\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/null/plugin.rb\n INFO manager: Registered plugin: null host\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/redhat/plugin.rb\n INFO manager: Registered plugin: Red Hat Enterprise Linux host\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/slackware/plugin.rb\n INFO manager: Registered plugin: Slackware host\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/suse/plugin.rb\n INFO manager: Registered plugin: SUSE host\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/hosts/windows/plugin.rb\n INFO manager: Registered plugin: Windows host\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/kernel_v1/plugin.rb\n INFO manager: Registered plugin: kernel\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/kernel_v2/plugin.rb\n INFO manager: Registered plugin: kernel\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/providers/docker/plugin.rb\n INFO manager: Registered plugin: docker-provider\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/providers/hyperv/plugin.rb\n INFO manager: Registered plugin: Hyper-V provider\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/providers/virtualbox/plugin.rb\n INFO manager: Registered plugin: VirtualBox provider\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/ansible/plugin.rb\n INFO manager: Registered plugin: ansible\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/cfengine/plugin.rb\n INFO manager: Registered plugin: CFEngine Provisioner\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/chef/plugin.rb\n INFO manager: Registered plugin: chef\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/docker/plugin.rb\n INFO manager: Registered plugin: docker\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/file/plugin.rb\n INFO manager: Registered plugin: file\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/puppet/plugin.rb\n INFO manager: Registered plugin: puppet\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/salt/plugin.rb\n INFO manager: Registered plugin: salt\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/provisioners/shell/plugin.rb\n INFO manager: Registered plugin: shell\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/pushes/atlas/plugin.rb\n INFO manager: Registered plugin: atlas\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/pushes/ftp/plugin.rb\n INFO manager: Registered plugin: ftp\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/pushes/heroku/plugin.rb\n INFO manager: Registered plugin: heroku\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/pushes/local-exec/plugin.rb\n INFO manager: Registered plugin: local-exec\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/pushes/noop/plugin.rb\n INFO manager: Registered plugin: noop\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/synced_folders/nfs/plugin.rb\n INFO manager: Registered plugin: NFS synced folders\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/synced_folders/rsync/plugin.rb\n INFO manager: Registered plugin: RSync synced folders\nDEBUG global: Loading core plugin: /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/plugins/synced_folders/smb/plugin.rb\n INFO manager: Registered plugin: SMB synced folders\n INFO manager: Registered plugin: VMware Fusion Provider\n INFO vmware_driver: VMX path is a directory. Finding VMX file...\n INFO vmware_driver: VMX file: /Users/quasiben/.vagrant/machines/dev/vmware_fusion/7890b8d8-98e2-4cd5-a989-d65c4e0279ae/trusty64.vmx\n INFO vmware_driver: Looking for VMware Fusion: /Applications/VMware Fusion.app\n INFO vmware_driver: VMware Fusion path: #<Pathname:/Applications/VMware Fusion.app>\nDEBUG vmware_driver: Attempting to read VMware version...\n INFO subprocess: Starting process: [\"/Applications/VMware Fusion.app/Contents/Library/vmware-vmx\", \"-v\"]\nDEBUG subprocess: Command not in installer, not touching env vars.\n INFO subprocess: Command is setuid/setgid, clearing DYLD_LIBRARY_PATH\n INFO subprocess: Command not in installer, restoring original environment...\nDEBUG subprocess: Selecting on IO\nDEBUG subprocess: stderr: \nVMware Fusion Information:\nVMware Fusion 7.1.0 build-2314774 Release\n\nDEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000\nDEBUG subprocess: Exit status: 0\n INFO vmware_driver: Detected VMware version: 7.1.0\nDEBUG vmware_driver: service starter path: /Applications/VMware Fusion.app/Contents/Library/services/Open VMware Fusion Services\nDEBUG vmware_driver: vmnet-cli path: /Applications/VMware Fusion.app/Contents/Library/vmnet-cli\n INFO vmware:sudo_helper: Calling command: create-vmnet-device\n INFO networking_file: Reading adapters from networking file...\nDEBUG networking_file: VNET: 1. KEY: 'DHCP' = 'yes'\nDEBUG networking_file: VNET: 1. KEY: 'DHCP_CFG_HASH' = 'D80210FE873BE2813B8C769A8E72B64979061717'\nDEBUG networking_file: VNET: 1. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'\nDEBUG networking_file: VNET: 1. KEY: 'HOSTONLY_SUBNET' = '192.168.27.0'\nDEBUG networking_file: VNET: 1. KEY: 'VIRTUAL_ADAPTER' = 'yes'\nDEBUG networking_file: VNET: 2. KEY: 'DHCP' = 'yes'\nDEBUG networking_file: VNET: 2. KEY: 'DHCP_CFG_HASH' = '87768080D35EC28F8A98E2922D0D6FE5E5C18A59'\nDEBUG networking_file: VNET: 2. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'\nDEBUG networking_file: VNET: 2. KEY: 'HOSTONLY_SUBNET' = '10.10.10.0'\nDEBUG networking_file: VNET: 2. KEY: 'VIRTUAL_ADAPTER' = 'yes'\nDEBUG networking_file: VNET: 3. KEY: 'DHCP' = 'yes'\nDEBUG networking_file: VNET: 3. KEY: 'DHCP_CFG_HASH' = '3EC4C96155C7AA76726042C1D3C8D9C208404144'\nDEBUG networking_file: VNET: 3. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'\nDEBUG networking_file: VNET: 3. KEY: 'HOSTONLY_SUBNET' = '192.168.18.0'\nDEBUG networking_file: VNET: 3. KEY: 'VIRTUAL_ADAPTER' = 'yes'\nDEBUG networking_file: VNET: 4. KEY: 'DHCP' = 'yes'\nDEBUG networking_file: VNET: 4. KEY: 'DHCP_CFG_HASH' = '6F6696B0E161F81ED0E3CE9F08794F4DD8D794EB'\nDEBUG networking_file: VNET: 4. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'\nDEBUG networking_file: VNET: 4. KEY: 'HOSTONLY_SUBNET' = '172.16.48.0'\nDEBUG networking_file: VNET: 4. KEY: 'VIRTUAL_ADAPTER' = 'yes'\nDEBUG networking_file: VNET: 5. KEY: 'DHCP' = 'yes'\nDEBUG networking_file: VNET: 5. KEY: 'DHCP_CFG_HASH' = '9B81D6F11FF984546E1C4E2B438F14AC3B559373'\nDEBUG networking_file: VNET: 5. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'\nDEBUG networking_file: VNET: 5. KEY: 'HOSTONLY_SUBNET' = '192.168.111.0'\nDEBUG networking_file: VNET: 5. KEY: 'VIRTUAL_ADAPTER' = 'yes'\nDEBUG networking_file: VNET: 8. KEY: 'DHCP' = 'yes'\nDEBUG networking_file: VNET: 8. KEY: 'DHCP_CFG_HASH' = '1BDC60FCCCD2EEB9E6AA5D403BE51F90BF3ACC00'\nDEBUG networking_file: VNET: 8. KEY: 'HOSTONLY_NETMASK' = '255.255.255.0'\nDEBUG networking_file: VNET: 8. KEY: 'HOSTONLY_SUBNET' = '192.168.186.0'\nDEBUG networking_file: VNET: 8. KEY: 'NAT' = 'yes'\nDEBUG networking_file: VNET: 8. KEY: 'VIRTUAL_ADAPTER' = 'yes'\nDEBUG networking_file: Pruning adapters that aren't actually active...\n INFO vmware_driver: Starting services starter and waiting for them to start...\n INFO vmware_driver: Killing vmnet-natd if it is alive...\n INFO subprocess: Starting process: [\"/usr/bin/pkill\", \"vmnet-natd\"]\nDEBUG subprocess: Command not in installer, not touching env vars.\n INFO subprocess: Command not in installer, restoring original environment...\nDEBUG subprocess: Selecting on IO\nDEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000\nDEBUG subprocess: Exit status: 0\n INFO subprocess: Starting process: [\"/Applications/VMware Fusion.app/Contents/Library/vmnet-cli\", \"--start\"]\nDEBUG subprocess: Command not in installer, not touching env vars.\n INFO subprocess: Command not in installer, restoring original environment...\nDEBUG subprocess: Selecting on IO\nDEBUG subprocess: stderr: Failed to start DHCP service on vmnet6\nDEBUG subprocess: stderr: Failed to start some/all services\nDEBUG subprocess: stdout: Enabled hostonly virtual adapter on vmnet1\nStarted DHCP service on vmnet1\nEnabled hostonly virtual adapter on vmnet2\nStarted DHCP service on vmnet2\nEnabled hostonly virtual adapter on vmnet3\nStarted DHCP service on vmnet3\nEnabled hostonly virtual adapter on vmnet4\nStarted DHCP service on vmnet4\nEnabled hostonly virtual adapter on vmnet5\nStarted DHCP service on vmnet5\nEnabled hostonly virtual adapter on vmnet6\nStarted NAT service on vmnet8\nEnabled hostonly virtual adapter on vmnet8\nStarted DHCP service on vmnet8\nDEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000\nDEBUG subprocess: Exit status: 1\n INFO subprocess: Starting process: [\"/Applications/VMware Fusion.app/Contents/Library/vmnet-cli\", \"--status\"]\nDEBUG subprocess: Command not in installer, not touching env vars.\n INFO subprocess: Command not in installer, restoring original environment...\nDEBUG subprocess: Selecting on IO\nDEBUG subprocess: stderr: Some/All of the configured services are not running\nDEBUG subprocess: stdout: DHCP service on vmnet1 is running\nHostonly virtual adapter on vmnet1 is enabled\nDHCP service on vmnet2 is running\nHostonly virtual adapter on vmnet2 is enabled\nDHCP service on vmnet3 is running\nHostonly virtual adapter on vmnet3 is enabled\nDHCP service on vmnet4 is running\nHostonly virtual adapter on vmnet4 is enabled\nDHCP service on vmnet5 is running\nHostonly virtual adapter on vmnet5 is enabled\nDHCP service on vmnet6 is not running\nHostonly virtual adapter on vmnet6 is enabled\nDHCP service on vmnet8 is running\nNAT service on vmnet8 is running\nHostonly virtual adapter on vmnet8 is enabled\nDEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000\nDEBUG subprocess: Exit status: 1\n INFO retryable: Retryable exception raised: #<HashiCorp::VagrantVMwarefusion::Errors::VMNetDevicesWontStart: The VMware \"vmnet\" devices are failing to start. The most common\nreason for this is collisions with existing network services. For\nexample, if a hostonly network space collides with another hostonly\nnetwork (such as with VirtualBox), it will fail to start. Likewise,\nif forwarded ports collide with other listening ports, it will\nfail to start.\n\nVagrant does its best to fix these issues, but in some cases it\ncannot determine the root cause of these failures.\n\nPlease verify you have no other colliding network services running.\nAs a last resort, restarting your computer often fixes this issue.>\n INFO vmware_driver: Killing vmnet-natd if it is alive...\n INFO subprocess: Starting process: [\"/usr/bin/pkill\", \"vmnet-natd\"]\nDEBUG subprocess: Command not in installer, not touching env vars.\n INFO subprocess: Command not in installer, restoring original environment...\nDEBUG subprocess: Selecting on IO\nDEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000\nDEBUG subprocess: Exit status: 0\n INFO subprocess: Starting process: [\"/Applications/VMware Fusion.app/Contents/Library/vmnet-cli\", \"--start\"]\nDEBUG subprocess: Command not in installer, not touching env vars.\n INFO subprocess: Command not in installer, restoring original environment...\nDEBUG subprocess: Selecting on IO\nDEBUG subprocess: stderr: Failed to start DHCP service on vmnet6\nDEBUG subprocess: stderr: Failed to start some/all services\nDEBUG subprocess: stdout: Enabled hostonly virtual adapter on vmnet1\nStarted DHCP service on vmnet1\nEnabled hostonly virtual adapter on vmnet2\nStarted DHCP service on vmnet2\nEnabled hostonly virtual adapter on vmnet3\nStarted DHCP service on vmnet3\nEnabled hostonly virtual adapter on vmnet4\nStarted DHCP service on vmnet4\nEnabled hostonly virtual adapter on vmnet5\nStarted DHCP service on vmnet5\nEnabled hostonly virtual adapter on vmnet6\nStarted NAT service on vmnet8\nEnabled hostonly virtual adapter on vmnet8\nStarted DHCP service on vmnet8\nDEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000\nDEBUG subprocess: Exit status: 1\n INFO subprocess: Starting process: [\"/Applications/VMware Fusion.app/Contents/Library/vmnet-cli\", \"--status\"]\nDEBUG subprocess: Command not in installer, not touching env vars.\n INFO subprocess: Command not in installer, restoring original environment...\nDEBUG subprocess: Selecting on IO\nDEBUG subprocess: stderr: Some/All of the configured services are not running\nDEBUG subprocess: stdout: DHCP service on vmnet1 is running\nHostonly virtual adapter on vmnet1 is enabled\nDHCP service on vmnet2 is running\nHostonly virtual adapter on vmnet2 is enabled\nDHCP service on vmnet3 is running\nHostonly virtual adapter on vmnet3 is enabled\nDHCP service on vmnet4 is running\nHostonly virtual adapter on vmnet4 is enabled\nDHCP service on vmnet5 is running\nHostonly virtual adapter on vmnet5 is enabled\nDHCP service on vmnet6 is not running\nHostonly virtual adapter on vmnet6 is enabled\nDHCP service on vmnet8 is running\nNAT service on vmnet8 is running\nHostonly virtual adapter on vmnet8 is enabled\nDEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000\nDEBUG subprocess: Exit status: 1\n INFO retryable: Retryable exception raised: #<HashiCorp::VagrantVMwarefusion::Errors::VMNetDevicesWontStart: The VMware \"vmnet\" devices are failing to start. The most common\nreason for this is collisions with existing network services. For\nexample, if a hostonly network space collides with another hostonly\nnetwork (such as with VirtualBox), it will fail to start. Likewise,\nif forwarded ports collide with other listening ports, it will\nfail to start.\n\nVagrant does its best to fix these issues, but in some cases it\ncannot determine the root cause of these failures.\n\nPlease verify you have no other colliding network services running.\nAs a last resort, restarting your computer often fixes this issue.>\n INFO vmware_driver: Killing vmnet-natd if it is alive...\n INFO subprocess: Starting process: [\"/usr/bin/pkill\", \"vmnet-natd\"]\nDEBUG subprocess: Command not in installer, not touching env vars.\n INFO subprocess: Command not in installer, restoring original environment...\nDEBUG subprocess: Selecting on IO\nDEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000\nDEBUG subprocess: Exit status: 0\n INFO subprocess: Starting process: [\"/Applications/VMware Fusion.app/Contents/Library/vmnet-cli\", \"--start\"]\nDEBUG subprocess: Command not in installer, not touching env vars.\n INFO subprocess: Command not in installer, restoring original environment...\nDEBUG subprocess: Selecting on IO\nDEBUG subprocess: stderr: Failed to start DHCP service on vmnet6\nDEBUG subprocess: stderr: Failed to start some/all services\nDEBUG subprocess: stdout: Enabled hostonly virtual adapter on vmnet1\nStarted DHCP service on vmnet1\nEnabled hostonly virtual adapter on vmnet2\nStarted DHCP service on vmnet2\nEnabled hostonly virtual adapter on vmnet3\nStarted DHCP service on vmnet3\nEnabled hostonly virtual adapter on vmnet4\nStarted DHCP service on vmnet4\nEnabled hostonly virtual adapter on vmnet5\nStarted DHCP service on vmnet5\nEnabled hostonly virtual adapter on vmnet6\nStarted NAT service on vmnet8\nEnabled hostonly virtual adapter on vmnet8\nStarted DHCP service on vmnet8\nDEBUG subprocess: Waiting for process to exit. Remaining to timeout: 31999\nDEBUG subprocess: Exit status: 1\n INFO subprocess: Starting process: [\"/Applications/VMware Fusion.app/Contents/Library/vmnet-cli\", \"--status\"]\nDEBUG subprocess: Command not in installer, not touching env vars.\n INFO subprocess: Command not in installer, restoring original environment...\nDEBUG subprocess: Selecting on IO\nDEBUG subprocess: stderr: Some/All of the configured services are not running\nDEBUG subprocess: stdout: DHCP service on vmnet1 is running\nHostonly virtual adapter on vmnet1 is enabled\nDHCP service on vmnet2 is running\nHostonly virtual adapter on vmnet2 is enabled\nDHCP service on vmnet3 is running\nHostonly virtual adapter on vmnet3 is enabled\nDHCP service on vmnet4 is running\nHostonly virtual adapter on vmnet4 is enabled\nDHCP service on vmnet5 is running\nHostonly virtual adapter on vmnet5 is enabled\nDHCP service on vmnet6 is not running\nHostonly virtual adapter on vmnet6 is enabled\nDHCP service on vmnet8 is running\nNAT service on vmnet8 is running\nHostonly virtual adapter on vmnet8 is enabled\nDEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000\nDEBUG subprocess: Exit status: 1\n INFO retryable: Retryable exception raised: #<HashiCorp::VagrantVMwarefusion::Errors::VMNetDevicesWontStart: The VMware \"vmnet\" devices are failing to start. The most common\nreason for this is collisions with existing network services. For\nexample, if a hostonly network space collides with another hostonly\nnetwork (such as with VirtualBox), it will fail to start. Likewise,\nif forwarded ports collide with other listening ports, it will\nfail to start.\n\nVagrant does its best to fix these issues, but in some cases it\ncannot determine the root cause of these failures.\n\nPlease verify you have no other colliding network services running.\nAs a last resort, restarting your computer often fixes this issue.>\n INFO vmware_driver: Killing vmnet-natd if it is alive...\n INFO subprocess: Starting process: [\"/usr/bin/pkill\", \"vmnet-natd\"]\nDEBUG subprocess: Command not in installer, not touching env vars.\n INFO subprocess: Command not in installer, restoring original environment...\nDEBUG subprocess: Selecting on IO\nDEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000\nDEBUG subprocess: Exit status: 0\n INFO subprocess: Starting process: [\"/Applications/VMware Fusion.app/Contents/Library/vmnet-cli\", \"--start\"]\nDEBUG subprocess: Command not in installer, not touching env vars.\n INFO subprocess: Command not in installer, restoring original environment...\nDEBUG subprocess: Selecting on IO\nDEBUG subprocess: stderr: Failed to start DHCP service on vmnet6\nDEBUG subprocess: stderr: Failed to start some/all services\nDEBUG subprocess: stdout: Enabled hostonly virtual adapter on vmnet1\nStarted DHCP service on vmnet1\nEnabled hostonly virtual adapter on vmnet2\nStarted DHCP service on vmnet2\nEnabled hostonly virtual adapter on vmnet3\nStarted DHCP service on vmnet3\nEnabled hostonly virtual adapter on vmnet4\nStarted DHCP service on vmnet4\nEnabled hostonly virtual adapter on vmnet5\nStarted DHCP service on vmnet5\nEnabled hostonly virtual adapter on vmnet6\nStarted NAT service on vmnet8\nEnabled hostonly virtual adapter on vmnet8\nStarted DHCP service on vmnet8\nDEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000\nDEBUG subprocess: Exit status: 1\n INFO subprocess: Starting process: [\"/Applications/VMware Fusion.app/Contents/Library/vmnet-cli\", \"--status\"]\nDEBUG subprocess: Command not in installer, not touching env vars.\n INFO subprocess: Command not in installer, restoring original environment...\nDEBUG subprocess: Selecting on IO\nDEBUG subprocess: stderr: Some/All of the configured services are not running\nDEBUG subprocess: stdout: DHCP service on vmnet1 is running\nHostonly virtual adapter on vmnet1 is enabled\nDHCP service on vmnet2 is running\nHostonly virtual adapter on vmnet2 is enabled\nDHCP service on vmnet3 is running\nHostonly virtual adapter on vmnet3 is enabled\nDHCP service on vmnet4 is running\nHostonly virtual adapter on vmnet4 is enabled\nDHCP service on vmnet5 is running\nHostonly virtual adapter on vmnet5 is enabled\nDHCP service on vmnet6 is not running\nHostonly virtual adapter on vmnet6 is enabled\nDHCP service on vmnet8 is running\nNAT service on vmnet8 is running\nHostonly virtual adapter on vmnet8 is enabled\nDEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000\nDEBUG subprocess: Exit status: 1\n INFO retryable: Retryable exception raised: #<HashiCorp::VagrantVMwarefusion::Errors::VMNetDevicesWontStart: The VMware \"vmnet\" devices are failing to start. The most common\nreason for this is collisions with existing network services. For\nexample, if a hostonly network space collides with another hostonly\nnetwork (such as with VirtualBox), it will fail to start. Likewise,\nif forwarded ports collide with other listening ports, it will\nfail to start.\n\nVagrant does its best to fix these issues, but in some cases it\ncannot determine the root cause of these failures.\n\nPlease verify you have no other colliding network services running.\nAs a last resort, restarting your computer often fixes this issue.>\n INFO vmware_driver: Killing vmnet-natd if it is alive...\n INFO subprocess: Starting process: [\"/usr/bin/pkill\", \"vmnet-natd\"]\nDEBUG subprocess: Command not in installer, not touching env vars.\n INFO subprocess: Command not in installer, restoring original environment...\nDEBUG subprocess: Selecting on IO\nDEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000\nDEBUG subprocess: Exit status: 0\n INFO subprocess: Starting process: [\"/Applications/VMware Fusion.app/Contents/Library/vmnet-cli\", \"--start\"]\nDEBUG subprocess: Command not in installer, not touching env vars.\n INFO subprocess: Command not in installer, restoring original environment...\nDEBUG subprocess: Selecting on IO\nDEBUG subprocess: stderr: Failed to start DHCP service on vmnet6\nDEBUG subprocess: stderr: Failed to start some/all services\nDEBUG subprocess: stdout: Enabled hostonly virtual adapter on vmnet1\nStarted DHCP service on vmnet1\nEnabled hostonly virtual adapter on vmnet2\nStarted DHCP service on vmnet2\nEnabled hostonly virtual adapter on vmnet3\nStarted DHCP service on vmnet3\nEnabled hostonly virtual adapter on vmnet4\nStarted DHCP service on vmnet4\nEnabled hostonly virtual adapter on vmnet5\nStarted DHCP service on vmnet5\nEnabled hostonly virtual adapter on vmnet6\nStarted NAT service on vmnet8\nEnabled hostonly virtual adapter on vmnet8\nStarted DHCP service on vmnet8\nDEBUG subprocess: Waiting for process to exit. Remaining to timeout: 31999\nDEBUG subprocess: Exit status: 1\n INFO subprocess: Starting process: [\"/Applications/VMware Fusion.app/Contents/Library/vmnet-cli\", \"--status\"]\nDEBUG subprocess: Command not in installer, not touching env vars.\n INFO subprocess: Command not in installer, restoring original environment...\nDEBUG subprocess: Selecting on IO\nDEBUG subprocess: stderr: Some/All of the configured services are not running\nDEBUG subprocess: stdout: DHCP service on vmnet1 is running\nHostonly virtual adapter on vmnet1 is enabled\nDHCP service on vmnet2 is running\nHostonly virtual adapter on vmnet2 is enabled\nDHCP service on vmnet3 is running\nHostonly virtual adapter on vmnet3 is enabled\nDHCP service on vmnet4 is running\nHostonly virtual adapter on vmnet4 is enabled\nDHCP service on vmnet5 is running\nHostonly virtual adapter on vmnet5 is enabled\nDHCP service on vmnet6 is not running\nHostonly virtual adapter on vmnet6 is enabled\nDHCP service on vmnet8 is running\nNAT service on vmnet8 is running\nHostonly virtual adapter on vmnet8 is enabled\nDEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000\nDEBUG subprocess: Exit status: 1\n INFO vmware_driver: Stopping services starter...\nThe VMware \"vmnet\" devices are failing to start. The most common\nreason for this is collisions with existing network services. For\nexample, if a hostonly network space collides with another hostonly\nnetwork (such as with VirtualBox), it will fail to start. Likewise,\nif forwarded ports collide with other listening ports, it will\nfail to start.\n\nVagrant does its best to fix these issues, but in some cases it\ncannot determine the root cause of these failures.\n\nPlease verify you have no other colliding network services running.\nAs a last resort, restarting your computer often fixes this issue."]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment