Re: [vagrant-up] Re: Vagrant Stopped Working Suddenly

2014-12-29 Thread Torben Knerr
Hi, you can try to log in via plain ssh from the commandline with verbose logging, this might give you some more information on what's going wrong, e.g.: ssh vagrant@127.0.0.1 -p -i .vagrant/machines/default/virtualbox/private_key -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/nu

[vagrant-up] Vagrant packaging issue

2014-12-29 Thread Michael Legleux
I'm trying to package a new box from a virtualbox machine on ubuntu 14.10. In 1.6.5, vagrant package --base works. Now in 1.7.2.dev, I am getting an error at: ../vagrant/plugins/commands/package/command.rb:83: in `package_vm': wrong argument type String (expected Symbol) (TypeError) At first I

Re: [vagrant-up] Vagrant -> Windows 8.1 WinRM remoting speed fix for slowness

2014-12-29 Thread ferrix
Good idea, but it was definitely not a "just at startup" thing. The delay happened every time a winrm context was invoked. On Monday, December 29, 2014 5:22:16 PM UTC-6, Umair Chagani wrote: > > I would also check the startup type of the winrm service. By default, > winrm service is set to "A

Re: [vagrant-up] Vagrant -> Windows 8.1 WinRM remoting speed fix for slowness

2014-12-29 Thread Umair Chagani
I would also check the startup type of the winrm service. By default, winrm service is set to "Automatic (delayed)". Setting this to just "Automatic" sped up connection to winrm a lot more. On Dec 29, 2014 5:31 PM, "ferrix" wrote: > I couldn't figure out why the WinRM communicator was *agonizingl

[vagrant-up] vagrant destroy in multi-machine mode sometimes takes 10-15 minutes?

2014-12-29 Thread Chris Whitten
The only thing I added into the "remote" machines before this started happening were some upstart scripts. I'm working with 3 VM's each with 512 MB of memory. Any tips on how to debug? -- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscrib

[vagrant-up] Vagrant -> Windows 8.1 WinRM remoting speed fix for slowness

2014-12-29 Thread ferrix
I couldn't figure out why the WinRM communicator was *agonizingly* slow to my Windows 8.1 VM. I think I may finally have nailed it: Turns out, it's the recurrence of a good ol' Powershell issue from back in the v1 days. The Win 8.1 install doesn't seem to (or maybe, doesn't have time to?) run

[vagrant-up] Re: Vagrant Stopped Working Suddenly

2014-12-29 Thread sharingsunshine
Thanks for your suggested fixes. However, none of them seemed to work. It seems the box I am using doesn't have vagrant vagrant setup. Also at the login I couldn't use vagrants ssh. The server still works but only if brought up from the gui. If I use vagrant up it comes up but then continua

Re: [vagrant-up] vagrant chef-client provisioner can't find chef binaries when client version downgraded

2014-12-29 Thread William Jimenez
Hi Torben, Seth: That happens to be the same version I'm using as well: config.vm.provision "chef_client" do |chef| chef.chef_server_url = "" chef.validation_key_path = "" chef.version = "11.16.4-1" chef.binary_path = "/opt/chef/bin" chef.delete_node = true chef.delete