Vagrant: There was an error while executing `VBoxManage`

[Exuviax]

I am so confused what to do at this point, I am just trying to get project Lita up, and I seem to be running into one issue after another. I am on the latest stable version of Ubuntu.

My err

root@randy-VirtualBox:~/lita/lita-dev$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'coreos-stable'...
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["import", "/home/randy/.vagrant.d/boxes/coreos-stable/835.10.0/virtualbox/box.ovf", "--vsys", "0", "--vmname", "coreos_production_vagrant-835-10-0_1453344987917_57721", "--vsys", "0", "--unit", "7", "--disk", "/home/randy/VirtualBox VMs/coreos_production_vagrant-835-10-0_1453344987917_57721/coreos_production_vagrant_image.vmdk"]

Stderr: 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Interpreting /home/randy/.vagrant.d/boxes/coreos-stable/835.10.0/virtualbox/box.ovf...
OK.
0%...
Progress state: VBOX_E_FILE_ERROR
VBoxManage: error: Appliance import failed
VBoxManage: error: Could not create the imported medium '/home/randy/VirtualBox VMs/coreos_production_vagrant-835-10-0_1453344987917_57721/coreos_production_vagrant_image.vmdk'.
VBoxManage: error: VMDK: cannot write allocated data block in '/home/randy/VirtualBox VMs/coreos_production_vagrant-835-10-0_1453344987917_57721/coreos_production_vagrant_image.vmdk' (VERR_DISK_FULL)
VBoxManage: error: Details: code VBOX_E_FILE_ERROR (0x80bb0004), component ApplianceWrap, interface IAppliance
VBoxManage: error: Context: "RTEXITCODE handleImportAppliance(HandlerArg*)" at line 877 of file VBoxManageAppliance.cpp

[sethvargo]

Hi @Exuviax

That error is coming from Virtualbox, not Vagrant. The error message seems to indicate your disk does not have enough space to create the VM.

[sethvargo]

Hi there,

I am going to close this issue due to inactivity. If this is still occurring, please open a _new_ issue and follow the accompanying template so we can reproduce and fix this as quickly as possible. Thanks!