Better documentation

[dergachev]

This plugin seems really cool!

I would guess it supports a use-case like having your MYSQL databases not blown away when you run vagrant destroy, with the main benefit over standard Virtualbox shared folders (which are also persistent) is speed.

It would be great to see a tutorial (eg blog post) about how it's used, what else it's good for. Also a Vagrantfile for quick testing/hacking might be useful.

I haven't had a chance to try this plugin yet, but here are some other questions I'm wondering about:

• what (if anything) will eventually destroy ~/development/sourcehdd.vdi?
• is it possible to mount ~/development/sourcehdd.vdi to multiple VMs, or is there a check against that?
• standard VM images seem to live under /Users/dergachev/VirtualBox VMs... should the persistent images also be stored there?
• does this plugin work with VBoxManage snapshot?

Cheers,

[kusnier]

👍 Yes, i will work on this if i have some free time.

[dergachev]

Awesome thanks!

By the way, looking at your plugin yesterday inspired me to write a little utility plugin for messing with VBoxManage:
https://github.com/dergachev/vagrant-vboxmanage

[realyst2k]

The "what (if anything) will eventually destroy ~/development/sourcehdd.vdi" is actually very important. I've seen my vdi destroyed and redone on vagrant up a few times. Noticed that changing the configuration options in the vagrantfile does it, but what else? Will running it within a new directory and copying/moving the old disk in place work?

Basically, how does the plugin decide whether it needs to scrap and redo the vdi?

Thanks!