Dynamically allocated disks are fast at creation time, but rather slow when working with them. 'VBoxManage createhd' supports the --variant flag which allows to create disks with fixed storage allocation ('Fixed' for the :disk_variant option here). We keep dynamically allocated storage ('Standard') as the default option. Signed-off-by: Thorsten Fischer <email@example.com>
…ate a vbox, the execution is "$ veewee vbox define 'myubuntubox' 'ubuntu-10.10-server-i386'"
I have made a fork from the master and successfully define/build/export/add/init/up a box on windows 7 x64. What I've done so far - https://github.com/whren/veewee.git : - Replacing simple quotes by double quotes as mentioned by ikka as VirtualBox does not support simple quote on windows - Fixed the get_vbox_home for windows has the 'Default machine path' from VBoxManage would include a drive letter, then a ':', so the split didn't correctly work in this case (ie "Default machine folder: C:\Users\[myUserName]\VirtualBox VMs" was resolved to "C" instead of "C:\Users\[myUserName]\VirtualBox VMs"). - Forced opening of files for writing and Tempfile in binary mode to prevent windows CR+LF line end style (see http://www.ruby-forum.com/topic/60697#58748 and http://www.ruby-forum.com/topic/127453#568546) - Fixed a defect, not windows related, for the nogui option not working - Include equivalent of pull request 252 (ui confirm switch to success as confirm does not exists in vagrant ui) - see #252 - Changed CRPropertyList dependency version as libxml-ruby dependency has been removed in version 2.1.1 allowing to build veewee on windows x64 - see ckruse/CFPropertyList#14 - Added an optional pre_postinstall_file in definition, allowing a script to be executed before each postinstall script. The purpose is, for ie, to export proxy env (http_proxy, https_proxy) for working behing a proxy, but not to add such modifications in the future box (modifying /etc/profile for ie). Thanks to this I can build a box behind a proxy, and later, choose to wheter set a fixed proxy by provisioning in the vm. Signed-off-by: Whren <firstname.lastname@example.org>