Restarting host machine always corrupts save file?

4 views
Skip to first unread message

Robert Lee

unread,
May 9, 2017, 12:08:46 PM5/9/17
to Vagrant
Without fail, anytime I'm SSH'd into my box and my host machine restarts, I'm stuck with a corrupt file. 

When I attempt to either restore an old save or just revert to a prior snapshot, Vagrant decides to provision a new box, which is effectively forcing me to rebuild the box every time.

Is this expected behavior? 

Alvaro Miranda Aguilera

unread,
May 9, 2017, 3:43:55 PM5/9/17
to vagra...@googlegroups.com
hello

how do you reboot the box?

how to reproduce this? if you can share a detailed set of instructions to reproduce this, i think will be easier to understand.

thanks


--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/4bf28297-827e-42e6-9b16-bcccf08a61cd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--
Alvaro

Robert Lee

unread,
May 9, 2017, 3:55:01 PM5/9/17
to Vagrant
I reboot it with a normal "vagrant up" and I get an error along the lines of 

"Failed to open a session for the virtual machaine ____.  VM cannot start because the saved state file ___ is invalid Delete the saved state prior to starting the VM."

I enter this state by:
1) vagrant up
2) vagrant ssh
3) Restart my host machine
4) vagrant up
And get the error

Now if I delete the save file, vagrant creates and provisions a new VM.

If I revert to a prior snapshot, vagrant still provisions a new VM.



On Tuesday, May 9, 2017 at 3:43:55 PM UTC-4, Alvaro Miranda Aguilera wrote:
hello

how do you reboot the box?

how to reproduce this? if you can share a detailed set of instructions to reproduce this, i think will be easier to understand.

thanks

On Tue, May 9, 2017 at 6:08 PM, Robert Lee <ggl...@gmail.com> wrote:
Without fail, anytime I'm SSH'd into my box and my host machine restarts, I'm stuck with a corrupt file. 

When I attempt to either restore an old save or just revert to a prior snapshot, Vagrant decides to provision a new box, which is effectively forcing me to rebuild the box every time.

Is this expected behavior? 

--
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.



--
Alvaro

Alvaro Miranda Aguilera

unread,
May 9, 2017, 3:58:14 PM5/9/17
to vagra...@googlegroups.com
Does this happen if you use Virtualbox without Vagrant?

not sure where you are using snapshots or state file.

Alvaro
Reply all
Reply to author
Forward
0 new messages