I was going from memory, actually VAGRANT_LOG=debug is the correct option for getting the full logs. Its packer that assumes anything other than 0 means do debug.
On Friday, March 27, 2015 at 7:25:14 AM UTC-5, dragon788 wrote: > > The best way to diagnose is to open your command prompt and run vagrant > from there. That's really the intended use case as doing it from the Run > dialog it will always close the prompt on success or failure. Once you are > running from the prompt you should see better error information. In order > to best help you troubleshoot please run 'vagrant_log=1 vagrant up' as this > will output a lot of debug information. If you want to capture this to file > for easier review/sharing you can add a small snippet, ' > debug_log.text > 2>&1 '. This when put after the command above will send all the debug and > regular information into the text file. -- 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.
