'vagrant package' did not save my state. Please assist

[Sina Tashakkori]

Hello friend,

So yesterday I worked on my Vagrant deployed Virtual Box Lubuntu desktop VM with GUI enabled. After my day’s work I ran the command ‘vagrant package’. It closed my VM then complains that there is already a package.box file in that directory. Couldn’t it tell me that BEFORE it closed my VM session?? Or couldn’t it package it to a box with a different name for example package2.box?? Anyway, so then I ran ‘vagrant package --output package2.box’. After a really long time I discover the great news: that it did not save the state of the machine and that I lost all of my work for the day. Please tell me where I went wrong or where you went wrong so that I may avoid this annoyance in the future. Thank you.

Best,

Sina

[Alvaro Miranda Aguilera]

Hello Sina,

What work you lost ?

If you turn on the same box again it will be where it was left.

The files and configuration you have done persist over reboots?

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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/3e4dca9d-d721-403d-a881-9e84d8efc631%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.