3 ms·
Ah, I didn't think you'd be interested in LXC as I thought you'd be running your VMs under OS X? If you're considering running VirtualBox (Vagrant) under Linux
by e12e 14y ago
Ah, I didn't think you'd be interested in LXC as I thought you'd be running your VMs under OS X?
If you're considering running VirtualBox (Vagrant) under Linux/Solaris, VirtualBox does support a limited form of overcommitting RAM (not under OS X, however):
https://www.virtualbox.org/manual/ch04.html#idp18673360
I believe you can use this with Vagrant via:
http://vagrantup.com/v1/docs/config/vm/customize.html
You still have to dedicate RAM to VirtualBox -- but you no longer have to dedicate it to each VM.
If you are already using Citrix, the Xen Server product has supported a limited form of overcommit since version 5.6:
http://support.citrix.com/article/CTX124972
I would think spending time automating deployment to the same environment as you use for production would be better than having a separate technology for development? I don't know what your internal politics are like, but setting up a dedicated server with a few tens of gigs of RAM for development and testing should be a worthwhile investment -- and running the same software there as in production should be good both for knowledge transfer and avoiding surprises going from testing to production (and vice versa).
Finally, I've been a impressed with vmware's new open source project, CloudFoundry.com/.org -- if not so impressed with their documentation for the free/open version. Apparently you can use that with VirtualBox as well:
http://matschaffer.com/2011/04/cloudfoundry-virtualbox/
Note that Vagrant is in the process of being refactored with the goal of adding support for other hosts than just VirtualBox in the (relatively) near future.