Blake
On Friday, October 22, 2010, Mike Williams <md...@dogbiscuit.org> wrote:
> Before discovering Vagrant, I had my own script to create VirtualBox VMs. While it was in most ways vastly inferior to Vagrant, I did manage to speed up creation of new VMs, by sharing the base disk image.
> I marked my base disk image as "immutable"I attached the base disk image directly to new VMs, rather than making a copy first. Being "immutable", VirtualBox creates a new copy-on-write "differencing image" for the VM.Finally, I disabled "auto-reset" the new "differencing image". When VirtualBox creates a "differencing" child of an immutable image, the default behaviour is to discard changes whenever the VM starts. That's most definitely not what I wanted.
Blake
> Raja,
> If this is indeed a copy-on-write method, then any changed blocks
> would be stored in a separate file for that VM. Unchanged blocks
> would remain in the original/master VM image.
Precisely.
See http://www.virtualbox.org/manual/ch05.html#diffimages for details.
--
cheers,
Mike Williams
Sorry it took so long to respond. This email was sent when I was out
of town and I completely forgot about it until now. This is definitely
something I will have to look into and that I'm very interested in
doing. I'll keep you up to date on what the status of this is. I don't
see any downsides to it if it works just as you described. I wasn't
even aware of this functionality!
Mitchell
Yes, see the linked clones section here:
https://www.vagrantup.com/docs/virtualbox/configuration.html
HTH, Torben
Was this ever implemented and if so can you point me to any details?
Tia
--
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/dc4f7a18-7324-4615-b55f-5d153a0c889c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Yes, see the linked clones section here:
https://www.vagrantup.com/docs/virtualbox/configuration.htmlHTH, Torben
Am 13.08.2016 8:11 nachm. schrieb "Edward Evans" <ed.e...@gmail.com>:
Was this ever implemented and if so can you point me to any details?
Tia
--
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 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/0ab52fb3-afd7-4d99-8611-d14a9ff52e3f%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/0ab52fb3-afd7-4d99-8611-d14a9ff52e3f%40googlegroups.com.
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/4dc2a6d0-9d5c-4fb5-ba0b-8a4fb8c1f06d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.