Created
July 25, 2013 20:22
-
-
Save joefitzgerald/6083383 to your computer and use it in GitHub Desktop.
Info Log Level For vagrant-windows Debugging
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| $ vagrant destroy --force | |
| [vagrant-windows] Stopping the VMware VM... | |
| [vagrant-windows] Deleting the VM... | |
| usxxfitzgj8m1:test joe$ VAGRANT_LOG=info vagrant up --provider=vmware_fusion | |
| INFO global: Vagrant version: 1.2.4 | |
| INFO manager: Registered plugin: box command | |
| INFO manager: Registered plugin: destroy command | |
| INFO manager: Registered plugin: halt command | |
| INFO manager: Registered plugin: init command | |
| INFO manager: Registered plugin: package command | |
| INFO manager: Registered plugin: plugin command | |
| INFO manager: Registered plugin: provision command | |
| INFO manager: Registered plugin: reload command | |
| INFO manager: Registered plugin: resume command | |
| INFO manager: Registered plugin: ssh command | |
| INFO manager: Registered plugin: ssh-config command | |
| INFO manager: Registered plugin: status command | |
| INFO manager: Registered plugin: suspend command | |
| INFO manager: Registered plugin: up command | |
| INFO manager: Registered plugin: ssh communicator | |
| INFO manager: Registered plugin: Arch guest | |
| INFO manager: Registered plugin: Debian guest | |
| INFO manager: Registered plugin: Fedora guest | |
| INFO manager: Registered plugin: FreeBSD guest | |
| INFO manager: Registered plugin: Gentoo guest | |
| INFO manager: Registered plugin: Linux guest. | |
| INFO manager: Registered plugin: OmniOS guest. | |
| INFO manager: Registered plugin: OpenBSD guest | |
| INFO manager: Registered plugin: PLD Linux guest | |
| INFO manager: Registered plugin: RedHat guest | |
| INFO manager: Registered plugin: Solaris guest. | |
| INFO manager: Registered plugin: SUSE guest | |
| INFO manager: Registered plugin: Ubuntu guest | |
| INFO manager: Registered plugin: Arch host | |
| INFO manager: Registered plugin: BSD host | |
| INFO manager: Registered plugin: Fedora host | |
| INFO manager: Registered plugin: FreeBSD host | |
| INFO manager: Registered plugin: Gentoo host | |
| INFO manager: Registered plugin: Linux host | |
| INFO manager: Registered plugin: OpenSUSE host | |
| INFO manager: Registered plugin: Windows host | |
| INFO manager: Registered plugin: kernel | |
| INFO manager: Registered plugin: kernel | |
| INFO manager: Registered plugin: VirtualBox provider | |
| INFO manager: Registered plugin: ansible | |
| INFO manager: Registered plugin: CFEngine Provisioner | |
| INFO manager: Registered plugin: chef | |
| INFO manager: Registered plugin: puppet | |
| INFO manager: Registered plugin: shell | |
| INFO vagrant: `vagrant` invoked: ["up", "--provider=vmware_fusion"] | |
| INFO environment: Environment initialized (#<Vagrant::Environment:0x0000010190a9c8>) | |
| INFO environment: - cwd: /Users/joe/Projects/test | |
| INFO environment: Home path: /Users/joe/.vagrant.d | |
| INFO environment: Local data path: /Users/joe/Projects/test/.vagrant | |
| INFO environment: Loading plugin from JSON: vagrant-vmware-fusion | |
| INFO manager: Registered plugin: VMware Fusion Provider | |
| INFO environment: Loading plugin from JSON: vagrant-windows | |
| INFO manager: Registered plugin: Windows guest | |
| INFO environment: Running hook: environment_load | |
| INFO environment: Initializing config... | |
| INFO loader: Set :default = "/Applications/Vagrant/embedded/gems/gems/vagrant-1.2.4/config/default.rb" | |
| INFO loader: Set :root = #<Pathname:/Users/joe/Projects/test/Vagrantfile> | |
| INFO loader: Loading configuration in order: [:default, :home, :root] | |
| INFO hosts: Host class: VagrantPlugins::HostBSD::Host | |
| INFO runner: Preparing hooks for middleware sequence... | |
| INFO runner: 1 hooks defined. | |
| INFO runner: Running action: #<Vagrant::Action::Builder:0x000001030c6008> | |
| INFO warden: Calling action: #<HashiCorp::VagrantVMwarefusion::SetupPlugin:0x0000010307f838> | |
| INFO warden: Calling action: HashiCorp Background Check: Start | |
| INFO cli: CLI: [] "up" ["--provider=vmware_fusion"] | |
| INFO environment: Getting machine: vagrant-windows (vmware_fusion) | |
| INFO environment: Uncached load of machine. | |
| INFO loader: Set :"vm_vagrant-windows" = [] | |
| INFO loader: Loading configuration in order: [:default, :home, :root, :"vm_vagrant-windows"] | |
| INFO environment: Provider-supported box formats: ["vmware_desktop", "vmware_fusion", "vmware_workstation"] | |
| INFO box_collection: Searching for box: windows2008r2 (vmware_desktop) in /Users/joe/.vagrant.d/boxes/windows2008r2/vmware_desktop/metadata.json | |
| INFO box_collection: Box found: windows2008r2 (vmware_desktop) | |
| INFO environment: Box found with format: vmware_desktop | |
| INFO environment: Box exists with Vagrantfile. Reloading machine config. | |
| INFO loader: Set :box_windows2008r2_vmware_desktop = #<Pathname:/Users/joe/.vagrant.d/boxes/windows2008r2/vmware_desktop/Vagrantfile> | |
| INFO loader: Loading configuration in order: [:default, :box_windows2008r2_vmware_desktop, :home, :root, :"vm_vagrant-windows"] | |
| INFO environment: Applying 2 provider overrides. Reloading config. | |
| INFO loader: Set :"vm_vagrant-windows_windows2008r2_vmware_fusion" = [["2", #<Proc:0x00000103257b60>], ["2", #<Proc:0x000001032540f0>]] | |
| INFO loader: Loading configuration in order: [:default, :box_windows2008r2_vmware_desktop, :home, :root, :"vm_vagrant-windows", :"vm_vagrant-windows_windows2008r2_vmware_fusion"] | |
| INFO machine: Initializing machine: vagrant-windows | |
| INFO machine: - Provider: HashiCorp::VagrantVMwarefusion::Provider | |
| INFO machine: - Box: #<Vagrant::Box:0x00000103274f80> | |
| INFO machine: - Data dir: /Users/joe/Projects/test/.vagrant/machines/vagrant-windows/vmware_fusion | |
| 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> | |
| INFO command: With machine: vagrant-windows (VMware Fusion) | |
| INFO interface: info: Bringing machine 'vagrant-windows' up with 'vmware_fusion' provider... | |
| Bringing machine 'vagrant-windows' up with 'vmware_fusion' provider... | |
| 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:0x000001032341d8> up {:parallel=>true, :provision_enabled=>true, :provision_types=>nil, :provider=>"vmware_fusion"} | |
| INFO machine: Calling action: up on provider VMware Fusion | |
| INFO runner: Running action: #<Vagrant::Action::Builder:0x00000102813d20> | |
| INFO warden: Calling action: #<Vagrant::Action::Builtin::ConfigValidate:0x00000102915598> | |
| INFO warden: Calling action: VMware Middleware: FixOldMachineID | |
| INFO warden: Calling action: VMware Middleware: CheckVMware | |
| INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmware-vmx", "-v"] | |
| INFO vmware_driver: Detected VMware version: 5.0.3 | |
| INFO warden: Calling action: VMware Middleware: MachineLock | |
| INFO lock: Locking: /Users/joe/Projects/test/.vagrant/machines/vagrant-windows/vmware_fusion/lock | |
| INFO warden: Calling action: VMware Middleware: SudoHelperInstall | |
| INFO sudo_helper: Sudo helper bin path: /Users/joe/.vagrant.d/gems/gems/vagrant-vmware-fusion-0.8.2/bin/vagrant_vmware_desktop_sudo_helper_wrapper_darwin_amd64 | |
| INFO warden: Calling action: #<Vagrant::Action::Builtin::Call:0x00000102a56b78> | |
| INFO runner: Running action: #<Vagrant::Action::Builder:0x000001031f6428> | |
| INFO warden: Calling action: VMware Middleware: Created | |
| INFO runner: Running action: #<Vagrant::Action::Warden:0x00000103253268> | |
| INFO warden: Calling action: #<Vagrant::Action::Builtin::HandleBoxUrl:0x000001032531a0> | |
| INFO handle_box_url: Skipping HandleBoxUrl because box or box_url not set. | |
| INFO warden: Calling action: VMware Middleware: Import | |
| INFO import: VMX file not in metadata, attempting to discover... | |
| INFO import: VMX file: /Users/joe/.vagrant.d/boxes/windows2008r2/vmware_desktop/packer-vmware.vmx | |
| INFO interface: info: Cloning VMware VM: 'windows2008r2'. This can take some time... | |
| [vagrant-windows] Cloning VMware VM: 'windows2008r2'. This can take some time... | |
| INFO vmware_driver: Cloning VM to /Users/joe/Projects/test/.vagrant/machines/vagrant-windows/vmware_fusion/222fd591-f0bc-4c8d-953f-c86110f7db17 | |
| INFO vmware_driver: VMX file: /Users/joe/Projects/test/.vagrant/machines/vagrant-windows/vmware_fusion/222fd591-f0bc-4c8d-953f-c86110f7db17/packer-vmware.vmx | |
| INFO vmware_driver: Looking for VMware Fusion: /Applications/VMware Fusion.app | |
| INFO vmware_driver: VMware Fusion path: #<Pathname:/Applications/VMware Fusion.app> | |
| INFO vmware_driver: Reading VMX data... | |
| INFO vmware_driver: Modifying VMX data... | |
| INFO machine: New machine ID: "/Users/joe/Projects/test/.vagrant/machines/vagrant-windows/vmware_fusion/222fd591-f0bc-4c8d-953f-c86110f7db17/packer-vmware.vmx" | |
| INFO vmware_driver: VMX file: /Users/joe/Projects/test/.vagrant/machines/vagrant-windows/vmware_fusion/222fd591-f0bc-4c8d-953f-c86110f7db17/packer-vmware.vmx | |
| INFO vmware_driver: Looking for VMware Fusion: /Applications/VMware Fusion.app | |
| INFO vmware_driver: VMware Fusion path: #<Pathname:/Applications/VMware Fusion.app> | |
| INFO warden: Calling action: VMware Middleware: SetDisplayName | |
| INFO vmx_modify: Setting the default display name: test: vagrant-windows | |
| INFO vmware_driver: Reading VMX data... | |
| INFO vmware_driver: Modifying VMX data... | |
| INFO warden: Calling action: VMware Middleware: FixOldMachineID | |
| INFO warden: Calling action: VMware Middleware: SudoHelperInstall | |
| INFO sudo_helper: Sudo helper bin path: /Users/joe/.vagrant.d/gems/gems/vagrant-vmware-fusion-0.8.2/bin/vagrant_vmware_desktop_sudo_helper_wrapper_darwin_amd64 | |
| INFO warden: Calling action: #<Vagrant::Action::Builtin::Call:0x00000103149bd8> | |
| INFO runner: Running action: #<Vagrant::Action::Builder:0x00000102910278> | |
| INFO warden: Calling action: VMware Middleware: Running | |
| INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmrun", "list"] | |
| INFO runner: Running action: #<Vagrant::Action::Warden:0x00000102a1e390> | |
| INFO warden: Calling action: VMware Middleware: PruneForwardedPorts | |
| INFO prune_forwarded_ports: Pruning forwarded ports... | |
| INFO subprocess: Starting process: ["/Users/joe/.vagrant.d/gems/gems/vagrant-vmware-fusion-0.8.2/bin/vagrant_vmware_desktop_sudo_helper_wrapper_darwin_amd64", "prune-forwarded-ports", "/var/folders/76/_jwgdgxj64z4w5m3s87nyc000000gn/T/vagrant-sudo-helper20130725-6152-18o1sft"] | |
| INFO warden: Calling action: VMware Middleware: CheckExistingNetwork | |
| INFO check_existing_network: Checking if the vmnet devices are healthy... | |
| INFO interface: info: Verifying vmnet devices are healthy... | |
| [vagrant-windows] Verifying vmnet devices are healthy... | |
| INFO subprocess: Starting process: ["/Users/joe/.vagrant.d/gems/gems/vagrant-vmware-fusion-0.8.2/bin/vagrant_vmware_desktop_sudo_helper_wrapper_darwin_amd64", "verify-vmnet", "/var/folders/76/_jwgdgxj64z4w5m3s87nyc000000gn/T/vagrant-sudo-helper20130725-6152-1g3kd3w"] | |
| ERROR warden: Error occurred: INFO global: Vagrant version: 1.2.4 | |
| INFO manager: Registered plugin: box command | |
| INFO manager: Registered plugin: destroy command | |
| INFO manager: Registered plugin: halt command | |
| INFO manager: Registered plugin: init command | |
| INFO manager: Registered plugin: package command | |
| INFO manager: Registered plugin: plugin command | |
| INFO manager: Registered plugin: provision command | |
| INFO manager: Registered plugin: reload command | |
| INFO manager: Registered plugin: resume command | |
| INFO manager: Registered plugin: ssh command | |
| INFO manager: Registered plugin: ssh-config command | |
| INFO manager: Registered plugin: status command | |
| INFO manager: Registered plugin: suspend command | |
| INFO manager: Registered plugin: up command | |
| INFO manager: Registered plugin: ssh communicator | |
| INFO manager: Registered plugin: Arch guest | |
| INFO manager: Registered plugin: Debian guest | |
| INFO manager: Registered plugin: Fedora guest | |
| INFO manager: Registered plugin: FreeBSD guest | |
| INFO manager: Registered plugin: Gentoo guest | |
| INFO manager: Registered plugin: Linux guest. | |
| INFO manager: Registered plugin: OmniOS guest. | |
| INFO manager: Registered plugin: OpenBSD guest | |
| INFO manager: Registered plugin: PLD Linux guest | |
| INFO manager: Registered plugin: RedHat guest | |
| INFO manager: Registered plugin: Solaris guest. | |
| INFO manager: Registered plugin: SUSE guest | |
| INFO manager: Registered plugin: Ubuntu guest | |
| INFO manager: Registered plugin: Arch host | |
| INFO manager: Registered plugin: BSD host | |
| INFO manager: Registered plugin: Fedora host | |
| INFO manager: Registered plugin: FreeBSD host | |
| INFO manager: Registered plugin: Gentoo host | |
| INFO manager: Registered plugin: Linux host | |
| INFO manager: Registered plugin: OpenSUSE host | |
| INFO manager: Registered plugin: Windows host | |
| INFO manager: Registered plugin: kernel | |
| INFO manager: Registered plugin: kernel | |
| INFO manager: Registered plugin: VirtualBox provider | |
| INFO manager: Registered plugin: ansible | |
| INFO manager: Registered plugin: CFEngine Provisioner | |
| INFO manager: Registered plugin: chef | |
| INFO manager: Registered plugin: puppet | |
| INFO manager: Registered plugin: shell | |
| INFO manager: Registered plugin: VMware Fusion Provider | |
| 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> | |
| INFO vmware:sudo_helper: Calling command: verify-vmnet | |
| INFO vmware_driver: Starting services starter and waiting for them to start... | |
| INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"] | |
| 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 subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"] | |
| 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 subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"] | |
| 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 subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"] | |
| 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 subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"] | |
| INFO vmware_driver: Stopping services starter... | |
| WARN vmware_driver: vmnet devices are NOT healthy. Attempting to fix. | |
| INFO vmware_driver: vmnet-bridge appears to be alive, killing it (pid 5768) | |
| INFO subprocess: Starting process: ["/bin/kill", "5768"] | |
| INFO vmware_driver: Stopping vmnet-* devices | |
| INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--stop"] | |
| INFO vmware_driver: Reconfiguring vmnet-* devices | |
| INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--configure"] | |
| INFO vmware_driver: Starting services starter and waiting for them to start... | |
| INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"] | |
| 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 subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"] | |
| 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 subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"] | |
| 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 subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"] | |
| 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 subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"] | |
| 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. | |
| ERROR warden: Error occurred: INFO global: Vagrant version: 1.2.4 | |
| INFO manager: Registered plugin: box command | |
| INFO manager: Registered plugin: destroy command | |
| INFO manager: Registered plugin: halt command | |
| INFO manager: Registered plugin: init command | |
| INFO manager: Registered plugin: package command | |
| INFO manager: Registered plugin: plugin command | |
| INFO manager: Registered plugin: provision command | |
| INFO manager: Registered plugin: reload command | |
| INFO manager: Registered plugin: resume command | |
| INFO manager: Registered plugin: ssh command | |
| INFO manager: Registered plugin: ssh-config command | |
| INFO manager: Registered plugin: status command | |
| INFO manager: Registered plugin: suspend command | |
| INFO manager: Registered plugin: up command | |
| INFO manager: Registered plugin: ssh communicator | |
| INFO manager: Registered plugin: Arch guest | |
| INFO manager: Registered plugin: Debian guest | |
| INFO manager: Registered plugin: Fedora guest | |
| INFO manager: Registered plugin: FreeBSD guest | |
| INFO manager: Registered plugin: Gentoo guest | |
| INFO manager: Registered plugin: Linux guest. | |
| INFO manager: Registered plugin: OmniOS guest. | |
| INFO manager: Registered plugin: OpenBSD guest | |
| INFO manager: Registered plugin: PLD Linux guest | |
| INFO manager: Registered plugin: RedHat guest | |
| INFO manager: Registered plugin: Solaris guest. | |
| INFO manager: Registered plugin: SUSE guest | |
| INFO manager: Registered plugin: Ubuntu guest | |
| INFO manager: Registered plugin: Arch host | |
| INFO manager: Registered plugin: BSD host | |
| INFO manager: Registered plugin: Fedora host | |
| INFO manager: Registered plugin: FreeBSD host | |
| INFO manager: Registered plugin: Gentoo host | |
| INFO manager: Registered plugin: Linux host | |
| INFO manager: Registered plugin: OpenSUSE host | |
| INFO manager: Registered plugin: Windows host | |
| INFO manager: Registered plugin: kernel | |
| INFO manager: Registered plugin: kernel | |
| INFO manager: Registered plugin: VirtualBox provider | |
| INFO manager: Registered plugin: ansible | |
| INFO manager: Registered plugin: CFEngine Provisioner | |
| INFO manager: Registered plugin: chef | |
| INFO manager: Registered plugin: puppet | |
| INFO manager: Registered plugin: shell | |
| INFO manager: Registered plugin: VMware Fusion Provider | |
| 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> | |
| INFO vmware:sudo_helper: Calling command: verify-vmnet | |
| INFO vmware_driver: Starting services starter and waiting for them to start... | |
| INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"] | |
| 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 subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"] | |
| 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 subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"] | |
| 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 subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"] | |
| 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 subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"] | |
| INFO vmware_driver: Stopping services starter... | |
| WARN vmware_driver: vmnet devices are NOT healthy. Attempting to fix. | |
| INFO vmware_driver: vmnet-bridge appears to be alive, killing it (pid 5768) | |
| INFO subprocess: Starting process: ["/bin/kill", "5768"] | |
| INFO vmware_driver: Stopping vmnet-* devices | |
| INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--stop"] | |
| INFO vmware_driver: Reconfiguring vmnet-* devices | |
| INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--configure"] | |
| INFO vmware_driver: Starting services starter and waiting for them to start... | |
| INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"] | |
| 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 subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"] | |
| 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 subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"] | |
| 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 subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"] | |
| 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 subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"] | |
| 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:0x00000103149bd8> | |
| 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"] | |
| 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.2.4 | |
| INFO manager: Registered plugin: box command | |
| INFO manager: Registered plugin: destroy command | |
| INFO manager: Registered plugin: halt command | |
| INFO manager: Registered plugin: init command | |
| INFO manager: Registered plugin: package command | |
| INFO manager: Registered plugin: plugin command | |
| INFO manager: Registered plugin: provision command | |
| INFO manager: Registered plugin: reload command | |
| INFO manager: Registered plugin: resume command | |
| INFO manager: Registered plugin: ssh command | |
| INFO manager: Registered plugin: ssh-config command | |
| INFO manager: Registered plugin: status command | |
| INFO manager: Registered plugin: suspend command | |
| INFO manager: Registered plugin: up command | |
| INFO manager: Registered plugin: ssh communicator | |
| INFO manager: Registered plugin: Arch guest | |
| INFO manager: Registered plugin: Debian guest | |
| INFO manager: Registered plugin: Fedora guest | |
| INFO manager: Registered plugin: FreeBSD guest | |
| INFO manager: Registered plugin: Gentoo guest | |
| INFO manager: Registered plugin: Linux guest. | |
| INFO manager: Registered plugin: OmniOS guest. | |
| INFO manager: Registered plugin: OpenBSD guest | |
| INFO manager: Registered plugin: PLD Linux guest | |
| INFO manager: Registered plugin: RedHat guest | |
| INFO manager: Registered plugin: Solaris guest. | |
| INFO manager: Registered plugin: SUSE guest | |
| INFO manager: Registered plugin: Ubuntu guest | |
| INFO manager: Registered plugin: Arch host | |
| INFO manager: Registered plugin: BSD host | |
| INFO manager: Registered plugin: Fedora host | |
| INFO manager: Registered plugin: FreeBSD host | |
| INFO manager: Registered plugin: Gentoo host | |
| INFO manager: Registered plugin: Linux host | |
| INFO manager: Registered plugin: OpenSUSE host | |
| INFO manager: Registered plugin: Windows host | |
| INFO manager: Registered plugin: kernel | |
| INFO manager: Registered plugin: kernel | |
| INFO manager: Registered plugin: VirtualBox provider | |
| INFO manager: Registered plugin: ansible | |
| INFO manager: Registered plugin: CFEngine Provisioner | |
| INFO manager: Registered plugin: chef | |
| INFO manager: Registered plugin: puppet | |
| INFO manager: Registered plugin: shell | |
| INFO manager: Registered plugin: VMware Fusion Provider | |
| 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> | |
| INFO vmware:sudo_helper: Calling command: verify-vmnet | |
| INFO vmware_driver: Starting services starter and waiting for them to start... | |
| INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"] | |
| 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 subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"] | |
| 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 subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"] | |
| 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 subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"] | |
| 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 subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"] | |
| INFO vmware_driver: Stopping services starter... | |
| WARN vmware_driver: vmnet devices are NOT healthy. Attempting to fix. | |
| INFO vmware_driver: vmnet-bridge appears to be alive, killing it (pid 5768) | |
| INFO subprocess: Starting process: ["/bin/kill", "5768"] | |
| INFO vmware_driver: Stopping vmnet-* devices | |
| INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--stop"] | |
| INFO vmware_driver: Reconfiguring vmnet-* devices | |
| INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--configure"] | |
| INFO vmware_driver: Starting services starter and waiting for them to start... | |
| INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"] | |
| 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 subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"] | |
| 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 subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"] | |
| 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 subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"] | |
| 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 subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"] | |
| 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:0x00000102a56b78> | |
| INFO warden: Beginning recovery process... | |
| INFO warden: Recovery complete. | |
| INFO warden: Recovery complete. | |
| INFO warden: Beginning recovery process... | |
| INFO warden: Recovery complete. | |
| INFO lock: Unlocking: /Users/joe/Projects/test/.vagrant/machines/vagrant-windows/vmware_fusion/lock | |
| 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: Running hook: environment_unload | |
| INFO runner: Preparing hooks for middleware sequence... | |
| INFO runner: 1 hooks defined. | |
| INFO runner: Running action: #<Vagrant::Action::Builder:0x00000103178b18> | |
| INFO warden: Calling action: HashiCorp Background Check: End | |
| INFO logger: Cleaning up background activation thread... | |
| ERROR vagrant: Vagrant experienced an error! Details: | |
| ERROR vagrant: #<HashiCorp::VagrantVMwarefusion::Errors::HelperFailed: INFO global: Vagrant version: 1.2.4 | |
| INFO manager: Registered plugin: box command | |
| INFO manager: Registered plugin: destroy command | |
| INFO manager: Registered plugin: halt command | |
| INFO manager: Registered plugin: init command | |
| INFO manager: Registered plugin: package command | |
| INFO manager: Registered plugin: plugin command | |
| INFO manager: Registered plugin: provision command | |
| INFO manager: Registered plugin: reload command | |
| INFO manager: Registered plugin: resume command | |
| INFO manager: Registered plugin: ssh command | |
| INFO manager: Registered plugin: ssh-config command | |
| INFO manager: Registered plugin: status command | |
| INFO manager: Registered plugin: suspend command | |
| INFO manager: Registered plugin: up command | |
| INFO manager: Registered plugin: ssh communicator | |
| INFO manager: Registered plugin: Arch guest | |
| INFO manager: Registered plugin: Debian guest | |
| INFO manager: Registered plugin: Fedora guest | |
| INFO manager: Registered plugin: FreeBSD guest | |
| INFO manager: Registered plugin: Gentoo guest | |
| INFO manager: Registered plugin: Linux guest. | |
| INFO manager: Registered plugin: OmniOS guest. | |
| INFO manager: Registered plugin: OpenBSD guest | |
| INFO manager: Registered plugin: PLD Linux guest | |
| INFO manager: Registered plugin: RedHat guest | |
| INFO manager: Registered plugin: Solaris guest. | |
| INFO manager: Registered plugin: SUSE guest | |
| INFO manager: Registered plugin: Ubuntu guest | |
| INFO manager: Registered plugin: Arch host | |
| INFO manager: Registered plugin: BSD host | |
| INFO manager: Registered plugin: Fedora host | |
| INFO manager: Registered plugin: FreeBSD host | |
| INFO manager: Registered plugin: Gentoo host | |
| INFO manager: Registered plugin: Linux host | |
| INFO manager: Registered plugin: OpenSUSE host | |
| INFO manager: Registered plugin: Windows host | |
| INFO manager: Registered plugin: kernel | |
| INFO manager: Registered plugin: kernel | |
| INFO manager: Registered plugin: VirtualBox provider | |
| INFO manager: Registered plugin: ansible | |
| INFO manager: Registered plugin: CFEngine Provisioner | |
| INFO manager: Registered plugin: chef | |
| INFO manager: Registered plugin: puppet | |
| INFO manager: Registered plugin: shell | |
| INFO manager: Registered plugin: VMware Fusion Provider | |
| 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> | |
| INFO vmware:sudo_helper: Calling command: verify-vmnet | |
| INFO vmware_driver: Starting services starter and waiting for them to start... | |
| INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"] | |
| 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 subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"] | |
| 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 subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"] | |
| 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 subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"] | |
| 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 subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"] | |
| INFO vmware_driver: Stopping services starter... | |
| WARN vmware_driver: vmnet devices are NOT healthy. Attempting to fix. | |
| INFO vmware_driver: vmnet-bridge appears to be alive, killing it (pid 5768) | |
| INFO subprocess: Starting process: ["/bin/kill", "5768"] | |
| INFO vmware_driver: Stopping vmnet-* devices | |
| INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--stop"] | |
| INFO vmware_driver: Reconfiguring vmnet-* devices | |
| INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--configure"] | |
| INFO vmware_driver: Starting services starter and waiting for them to start... | |
| INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"] | |
| 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 subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"] | |
| 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 subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"] | |
| 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 subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"] | |
| 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 subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"] | |
| 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.2.4 | |
| INFO manager: Registered plugin: box command | |
| INFO manager: Registered plugin: destroy command | |
| INFO manager: Registered plugin: halt command | |
| INFO manager: Registered plugin: init command | |
| INFO manager: Registered plugin: package command | |
| INFO manager: Registered plugin: plugin command | |
| INFO manager: Registered plugin: provision command | |
| INFO manager: Registered plugin: reload command | |
| INFO manager: Registered plugin: resume command | |
| INFO manager: Registered plugin: ssh command | |
| INFO manager: Registered plugin: ssh-config command | |
| INFO manager: Registered plugin: status command | |
| INFO manager: Registered plugin: suspend command | |
| INFO manager: Registered plugin: up command | |
| INFO manager: Registered plugin: ssh communicator | |
| INFO manager: Registered plugin: Arch guest | |
| INFO manager: Registered plugin: Debian guest | |
| INFO manager: Registered plugin: Fedora guest | |
| INFO manager: Registered plugin: FreeBSD guest | |
| INFO manager: Registered plugin: Gentoo guest | |
| INFO manager: Registered plugin: Linux guest. | |
| INFO manager: Registered plugin: OmniOS guest. | |
| INFO manager: Registered plugin: OpenBSD guest | |
| INFO manager: Registered plugin: PLD Linux guest | |
| INFO manager: Registered plugin: RedHat guest | |
| INFO manager: Registered plugin: Solaris guest. | |
| INFO manager: Registered plugin: SUSE guest | |
| INFO manager: Registered plugin: Ubuntu guest | |
| INFO manager: Registered plugin: Arch host | |
| INFO manager: Registered plugin: BSD host | |
| INFO manager: Registered plugin: Fedora host | |
| INFO manager: Registered plugin: FreeBSD host | |
| INFO manager: Registered plugin: Gentoo host | |
| INFO manager: Registered plugin: Linux host | |
| INFO manager: Registered plugin: OpenSUSE host | |
| INFO manager: Registered plugin: Windows host | |
| INFO manager: Registered plugin: kernel | |
| INFO manager: Registered plugin: kernel | |
| INFO manager: Registered plugin: VirtualBox provider | |
| INFO manager: Registered plugin: ansible | |
| INFO manager: Registered plugin: CFEngine Provisioner | |
| INFO manager: Registered plugin: chef | |
| INFO manager: Registered plugin: puppet | |
| INFO manager: Registered plugin: shell | |
| INFO manager: Registered plugin: VMware Fusion Provider | |
| 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> | |
| INFO vmware:sudo_helper: Calling command: verify-vmnet | |
| INFO vmware_driver: Starting services starter and waiting for them to start... | |
| INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"] | |
| 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 subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"] | |
| 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 subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"] | |
| 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 subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"] | |
| 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 subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"] | |
| INFO vmware_driver: Stopping services starter... | |
| WARN vmware_driver: vmnet devices are NOT healthy. Attempting to fix. | |
| INFO vmware_driver: vmnet-bridge appears to be alive, killing it (pid 5768) | |
| INFO subprocess: Starting process: ["/bin/kill", "5768"] | |
| INFO vmware_driver: Stopping vmnet-* devices | |
| INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--stop"] | |
| INFO vmware_driver: Reconfiguring vmnet-* devices | |
| INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--configure"] | |
| INFO vmware_driver: Starting services starter and waiting for them to start... | |
| INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"] | |
| 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 subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"] | |
| 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 subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"] | |
| 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 subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"] | |
| 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 subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"] | |
| 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/joe/.vagrant.d/gems/gems/vagrant-vmware-fusion-0.8.2/lib/vagrant-vmware-fusion/sudo_helper.rb:53:in `call' | |
| /Users/joe/.vagrant.d/gems/gems/vagrant-vmware-fusion-0.8.2/lib/vagrant-vmware-fusion/driver.rb:818:in `verify_vmnet!' | |
| /Users/joe/.vagrant.d/gems/gems/vagrant-vmware-fusion-0.8.2/lib/vagrant-vmware-fusion/action_farm.rb:78:in `call' | |
| /Applications/Vagrant/embedded/gems/gems/vagrant-1.2.4/lib/vagrant/action/warden.rb:34:in `call' | |
| /Users/joe/.vagrant.d/gems/gems/vagrant-vmware-fusion-0.8.2/lib/vagrant-vmware-fusion/action_farm.rb:924:in `call' | |
| /Applications/Vagrant/embedded/gems/gems/vagrant-1.2.4/lib/vagrant/action/warden.rb:34:in `call' | |
| /Applications/Vagrant/embedded/gems/gems/vagrant-1.2.4/lib/vagrant/action/runner.rb:61:in `block in run' | |
| /Applications/Vagrant/embedded/gems/gems/vagrant-1.2.4/lib/vagrant/util/busy.rb:19:in `busy' | |
| /Applications/Vagrant/embedded/gems/gems/vagrant-1.2.4/lib/vagrant/action/runner.rb:61:in `run' | |
| /Applications/Vagrant/embedded/gems/gems/vagrant-1.2.4/lib/vagrant/action/builtin/call.rb:51:in `call' | |
| /Applications/Vagrant/embedded/gems/gems/vagrant-1.2.4/lib/vagrant/action/warden.rb:34:in `call' | |
| /Users/joe/.vagrant.d/gems/gems/vagrant-vmware-fusion-0.8.2/lib/vagrant-vmware-fusion/action_farm.rb:1121:in `call' | |
| /Applications/Vagrant/embedded/gems/gems/vagrant-1.2.4/lib/vagrant/action/warden.rb:34:in `call' | |
| /Users/joe/.vagrant.d/gems/gems/vagrant-vmware-fusion-0.8.2/lib/vagrant-vmware-fusion/action_farm.rb:240:in `call' | |
| /Applications/Vagrant/embedded/gems/gems/vagrant-1.2.4/lib/vagrant/action/warden.rb:34:in `call' | |
| /Users/joe/.vagrant.d/gems/gems/vagrant-vmware-fusion-0.8.2/lib/vagrant-vmware-fusion/action_farm.rb:995:in `call' | |
| /Applications/Vagrant/embedded/gems/gems/vagrant-1.2.4/lib/vagrant/action/warden.rb:34:in `call' | |
| /Users/joe/.vagrant.d/gems/gems/vagrant-vmware-fusion-0.8.2/lib/vagrant-vmware-fusion/action_farm.rb:400:in `call' | |
| /Applications/Vagrant/embedded/gems/gems/vagrant-1.2.4/lib/vagrant/action/warden.rb:34:in `call' | |
| /Applications/Vagrant/embedded/gems/gems/vagrant-1.2.4/lib/vagrant/action/builtin/handle_box_url.rb:24:in `call' | |
| /Applications/Vagrant/embedded/gems/gems/vagrant-1.2.4/lib/vagrant/action/warden.rb:34:in `call' | |
| /Applications/Vagrant/embedded/gems/gems/vagrant-1.2.4/lib/vagrant/action/runner.rb:61:in `block in run' | |
| /Applications/Vagrant/embedded/gems/gems/vagrant-1.2.4/lib/vagrant/util/busy.rb:19:in `busy' | |
| /Applications/Vagrant/embedded/gems/gems/vagrant-1.2.4/lib/vagrant/action/runner.rb:61:in `run' | |
| /Applications/Vagrant/embedded/gems/gems/vagrant-1.2.4/lib/vagrant/action/builtin/call.rb:51:in `call' | |
| /Applications/Vagrant/embedded/gems/gems/vagrant-1.2.4/lib/vagrant/action/warden.rb:34:in `call' | |
| /Users/joe/.vagrant.d/gems/gems/vagrant-vmware-fusion-0.8.2/lib/vagrant-vmware-fusion/action_farm.rb:1121:in `call' | |
| /Applications/Vagrant/embedded/gems/gems/vagrant-1.2.4/lib/vagrant/action/warden.rb:34:in `call' | |
| /Applications/Vagrant/embedded/gems/gems/vagrant-1.2.4/lib/vagrant/action/builtin/lock.rb:42:in `block in call' | |
| /Applications/Vagrant/embedded/gems/gems/vagrant-1.2.4/lib/vagrant/action/builtin/lock.rb:27:in `open' | |
| /Applications/Vagrant/embedded/gems/gems/vagrant-1.2.4/lib/vagrant/action/builtin/lock.rb:27:in `call' | |
| /Applications/Vagrant/embedded/gems/gems/vagrant-1.2.4/lib/vagrant/action/warden.rb:34:in `call' | |
| /Users/joe/.vagrant.d/gems/gems/vagrant-vmware-fusion-0.8.2/lib/vagrant-vmware-fusion/action_farm.rb:108:in `call' | |
| /Applications/Vagrant/embedded/gems/gems/vagrant-1.2.4/lib/vagrant/action/warden.rb:34:in `call' | |
| /Users/joe/.vagrant.d/gems/gems/vagrant-vmware-fusion-0.8.2/lib/vagrant-vmware-fusion/action_farm.rb:240:in `call' | |
| /Applications/Vagrant/embedded/gems/gems/vagrant-1.2.4/lib/vagrant/action/warden.rb:34:in `call' | |
| /Applications/Vagrant/embedded/gems/gems/vagrant-1.2.4/lib/vagrant/action/builtin/config_validate.rb:25:in `call' | |
| /Applications/Vagrant/embedded/gems/gems/vagrant-1.2.4/lib/vagrant/action/warden.rb:34:in `call' | |
| /Applications/Vagrant/embedded/gems/gems/vagrant-1.2.4/lib/vagrant/action/builder.rb:116:in `call' | |
| /Applications/Vagrant/embedded/gems/gems/vagrant-1.2.4/lib/vagrant/action/runner.rb:61:in `block in run' | |
| /Applications/Vagrant/embedded/gems/gems/vagrant-1.2.4/lib/vagrant/util/busy.rb:19:in `busy' | |
| /Applications/Vagrant/embedded/gems/gems/vagrant-1.2.4/lib/vagrant/action/runner.rb:61:in `run' | |
| /Applications/Vagrant/embedded/gems/gems/vagrant-1.2.4/lib/vagrant/machine.rb:147:in `action' | |
| /Applications/Vagrant/embedded/gems/gems/vagrant-1.2.4/lib/vagrant/batch_action.rb:63:in `block (2 levels) in run' | |
| INFO interface: error: INFO global: Vagrant version: 1.2.4 | |
| INFO manager: Registered plugin: box command | |
| INFO manager: Registered plugin: destroy command | |
| INFO manager: Registered plugin: halt command | |
| INFO manager: Registered plugin: init command | |
| INFO manager: Registered plugin: package command | |
| INFO manager: Registered plugin: plugin command | |
| INFO manager: Registered plugin: provision command | |
| INFO manager: Registered plugin: reload command | |
| INFO manager: Registered plugin: resume command | |
| INFO manager: Registered plugin: ssh command | |
| INFO manager: Registered plugin: ssh-config command | |
| INFO manager: Registered plugin: status command | |
| INFO manager: Registered plugin: suspend command | |
| INFO manager: Registered plugin: up command | |
| INFO manager: Registered plugin: ssh communicator | |
| INFO manager: Registered plugin: Arch guest | |
| INFO manager: Registered plugin: Debian guest | |
| INFO manager: Registered plugin: Fedora guest | |
| INFO manager: Registered plugin: FreeBSD guest | |
| INFO manager: Registered plugin: Gentoo guest | |
| INFO manager: Registered plugin: Linux guest. | |
| INFO manager: Registered plugin: OmniOS guest. | |
| INFO manager: Registered plugin: OpenBSD guest | |
| INFO manager: Registered plugin: PLD Linux guest | |
| INFO manager: Registered plugin: RedHat guest | |
| INFO manager: Registered plugin: Solaris guest. | |
| INFO manager: Registered plugin: SUSE guest | |
| INFO manager: Registered plugin: Ubuntu guest | |
| INFO manager: Registered plugin: Arch host | |
| INFO manager: Registered plugin: BSD host | |
| INFO manager: Registered plugin: Fedora host | |
| INFO manager: Registered plugin: FreeBSD host | |
| INFO manager: Registered plugin: Gentoo host | |
| INFO manager: Registered plugin: Linux host | |
| INFO manager: Registered plugin: OpenSUSE host | |
| INFO manager: Registered plugin: Windows host | |
| INFO manager: Registered plugin: kernel | |
| INFO manager: Registered plugin: kernel | |
| INFO manager: Registered plugin: VirtualBox provider | |
| INFO manager: Registered plugin: ansible | |
| INFO manager: Registered plugin: CFEngine Provisioner | |
| INFO manager: Registered plugin: chef | |
| INFO manager: Registered plugin: puppet | |
| INFO manager: Registered plugin: shell | |
| INFO manager: Registered plugin: VMware Fusion Provider | |
| 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> | |
| INFO vmware:sudo_helper: Calling command: verify-vmnet | |
| INFO vmware_driver: Starting services starter and waiting for them to start... | |
| INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"] | |
| 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 subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"] | |
| 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 subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"] | |
| 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 subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"] | |
| 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 subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"] | |
| INFO vmware_driver: Stopping services starter... | |
| WARN vmware_driver: vmnet devices are NOT healthy. Attempting to fix. | |
| INFO vmware_driver: vmnet-bridge appears to be alive, killing it (pid 5768) | |
| INFO subprocess: Starting process: ["/bin/kill", "5768"] | |
| INFO vmware_driver: Stopping vmnet-* devices | |
| INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--stop"] | |
| INFO vmware_driver: Reconfiguring vmnet-* devices | |
| INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--configure"] | |
| INFO vmware_driver: Starting services starter and waiting for them to start... | |
| INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"] | |
| 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 subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"] | |
| 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 subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"] | |
| 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 subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"] | |
| 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 subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"] | |
| 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.2.4 | |
| INFO manager: Registered plugin: box command | |
| INFO manager: Registered plugin: destroy command | |
| INFO manager: Registered plugin: halt command | |
| INFO manager: Registered plugin: init command | |
| INFO manager: Registered plugin: package command | |
| INFO manager: Registered plugin: plugin command | |
| INFO manager: Registered plugin: provision command | |
| INFO manager: Registered plugin: reload command | |
| INFO manager: Registered plugin: resume command | |
| INFO manager: Registered plugin: ssh command | |
| INFO manager: Registered plugin: ssh-config command | |
| INFO manager: Registered plugin: status command | |
| INFO manager: Registered plugin: suspend command | |
| INFO manager: Registered plugin: up command | |
| INFO manager: Registered plugin: ssh communicator | |
| INFO manager: Registered plugin: Arch guest | |
| INFO manager: Registered plugin: Debian guest | |
| INFO manager: Registered plugin: Fedora guest | |
| INFO manager: Registered plugin: FreeBSD guest | |
| INFO manager: Registered plugin: Gentoo guest | |
| INFO manager: Registered plugin: Linux guest. | |
| INFO manager: Registered plugin: OmniOS guest. | |
| INFO manager: Registered plugin: OpenBSD guest | |
| INFO manager: Registered plugin: PLD Linux guest | |
| INFO manager: Registered plugin: RedHat guest | |
| INFO manager: Registered plugin: Solaris guest. | |
| INFO manager: Registered plugin: SUSE guest | |
| INFO manager: Registered plugin: Ubuntu guest | |
| INFO manager: Registered plugin: Arch host | |
| INFO manager: Registered plugin: BSD host | |
| INFO manager: Registered plugin: Fedora host | |
| INFO manager: Registered plugin: FreeBSD host | |
| INFO manager: Registered plugin: Gentoo host | |
| INFO manager: Registered plugin: Linux host | |
| INFO manager: Registered plugin: OpenSUSE host | |
| INFO manager: Registered plugin: Windows host | |
| INFO manager: Registered plugin: kernel | |
| INFO manager: Registered plugin: kernel | |
| INFO manager: Registered plugin: VirtualBox provider | |
| INFO manager: Registered plugin: ansible | |
| INFO manager: Registered plugin: CFEngine Provisioner | |
| INFO manager: Registered plugin: chef | |
| INFO manager: Registered plugin: puppet | |
| INFO manager: Registered plugin: shell | |
| INFO manager: Registered plugin: VMware Fusion Provider | |
| 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> | |
| INFO vmware:sudo_helper: Calling command: verify-vmnet | |
| INFO vmware_driver: Starting services starter and waiting for them to start... | |
| INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"] | |
| 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 subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"] | |
| 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 subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"] | |
| 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 subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"] | |
| 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 subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"] | |
| INFO vmware_driver: Stopping services starter... | |
| WARN vmware_driver: vmnet devices are NOT healthy. Attempting to fix. | |
| INFO vmware_driver: vmnet-bridge appears to be alive, killing it (pid 5768) | |
| INFO subprocess: Starting process: ["/bin/kill", "5768"] | |
| INFO vmware_driver: Stopping vmnet-* devices | |
| INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--stop"] | |
| INFO vmware_driver: Reconfiguring vmnet-* devices | |
| INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--configure"] | |
| INFO vmware_driver: Starting services starter and waiting for them to start... | |
| INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"] | |
| 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 subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"] | |
| 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 subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"] | |
| 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 subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"] | |
| 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 subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmnet-cli", "--status"] | |
| 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. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment