I've worked some with vagrant ubuntu (precise64) on windoz7, from cygwin, and not really using the VBox Manager app. On WInXP, I setup vagrant with an old precise32 and after running it and installing several ruby packages, I come back a couple of days later and 'vagrant up' provisions a new box, where I want my old one. I tried using VBox Manager to add the machine under cygwin, and could start it, but it lacks all the ruby stuff. Also it has no mouse so I lost control of the PC whci I suppose I would need to press 'ESC' or something. Why does 'vagrant halt' destroy my vm with ruby? Is there a way to get it back and start it?
-- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/vagrant/issues IRC: #vagrant on Freenode --- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/d4c9c1a6-f8db-4f17-a48b-24367694eef6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
