Hi, I had the same problem with Vagrant 1.5.x and the recently released 1.6. Trying to call *vagrant init* or simply *vagrant* from the windows command line failed. Calling it throught Cygwin did work.
I'm using a Win7 Enterprise 64bit on a 8 core Xeon with 12Go of ram. Hope this can help some, MT Le vendredi 25 avril 2014 05:34:17 UTC-4, Torsten Kleiber a écrit : > > Hi! > > This solves the problem here too, I don't know any other solution at the > moment. > I hope that somebody of vagrant pay attention to this, as we can not use > new features and fixes of newer versions of this. > Is there a way to open a bug for this? > > Kind regards > Torsten > > > Am Mittwoch, 23. April 2014 18:39:29 UTC+2 schrieb Quinton McCombs: > >> To get past this problem I went back to Vagrant 1.4.3. >> > -- 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/d/optout.
