I can verify that Kevin's issue is a valid one.  I am getting the exact 
same error that Kevin is getting, but I'm on a Mac running Mavericks.  I 
can't speak for Kevin, but the reason why I am not using 1.5.x is because 
it is not compatible with the vagrant-berkshelf plugin.

Andrew



On Wednesday, April 16, 2014 11:56:55 PM UTC-4, Alvaro Miranda Aguilera 
wrote:
>
> why not 1.5.x?
>
> what's the output of  vagrant plugin list
>
> ?
>
>
> On Thu, Apr 17, 2014 at 5:42 AM, Kevin Meredith 
> <[email protected]<javascript:>
> > wrote:
>
>> C:\Users\Kevin>vagrant -v
>> Vagrant 1.4.3
>>
>> C:\Users\Kevin>VBoxManage -version
>> 4.3.10r93012
>>
>> C:\Users\Kevin>vagrant plugin list
>> vagrant-berkshelf (2.0.0)
>> vagrant-omnibus (1.3.1)
>> vagrant-vbguest (0.10.0)
>>
>> On a Windows 7 PC, I was using Vagrant 1.3.5 with VirtualBox 4.3.8, but 
>> upgraded to the above versions in order to attempt to fix a shared 
>> directory problem - 
>> https://groups.google.com/forum/#!topic/vagrant-up/eC72_YXdtYE.
>>
>> Anyway, after upgrading to the first listed versions, I destroyed my VM 
>> with VirtualBox using "Remove / Delete All Files." Then I tried, 
>> unsuccessfully, to spin up a VM:
>>
>> Bringing machine 'default' up with 'virtualbox' provider...
>> C:/Users/Kevin/.vagrant.d/gems/gems/vagrant-berkshelf-2.0.0/lib/berkshelf/vagrant/env.rb:16:in
>>  
>> `initialize': undefined method `opts' for #<Vagrant::
>> UI::Colored:0x565e7c8> (NoMethodError)
>>         from 
>> C:/Users/Kevin/.vagrant.d/gems/gems/vagrant-berkshelf-2.0.0/lib/berkshelf/vagrant/action.rb:57:in
>>  
>> `new'
>>         from 
>> C:/Users/Kevin/.vagrant.d/gems/gems/vagrant-berkshelf-2.0.0/lib/berkshelf/vagrant/action.rb:57:in
>>  
>> `block in setup'
>>         from 
>> C:/Users/Kevin/.vagrant.d/gems/gems/vagrant-berkshelf-2.0.0/lib/berkshelf/vagrant/action.rb:56:in
>>  
>> `tap'
>>         from 
>> C:/Users/Kevin/.vagrant.d/gems/gems/vagrant-berkshelf-2.0.0/lib/berkshelf/vagrant/action.rb:56:in
>>  
>> `setup'
>>         from 
>> C:/Users/Kevin/.vagrant.d/gems/gems/vagrant-berkshelf-2.0.0/lib/berkshelf/vagrant/plugin.rb:15:in
>>  
>> `provision'
>>         from 
>> C:/HashiCorp/Vagrant_1.4.3/embedded/gems/gems/vagrant-1.4.3/lib/vagrant/action/runner.rb:45:in
>>  
>> `call'
>>         from 
>> C:/HashiCorp/Vagrant_1.4.3/embedded/gems/gems/vagrant-1.4.3/lib/vagrant/action/runner.rb:45:in
>>  
>> `block (2 levels) in run'
>>         from 
>> C:/HashiCorp/Vagrant_1.4.3/embedded/gems/gems/vagrant-1.4.3/lib/vagrant/action/runner.rb:44:in
>>  
>> `tap'
>>         from 
>> C:/HashiCorp/Vagrant_1.4.3/embedded/gems/gems/vagrant-1.4.3/lib/vagrant/action/runner.rb:44:in
>>  
>> `block in run'
>>         from 
>> C:/HashiCorp/Vagrant_1.4.3/embedded/gems/gems/vagrant-1.4.3/lib/vagrant/action/runner.rb:43:in
>>  
>> `map'
>>         from 
>> C:/HashiCorp/Vagrant_1.4.3/embedded/gems/gems/vagrant-1.4.3/lib/vagrant/action/runner.rb:43:in
>>  
>> `run'
>>         from 
>> C:/HashiCorp/Vagrant_1.4.3/embedded/gems/gems/vagrant-1.4.3/lib/vagrant/machine.rb:147:in
>>  
>> `action'
>>         from 
>> C:/HashiCorp/Vagrant_1.4.3/embedded/gems/gems/vagrant-1.4.3/lib/vagrant/batch_action.rb:63:in
>>  
>> `block (2 levels) in run'
>>
>> Please let me know know to debug this problem.
>>
>> -- 
>> 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