stderr from Vagrant::SSH::Session should be included in error reports

[charles-dyfis-net]

Right now, when an ssh exec! call fails, only the command which was run is emitted.

However, as Vagrant does not transfer commands to the client in a way which avoids unquoting or other modification in-flight, it is not guaranteed that re-running the command as given in the code will actually reproduce the failure. To permit the user to understand these errors, the actual message should be emitted with the error.

[mitchellh]

Charles,

This is a good idea. I think your issue report here outlines a larger issue in Vagrant that there is poor internal logging. Logging in general needs to be much improved.

I'll consider this a first step in that process.

[charles-dyfis-net]

I'm personally using 951bef8f151f0a121cb93f5f3f232a5a09ec1d1b for this issue.

[mitchellh]

Failed SSH commands show output in error message. [closed by c1373f4]