Re: [vagrant-up] Vagrand 2.0.1 + VMWare WS 14 // ERR: Failed to add NAT port entry

[Sven Bluege]

If I run vagrant from a normal command line, I get this: 

Vagrant failed to initialize at a very early stage:

Failed to invoke the VMware utility task.

  Cause: FEHLER: Zugriff verweigert

Please address the issue above and try again. If
this problem persists, please contact supp...@hashicorp.com

Virus scanner is disabled and did not change the behavior.

On Tuesday, December 5, 2017 at 8:36:00 AM UTC+1, Alvaro Miranda Aguilera 
wrote:
>
> vagrant 2.X with plugin 5.x can be run as a normal user.
>
> the Zugriff verweigert is coming from somewhere.
>
> try running this as normal user
>
> if still fails, try disabling AntiVirus 
>
> Alvaro
>
> On Mon, Dec 4, 2017 at 2:46 PM, Sven Bluege  > wrote:
>
>> I try to run vagrant 2.0.1 with VMware Workstation 14. While I had no 
>> issues with VMWare Workstation 12, I get now this message: 
>>
>> ==> machine1: Starting the VMware VM...
>> ==> machine1: Waiting for the VM to receive an address...
>> ==> machine1: Forwarding ports...
>> machine1: -- 22 => 
>> C:/Users/User.Name/.vagrant.d/gems/2.4.2/gems/vagrant-vmware-workstation-5.0.4/lib/vagrant-vmware-workstation/driver.rb:2138:in
>>  
>> `win_set_forwarded_port': Port forward registry set failure. (RuntimeError)
>> OUT:
>> ERR: Failed to add NAT port entry: Zugriff verweigert
>>
>> from 
>> C:/Users/User.Name/.vagrant.d/gems/2.4.2/gems/vagrant-vmware-workstation-5.0.4/lib/vagrant-vmware-workstation/driver.rb:1825:in
>>  
>> `block in forward_ports'
>>
>> I'm running this from an elevated command line. 
>>
>> Can somebody help with this error message? How can I get a running 
>> vm back?
>>
>> Thanks!!
>>
>> -- 
>> This mailing list is governed under the HashiCorp Community Guidelines - 
>> https://www.hashicorp.com/community-guidelines.html. Behavior in 
>> violation of those guidelines may result in your removal from this mailing 
>> list.
>>  
>> GitHub Issues: https://github.com/mitchellh/vagrant/issues
>> IRC: #vagrant on Freenode
>> --- 
>> 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 .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/vagrant-up/8cb68fc2-5d88-42ad-a50b-583e4bbd444c%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> Alvaro
>
>

-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
--- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/d877a3ee-597f-4b58-861d-6825e496e62f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] Vagrand 2.0.1 + VMWare WS 14 // ERR: Failed to add NAT port entry

[Alvaro Miranda Aguilera]

vagrant 2.X with plugin 5.x can be run as a normal user.

the Zugriff verweigert is coming from somewhere.

try running this as normal user

if still fails, try disabling AntiVirus

Alvaro

On Mon, Dec 4, 2017 at 2:46 PM, Sven Bluege  wrote:

> I try to run vagrant 2.0.1 with VMware Workstation 14. While I had no
> issues with VMWare Workstation 12, I get now this message:
>
> ==> machine1: Starting the VMware VM...
> ==> machine1: Waiting for the VM to receive an address...
> ==> machine1: Forwarding ports...
> machine1: -- 22 => 
> C:/Users/User.Name/.vagrant.d/gems/2.4.2/gems/vagrant-
> vmware-workstation-5.0.4/lib/vagrant-vmware-workstation/driver.rb:2138:in
> `win_set_forwarded_port': Port forward registry set failure. (RuntimeError)
> OUT:
> ERR: Failed to add NAT port entry: Zugriff verweigert
>
> from C:/Users/User.Name/.vagrant.d/gems/2.4.2/gems/vagrant-
> vmware-workstation-5.0.4/lib/vagrant-vmware-workstation/driver.rb:1825:in
> `block in forward_ports'
>
> I'm running this from an elevated command line.
>
> Can somebody help with this error message? How can I get a running vm back?
>
> Thanks!!
>
> --
> This mailing list is governed under the HashiCorp Community Guidelines -
> https://www.hashicorp.com/community-guidelines.html. Behavior in
> violation of those guidelines may result in your removal from this mailing
> list.
>
> GitHub Issues: https://github.com/mitchellh/vagrant/issues
> IRC: #vagrant on Freenode
> ---
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/vagrant-up/8cb68fc2-5d88-42ad-a50b-583e4bbd444c%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Alvaro

-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
--- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/CAHqq0ex-Ch74nwCgttZ5m_E_nfX8xuzEEwGnwEDHKGRjSATGmg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] Unplanned host reboot causes vagrant to lose all virtualbox guest associations

[Alvaro Miranda Aguilera]

hello

the state of the VM is stored in the running directory of the project.

where the Vagrantfile is, a directory .vagrant is created

some of that state is pointed also to your home/.vagrant.d

When your machine starts, does anything gets deleted?

I have a Win10 machine and i don't lose any VM that is registered.

Alvaro.

On Mon, Dec 4, 2017 at 11:34 PM, Charlie  wrote:

> Hi group,
>
> Is it expected behaviour that vagrant loses all it's associations to
> virtualbox guests if the host machine is rebooted without running vagrant
> halt/suspend first on the guests first (e.g. due to power loss or a system
> update)?
>
> I see this every time a Windows host running Vagrant 2.0.1 and Virtualbox
> 5.1.30 r118389 reboots for e.g. an unattended windows update (and it's been
> happening with every version of vagrant and virtualbox I've used prior to
> the current ones).
>
> Is there anything that can be done to get vagrant not to lose track of
> guests after such a host reboot? Re-creating and re-provisioning them is
> quite tedious (even with the aid of ansible).
>
> Thanks,
> Charlie
>
> --
> This mailing list is governed under the HashiCorp Community Guidelines -
> https://www.hashicorp.com/community-guidelines.html. Behavior in
> violation of those guidelines may result in your removal from this mailing
> list.
>
> GitHub Issues: https://github.com/mitchellh/vagrant/issues
> IRC: #vagrant on Freenode
> ---
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/vagrant-up/700b6dca-b73a-4cb8-8c4c-fb9853fd7361%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Alvaro

-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
--- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/CAHqq0ezXrBnzRWvt%2BB3xSNGoYZoBwM4KCoAVOn_PwsecOAWujg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] Running a Python script on a Win10

[Alvaro Miranda Aguilera]

Hello

Can you try this:

https://github.com/kikitux/vagrant-win10-python

This repo can run a python script (will install it if not there)

I am not sure will be able to run with a provisioning scrip a desktop task
as there is no desktop if there is no auto login.


Thanks
Alvaro

On Mon, Dec 4, 2017 at 3:07 PM,  wrote:

> Hi,
>
> I am having difficulties running a Python script on a Win10 box -
> "talisker/windows10pro" (I tried different boxes, all are acting the same).
>
> *MY VAGRANT FILE*:
> # -*- mode: ruby -*-
> # vi: set ft=ruby :
>
> Vagrant.configure("2") do |config|
>
>config.vm.define "win10" do |win10|
>  win10.vm.box = "talisker/windows10pro"
>  win10.vm.provision :shell, :inline => 
> "C:\\Users\\vagrant\\Desktop\\brow.py",
> privileged: true
>end
>
>  # ENABLE GUI WHEN MACHINE IS BOOTING
>config.vm.provider "virtualbox" do |v|
>  v.gui = true
>end
> end
>
> The script is present on the box, Python is installed and I am able to run
> it when connected to the VM/box itself.
> The issue happens when I try to run "vagrant provision".
>
> It seems that every time I run the "vagrant provision" command, a popup
> window jumps on the Win machine saying "The Scheduled logoff is canceled"
>
> Any assistance will be much much appreciated!!!
>
>
> BTW, I have this exact setup on several Linux machines and everything
> works fine.
>
>
>
> Thanks.
> Avi.
>
>
>
>
> --
> This mailing list is governed under the HashiCorp Community Guidelines -
> https://www.hashicorp.com/community-guidelines.html. Behavior in
> violation of those guidelines may result in your removal from this mailing
> list.
>
> GitHub Issues: https://github.com/mitchellh/vagrant/issues
> IRC: #vagrant on Freenode
> ---
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/vagrant-up/a4b9b649-3ae1-406a-869b-53884fccf42c%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Alvaro

-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
--- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/CAHqq0ezSfMG0zu7%3DEfCp9jaM2j%2BLg4YVEOSYxPn4SeCj0_gZHQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[vagrant-up] Unplanned host reboot causes vagrant to lose all virtualbox guest associations

[Charlie]

Hi group, 

Is it expected behaviour that vagrant loses all it's associations to 
virtualbox guests if the host machine is rebooted without running vagrant 
halt/suspend first on the guests first (e.g. due to power loss or a system 
update)? 

I see this every time a Windows host running Vagrant 2.0.1 and Virtualbox 
5.1.30 r118389 reboots for e.g. an unattended windows update (and it's been 
happening with every version of vagrant and virtualbox I've used prior to 
the current ones).

Is there anything that can be done to get vagrant not to lose track of 
guests after such a host reboot? Re-creating and re-provisioning them is 
quite tedious (even with the aid of ansible).

Thanks,
Charlie

-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
--- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/700b6dca-b73a-4cb8-8c4c-fb9853fd7361%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] rdp for remote vagrant?

[pixel fairy]

thanks!

-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
--- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/58192275-f94d-4325-a34f-96c9f9c84532%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[vagrant-up] Running a Python script on a Win10

[vagrantfp]

Hi,

I am having difficulties running a Python script on a Win10 box - 
"talisker/windows10pro" (I tried different boxes, all are acting the same).

*MY VAGRANT FILE*:
# -*- mode: ruby -*-
# vi: set ft=ruby :

Vagrant.configure("2") do |config|

   config.vm.define "win10" do |win10|
 win10.vm.box = "talisker/windows10pro"
 win10.vm.provision :shell, :inline => 
"C:\\Users\\vagrant\\Desktop\\brow.py", privileged: true
   end

 # ENABLE GUI WHEN MACHINE IS BOOTING
   config.vm.provider "virtualbox" do |v|
 v.gui = true
   end
end

The script is present on the box, Python is installed and I am able to run 
it when connected to the VM/box itself.
The issue happens when I try to run "vagrant provision".

It seems that every time I run the "vagrant provision" command, a popup 
window jumps on the Win machine saying "The Scheduled logoff is canceled"

Any assistance will be much much appreciated!!!


BTW, I have this exact setup on several Linux machines and everything works 
fine.



Thanks.
Avi.




-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
--- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/a4b9b649-3ae1-406a-869b-53884fccf42c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[vagrant-up] Vagrand 2.0.1 + VMWare WS 14 // ERR: Failed to add NAT port entry

[Sven Bluege]

I try to run vagrant 2.0.1 with VMware Workstation 14. While I had no 
issues with VMWare Workstation 12, I get now this message: 

==> machine1: Starting the VMware VM...
==> machine1: Waiting for the VM to receive an address...
==> machine1: Forwarding ports...
machine1: -- 22 => 
C:/Users/User.Name/.vagrant.d/gems/2.4.2/gems/vagrant-vmware-workstation-5.0.4/lib/vagrant-vmware-workstation/driver.rb:2138:in
 
`win_set_forwarded_port': Port forward registry set failure. (RuntimeError)
OUT:
ERR: Failed to add NAT port entry: Zugriff verweigert

from 
C:/Users/User.Name/.vagrant.d/gems/2.4.2/gems/vagrant-vmware-workstation-5.0.4/lib/vagrant-vmware-workstation/driver.rb:1825:in
 
`block in forward_ports'

I'm running this from an elevated command line. 

Can somebody help with this error message? How can I get a running vm back?

Thanks!!

-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
--- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/8cb68fc2-5d88-42ad-a50b-583e4bbd444c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[vagrant-up] Vagrant issue version

[Ronak Jain]

vagrant up


No usable default provider could be found for your system.

Vagrant relies on interactions with 3rd party systems, known as
"providers", to provide Vagrant with resources to run development
environments. Examples are VirtualBox, VMware, Hyper-V.

The easiest solution to this message is to install VirtualBox, which
is available for free on all major platforms.

If you believe you already have a provider available, make sure it
is properly installed and configured. You can see more details about
why a particular provider isn't working by forcing usage with
`vagrant up --provider=PROVIDER`, which should give you a more specific
error message for that particular provider.


vagrant version 
4.0,4.1,5.1
please install version  5.1 or 5.0 but I installed Virtualbox  

-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
--- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/dcff978c-dc48-47d4-b0f4-d11e55057328%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.