Rarely VM could enter some "weird" unfinished state, for example if I hits Ctrl+C during "vagrant up", or if I do "vagrant halt" without "-f" followed immediately by "vagrant up" again. In that state, "vagrant up" causes a new machine to be created, even though the previous machine simply needs to be force-stopped. This causes lots of aggravation since I now have to re-attach proper VM to vagrant.

I wrote about it in January 2013 at https://www.mediawiki.org/wiki/User:Yurik/Installing_Linux_virtual_box_under_Windows_7#Losing_VM_association -- how to restore that assoc, but I think our vagrant should be smart enough to warn users and/or attempt to force shutdown existing machine instead of creating a new one.

Version: unspecified
Severity: normal