Network issues after rollback

[simensen]

I seem to have some weird network issues after a rollback. I've taken to having to run the following:

vagrant sandbox rollback
vagrant halt -f
vagrant up

The halt command without -f may eventually work but I've never bothered to wait to find out. I've waited well over a minute with no perceived activity on the VM. vagrant ssh and the likes fail so I have worked under the assumption that the administration interface gets messed up so some commands won't make it to the host.

Am I doing something wrong? Is this a known issue?

The sandbox feature is really nice and still faster than any other option, but I can't help but feel like it should be a cleaner experience.

Host OSX 10.8.2
Guest
VirtualBox 4.2.4
Vagrant 1.0.5

Please let me know how I can help debug this on my side and I'll see what I can do.

Also, thanks for the awesome plugin. :)

[BrianBland]

I am also encountering this issue, with both OSX 10.8.2 and Ubuntu 12.04 as hosts. It seems to happen most frequently when running vagrant sandbox on immediately after a vagrant up.
The following script is usually enough to trigger it, as the final call won't ever connect.

vagrant up --no-provision
vagrant sandbox on
vagrant provision
vagrant sandbox rollback
vagrant ssh -c true

[tuzz]

I'm seeing the same issue. Sometimes, SSH hangs after rolling back to a snapshot.

We tried SSHing in before creating the snapshot, thinking that the SSH daemon may not have initialised when the snapshot was taken. This doesn't seem to be the case, because it still failed to come back afterwards some of the time.

[ryuzee]

It's old issue and at present we do not see any similar issues. so I would like to close this issue.