You're missing a significant portion of the debug log making this relatively useless. Please upload the full thing and I'll take a look. Gist it, because it'll be large.
On Mon, Jan 20, 2014 at 6:55 AM, Stephan Buys <[email protected]>wrote: > Hi, > > When trying to boot a VMWare Fusion (and Workstation) machine after the > machine is running already I sometimes get the exception below. This seems > to be pretty consistent even with version 2.2.8 of the plugins. Please let > me know if I can contact support for this issue. > > Kind regards, > Stephan Buys > > 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:0x00000100e94b10> > INFO warden: Calling IN action: HashiCorp Background Check: End > INFO logger: Cleaning up background activation thread... > INFO warden: Calling OUT action: HashiCorp Background Check: End > ERROR vagrant: Vagrant experienced an error! Details: > ERROR vagrant: #<Vagrant::Errors::SSHNotReady: The provider for this > Vagrant-managed machine is reporting that it > is not yet ready for SSH. Depending on your provider this can carry > different meanings. Make sure your machine is created and running and > try again. Additionally, check the output of `vagrant status` to verify > that the machine is in the state that you expect. If you continue to > get this error message, please view the documentation for the provider > you're using.> > ERROR vagrant: The provider for this Vagrant-managed machine is reporting > that it > is not yet ready for SSH. Depending on your provider this can carry > different meanings. Make sure your machine is created and running and > try again. Additionally, check the output of `vagrant status` to verify > that the machine is in the state that you expect. If you continue to > get this error message, please view the documentation for the provider > you're using. > ERROR vagrant: > /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.3/lib/vagrant/action/builtin/ssh_run.rb:27:in > `call' > /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.3/lib/vagrant/action/warden.rb:34:in > `call' > /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.3/lib/vagrant/action/warden.rb:95:in > `block in finalize_action' > /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.3/lib/vagrant/action/warden.rb:34:in > `call' > /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.3/lib/vagrant/action/warden.rb:34:in > `call' > /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.3/lib/vagrant/action/builder.rb:116:in > `call' > /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.3/lib/vagrant/action/runner.rb:69:in > `block in run' > /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.3/lib/vagrant/util/busy.rb:19:in > `busy' > /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.3/lib/vagrant/action/runner.rb:69:in > `run' > /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.3/lib/vagrant/action/builtin/call.rb:51:in > `call' > /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.3/lib/vagrant/action/warden.rb:34:in > `call' > /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.3/lib/vagrant/action/warden.rb:95:in > `block in finalize_action' > /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.3/lib/vagrant/action/warden.rb:34:in > `call' > /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.3/lib/vagrant/action/warden.rb:34:in > `call' > /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.3/lib/vagrant/action/builder.rb:116:in > `call' > /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.3/lib/vagrant/action/runner.rb:69:in > `block in run' > /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.3/lib/vagrant/util/busy.rb:19:in > `busy' > /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.3/lib/vagrant/action/runner.rb:69:in > `run' > /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.3/lib/vagrant/action/builtin/call.rb:51:in > `call' > /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.3/lib/vagrant/action/warden.rb:34:in > `call' > /Users/stephanbuys/.vagrant.d/gems/gems/vagrant-vmware-fusion-2.2.8/lib/vagrant-vmware-fusion/action_farm.rb:108:in > `call' > /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.3/lib/vagrant/action/warden.rb:34:in > `call' > /Users/stephanbuys/.vagrant.d/gems/gems/vagrant-vmware-fusion-2.2.8/lib/vagrant-vmware-fusion/action_farm.rb:246:in > `call' > /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.3/lib/vagrant/action/warden.rb:34:in > `call' > /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.3/lib/vagrant/action/builtin/config_validate.rb:25:in > `call' > /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.3/lib/vagrant/action/warden.rb:34:in > `call' > /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.3/lib/vagrant/action/builder.rb:116:in > `call' > /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.3/lib/vagrant/action/runner.rb:69:in > `block in run' > /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.3/lib/vagrant/util/busy.rb:19:in > `busy' > /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.3/lib/vagrant/action/runner.rb:69:in > `run' > /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.3/lib/vagrant/machine.rb:147:in > `action' > /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.3/plugins/commands/ssh/command.rb:48:in > `block in execute' > /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.3/lib/vagrant/plugin/v2/command.rb:193:in > `block in with_target_vms' > /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.3/lib/vagrant/plugin/v2/command.rb:191:in > `each' > /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.3/lib/vagrant/plugin/v2/command.rb:191:in > `with_target_vms' > /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.3/plugins/commands/ssh/command.rb:40:in > `execute' > /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.3/lib/vagrant/cli.rb:38:in > `execute' > /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.3/lib/vagrant/environment.rb:484:in > `cli' > /Applications/Vagrant/embedded/gems/gems/vagrant-1.4.3/bin/vagrant:127:in > `<top (required)>' > /Applications/Vagrant/bin/../embedded/gems/bin/vagrant:23:in `load' > /Applications/Vagrant/bin/../embedded/gems/bin/vagrant:23:in `<main>' > INFO interface: error: The provider for this Vagrant-managed machine is > reporting that it > is not yet ready for SSH. Depending on your provider this can carry > different meanings. Make sure your machine is created and running and > try again. Additionally, check the output of `vagrant status` to verify > that the machine is in the state that you expect. If you continue to > get this error message, please view the documentation for the provider > you're using. > The provider for this Vagrant-managed machine is reporting that it > is not yet ready for SSH. Depending on your provider this can carry > different meanings. Make sure your machine is created and running and > try again. Additionally, check the output of `vagrant status` to verify > that the machine is in the state that you expect. If you continue to > get this error message, please view the documentation for the provider > you're using. > ERROR: provided hosts list is empty > > -- > You received this message because you are subscribed to the Google Groups > "Vagrant" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
