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+unsubscr...@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. For more options, visit https://groups.google.com/d/optout.
