vagrant reload stuck waiting machine to boot

[melezhik]

• vagrant 0.8.8
• VirtualBox 4.1.6 r74727

---

when saying vagrant reload, it stuck waiting :

[default] Attempting graceful shutdown of linux...
[default] Clearing any previously set forwarded ports...
[default] Forwarding ports...
[default] -- ssh: 22 => 2222 (adapter 1)
[default] Cleaning previously set shared folders...
[default] Creating shared folders metadata...
[default] Running any VM customizations...
[default] Booting VM...
[default] Waiting for VM to boot. This can take a few minutes.

.... and it will never get response from bootted machine! although machine is booted and accessible via ssh

---

well, when I removed vagrant 1.8.8 and switched to 1.8.7 everything okay:

[default] Attempting graceful shutdown of linux...
[default] Clearing any previously set forwarded ports...
[default] Forwarding ports...
[default] -- ssh: 22 => 2222 (adapter 1)
[default] Cleaning previously set shared folders...
[default] Creating shared folders metadata...
[default] Running any VM customizations...
[default] Booting VM...
[default] Waiting for VM to boot. This can take a few minutes.
[default] VM booted and ready for use!

[hedgehog]

I think this is a duplicate of #391 and #455.
@melezhik, if you agree, could you close this and track either of those issues instead?

[cubes]

Sorry to pile on a closed ticket, but I just encountered the same issue, and it does not appear to be networking related.

• vagrant 0.8.8
• VirtualBox 4.1.6r74713

[hedgehog]

@cubes, I think #391 and #455 are both still open and generally ack to be ssh related, though #91 does have a network-error flavor to it. Please try #455 if you think it more closely resembles what you experience than #391.

[hedgehog]

Hmm, why do people insist on adding to a closed issue, when an open issue is referred to and is not closed :)

[hyorch]

I had the same problem, but running with "--debug":
vagrant up --debug
command finish starting the machine, without "--debug" never ends.
Vagrant 0.8.8

[hedgehog]

@hyorch, this issue is marked closed. As noted above, please report your experiences in either #391 or #455, both of those are still open.