Host is Windows 10 I have one vagrant file that defines 4 guests (all ubuntu 16.04 LTS).
Cutting the power causes either virtualbox or vagarant (not sure which) to lose these guests even though the vmdk etc files remain on disk. As mentioned before, I also have three manually created virtualbox guest machines (unrelated to the project or vagrant) and they survive unplanned reboots without issue. On Tuesday, December 5, 2017 at 5:04:20 PM UTC, Alvaro Miranda Aguilera wrote: > > to try to repro this. > > you have multiple vagrant projects that were provisioned > you did cut the power > started, the machins gone. > > what host OS? > > Alvaro. > > On Tue, Dec 5, 2017 at 5:32 PM, Charlie <charlie...@gmail.com > <javascript:>> wrote: > >> Hi Alvaro >> >> After simulating an unplanned host reboot (i.e. forcibly turning the >> laptop off and then on), this is what happens: >> >> 1. The machine dirs and files under ".vagrant/machines" (in the directory >> where the Vagrant file is) remain as they were >> 2. Running `vagrant global-status` shows the machines (although I think >> this is cached info as the warning message suggests) >> 3. Running `vagrant status` lists all the machines but their status is >> marked as "not created" >> 4. After running `vagrant status`, all the files in the machine dirs >> (under ".vagrant/machines/machine_name/vagrant" in the project directory >> with the Vagrant file) disappear >> 5. Running `VBoxManage list vms` no longer shows the machines >> 6. Despite this, the virtualbox files and vmdks for each machine all >> still exist under C:\Users\Charlie\VirtualBox VMs >> 7. Running `vagrant up` re-creates all the machines and re-provisions >> them (effectively duplicating the virtualbox machine files and vmdks that >> were already present in C:\Users\Charlie\VirtualBox VMs) >> >> It's not clear to me if the issue is with vagrant losing the associations >> after a reboot or with Virtualbox losing track of the VMs after a reboot >> and causing vagrant to assume they don't exist. If the latter, I don't >> understand why virtualbox doesn't also lose track of other non-vagrant VMs >> I have created. They continue to exist and work as normal after a reboot. >> >> Charlie >> >> On Tuesday, December 5, 2017 at 7:33:09 AM UTC, Alvaro Miranda Aguilera >> wrote: >>> >>> hello >>> >>> the state of the VM is stored in the running directory of the project. >>> >>> where the Vagrantfile is, a directory .vagrant is created >>> >>> some of that state is pointed also to your home/.vagrant.d >>> >>> When your machine starts, does anything gets deleted? >>> >>> I have a Win10 machine and i don't lose any VM that is registered. >>> >>> Alvaro. >>> >>> On Mon, Dec 4, 2017 at 11:34 PM, Charlie <charlie...@gmail.com> wrote: >>> >>>> Hi group, >>>> >>>> Is it expected behaviour that vagrant loses all it's associations to >>>> virtualbox guests if the host machine is rebooted without running vagrant >>>> halt/suspend first on the guests first (e.g. due to power loss or a system >>>> update)? >>>> >>>> I see this every time a Windows host running Vagrant 2.0.1 and >>>> Virtualbox 5.1.30 r118389 reboots for e.g. an unattended windows update >>>> (and it's been happening with every version of vagrant and virtualbox I've >>>> used prior to the current ones). >>>> >>>> Is there anything that can be done to get vagrant not to lose track of >>>> guests after such a host reboot? Re-creating and re-provisioning them is >>>> quite tedious (even with the aid of ansible). >>>> >>>> Thanks, >>>> Charlie >>>> >>>> -- >>>> 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. >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/vagrant-up/700b6dca-b73a-4cb8-8c4c-fb9853fd7361%40googlegroups.com >>>> >>>> <https://groups.google.com/d/msgid/vagrant-up/700b6dca-b73a-4cb8-8c4c-fb9853fd7361%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+...@googlegroups.com <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/vagrant-up/264b82e7-ba18-47c8-965f-95d362b28b55%40googlegroups.com >> >> <https://groups.google.com/d/msgid/vagrant-up/264b82e7-ba18-47c8-965f-95d362b28b55%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/fcc40b62-1534-4216-b077-929b68a7def2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
