Clean install on OS X 10.8.4 w/ latest VirtualBox not working #1847

hrak · 2013-06-21T22:13:44Z

Hi,

I wanted to check out Vagrant for Chef development but it doesn't seem to work.

Installed from scratch:

VirtualBox 4.2.14 r86644 with extension pack
Vagrant 1.2.2

Did the following, just like the getting started guide:

iMac:dev hans$ mkdir vagrant_test
iMac:dev hans$ cd vagrant_test
iMac:vagrant_test hans$ vagrant init precise32 http://files.vagrantup.com/precise32.box
A `Vagrantfile` has been placed in this directory. You are now
ready to `vagrant up` your first virtual environment! Please read
the comments in the Vagrantfile as well as documentation on
`vagrantup.com` for more information on using Vagrant.
iMac:vagrant_test hans$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
[default] Box 'precise32' was not found. Fetching box from specified URL for
the provider 'virtualbox'. Note that if the URL does not have
a box for this provider, you should interrupt Vagrant now and add
the box yourself. Otherwise Vagrant will attempt to download the
full box prior to discovering this error.
Downloading or copying the box...
Extracting box...te: 2799k/s, Estimated time remaining: 0:00:01)
Successfully added box 'precise32' with provider 'virtualbox'!
[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/hans/.vagrant.d/boxes/precise32/virtualbox/box.ovf"]

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

Then manually ran VBoxManage but didn't get much info from that:

iMac:vagrant_test hans$ VBoxManage import "/Users/hans/.vagrant.d/boxes/precise32/virtualbox/box.ovf"
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Interpreting /Users/hans/.vagrant.d/boxes/precise32/virtualbox/box.ovf...
OK.
Disks:  vmdisk1 85899345920 -1  http://www.vmware.com/interfaces/specifications/vmdk.html#streamOptimized   box-disk1.vmdk  -1  -1
Virtual system 0:
 0: Suggested OS type: "Ubuntu"
    (change with "--vsys 0 --ostype "; use "list ostypes" to list all possible values)
 1: Suggested VM name "precise32"
    (change with "--vsys 0 --vmname ")
 2: Number of CPUs: 1
    (change with "--vsys 0 --cpus ")
 3: Guest memory: 384 MB
    (change with "--vsys 0 --memory ")
 4: Network adapter: orig NAT, config 3, extra slot=0;type=NAT
 5: CD-ROM
    (disable with "--vsys 0 --unit 5 --ignore")
 6: IDE controller, type PIIX4
    (disable with "--vsys 0 --unit 6 --ignore")
 7: IDE controller, type PIIX4
    (disable with "--vsys 0 --unit 7 --ignore")
 8: SATA controller, type AHCI
    (disable with "--vsys 0 --unit 8 --ignore")
 9: Hard disk image: source image=box-disk1.vmdk, target path=/Users/hans/VirtualBox VMs/precise32/box-disk1.vmdk, controller=8;channel=0
    (change target path with "--vsys 0 --unit 9 --disk path";
    disable with "--vsys 0 --unit 9 --ignore")
0%...
Progress object failure: NS_ERROR_CALL_FAILED
iMac:vagrant_test hans$ vagrant -v
Vagrant version 1.2.2

bradleyy · 2013-06-22T04:54:37Z

I'm having the exact same issue; only change is that I have MacOS 10.7.5.

bannio · 2013-06-22T21:44:37Z

Exactly the same for me too. Same software versions (OS X 10.8.4, VirtualBox 4.2.14 r86644, Vagrant 1.2.2) but with precise64. Tried precise32 with same effect.

lhoBas · 2013-06-22T22:04:17Z

Having the same problem here. Also on OS X 10.8.4, VirtualBox 4.2.14 r86644, Vagrant 1.2.2. Experienced it with both precise64 & precise32.

Since this seems to be related to the VirtualBox update in combination with OS X, every user who runs a fresh install on OS X will most likely run into this issue.

On 22 jun. 2013, at 23:44, Owen Bannister notifications@github.com wrote:

Exactly the same for me too. Same software versions (OS X 10.8.4, VirtualBox 4.2.14 r86644, Vagrant 1.2.2) but with precise64. Tried precise32 with same effect.

—
Reply to this email directly or view it on GitHub.

bradleyy · 2013-06-22T22:15:13Z

It looks like rolling back to the previous version of VirtualBox (4.2.10) is the beginning of a suitable workaround; I am now able to run:

vagrant up

and it gets further, but hangs at "waiting for boot". The VirtualBox log is at: http://pastebin.com/7RsU31EV

jaydrogers · 2013-06-23T04:39:36Z

Downgrading from 4.2.14 to 4.2.10 worked for me too.

Mac OS X 10.8.4 15" Macbook Pro

I grabbed the older version from here: https://www.virtualbox.org/wiki/Download_Old_Builds

lkdjiin · 2013-06-23T06:49:34Z

Same issue on Debian with vagrant 1.2.2 or 1.1.5. Downgrading to virtualbox 4.2.10 and all works as before.

ksylvan · 2013-06-23T07:09:05Z

Same issue with Fedora 18, running vagrant 1.2.2 and VirtualBox-4.2-4.2.14_86644_fedora18-1.x86_64:

$ vagrant init precise32 http://files.vagrantup.com/precise32.box
A Vagrantfile has been placed in this directory. You are now
ready to vagrant up your first virtual environment! Please read
the comments in the Vagrantfile as well as documentation on
vagrantup.com for more information on using Vagrant.

$ vagrant up
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", "/home/ksylvan/.vagrant.d/boxes/precise32/virtualbox/box.ovf"]

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

thomassittig · 2013-06-23T08:47:03Z

same issue as described above here with a macbook and osx 10.8.4.
and the workaround with the virtualbox downgrade to the 4.2.10 works fine

bjwschaap · 2013-06-23T13:59:50Z

Reproduced this exact issue as well. Using Ubuntu 12.10, Vagrant 1.2.2 and VirtualBox 4.2.14 r86644. Reverting back to a previous VirtualBox version helps, but I'd like to use 4.2.14 a.s.a.p. ofcourse..

jcook793 · 2013-06-23T16:01:38Z

Ran into the same issue here. Reverting VirtualBox fixed the situation. Thanks for figuring out the temp fix.

daniellangnet · 2013-06-23T16:35:24Z

Same issue here. Reverting helped.

trappar · 2013-06-23T16:48:40Z

Same issue. Thought it was due to running 10.9 DP but I guess not. Reverting did at least get me past that stage.

wesray · 2013-06-23T19:15:14Z

Downgrading also fixed this for me as well. Cheers.

mitchellh · 2013-06-23T19:32:17Z

It appears that VirtualBox 4.2.14 import is just broken. Please downgrade and hope that VirtualBox fixes this.

terrywang · 2013-06-23T22:56:39Z

1 of the 3 items in VirtualBox 4.2.14 Changelog 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)

terrywang · 2013-06-24T10:33:54Z

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

mitchellh · 2013-06-24T16:05:59Z

@terrywang Great! Let me know if/when they fix it. :)

terrywang · 2013-06-25T10:24:39Z

@mitchellh Public ticket here => https://www.virtualbox.org/ticket/11895

The problem has already been fix, a maintenance release will be available soon;-)

mooru · 2013-07-01T21:43:06Z

downgrade did not help me

terrywang · 2013-07-01T23:10:40Z

@mooru See the other workaround provided by @ehthayer in #1850

Simply go into ~/.vagrant.d/boxes/BaseBoxName/virtualbox and do openssl sha1 *.vmdk *.ovf > box.mf, vagrant up, it is reported to be working fine with VirtualBox 4.2.14.

ksylvan · 2013-07-01T23:30:14Z

@terrywang Yes, that works perfectly. Thank you.

ghost · 2013-07-01T23:40:52Z

@terrywang Worked for my setup as well: CentOS box, vagrant 1.2.2, VirtualBox 4.2.14 r86644

barapa · 2013-07-02T16:21:50Z

@terrywang Worked for me as well. Thanks!

ksylvan · 2013-07-02T20:27:13Z

Using @terrywang solution, I created this quick shell script. Copy and paste the shell script code below into a file and run it to fix any boxes you have in your ~/.vagrant.d directory.

I put this in fix-vagrant-manifest. A sample run:

[ksylvan@ksylvan-t420 vagrant-lamp:(master)]$ vagrant up
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", "/home/ksylvan/.vagrant.d/boxes/precise32/virtualbox/box.ovf"]

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

So, run the script:

[ksylvan@ksylvan-t420 vagrant-lamp:(master)]$ fix-vagrant-manifest 
precise32 manifest generated.

Now the "vagrant up" command runs.

[ksylvan@ksylvan-t420 vagrant-lamp:(master)]$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
[default] Importing base box 'precise32'...
[default] Matching MAC address for NAT networking...
[default] Setting the name of the VM...
[default] Clearing any previously set forwarded ports...
[default] Creating shared folders metadata...
[default] Clearing any previously set network interfaces...
[default] Preparing network interfaces based on configuration...
[default] Forwarding ports...

Here is the script:

#!/bin/sh

gen_mf()
{
  openssl sha1 *.vmdk *.ovf > box.mf
}

cd $HOME/.vagrant.d/boxes
c=$(pwd)
for i in *
do
  if [ -r $i/virtualbox/box.mf ]
  then
    echo $i already has a manifest. Skipped.
  else
    cd $i/virtualbox
    gen_mf
    echo $i manifest generated.
  fi
  cd $c
done

eudisd · 2013-07-03T01:16:47Z

@terrywang Worked for me as well, thanks!

faceleg · 2013-07-03T10:00:36Z

@terrywang thanks for posting, worked here as well.

agemmell · 2013-07-03T18:55:30Z

@terrywang Thumbs-up, worked for me too!

weiser · 2013-07-03T19:49:39Z

Simply go into ~/.vagrant.d/boxes/BaseBoxName/virtualbox and do openssl sha1 *.vmdk *.ovf > box.mf, vagrant up, it is reported to be working fine with VirtualBox 4.2.14.

Worked for me, thanks!

hbokh · 2013-07-04T20:22:43Z

FYI VirtualBox 4.2.16 was released today (Indepenence Day): seems to have it fixed overhere.
URL to DL-directory: http://download.virtualbox.org/virtualbox/4.2.16/
File: VirtualBox-4.2.16-86992-OSX.dmg

terrywang · 2013-07-04T21:50:17Z

VirtualBox 4.2.16 released. I have confirmed (only on Linux x86_64 though) that it (vagrant init - importing base box) works fine with vagrant 1.2.2.

nterray · 2013-07-04T22:33:14Z

I confirm that the issue is fixed with VirtualBox 4.2.16.

wietsevenema · 2013-07-05T12:40:55Z

Yes, fixed with VirtualBox 4.2.16

niftylettuce · 2013-07-05T18:18:33Z

thanks

bradleyy mentioned this issue Jun 22, 2013

VirtualBox 4.2.14 Breaks Vagrant 1.2.2 When Importing Boxes #1850

Closed

mitchellh closed this as completed Jun 23, 2013

MaciekBaron mentioned this issue Jun 26, 2013

"Guru meditation" on boot, every version of VirtualBox and Vagrant and Ubuntu on OS X 10.8.4 #1871

Closed

felipecvo mentioned this issue Jul 5, 2013

Update VirtualBox to 4.2.16 boxen/puppet-virtualbox#11

Merged

yellis mentioned this issue Nov 9, 2013

Error with machine config JasonPunyon/redishobo#5

Closed

ghost locked and limited conversation to collaborators Apr 14, 2020

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Clean install on OS X 10.8.4 w/ latest VirtualBox not working #1847

Clean install on OS X 10.8.4 w/ latest VirtualBox not working #1847

hrak commented Jun 21, 2013

bradleyy commented Jun 22, 2013

bannio commented Jun 22, 2013

lhoBas commented Jun 22, 2013

bradleyy commented Jun 22, 2013

jaydrogers commented Jun 23, 2013

lkdjiin commented Jun 23, 2013

ksylvan commented Jun 23, 2013

thomassittig commented Jun 23, 2013

bjwschaap commented Jun 23, 2013

jcook793 commented Jun 23, 2013

daniellangnet commented Jun 23, 2013

trappar commented Jun 23, 2013

wesray commented Jun 23, 2013

mitchellh commented Jun 23, 2013

terrywang commented Jun 23, 2013

terrywang commented Jun 24, 2013

mitchellh commented Jun 24, 2013

terrywang commented Jun 25, 2013

mooru commented Jul 1, 2013

terrywang commented Jul 1, 2013

ksylvan commented Jul 1, 2013

ghost commented Jul 1, 2013

barapa commented Jul 2, 2013

ksylvan commented Jul 2, 2013

eudisd commented Jul 3, 2013

faceleg commented Jul 3, 2013

agemmell commented Jul 3, 2013

weiser commented Jul 3, 2013

hbokh commented Jul 4, 2013

terrywang commented Jul 4, 2013

nterray commented Jul 4, 2013

wietsevenema commented Jul 5, 2013

niftylettuce commented Jul 5, 2013

Clean install on OS X 10.8.4 w/ latest VirtualBox not working #1847

Clean install on OS X 10.8.4 w/ latest VirtualBox not working #1847

Comments

hrak commented Jun 21, 2013

bradleyy commented Jun 22, 2013

bannio commented Jun 22, 2013

lhoBas commented Jun 22, 2013

bradleyy commented Jun 22, 2013

jaydrogers commented Jun 23, 2013

lkdjiin commented Jun 23, 2013

ksylvan commented Jun 23, 2013

thomassittig commented Jun 23, 2013

bjwschaap commented Jun 23, 2013

jcook793 commented Jun 23, 2013

daniellangnet commented Jun 23, 2013

trappar commented Jun 23, 2013

wesray commented Jun 23, 2013

mitchellh commented Jun 23, 2013

terrywang commented Jun 23, 2013

terrywang commented Jun 24, 2013

mitchellh commented Jun 24, 2013

terrywang commented Jun 25, 2013

mooru commented Jul 1, 2013

terrywang commented Jul 1, 2013

ksylvan commented Jul 1, 2013

ghost commented Jul 1, 2013

barapa commented Jul 2, 2013

ksylvan commented Jul 2, 2013

eudisd commented Jul 3, 2013

faceleg commented Jul 3, 2013

agemmell commented Jul 3, 2013

weiser commented Jul 3, 2013

hbokh commented Jul 4, 2013

terrywang commented Jul 4, 2013

nterray commented Jul 4, 2013

wietsevenema commented Jul 5, 2013

niftylettuce commented Jul 5, 2013