Hi Alvaro The on-disk location of the vmdk files never changed. It just seems that the VirtualBox Manager GUI sometimes can't see them if `vagrant up` was issued from an elevated command prompt (which in turn causes vagrant to lose them after a reboot). If I run the VirtualBox Manager GUI with admin rights, the vagrant machines show up (and the powered off/running status is correct). If I run the VirtualBox Manager GUI with normal user privs, the vagrant machines (created vwith an elevated command prompt) sometimes show up (but always listed as "powered off") or simply don't appear in the VirtualBox Manager GUI.
If I issue `vagrant up` from an non-elevated command prompt and run VirtualBox Manager GUI with normal privs too, everything works as intended. The vagrant machines are correctly listed in the GUI (with correct powered off/running status) and they survive an unplanned host reboot. Charlie On Friday, December 8, 2017 at 9:51:27 AM UTC, Alvaro Miranda Aguilera wrote: > > hello > > if you run the vagrant command as administrator, maybe all those lost vms > are under the admin user > > vagrant by default will create VMs on the default dir for each user. > > Virtualbox uses USER/VirtualBox VMs > > C:\Users\Administrator\VirtualBox VMs > > or maybe you can use that cmder thing to run Virtualbox and check the gui > under admin. > > Alvaro > > On Fri, Dec 8, 2017 at 1:50 AM, Charlie <charlie...@gmail.com > <javascript:>> 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 the Google Groups >> "Vagrant" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to vagrant-up+...@googlegroups.com <javascript:>. >> 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. >> > > > > -- > Alvaro > > -- 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/27af780b-30de-42bf-bfd2-f2d55b392d31%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
