[makmanalp]

I know this isn't the right place for it but here we go: it's a total PITA when somehow the VM connection gets severed and "vagrant ssh" won't work and "vagrant shutdown" won't shutdown cleanly, so you have to kill it by hand and then reboot MANUALLY in virtualbox because the VM gets stuck in the grub menu after a non-clean kill. So then you have to wait for it to boot completely, then shut down normally and then run vagrant up again.

That connection dies for me periodically, like a few times a week. Anyone manage to solve that one?

[colinc]

I ran into a similar (completely maddening) situation when using an Ubuntu 12.04 LTS guest with Vagrant configured to create a private network.

I don't recall the exact cause of the failure, but switching to the virtio networking drivers has completely solved this issue for me.

  config.vm.provider :virtualbox do |vb|
    vb.customize ['modifyvm', :id, '--nictype1', 'virtio']
  end

[kayoone]

If i somehow can't connect to the VM anymore "vagrant halt" followed by "vagrant up" usually fixes that. Doesn't happen alot though.

[makmanalp]

Halt breaks too, though!

[kayoone]

Strange, question might be why your ssh connection breaks down like that. I get disconnected when i put my machine to sleep but after waking up i can just vagrant ssh back into it.

[lojack]

I run into similar problems. Seems to happen when I disconnect and then reconnect to a different network.

[makmanalp]

I think it may be this for me too, I code at work and then carry the laptop home to finish up sometimes.

[akngo]

I've been running into this issue as well. A similar one is that the SSH connection is lost whenever the network is lost. I think both issues are supposed to be solved with the latest version of VB (4.3.8) from this ticket (https://github.com/mitchellh/vagrant/issues/2691).

[xofer]

If your VM is stuck on a GRUB prompt, that's an issue with its GRUB config. You could have the same problem with any VM. Change the GRUB config to stop this behavior and repackage.