Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.

cmarfil's avatar

Error with homestead up

Hello, i following the instructions to setup homestead and homstead up return:

☁  ~  homestead up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'laravel/homestead'...
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["import", "/Users/cmarfil/.vagrant.d/boxes/laravel-VAGRANTSLASH-homestead/0.2.2/virtualbox/box.ovf", "--vsys", "0", "--vmname", "settler_default_1419000625797_92760_1424667778246_80033", "--vsys", "0", "--unit", "7", "--disk", "/Users/cmarfil/VirtualBox VMs/settler_default_1419000625797_92760_1424667778246_80033/box-disk1.vmdk"]

Stderr: 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Interpreting /Users/cmarfil/.vagrant.d/boxes/laravel-VAGRANTSLASH-homestead/0.2.2/virtualbox/box.ovf...
OK.
0%...
Progress state: VBOX_E_FILE_ERROR
VBoxManage: error: Appliance import failed
VBoxManage: error: Could not create the imported medium '/Users/cmarfil/VirtualBox VMs/settler_default_1419000625797_92760_1424667778246_80033/box-disk1.vmdk'.
VBoxManage: error: VMDK: Compressed image is corrupted '/Users/cmarfil/.vagrant.d/boxes/laravel-VAGRANTSLASH-homestead/0.2.2/virtualbox/box-disk1.vmdk' (VERR_ZIP_CORRUPTED)
VBoxManage: error: Details: code VBOX_E_FILE_ERROR (0x80bb0004), component Appliance, interface IAppliance
VBoxManage: error: Context: "int handleImportAppliance(HandlerArg*)" at line 779 of file VBoxManageAppliance.cpp

I tested the method without composer with git clone and same result.

Any idea?

Thanks!

0 likes
12 replies
bobbybouwmann's avatar

Try updating VirualBox ;) They patched some stuff around this subject

cmarfil's avatar

I have the last version, downloaded for the first time yesterday :/

@blackbird u are on all topics ;P

bashy's avatar

Worrying: VBoxManage: error: VMDK: Compressed image is corrupted

rawfan's avatar

Open vbox and try to run anything at all (just create an emty vm and boot it). Could be that your imac doesn't support virtualization.

Pendo's avatar

Same problem here, did you get this fixed @cmarfil?

What I tried so far:

  1. Forcing to re-add the laravel/homestead vagrant box
  2. Removing the VMs from VirtualBox
  3. Removing all files under ~/VirtualBox VMs/
  4. Perform a 'sudo VirtualBox restart' command from the command line
  5. Re-install VirtualBox
  6. Re-install Vagrant
  7. Rebooting my machine

The error message doens't ring any bells to me unfortunately

pendo@pendo:~$ homestead up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'laravel/homestead'...
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["import", "/Users/pendo/.vagrant.d/boxes/laravel-VAGRANTSLASH-homestead/0.2.6/virtualbox/box.ovf", "--vsys", "0", "--vmname", "settler_default_1430450956915_11366_1432468719324_89357", "--vsys", "0", "--unit", "7", "--disk", "/Users/PendoMBP/VirtualBox VMs/settler_default_1430450956915_11366_1432468719324_89357/box-disk1.vmdk"]

Stderr: 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Interpreting /Users/pendo/.vagrant.d/boxes/laravel-VAGRANTSLASH-homestead/0.2.6/virtualbox/box.ovf...
OK.
0%...
Progress state: VBOX_E_IPRT_ERROR
VBoxManage: error: Appliance import failed
VBoxManage: error: Could not create the directory '/Users/PendoMBP/VirtualBox VMs/settler_default_1430450956915_11366_1432468719324_89357' (VERR_ACCESS_DENIED)
VBoxManage: error: Details: code VBOX_E_IPRT_ERROR (0x80bb0005), component Appliance, interface IAppliance
VBoxManage: error: Context: "int handleImportAppliance(HandlerArg*)" at line 779 of file VBoxManageAppliance.cpp
Pendo's avatar

I guess I see where it goes wrong on my part. It's refering to the PendoBMP folder, which was changed to Pendo. Let's dive into VirtualBox and see if I can set the folder somewhere.

// Edit: fixed! Stupid mistake :-)

alexandrobazan's avatar

Same problem here, i'm use Windows 8.1, git bash, homestead 2.0 and the last version of vagrand and virtualbox u.u

sitesense's avatar

@alexandrobazan If you're following the current instructions at the link below (and not a 3 month old version), I guess your problem is not the same.

You need to open a command line at your Homestead folder and run vagrant up instead instead of homestead up.

Current Homestead installation instructions:

http://laravel.com/docs/5.1/homestead

davidangel's avatar

I had the same issue after I renamed my Mac's user account (a rare edge case I'm sure). I had to change Preferences > Default Machine Path in Virtualbox as well.

meilunzhi's avatar

Last login: Mon Nov 23 03:01:57 on ttys001 VBoxManage unregistervm homestead --delete% ☁ ~ VBoxManage unregistervm homestead --delete 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100% ☁ ~ homestead up Bringing machine 'default' up with 'virtualbox' provider... ==> default: Importing base box 'laravel/homestead'... ==> default: Matching MAC address for NAT networking... ==> default: Setting the name of the VM: homestead ==> default: Clearing any previously set network interfaces... ==> default: Preparing network interfaces based on configuration... default: Adapter 1: nat default: Adapter 2: hostonly ==> default: Forwarding ports... default: 80 => 8000 (adapter 1) default: 443 => 44300 (adapter 1) default: 3306 => 33060 (adapter 1) default: 5432 => 54320 (adapter 1) default: 22 => 2222 (adapter 1) ==> default: Running 'pre-boot' VM customizations... ==> default: Booting VM... ==> default: Waiting for machine to boot. This may take a few minutes... The guest machine entered an invalid state while waiting for it to boot. Valid states are 'starting, running'. The machine is in the 'poweroff' state. Please verify everything is configured properly and try again.

If the provider you're using has a GUI that comes with it, it is often helpful to open that and watch the machine, since the GUI often has more helpful error messages than Vagrant can retrieve. For example, if you're using VirtualBox, run vagrant up while the VirtualBox GUI is open.

The primary issue for this error is that the provider you're using is not properly configured. This is very rarely a Vagrant issue. ☁ ~ what think about this? help!

Please or to participate in this conversation.