Skip to content


Subversion checkout URL

You can clone with
Download ZIP


VirtualBox 4.2.14 Breaks Vagrant 1.2.2 When Importing Boxes #1850

terrywang opened this Issue · 23 comments

Vagrant 1.2.2 was working perfectly fine with VirtualBox 4.2.12.

After upgrading to 4.2.14, Vagrant fails to at init - importing the box

It happens on both Linux and OS X, with the same base box (could be related to base box format).

Screen shot
Vagrant 1.2.2 breaks


  • Rolling back to 4.2.12, everything started to work again.
  • @ehthayer provided another workaround without rolling back to old versionsWorked around this issue on Centos 5.9 by going to ~/.vagrant.d/boxes/BoxName/virtualbox and doing openssl sha1 *.vmdk *.ovf >, vagrant up then worked fine with VirtualBox 4.2.14, many thanks to him!
  • For Ubuntu amd64 users, try the 4.2.15 test build

Official Fix

It's been confirmed that this is a VirtualBox bug, see Ticket 11895. It'll be fixed in the next VirtualBox maintenance release. Hopefully it'll be released soon.


I believe this is a duplicate of issue #1847 .


Heads up: VirtualBox team is investigating the issue. Looks like there is a problem with importing appliances without manifests.


@terrywang Have you got a URL to the relevant discussion in VirtualBox?


We also had this error with Vagrant 1.0.7 and VBox 4.2.14 on Windows. Downgrading to 4.2.10 helped.


Public VirtualBox Ticket =>

The problem has already been fix in mainline/master (whatever you call it), a maintenance release will be available soon;-)


For those of us on Raring 64 bit who are impatient and need this fixed now, we can try the test build on comment 2 on the upstream ticket.


@jrgifford Thanks for mentioning this. I didn't notice there was a hidden link in comment 2.

I just tried the test build 4.2.15-86695 on Ubuntu 13.04 amd64. It does fix the import issue, Vagrant is up and running again;-)

Once an official maintenance release is available, I'll update and close this issue.


Awesome, was having this issue as well, downgrading in the meantime fixed it :+1:


Same issue on OS X 10.9 (13A497d), downgrading Virtualbox 4.2.12 fixes it.

Bringing machine 'default' up with 'virtualbox' provider...
[default] Importing base box 'precise32'...
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/edg3e/.vagrant.d/boxes/precise32/virtualbox/box.ovf"]

Stderr: 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Interpreting /Users/mp4976qpa/.vagrant.d/boxes/precise32/virtualbox/box.ovf...
Progress object failure: NS_ERROR_CALL_FAILED 

Worked around this issue on Centos 5.9 by going to ~/.vagrant.d/boxes/MyBoxName/virtualbox and doing

openssl sha1 *.vmdk *.ovf >

vagrant up then worked fine with VirtualBox 4.2.14


Downgrading to VirtualBox 4.2.12 on Win8 64 pro fixed the issue I was having..


:+1: for @ehthayer 's workaround, works perfectly and no need to up/downgrade virtualbox


:+1: for @ehthayer's workaround. Worked perfectly for me on Win 8 Pro command line using Git for Windows' openssl.exe


:+1: for @ehthayer's workaround. Thanks for sharing this!


@ehthayer +1. Fixed me up on ArchLinux!


+1 for @ehthayer 's workaround, fixed me on Mac OS X 10.8.4


Same issue on windows7 , even with self generated box. issue fixed Create Manifest File like in @ehthayer's workaround with msysgit.

  • OS X 10.8.4
  • VirtualBox 4.2.14

As detailed earlier this results in:
Progress object failure: NS_ERROR_CALL_FAILED

:v: To Confirm: downgrading VirtualBox to 4.2.12 resolved - and updating VirtualBox (to 4.2.14) thereafter worked for a colleague but not for me.

Wanted to try @ehthayer suggestion with SHA1 signature - I was however unable to upgrade to 4.2.14.


Guys, just to let you know that VirtualBox 4.2.16 has just been released. The OVF/OVA import issue has been fixed.

I have confirmed that Vagrant 1.2.2 works perfectly fine with 4.2.16, just like the old times.

Closing this issue, cc @mitchellh

Include the ChangeLog for your reference.

VirtualBox 4.2.16 (released 2013-07-04)

This is a maintenance release. The following items were fixed and/or added:

  • OVF/OVA: don't crash on import if no manifest is used (4.2.14 regression; bug #11895)
  • GUI: do not restore the current snapshot if we power-off after a Guru Mediation
  • Storage: fixed a crash when hotplugging an empty DVD drive to the VM
  • Storage: fixed a crash when a guest read from a DVD drive attached to the SATA controller under certain circumstances
  • EFI: don't fail with 64-bit guests on 32-bit hosts (bug #11456)
  • Autostart: fixed VM startup on OS X
  • Windows hosts: native Windows 8 controls
  • Windows hosts: restore native style on Vista 32
  • Windows hosts / guests: Windows 8.1 adaptions (bug #11899)
  • Mac OS X hosts: after removing VirtualBox with VirtualBox_Uninstall.tool, remove it from the pkgutil --pkgs list as well
@terrywang terrywang closed this

:+1: tks @ehthayer, you tip fixed the error on my mac os x 10.8.4 :D

@chad-thompson chad-thompson referenced this issue in chad-thompson/vagrantpress

Failing to see Wordpress installation #23

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.