Add some way to increase disk space from Vagrantfile

[peterbraden]

At the moment you can increase memory in the vagrantfile, but if you want to increase disk space you have to use the VBoxManage tool to enlarge the image. It would be great to be able to specify this in the vagrantfile.

[mitchellh]

You can do this already.

config.vm.customize "virtualbox" do |vb|
  vb.customize "pre-boot", ["..."]
end

It just isn't documented yet. But will be soon. Sorry!

[peterbraden]

what would I put in the pre-boot list - does it take the same commands as the VBoxManage tool?

[mitchellh]

Yes, it is VBoxManage.

[peterbraden]

This gives me:

"Bringing machine 'default' up with 'virtualbox' provider...
There are errors in the configuration of this machine. Please fix
the following errors and try again:

VirtualBox Provider:

• virtualbox is not a valid event for customization. Valid events
  are: pre-import, pre-boot, post-boot"

[tmatilai]

The example should be:

config.vm.provider "virtualbox" do |vb|
  vb.customize "pre-boot", ["..."]
end

[haf]

What are you supposed to put in there?

I tried

v.customize 'pre-boot', ['modifyhd', :id, '--resize', '15360']

Giving

[app] Running 'pre-boot' VM customizations...
A customization command failed:

["modifyhd", "f7ee3447-5748-4562-9ca2-87639ec39515", "--resize", "15360"]

The following error was experienced:

VBoxManage: error: The given path 'f7ee3447-5748-4562-9ca2-87639ec39515' is not fully qualified
VBoxManage: error: Details: code VBOX_E_FILE_ERROR (0x80bb0004), component Medium, interface IMedium, callee nsISupports
VBoxManage: error: Context: "OpenMedium(Bstr(pszFilenameOrUuid).raw(), enmDevType, enmAccessMode, fForceNewUuidOnOpen, pMedium.asOutParam())" at line 178 of file VBoxManageDisk.cpp


Please fix this customization and try again.

[odino]

hey @haf did you find a way out? :)

[haf]

Hi @odino, no shortly afterwards VMWare blue-screened my Mac and corrupted the VM anyway so I had to redo all the work. This time I chose a larger size initially.

[tmatilai]

That :id will expand to the machine ID, while modifyhd expects ID or file system path of the disk image.
But I don't know how to get access to those in Vagrantfile context.

[snowch]

You can use vboxmanage showvminfo UUID to find the disk UUID

vboxmanage showvminfo e47cb0df-0799-4de7-8073-58239da86216
...
SATA Controller (0, 0): /home/me/VirtualBox VMs/mybox_1389356990435_59717/box-disk1.vmdk (UUID: 6eb5858a-a486-4b41-a1fb-1cb9f0eb7e5f)
...

I was hoping that the showvminfo command could be executed by vb.customize and the response parsed.

vb.customize [ "showvminfo", :id ]

Howver, vb.customize does not return a response.

[kikitux]

for virtualbox, if the disk is not VDI, then is not easy to expand the disk.

you should turn the guest off, clone the disk from vmdk to vdi, dettach
vmdk, attach vdi, expand vdi, then turn the machine on, and expand the
filesystem on the disk.

What OS you are using ?? I think will be way easier create a new VM with
the desired disk with packer and then use it in vagrant.

Alvaro.

On Wed, Jan 22, 2014 at 11:50 AM, snowch notifications@github.com wrote:

You can use vboxmanage showvminfo UUID to find the disk UUID

vboxmanage showvminfo e47cb0df-0799-4de7-8073-58239da86216
...
SATA Controller (0, 0): /home/me/VirtualBox VMs/mybox_1389356990435_59717/box-disk1.vmdk (UUID: 6eb5858a-a486-4b41-a1fb-1cb9f0eb7e5f)
...

I was hoping that the showvminfo command could be executed by
vb.customize and the response parsed.

vb.customize [ "showvminfo", :id ]

Howver, vb.customize does not return a response.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/2339#issuecomment-32973372
.

[snowch]

@kikitux it's not easy, but it should be possible to automate shouldn't it?

The guest OS is CentOS 6.4. The host OS could be any OS supported by Vagrant.

The driver behind this requirement to increase the disk size of an existing box is that many security teams will only the use a 'trusted' third party boxes. It is better for me to expand a trusted image than create and make available my own non trusted image.

I've just taken a look at packer - thanks for the tip! I'll take a look and see if that solves the problem.

[kikitux]

When you say my box, then i understand you are creating in some way the box.

I will say the easiest will be when you create the box, create a BIG disk,
say 50GB, as the disk will be an sparse disk, it will use only the size
that is actually used.

I do custom boxes for my test and I use 4 disks of 32GB, so should use
128GB, but the vagrant box is just 700MB for the OS, or couple of gigs when
I install the software.

If this approach work for you, then I will suggest import the box to
vagrant, do the expansion manually (or by some script outside vagrant) and
then export the box and you will get the new machine.

If, the boxes are not yours, and are 3rd party (created, managed by
others), then I will suggest teach the users how to do it, (teach them to
catch fish), or you will be the man in the middle all the time.

I don't think this is an Vagrant issue, so I think the best is to talk in
the mailing list..

I am more than happy to assist if you need any help with the
commands/order/etc, in the mailing list.

(vagrantup.com -> about -> support -> check around for the mailing list)

Alvaro.

On Wed, Jan 22, 2014 at 7:34 PM, snowch notifications@github.com wrote:

@kikitux https://github.com/kikitux it's not easy, but it is possible
to automate isn't it?

The guest OS is CentOS 6.4. The host OS could be any OS supported by
Vagrant.

The driver behind this requirement is that many security teams will only
the use a 'trusted' third party boxes. It is better for me to expand a
trusted image than create and make available my own non trusted image.

I've just taken a look at packer - thanks for the tip! Packer may overcome
the issue of automating the image, but it looks as though it adds another
installation step for users of my box. Asking my users to install vagrant,
virtualbox, cygwin/putty (windows users), 3 vagrant plugins, and packer is
a big barrier to people using my box.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/2339#issuecomment-32996903
.

[snowch]

@kikitux I'm not creating a box. I don't want to do this because my security team don't trust boxes that are available in places like dropbox.

I'm using a box from a trusted place (the specific box is http://puppet-vagrant-boxes.puppetlabs.com/centos-64-x64-vbox4210.box). Someone raised an issue against them 4 months ago to increase the box size:

puppetlabs/puppet-vagrant-boxes#33

The pull request seems to still be open :(

Thanks for your feedback and kind offer of assistance.