On Windows 8.1 x64, when a new VM is created, it almost always does not start from the first time (I get lots of "default: Warning: Remote connection disconnect. Retrying..." followed by an error). Repeating it with "vagrant up" states that the machine is up. I have to "vagrant halt -f" and "vagrant up", sometimes several times, until initial provisioning starts up. I saw this behavior in 1.5.x and now in the latest 1.6.3 version.
Version: unspecified
Severity: normal
This sounds like a Vagrant and/or Virtualbox issue rather than an MediaWiki-Vagrant issue. Is there anything actionable for the MWV maintainer team here?
This probably means that the VM is unable to start. The first step in debugging it is to launch it in GUI mode from virtualbox. In my case it was filesystem corruption (something about orphaned indoes) and running e2fsck fixed it.
No reply to T69571#822615 and nothing actionable here, hence closing. Feel free to reopen if still a problem and when providing more info.