New v1.1.1 install fails to UP on windows

classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|

New v1.1.1 install fails to UP on windows

Hans K
Went through the standard installation with v1.1.1 but it fails to startup:

  1. Installed v1.1.1
  2. Ran "vagrant -v" to verify the version
  3. Ran "vagrant box add precise32 http://files.vagrantup.com/precise32.box"
  4. Ran "vagrant up"
The "up" resulted in the following output:

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...
[default] -- 22 => 2222 (adapter 1)
[default] Booting VM...
[default] Waiting for VM to boot. This can take a few minutes.
[default] VM booted and ready for use!
[default] Configuring and enabling network interfaces...
[default] Mounting shared folders...
[default] -- /vagrant
[default] Forcing shutdown of VM...
[default] Destroying VM and associated drives...
C:/vagrant/vagrant/embedded/gems/gems/vagrant-1.1.1/plugins/providers/virtualbox/action/prepare_nfs_settings.rb:16:in `call': uninitialized constant VagrantPlugins::ProviderVirtualBox::Action::PrepareNFSSettings::Errors (NameError)
        from C:/vagrant/vagrant/embedded/gems/gems/vagrant-1.1.1/lib/vagrant/action/warden.rb:34:in `call'
        from C:/vagrant/vagrant/embedded/gems/gems/vagrant-1.1.1/lib/vagrant/action/builtin/nfs.rb:28:in `call'

... multiple more lines of these ...

The Vagrantfile contains the following two settings uncommented:

  # Every Vagrant virtual environment requires a box to build off of.
  config.vm.box = "precise32"

  # The url from where the 'config.vm.box' box will be fetched if it
  # doesn't already exist on the user's system.
  config.vm.box_url = "http://files.vagrantup.com/precise32.box"

Any thoughts on what might be wrong?

Thanks.

--
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 [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 
Reply | Threaded
Open this post in threaded view
|

Re: New v1.1.1 install fails to UP on windows

Mitchell Hashimoto
I'm going to quickly turn around a 1.1.2 to fix this shortly.


On Mon, Mar 18, 2013 at 12:27 PM, Hans K <[hidden email]> wrote:
Went through the standard installation with v1.1.1 but it fails to startup:

  1. Installed v1.1.1
  2. Ran "vagrant -v" to verify the version
  3. Ran "vagrant box add precise32 http://files.vagrantup.com/precise32.box"
  4. Ran "vagrant up"
The "up" resulted in the following output:

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...
[default] -- 22 => 2222 (adapter 1)
[default] Booting VM...
[default] Waiting for VM to boot. This can take a few minutes.
[default] VM booted and ready for use!
[default] Configuring and enabling network interfaces...
[default] Mounting shared folders...
[default] -- /vagrant
[default] Forcing shutdown of VM...
[default] Destroying VM and associated drives...
C:/vagrant/vagrant/embedded/gems/gems/vagrant-1.1.1/plugins/providers/virtualbox/action/prepare_nfs_settings.rb:16:in `call': uninitialized constant VagrantPlugins::ProviderVirtualBox::Action::PrepareNFSSettings::Errors (NameError)
        from C:/vagrant/vagrant/embedded/gems/gems/vagrant-1.1.1/lib/vagrant/action/warden.rb:34:in `call'
        from C:/vagrant/vagrant/embedded/gems/gems/vagrant-1.1.1/lib/vagrant/action/builtin/nfs.rb:28:in `call'

... multiple more lines of these ...

The Vagrantfile contains the following two settings uncommented:

  # Every Vagrant virtual environment requires a box to build off of.
  config.vm.box = "precise32"

  # The url from where the 'config.vm.box' box will be fetched if it
  # doesn't already exist on the user's system.

Any thoughts on what might be wrong?

Thanks.

--
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 [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
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 [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 
Reply | Threaded
Open this post in threaded view
|

Re: New v1.1.1 install fails to UP on windows

RH Becker
In reply to this post by Hans K
Reported on github: https://github.com/mitchellh/vagrant/issues/1450

If Mitchell sees this: Trying to decide whether to rollback my version or wait for 1.1.2 ... any sense of when you'll release?

On Monday, March 18, 2013 12:27:40 PM UTC-7, Hans K wrote:
Went through the standard installation with v1.1.1 but it fails to startup:

  1. Installed v1.1.1
  2. Ran "vagrant -v" to verify the version
  3. Ran "vagrant box add precise32 http://files.vagrantup.com/precise32.box"
  4. Ran "vagrant up"
The "up" resulted in the following output:

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...
[default] -- 22 => 2222 (adapter 1)
[default] Booting VM...
[default] Waiting for VM to boot. This can take a few minutes.
[default] VM booted and ready for use!
[default] Configuring and enabling network interfaces...
[default] Mounting shared folders...
[default] -- /vagrant
[default] Forcing shutdown of VM...
[default] Destroying VM and associated drives...
C:/vagrant/vagrant/embedded/gems/gems/vagrant-1.1.1/plugins/providers/virtualbox/action/prepare_nfs_settings.rb:16:in `call': uninitialized constant VagrantPlugins::ProviderVirtualBox::Action::PrepareNFSSettings::Errors (NameError)
        from C:/vagrant/vagrant/embedded/gems/gems/vagrant-1.1.1/lib/vagrant/action/warden.rb:34:in `call'
        from C:/vagrant/vagrant/embedded/gems/gems/vagrant-1.1.1/lib/vagrant/action/builtin/nfs.rb:28:in `call'

... multiple more lines of these ...

The Vagrantfile contains the following two settings uncommented:

  # Every Vagrant virtual environment requires a box to build off of.
  config.vm.box = "precise32"

  # The url from where the 'config.vm.box' box will be fetched if it
  # doesn't already exist on the user's system.

Any thoughts on what might be wrong?

Thanks.

--
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 [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 
Reply | Threaded
Open this post in threaded view
|

Re: New v1.1.1 install fails to UP on windows

RH Becker
In reply to this post by Mitchell Hashimoto
awesome response time ... thanks!

On Monday, March 18, 2013 1:17:47 PM UTC-7, Mitchell Hashimoto wrote:
I'm going to quickly turn around a 1.1.2 to fix this shortly.


On Mon, Mar 18, 2013 at 12:27 PM, Hans K <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="rp5ubuVhqrkJ">hansk...@...> wrote:
Went through the standard installation with v1.1.1 but it fails to startup:

  1. Installed v1.1.1
  2. Ran "vagrant -v" to verify the version
  3. Ran "vagrant box add precise32 http://files.vagrantup.com/precise32.box"
  4. Ran "vagrant up"
The "up" resulted in the following output:

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...
[default] -- 22 => 2222 (adapter 1)
[default] Booting VM...
[default] Waiting for VM to boot. This can take a few minutes.
[default] VM booted and ready for use!
[default] Configuring and enabling network interfaces...
[default] Mounting shared folders...
[default] -- /vagrant
[default] Forcing shutdown of VM...
[default] Destroying VM and associated drives...
C:/vagrant/vagrant/embedded/gems/gems/vagrant-1.1.1/plugins/providers/virtualbox/action/prepare_nfs_settings.rb:16:in `call': uninitialized constant VagrantPlugins::ProviderVirtualBox::Action::PrepareNFSSettings::Errors (NameError)
        from C:/vagrant/vagrant/embedded/gems/gems/vagrant-1.1.1/lib/vagrant/action/warden.rb:34:in `call'
        from C:/vagrant/vagrant/embedded/gems/gems/vagrant-1.1.1/lib/vagrant/action/builtin/nfs.rb:28:in `call'

... multiple more lines of these ...

The Vagrantfile contains the following two settings uncommented:

  # Every Vagrant virtual environment requires a box to build off of.
  config.vm.box = "precise32"

  # The url from where the 'config.vm.box' box will be fetched if it
  # doesn't already exist on the user's system.

Any thoughts on what might be wrong?

Thanks.

--
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 <a href="javascript:" target="_blank" gdf-obfuscated-mailto="rp5ubuVhqrkJ">vagrant-up+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
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 [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 
Reply | Threaded
Open this post in threaded view
|

Re: New v1.1.1 install fails to UP on windows

Mitchell Hashimoto
Yep, 1.1.2 was released to address this. Super sorry about that.


On Mon, Mar 18, 2013 at 2:26 PM, RH Becker <[hidden email]> wrote:
awesome response time ... thanks!


On Monday, March 18, 2013 1:17:47 PM UTC-7, Mitchell Hashimoto wrote:
I'm going to quickly turn around a 1.1.2 to fix this shortly.


On Mon, Mar 18, 2013 at 12:27 PM, Hans K <[hidden email]> wrote:
Went through the standard installation with v1.1.1 but it fails to startup:

  1. Installed v1.1.1
  2. Ran "vagrant -v" to verify the version
  3. Ran "vagrant box add precise32 http://files.vagrantup.com/precise32.box"
  4. Ran "vagrant up"
The "up" resulted in the following output:

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...
[default] -- 22 => 2222 (adapter 1)
[default] Booting VM...
[default] Waiting for VM to boot. This can take a few minutes.
[default] VM booted and ready for use!
[default] Configuring and enabling network interfaces...
[default] Mounting shared folders...
[default] -- /vagrant
[default] Forcing shutdown of VM...
[default] Destroying VM and associated drives...
C:/vagrant/vagrant/embedded/gems/gems/vagrant-1.1.1/plugins/providers/virtualbox/action/prepare_nfs_settings.rb:16:in `call': uninitialized constant VagrantPlugins::ProviderVirtualBox::Action::PrepareNFSSettings::Errors (NameError)
        from C:/vagrant/vagrant/embedded/gems/gems/vagrant-1.1.1/lib/vagrant/action/warden.rb:34:in `call'
        from C:/vagrant/vagrant/embedded/gems/gems/vagrant-1.1.1/lib/vagrant/action/builtin/nfs.rb:28:in `call'

... multiple more lines of these ...

The Vagrantfile contains the following two settings uncommented:

  # Every Vagrant virtual environment requires a box to build off of.
  config.vm.box = "precise32"

  # The url from where the 'config.vm.box' box will be fetched if it
  # doesn't already exist on the user's system.

Any thoughts on what might be wrong?

Thanks.

--
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 vagrant-up+...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
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 [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
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 [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 
Reply | Threaded
Open this post in threaded view
|

Re: New v1.1.1 install fails to UP on windows

Hans K
In reply to this post by RH Becker
Agreed.  Thanks for the fast response.

On Monday, March 18, 2013 2:26:45 PM UTC-7, RH Becker wrote:
awesome response time ... thanks!

On Monday, March 18, 2013 1:17:47 PM UTC-7, Mitchell Hashimoto wrote:
I'm going to quickly turn around a 1.1.2 to fix this shortly.


--
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 [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 
Reply | Threaded
Open this post in threaded view
|

Re: New v1.1.1 install fails to UP on windows

Mark Kremer-2
In reply to this post by RH Becker
In case you haven't seen it, 1.1.2 is already released :)

On 03/18/2013 09:19 PM, RH Becker wrote:
Reported on github: https://github.com/mitchellh/vagrant/issues/1450

If Mitchell sees this: Trying to decide whether to rollback my version or wait for 1.1.2 ... any sense of when you'll release?

On Monday, March 18, 2013 12:27:40 PM UTC-7, Hans K wrote:
Went through the standard installation with v1.1.1 but it fails to startup:

  1. Installed v1.1.1
  2. Ran "vagrant -v" to verify the version
  3. Ran "vagrant box add precise32 http://files.vagrantup.com/precise32.box"
  4. Ran "vagrant up"
The "up" resulted in the following output:

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...
[default] -- 22 => 2222 (adapter 1)
[default] Booting VM...
[default] Waiting for VM to boot. This can take a few minutes.
[default] VM booted and ready for use!
[default] Configuring and enabling network interfaces...
[default] Mounting shared folders...
[default] -- /vagrant
[default] Forcing shutdown of VM...
[default] Destroying VM and associated drives...
C:/vagrant/vagrant/embedded/gems/gems/vagrant-1.1.1/plugins/providers/virtualbox/action/prepare_nfs_settings.rb:16:in `call': uninitialized constant VagrantPlugins::ProviderVirtualBox::Action::PrepareNFSSettings::Errors (NameError)
        from C:/vagrant/vagrant/embedded/gems/gems/vagrant-1.1.1/lib/vagrant/action/warden.rb:34:in `call'
        from C:/vagrant/vagrant/embedded/gems/gems/vagrant-1.1.1/lib/vagrant/action/builtin/nfs.rb:28:in `call'

... multiple more lines of these ...

The Vagrantfile contains the following two settings uncommented:

  # Every Vagrant virtual environment requires a box to build off of.
  config.vm.box = "precise32"

  # The url from where the 'config.vm.box' box will be fetched if it
  # doesn't already exist on the user's system.

Any thoughts on what might be wrong?

Thanks.
--
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 [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
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 [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 
Reply | Threaded
Open this post in threaded view
|

Re: New v1.1.1 install fails to UP on windows

Mark Kremer
In reply to this post by RH Becker
In case you haven't seen it, 1.1.2 is already released :)

On 03/18/2013 09:19 PM, RH Becker wrote:
Reported on github: https://github.com/mitchellh/vagrant/issues/1450

If Mitchell sees this: Trying to decide whether to rollback my version or wait for 1.1.2 ... any sense of when you'll release?

On Monday, March 18, 2013 12:27:40 PM UTC-7, Hans K wrote:
Went through the standard installation with v1.1.1 but it fails to startup:

  1. Installed v1.1.1
  2. Ran "vagrant -v" to verify the version
  3. Ran "vagrant box add precise32 http://files.vagrantup.com/precise32.box"
  4. Ran "vagrant up"
The "up" resulted in the following output:

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...
[default] -- 22 => 2222 (adapter 1)
[default] Booting VM...
[default] Waiting for VM to boot. This can take a few minutes.
[default] VM booted and ready for use!
[default] Configuring and enabling network interfaces...
[default] Mounting shared folders...
[default] -- /vagrant
[default] Forcing shutdown of VM...
[default] Destroying VM and associated drives...
C:/vagrant/vagrant/embedded/gems/gems/vagrant-1.1.1/plugins/providers/virtualbox/action/prepare_nfs_settings.rb:16:in `call': uninitialized constant VagrantPlugins::ProviderVirtualBox::Action::PrepareNFSSettings::Errors (NameError)
        from C:/vagrant/vagrant/embedded/gems/gems/vagrant-1.1.1/lib/vagrant/action/warden.rb:34:in `call'
        from C:/vagrant/vagrant/embedded/gems/gems/vagrant-1.1.1/lib/vagrant/action/builtin/nfs.rb:28:in `call'

... multiple more lines of these ...

The Vagrantfile contains the following two settings uncommented:

  # Every Vagrant virtual environment requires a box to build off of.
  config.vm.box = "precise32"

  # The url from where the 'config.vm.box' box will be fetched if it
  # doesn't already exist on the user's system.

Any thoughts on what might be wrong?

Thanks.
--
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 [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
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 [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 
Reply | Threaded
Open this post in threaded view
|

Re: New v1.1.1 install fails to UP on windows

Mark Kremer
Oops, I see Mitchell already replied after my message went through. I had some technical difficulties with my Google Groups membership. Sorry for the duplication!

On Tuesday, March 19, 2013 8:57:47 AM UTC+1, Mark Kremer wrote:
In case you haven't seen it, 1.1.2 is already released :)

On 03/18/2013 09:19 PM, RH Becker wrote:
Reported on github: https://github.com/mitchellh/vagrant/issues/1450

If Mitchell sees this: Trying to decide whether to rollback my version or wait for 1.1.2 ... any sense of when you'll release?

On Monday, March 18, 2013 12:27:40 PM UTC-7, Hans K wrote:
Went through the standard installation with v1.1.1 but it fails to startup:

  1. Installed v1.1.1
  2. Ran "vagrant -v" to verify the version
  3. Ran "vagrant box add precise32 http://files.vagrantup.com/precise32.box"
  4. Ran "vagrant up"
The "up" resulted in the following output:

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...
[default] -- 22 => 2222 (adapter 1)
[default] Booting VM...
[default] Waiting for VM to boot. This can take a few minutes.
[default] VM booted and ready for use!
[default] Configuring and enabling network interfaces...
[default] Mounting shared folders...
[default] -- /vagrant
[default] Forcing shutdown of VM...
[default] Destroying VM and associated drives...
C:/vagrant/vagrant/embedded/gems/gems/vagrant-1.1.1/plugins/providers/virtualbox/action/prepare_nfs_settings.rb:16:in `call': uninitialized constant VagrantPlugins::ProviderVirtualBox::Action::PrepareNFSSettings::Errors (NameError)
        from C:/vagrant/vagrant/embedded/gems/gems/vagrant-1.1.1/lib/vagrant/action/warden.rb:34:in `call'
        from C:/vagrant/vagrant/embedded/gems/gems/vagrant-1.1.1/lib/vagrant/action/builtin/nfs.rb:28:in `call'

... multiple more lines of these ...

The Vagrantfile contains the following two settings uncommented:

  # Every Vagrant virtual environment requires a box to build off of.
  config.vm.box = "precise32"

  # The url from where the 'config.vm.box' box will be fetched if it
  # doesn't already exist on the user's system.

Any thoughts on what might be wrong?

Thanks.
--
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 [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
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 [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.