Charlie, Thank you for the follow-up. That explanation makes a lot of sense. ~R
Robert On Thu, Dec 7, 2017 at 4:50 PM, Charlie <charlie.orf...@gmail.com> wrote: > Alvaro, Robert: > > I think I've tracked down the culprit. The non-vagrant virtualboxes were > running at the time of the power down/reboot and survived with no problem - > digging further in to this is what revealed the issue: > > I start all my vagrant machines with a command line emulator called Cmder > and rarely pay attention to the VirtualBox Manager GUI. > > While doing some more debugging today I noticed that my non-vagrants were > always present in the VirtualBox Manager GUI but the vagrant machines only > sporadically showed up (and always showed as being powered off, even if > running). > > I remembered I had set the Cmder emulator to run as administrator (for an > unrelated reason, nothing to do with vagrant or this issue). As soon as I > ran the emulator with normal privs and issued `vagrant up` the vagrant > machines started surviving reboots with no issue. > > So I guess virtualbox and/or vagrant don't like communicating with each > other if running under different user contexts. I don't think that's a bug > (more like an implementation limitation/constraint) so, for me at least, > the issue is marked 'solved' :) > > Charlie > > > > > > On Wednesday, December 6, 2017 at 3:53:05 PM UTC, Robert Lilly wrote: >> >> Charlie, just for clarification, were the non-Vagrant Virtualbox VMs >> running at the time of the power down / reboot as well as the the Vagrant >> ones? >> >> I have experienced this problem before on Windows 7 and 10, as well as OS >> X / MacOS. I didn't take the time to troubleshoot, I just made a habit of >> not leaving any VMs running when I was finished for the day. >> > -- > 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 a topic in the > Google Groups "Vagrant" group. > To unsubscribe from this topic, visit https://groups.google.com/d/ > topic/vagrant-up/Gn0BxZh6Peg/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > vagrant-up+unsubscr...@googlegroups.com. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/vagrant-up/831f9c40-ba2a-4de3-9555-88eba86e51e6%40googlegroups.com > <https://groups.google.com/d/msgid/vagrant-up/831f9c40-ba2a-4de3-9555-88eba86e51e6%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 vagrant-up+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CAPqfOOUZmWSJzvTZoAyPdBKL%3DFdTHbk-5T6c1D%2BVYmDZ-GJ1-g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
