I tried that and got 'command not found', but have now added vboxmgr to my (windoz7) path (which is exported to cygwin in bashrc).
On windoz7 it lists the vbox name under my cygwin home, where I did the init. It comes up OK and says 'Machine already provisioned.'. When I exec 'ruby -v' it has the new ruby so that setup seems to work OK. The XP setup is the problem then. I'll have to add VBoxManager to its path and see on that. On XP, there's a VBox VM dir under cygwin home with the VM I installed pkgs in, and under 'c:\docs and settings\username\VBox VMs' I see new ones get created there when I run 'vagrant up', though I didn't 'init' a vbox there. Maybe the system is confused on the 'owner/user', with cygwin not really doing things the windoz way. Maybe I should just cd into the windoz user dir, init a vbox there, install pkgs and work from there instead of cygwin home. I actually saved all the commands to install all the stuff I added so am able to go through it again, as I have once already. I intend on putting them into a script called by vagrant during provisioning so I can recreate this sort of setup, but I also need to be able to reuse a setup, like when I start adding data into psql. On Thursday, July 14, 2016 at 2:01:36 PM UTC-7, Alvaro Miranda Aguilera wrote: > > Hello, > > whats the output of VBoxManage list vms ? > > What could happen is that the machine is there but not being used. > > Alvaro. > > On Wed, Jul 13, 2016 at 10:07 PM, Bob Van <[email protected] > <javascript:>> wrote: > >> 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] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/vagrant-up/d4c9c1a6-f8db-4f17-a48b-24367694eef6%40googlegroups.com >> >> <https://groups.google.com/d/msgid/vagrant-up/d4c9c1a6-f8db-4f17-a48b-24367694eef6%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > -- 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/15406ca7-b652-4164-ae7f-980b311c4518%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
