Is shortly days or weeks? I'm doing a proof of concept with chef and 
vagrant and I'd like to use Hyper-V. However, if 1.5.1 is more than a 
couple days away I'll downgrade and use virtual box.

Alternatively, is there a known workaround for the time being?

On Wednesday, March 12, 2014 3:55:44 PM UTC-6, Mitchell Hashimoto wrote:
>
> Marc,
>
> This was a bug introduced in 1.5.0 that is now fixed. It will be part of 
> 1.5.1 that will be released shortly.
>
> Best,
> Mitchell
>
>
> On Wed, Mar 12, 2014 at 12:39 PM, Marc Bejerano 
> <[email protected]<javascript:>
> > wrote:
>
>> Trying to add a box (that works just fine, BTW, on 4 other machines). All 
>> are configured with the same amount of RAM, Windows 7 64-bit, same disk 
>> size. All are on the same network.
>>
>> I am completely flummoxed why this works on 4 out of 6 machines and not 6 
>> out of 6 machines. Any hints/suggestions/ideas are greatly appreciated.
>>
>>
>> C:\Projects\Vagrant>vagrant box add --name vboxdev vboxdev.box
>>
>> C:/HashiCorp/Vagrant/embedded/lib/ruby/2.0.0/json/common.rb:328:in 
>> `read': file too big for single read (IOError)
>>
>>         from 
>> C:/HashiCorp/Vagrant/embedded/lib/ruby/2.0.0/json/common.rb:328:in `load'
>>
>>         from 
>> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.5.0/lib/vagrant/box_metadata.rb:24:in
>>  
>> `initialize'
>>
>>         from 
>> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.5.0/lib/vagrant/action/builtin/box_add.rb:448:in
>>  
>> `new'
>>
>>         from 
>> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.5.0/lib/vagrant/action/builtin/box_add.rb:448:in
>>  
>> `block i
>>
>> n metadata_url?'
>>
>>         from 
>> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.5.0/lib/vagrant/action/builtin/box_add.rb:447:in
>>  
>> `open'
>>
>>         from 
>> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.5.0/lib/vagrant/action/builtin/box_add.rb:447:in
>>  
>> `metadat
>>
>> a_url?'
>>
>>         from 
>> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.5.0/lib/vagrant/action/builtin/box_add.rb:72:in
>>  
>> `block in
>>
>> call'
>>
>>         from 
>> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.5.0/lib/vagrant/action/builtin/box_add.rb:70:in
>>  
>> `map'
>>
>>         from 
>> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.5.0/lib/vagrant/action/builtin/box_add.rb:70:in
>>  
>> `call'
>>
>>         from 
>> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.5.0/lib/vagrant/action/warden.rb:34:in
>>  
>> `call'
>>
>>         from 
>> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.5.0/lib/vagrant/action/builder.rb:116:in
>>  
>> `call'
>>
>>         from 
>> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.5.0/lib/vagrant/action/runner.rb:69:in
>>  
>> `block in run'
>>
>>         from 
>> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.5.0/lib/vagrant/util/busy.rb:19:in
>>  
>> `busy'
>>
>>         from 
>> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.5.0/lib/vagrant/action/runner.rb:69:in
>>  
>> `run'
>>
>>         from 
>> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.5.0/plugins/commands/box/command/add.rb:77:in
>>  
>> `execute'
>>
>>         from 
>> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.5.0/plugins/commands/box/command/root.rb:61:in
>>  
>> `execute'
>>
>>         from 
>> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.5.0/lib/vagrant/cli.rb:42:in
>>  
>> `execute'
>>
>>         from 
>> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.5.0/lib/vagrant/environment.rb:244:in
>>  
>> `cli'
>>
>>         from 
>> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.5.0/bin/vagrant:147:in 
>> `<main>'
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Vagrant" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to [email protected] <javascript:>.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to