Skip to content

Instantly share code, notes, and snippets.

@rupebac

rupebac/DeployVM

Created Mar 27, 2018
Embed
What would you like to do?
==> default: Starting the VMware VM...
INFO subprocess: Starting process: ["C:\\Program Files (x86)\\VMware\\VMware Workstation/vmrun.exe", "start", "D:/companyBoxes/buildBox/.vagrant/machines/default/vmware_workstation/ad8558bd-7551-4676-9954-c68e133a0893/VagrantBase.vmx", "nogui"]
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
ERROR warden: Error occurred: Vagrant timed out while trying to start the VMware machine. This
error is caused by VMware never successfully starting the machine.
This can often be fixed by simply retrying. If the error persists,
please verify that VMware is functional. This is not a Vagrant
issue.
INFO warden: Beginning recovery process...
INFO warden: Calling recover: #<Vagrant::Action::Builtin::HandleForwardedPortCollisions:0x00000000052ac3a8>
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
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: Vagrant timed out while trying to start the VMware machine. This
error is caused by VMware never successfully starting the machine.
This can often be fixed by simply retrying. If the error persists,
please verify that VMware is functional. This is not a Vagrant
issue.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
ERROR warden: Error occurred: Vagrant timed out while trying to start the VMware machine. This
error is caused by VMware never successfully starting the machine.
This can often be fixed by simply retrying. If the error persists,
please verify that VMware is functional. This is not a Vagrant
issue.
INFO warden: Beginning recovery process...
INFO warden: Calling recover: #<Vagrant::Action::Builtin::Call:0x0000000004764d88>
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
ERROR warden: Error occurred: Vagrant timed out while trying to start the VMware machine. This
error is caused by VMware never successfully starting the machine.
This can often be fixed by simply retrying. If the error persists,
please verify that VMware is functional. This is not a Vagrant
issue.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
ERROR warden: Error occurred: Vagrant timed out while trying to start the VMware machine. This
error is caused by VMware never successfully starting the machine.
This can often be fixed by simply retrying. If the error persists,
please verify that VMware is functional. This is not a Vagrant
issue.
INFO warden: Beginning recovery process...
INFO warden: Calling recover: #<Vagrant::Action::Builtin::Call:0x0000000004a2d628>
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Calling recover: VMware Middleware: Import
INFO subprocess: Starting process: ["C:\\Program Files (x86)\\VMware\\VMware Workstation/vmrun.exe", "list"]
INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stdout: Total running VMs: 4
D:\companyBoxes\1.27.0-5a45dbc1.1436\.vagrant\machines\default\vmware_workstation\62ba54e9-84e8-48ac-82c0-9241c4864727\VagrantBase.vmx
D:\companyBoxes\1.27.0-5a45dbc1.1437\.vagrant\machines\default\vmware_workstation\5923641d-4273-4b36-bade-ec10d960035c\VagrantBase.vmx
D:\companyBoxes\1.27.0-52b03587.1434\.vagrant\machines\default\vmware_workstation\42d88dba-0802-4c6d-9fda-13ec433e84c0\VagrantBase.vmx
D:\workspace\build\vagrant\master\companySquish\build\1.27.0-5a45dbc1.1440_squish\.vagrant\machines\default\vmware_workstation\3bfc0da1-93d7-4231-8464-c7f59c32d799\company.vmx
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
DEBUG vmware: VM state requested. Current state: not_running
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
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: Vagrant timed out while trying to start the VMware machine. This
error is caused by VMware never successfully starting the machine.
This can often be fixed by simply retrying. If the error persists,
please verify that VMware is functional. This is not a Vagrant
issue.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
ERROR warden: Error occurred: Vagrant timed out while trying to start the VMware machine. This
error is caused by VMware never successfully starting the machine.
This can often be fixed by simply retrying. If the error persists,
please verify that VMware is functional. This is not a Vagrant
issue.
INFO warden: Beginning recovery process...
INFO warden: Calling recover: #<Vagrant::Action::Builtin::Call:0x00000000051e71e8>
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO warden: Beginning recovery process...
INFO warden: Recovery complete.
INFO environment: Released process lock: machine-action-28bea755a04f243cc04d09001005b71b
INFO environment: Running hook: environment_unload
INFO runner: Preparing hooks for middleware sequence...
INFO runner: 6 hooks defined.
INFO runner: Running action: environment_unload #<Vagrant::Action::Builder:0x00000000052f8c08>
INFO warden: Calling IN action: HashiCorp Background Check: End
INFO logger: Cleaning up background activation thread...
INFO warden: Calling IN action: #<VagrantPlugins::Triggers::Action::Trigger:0x0000000005295fb8>
INFO warden: Calling IN action: #<VagrantPlugins::Triggers::Action::Trigger:0x000000000524f0e0>
INFO warden: Calling IN action: #<VagrantPlugins::Triggers::Action::Trigger:0x000000000520e158>
INFO warden: Calling OUT action: #<VagrantPlugins::Triggers::Action::Trigger:0x000000000520e158>
INFO warden: Calling OUT action: #<VagrantPlugins::Triggers::Action::Trigger:0x000000000524f0e0>
INFO warden: Calling OUT action: #<VagrantPlugins::Triggers::Action::Trigger:0x0000000005295fb8>
INFO warden: Calling OUT action: HashiCorp Background Check: End
ERROR vagrant: Vagrant experienced an error! Details:
ERROR vagrant: #<HashiCorp::VagrantVMwareworkstation::Errors::StartTimeout: Vagrant timed out while trying to start the VMware machine. This
error is caused by VMware never successfully starting the machine.
This can often be fixed by simply retrying. If the error persists,
please verify that VMware is functional. This is not a Vagrant
issue.>
ERROR vagrant: Vagrant timed out while trying to start the VMware machine. This
error is caused by VMware never successfully starting the machine.
This can often be fixed by simply retrying. If the error persists,
please verify that VMware is functional. This is not a Vagrant
issue.
ERROR vagrant: C:/Users/developer/.vagrant.d/gems/2.4.3/gems/vagrant-vmware-workstation-5.0.4/lib/vagrant-vmware-workstation/driver.rb:609:in `rescue in start'
C:/Users/developer/.vagrant.d/gems/2.4.3/gems/vagrant-vmware-workstation-5.0.4/lib/vagrant-vmware-workstation/driver.rb:604:in `start'
C:/Users/developer/.vagrant.d/gems/2.4.3/gems/vagrant-vmware-workstation-5.0.4/lib/vagrant-vmware-workstation/action_farm.rb:38:in `call'
C:/devTools/Vagrant/embedded/gems/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
C:/devTools/Vagrant/embedded/gems/gems/vagrant-2.0.2/lib/vagrant/action/builtin/handle_forwarded_port_collisions.rb:49:in `call'
C:/devTools/Vagrant/embedded/gems/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
C:/Users/developer/.vagrant.d/gems/2.4.3/gems/vagrant-vmware-workstation-5.0.4/lib/vagrant-vmware-workstation/action_farm.rb:1028:in `call'
C:/devTools/Vagrant/embedded/gems/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
C:/Users/developer/.vagrant.d/gems/2.4.3/gems/vagrant-vmware-workstation-5.0.4/lib/vagrant-vmware-workstation/action_farm.rb:1458:in `call'
C:/devTools/Vagrant/embedded/gems/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
C:/devTools/Vagrant/embedded/gems/gems/vagrant-2.0.2/lib/vagrant/action/builtin/set_hostname.rb:16:in `call'
C:/devTools/Vagrant/embedded/gems/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
C:/Users/developer/.vagrant.d/gems/2.4.3/gems/vagrant-vmware-workstation-5.0.4/lib/vagrant-vmware-workstation/action_farm.rb:742:in `call'
C:/devTools/Vagrant/embedded/gems/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
C:/Users/developer/.vagrant.d/gems/2.4.3/gems/vagrant-vmware-workstation-5.0.4/lib/vagrant-vmware-workstation/action_farm.rb:975:in `call'
C:/devTools/Vagrant/embedded/gems/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
C:/devTools/Vagrant/embedded/gems/gems/vagrant-2.0.2/lib/vagrant/action/builtin/synced_folders.rb:87:in `call'
C:/devTools/Vagrant/embedded/gems/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
C:/devTools/Vagrant/embedded/gems/gems/vagrant-2.0.2/lib/vagrant/action/builtin/synced_folder_cleanup.rb:28:in `call'
C:/devTools/Vagrant/embedded/gems/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
C:/devTools/Vagrant/embedded/gems/gems/vagrant-2.0.2/plugins/synced_folders/nfs/action_cleanup.rb:19:in `call'
C:/devTools/Vagrant/embedded/gems/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
C:/Users/developer/.vagrant.d/gems/2.4.3/gems/vagrant-vmware-workstation-5.0.4/lib/vagrant-vmware-workstation/action_farm.rb:1047:in `call'
C:/devTools/Vagrant/embedded/gems/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
C:/devTools/Vagrant/embedded/gems/gems/vagrant-2.0.2/lib/vagrant/action/builtin/provision.rb:80:in `call'
C:/devTools/Vagrant/embedded/gems/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
C:/devTools/Vagrant/embedded/gems/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
C:/devTools/Vagrant/embedded/gems/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
C:/devTools/Vagrant/embedded/gems/gems/vagrant-2.0.2/lib/vagrant/action/builder.rb:116:in `call'
C:/devTools/Vagrant/embedded/gems/gems/vagrant-2.0.2/lib/vagrant/action/runner.rb:66:in `block in run'
C:/devTools/Vagrant/embedded/gems/gems/vagrant-2.0.2/lib/vagrant/util/busy.rb:19:in `busy'
C:/devTools/Vagrant/embedded/gems/gems/vagrant-2.0.2/lib/vagrant/action/runner.rb:66:in `run'
C:/devTools/Vagrant/embedded/gems/gems/vagrant-2.0.2/lib/vagrant/action/builtin/call.rb:53:in `call'
C:/devTools/Vagrant/embedded/gems/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
C:/Users/developer/.vagrant.d/gems/2.4.3/gems/vagrant-vmware-workstation-5.0.4/lib/vagrant-vmware-workstation/action_farm.rb:1077:in `call'
C:/devTools/Vagrant/embedded/gems/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
C:/Users/developer/.vagrant.d/gems/2.4.3/gems/vagrant-vmware-workstation-5.0.4/lib/vagrant-vmware-workstation/action_farm.rb:76:in `call'
C:/devTools/Vagrant/embedded/gems/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
C:/devTools/Vagrant/embedded/gems/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
C:/devTools/Vagrant/embedded/gems/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
C:/devTools/Vagrant/embedded/gems/gems/vagrant-2.0.2/lib/vagrant/action/builder.rb:116:in `call'
C:/devTools/Vagrant/embedded/gems/gems/vagrant-2.0.2/lib/vagrant/action/runner.rb:66:in `block in run'
C:/devTools/Vagrant/embedded/gems/gems/vagrant-2.0.2/lib/vagrant/util/busy.rb:19:in `busy'
C:/devTools/Vagrant/embedded/gems/gems/vagrant-2.0.2/lib/vagrant/action/runner.rb:66:in `run'
C:/devTools/Vagrant/embedded/gems/gems/vagrant-2.0.2/lib/vagrant/action/builtin/call.rb:53:in `call'
C:/devTools/Vagrant/embedded/gems/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
C:/Users/developer/.vagrant.d/gems/2.4.3/gems/vagrant_hook-0.1.6/lib/vagrant_hook/plugin.rb:40:in `call'
C:/devTools/Vagrant/embedded/gems/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
C:/devTools/Vagrant/embedded/gems/gems/vagrant-2.0.2/lib/vagrant/action/builtin/box_check_outdated.rb:79:in `call'
C:/devTools/Vagrant/embedded/gems/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
C:/Users/developer/.vagrant.d/gems/2.4.3/gems/vagrant-vmware-workstation-5.0.4/lib/vagrant-vmware-workstation/action_farm.rb:1369:in `call'
C:/devTools/Vagrant/embedded/gems/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
C:/Users/developer/.vagrant.d/gems/2.4.3/gems/vagrant-vmware-workstation-5.0.4/lib/vagrant-vmware-workstation/action_farm.rb:278:in `call'
C:/devTools/Vagrant/embedded/gems/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
C:/Users/developer/.vagrant.d/gems/2.4.3/gems/vagrant-vmware-workstation-5.0.4/lib/vagrant-vmware-workstation/action_farm.rb:148:in `call'
C:/devTools/Vagrant/embedded/gems/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
C:/Users/developer/.vagrant.d/gems/2.4.3/gems/vagrant-vmware-workstation-5.0.4/lib/vagrant-vmware-workstation/action_farm.rb:1156:in `call'
C:/devTools/Vagrant/embedded/gems/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
C:/Users/developer/.vagrant.d/gems/2.4.3/gems/vagrant-vmware-workstation-5.0.4/lib/vagrant-vmware-workstation/action_farm.rb:519:in `call'
C:/devTools/Vagrant/embedded/gems/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
C:/Users/developer/.vagrant.d/gems/2.4.3/gems/vagrant_hook-0.1.6/lib/vagrant_hook/plugin.rb:40:in `call'
C:/devTools/Vagrant/embedded/gems/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
C:/devTools/Vagrant/embedded/gems/gems/vagrant-2.0.2/lib/vagrant/action/builtin/prepare_clone.rb:15:in `call'
C:/devTools/Vagrant/embedded/gems/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
C:/devTools/Vagrant/embedded/gems/gems/vagrant-2.0.2/lib/vagrant/action/builtin/handle_box.rb:56:in `call'
C:/devTools/Vagrant/embedded/gems/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
C:/devTools/Vagrant/embedded/gems/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
C:/devTools/Vagrant/embedded/gems/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
C:/devTools/Vagrant/embedded/gems/gems/vagrant-2.0.2/lib/vagrant/action/builder.rb:116:in `call'
C:/devTools/Vagrant/embedded/gems/gems/vagrant-2.0.2/lib/vagrant/action/runner.rb:66:in `block in run'
C:/devTools/Vagrant/embedded/gems/gems/vagrant-2.0.2/lib/vagrant/util/busy.rb:19:in `busy'
C:/devTools/Vagrant/embedded/gems/gems/vagrant-2.0.2/lib/vagrant/action/runner.rb:66:in `run'
C:/devTools/Vagrant/embedded/gems/gems/vagrant-2.0.2/lib/vagrant/action/builtin/call.rb:53:in `call'
C:/devTools/Vagrant/embedded/gems/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
C:/Users/developer/.vagrant.d/gems/2.4.3/gems/vagrant-vmware-workstation-5.0.4/lib/vagrant-vmware-workstation/action_farm.rb:1369:in `call'
C:/devTools/Vagrant/embedded/gems/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
C:/Users/developer/.vagrant.d/gems/2.4.3/gems/vagrant-vmware-workstation-5.0.4/lib/vagrant-vmware-workstation/action_farm.rb:104:in `call'
C:/devTools/Vagrant/embedded/gems/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
C:/Users/developer/.vagrant.d/gems/2.4.3/gems/vagrant-vmware-workstation-5.0.4/lib/vagrant-vmware-workstation/action_farm.rb:278:in `call'
C:/devTools/Vagrant/embedded/gems/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
C:/devTools/Vagrant/embedded/gems/gems/vagrant-2.0.2/lib/vagrant/action/builtin/config_validate.rb:25:in `call'
C:/devTools/Vagrant/embedded/gems/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
C:/Users/developer/.vagrant.d/gems/2.4.3/gems/vagrant-vmware-workstation-5.0.4/lib/vagrant-vmware-workstation/action_farm.rb:165:in `call'
C:/devTools/Vagrant/embedded/gems/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
C:/Users/developer/.vagrant.d/gems/2.4.3/gems/vagrant-triggers-0.5.3/lib/vagrant-triggers/action/trigger.rb:17:in `call'
C:/devTools/Vagrant/embedded/gems/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
C:/Users/developer/.vagrant.d/gems/2.4.3/gems/vagrant-triggers-0.5.3/lib/vagrant-triggers/action/trigger.rb:17:in `call'
C:/devTools/Vagrant/embedded/gems/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
C:/Users/developer/.vagrant.d/gems/2.4.3/gems/vagrant-triggers-0.5.3/lib/vagrant-triggers/action/trigger.rb:17:in `call'
C:/devTools/Vagrant/embedded/gems/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
C:/devTools/Vagrant/embedded/gems/gems/vagrant-2.0.2/lib/vagrant/action/builder.rb:116:in `call'
C:/devTools/Vagrant/embedded/gems/gems/vagrant-2.0.2/lib/vagrant/action/runner.rb:66:in `block in run'
C:/devTools/Vagrant/embedded/gems/gems/vagrant-2.0.2/lib/vagrant/util/busy.rb:19:in `busy'
C:/devTools/Vagrant/embedded/gems/gems/vagrant-2.0.2/lib/vagrant/action/runner.rb:66:in `run'
C:/devTools/Vagrant/embedded/gems/gems/vagrant-2.0.2/lib/vagrant/machine.rb:227:in `action_raw'
C:/devTools/Vagrant/embedded/gems/gems/vagrant-2.0.2/lib/vagrant/machine.rb:202:in `block in action'
C:/devTools/Vagrant/embedded/gems/gems/vagrant-2.0.2/lib/vagrant/environment.rb:592:in `lock'
C:/devTools/Vagrant/embedded/gems/gems/vagrant-2.0.2/lib/vagrant/machine.rb:188:in `call'
C:/devTools/Vagrant/embedded/gems/gems/vagrant-2.0.2/lib/vagrant/machine.rb:188:in `action'
C:/devTools/Vagrant/embedded/gems/gems/vagrant-2.0.2/lib/vagrant/batch_action.rb:82:in `block (2 levels) in run'
INFO interface: error: Vagrant timed out while trying to start the VMware machine. This
error is caused by VMware never successfully starting the machine.
This can often be fixed by simply retrying. If the error persists,
please verify that VMware is functional. This is not a Vagrant
issue.
Vagrant timed out while trying to start the VMware machine. This
error is caused by VMware never successfully starting the machine.
This can often be fixed by simply retrying. If the error persists,
please verify that VMware is functional. This is not a Vagrant
issue.
INFO interface: Machine: error-exit ["HashiCorp::VagrantVMwareworkstation::Errors::StartTimeout", "Vagrant timed out while trying to start the VMware machine. This\nerror is caused by VMware never successfully starting the machine.\nThis can often be fixed by simply retrying. If the error persists,\nplease verify that VMware is functional. This is not a Vagrant\nissue."]
admin process quited!
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.