VirtualBox 4.2.14 Breaks Vagrant 1.2.2 When Importing Boxes

[terrywang]

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 opscode_ubuntu-12.04_chef-11.4.4.box.

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

Screen shot

Workaround

• 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 > box.mf, 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.

[marsmensch]

Works fine for me on Linux, but most parts of your issue report are simply
confusing.

Which "Germans" are you referring to?
Why do you mention your switch from pacman?
Which linux distribution and version are you using?
Which osx version are you using?
Why are you dist-upgrading?

Try to structure your issue feedback a bit, you can do better.

Cheers

Florian

Am 22.06.2013 um 14:08 schrieb Terry Wang [email protected]:

Vagrant 1.2.2 was working perfectly fine with VirtualBox 4.2.12.

When testing some cookbooks using chef-solo, I did a apt-get update &&
apt-get dist-upgrade -y (used to run pacman -Syu but for some reason I
switched;-) which Linux dudes do all the time and it updated to 4.2.14.

The Germans like to release new versions at their Friday, LOL

After the update vagrant init breaks. I have verified that it happens on
both Linux and OS X.

Screen shot
[image: Vagrant 1.2.2
breaks]https://a248.e.akamai.net/camo.github.com/be1d4ea35ab2a0280ca26043f2b058c65d17761e/687474703a2f2f6661726d362e737461746963666c69636b722e636f6d2f353534372f393130373834303637325f333639346161396666645f6f2e706e67

Rolling back to 4.2.12, everything started to work again.

Looking at the Changelog https://www.virtualbox.org/wiki/Changelog, I
reckon the following 3 OVF related items may be the culprit.

• Main/OVF: don't crash during import if the client forgot to call
  Appliance::interpret() (bug InvalidByteSequenceError on vagrant plugin install #10845)
• Main/OVF: don't create invalid appliances by stripping the file name
  if the VM name is very long (bug Updates to address all Ruby deprecations and warnings #11814)
• Main/OVF: don't fail if the appliance contains multiple file
  references (bug vagrant.provision runs inline powershell script twice #10689)

I'll add more details, hopefully debug logs VAGRANT_LOG=debug on Monday
when I get back to work.

—
Reply to this email directly or view it on
GitHubhttps://github.com//issues/1850
.

[bradleyy]

I believe this is a duplicate of issue #1847 .

[terrywang]

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

[offby1]

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

[athiele]

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

[terrywang]

Public VirtualBox Ticket => https://www.virtualbox.org/ticket/11895

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

[benben]

👍

[jrgifford]

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.

[terrywang]

@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.

[ngpestelos]

👍

[petems]

Awesome, was having this issue as well, downgrading in the meantime fixed it 👍

[ghost]

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...
OK.
0%...
Progress object failure: NS_ERROR_CALL_FAILED 

[ehthayer]

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

openssl sha1 *.vmdk *.ovf > box.mf

vagrant up then worked fine with VirtualBox 4.2.14

[science]

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

[plexus]

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

[rossipedia]

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

[php-coder]

👍 for @ehthayer's workaround. Thanks for sharing this!

[fooblahblah]

@ehthayer +1. Fixed me up on ArchLinux!

[oieduardorabelo]

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

[oliverhr]

Same issue on windows7 , even with self generated box. issue fixed Create Manifest File like in @ehthayer's workaround with msysgit.
http://www.virtuallyghetto.com/2012/01/how-to-create-manifest-file-for-ovf.html

[aphorise]

• OS X 10.8.4
• VirtualBox 4.2.14

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

✌️ 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.

[terrywang]

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 vagrant + docker desktop - vagrant reload fails - Guest-specific operations were attempted on a machine that is not ready for guest communication #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 Configuring and enabling network interfaces... `await_response_state': Agent pid 3330 (RuntimeError) #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 Don't try to "fix" a /etc/fstab that does not exist #11899)
• Mac OS X hosts: after removing VirtualBox with VirtualBox_Uninstall.tool, remove it from the pkgutil --pkgs list as well

[lucasdavila]

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