Re: [vagrant-up] Configuration of the /etc/network/interfaces and /etc/dhcp/dhcpd.conf by Vagrantfile?

[Alvaro Miranda Aguilera]

hello

choose one of these:

- you pass the USB to the VM and configure that in the VM . what you are
doing with vbox manage is plug the usb IN the VM
- configure the USB on the host, check what eth is, and use network_private
to make a nic on the VM using that.

one or the other, no both

then use a shell script to remove the default gw and add one to the
network/gwip you want, on the documentation is one example

you are very close, but I think you need to take 1 step back on my
questions and then you should be there

good work

Alvaro

On Wed, Jan 31, 2018 at 4:38 PM, _nobody_ _nobody_ 
wrote:

> Hello Alvaro,
>
> Here is my VBox Vagrant file (important part of it):
>
> I have one physical ETH0 interface, and I also configured NAT forwarding,
> and here it is:
>
> # Forward port  for the internal REST server
>   config.vm.network :forwarded_port, guest: , host: 
>   # Forward port 8010 for the Storage Server
>   config.vm.network :forwarded_port, guest: 8010, host: 8010
>   # Forward port 5000 for the KernelCI Frontend Web Server
>   config.vm.network :forwarded_port, guest: 5000, host: 5000
>   # Forward port 80 for the http Lava Frontend Web Server
>   config.vm.network :forwarded_port, guest: 8080, host: 8080
>   # Forward port 443 for the https Lava Frontend Web Server
>   config.vm.network :forwarded_port, guest: 443, host: 4443
>   # Configure network accessibility for tftp server
>   config.vm.network "public_network", :dev => "eth1",
> use_dhcp_assigned_default_route: true
>   config.vm.network "private_network", bridge: "eth2", ip: "192.168.15.2"
>
> I would like to have private network hanging of VM, which is actually
> coming from USB->ETH convertor (AX88772) hanging of the host. Here is its
> configuration:
>
> vbox.customize ["modifyvm", :id, "--usb", "on"]
> vbox.customize ["modifyvm", :id, "--usbehci", "on"]
> vbox.customize ["usbfilter", "add", "0",
>   "--target", :id,
>   "--name", "ASIX Electronics Corp. AX88772 [0001]",
>   "--vendorid", "0B95",
>   "--productid", "7720",
>   "--revision", "0001",
>   "--manufacturer", "ASIX Electronics Corp.",
>   "--product", "AX88772"]
>
> Now, I would like to associate this device with my ETH2 adapter, give it
> the address 192.168.15.2, and configure it as: "ip route add default via
> 192.168.15.1 dev eth2" .
>
> So, I would like to have ETH0 as port forwarding (so I do NOT need IP
> address on it), I also would like ETH1 to be inactive, and ETH2 to be my
> interface to the small private network.
>
> In other words, I would like to hijack USB port (from where AX88772 hangs)
> from host, use it on VM for my external purposes. But I am not succeeding???
>
> Here is my ifconfig:
>
> root@stretch:~# ifconfig
> eth0: flags=4163  mtu 1500
> inet 10.0.2.15  netmask 255.255.255.0  broadcast 10.0.2.255
> inet6 fe80::a00:27ff:fe8d:c04d  prefixlen 64  scopeid 0x20
> ether 08:00:27:8d:c0:4d  txqueuelen 1000  (Ethernet)
> RX packets 3235  bytes 290021 (283.2 KiB)
> RX errors 0  dropped 0  overruns 0  frame 0
> TX packets 2492  bytes 461392 (450.5 KiB)
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>
> eth1: flags=4163  mtu 1500
> inet6 fe80::a00:27ff:fe57:855c  prefixlen 64  scopeid 0x20
> ether 08:00:27:57:85:5c  txqueuelen 1000  (Ethernet)
> RX packets 6498  bytes 658331 (642.9 KiB)
> RX errors 0  dropped 1  overruns 0  frame 0
> TX packets 119  bytes 28152 (27.4 KiB)
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>
> eth2: flags=4163  mtu 1500
> inet 192.168.15.2  netmask 255.255.255.0  broadcast 192.168.15.255
> inet6 fe80::a00:27ff:fec9:a365  prefixlen 64  scopeid 0x20
> ether 08:00:27:c9:a3:65  txqueuelen 1000  (Ethernet)
> RX packets 80  bytes 7816 (7.6 KiB)
> RX errors 0  dropped 0  overruns 0  frame 0
> TX packets 108  bytes 8436 (8.2 KiB)
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>
> lo: flags=73  mtu 65536
> inet 127.0.0.1  netmask 255.0.0.0
> inet6 ::1  prefixlen 128  scopeid 0x10
> loop  txqueuelen 1  (Local Loopback)
> RX packets 28690  bytes 9108243 (8.6 MiB)
> RX errors 0  dropped 0  overruns 0  frame 0
> TX packets 28690  bytes 9108243 (8.6 MiB)
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>
> root@stretch:~#
>
> The question is: how I associate via Vagrant AX88772 with ETH2 port???
>
> Thank you,
> Zoran
>
> --
> 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: 

Re: [vagrant-up] Deploy VMs Template with vagrant to an external host

[Alvaro Miranda Aguilera]

hello

can you explain why you want to do this :

- on servers ?
- with vagrant?


Vagrant first use case is development kind of workloads, can be local or
remote, based on plugins

so here we can check what tech are you using? there are plugin from vmware
vsphere and other s

but i want to stress this development

if your vms will be other than dev work better keep eyes open and include
other tools

in my opinionm the question should be "I want to do this, what tool should
i try first?"

instead of "how i do x y z with vagrant"

Thanks
Alvaro.


On Wed, Jan 31, 2018 at 4:59 PM, Audrain Landry Fanko 
wrote:

> hey evryone,
> i am new with vagrant and i have this plan:
>
> i have my vagrant Base box file on Server a. my vagrant ist install on the
> same server an i want to build or deploy multiple vms on server B, C or D
> how can i do this with Vagrant? if not can u explain me a go scenario.
>
> best regard.
>
> --
> 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/b9b32ab7-f9b7-4936-8b58-15d0534302bb%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/CAHqq0ewLpzW2xdJ8%3DLLhUGP3pkUuY_-Yc9307-e63qXF5aoMPQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] Free IPA unable to access it web url

[Alvaro Miranda Aguilera]

hello

not a vagrant issue from here
if you expect this to be running on port 80, there is nothing listening on
port 80

you make sure sure it will bind to 0.0.0.0 and then you can use the IP
of 192.168.2.40
like 192.168.2.40:

i think will be more appropiate in a IPA forum

thanks


On Thu, Feb 1, 2018 at 10:17 AM,  wrote:

> Dear Team,
>
> I have successfully installed Free IPA in Web URL where i am unable to
> access it in we url with its ip
>
> i have done installation of Free IPA service inside the vagrant instance
> of host machine
>
> [root@ipa vagrant]# ifconfig
> eth0: flags=4163  mtu 1500
> inet 10.0.2.15  netmask 255.255.255.0  broadcast 10.0.2.255
> inet6 fe80::5054:ff:feca:e48b  prefixlen 64  scopeid 0x20
> ether 52:54:00:ca:e4:8b  txqueuelen 1000  (Ethernet)
> RX packets 741  bytes 91595 (89.4 KiB)
> RX errors 0  dropped 0  overruns 0  frame 0
> TX packets 656  bytes 96725 (94.4 KiB)
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>
> eth1: flags=4163  mtu 1500
> inet 192.168.2.40  netmask 255.255.255.0  broadcast 192.168.2.255
> inet6 fe80::a00:27ff:fe3b:bb11  prefixlen 64  scopeid 0x20
> ether 08:00:27:3b:bb:11  txqueuelen 1000  (Ethernet)
> RX packets 3883  bytes 247523 (241.7 KiB)
> RX errors 0  dropped 1  overruns 0  frame 0
> TX packets 91  bytes 11936 (11.6 KiB)
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>
> lo: flags=73  mtu 65536
> inet 127.0.0.1  netmask 255.0.0.0
> inet6 ::1  prefixlen 128  scopeid 0x10
> loop  txqueuelen 1  (Local Loopback)
> RX packets 1106  bytes 120102 (117.2 KiB)
> RX errors 0  dropped 0  overruns 0  frame 0
> TX packets 1106  bytes 120102 (117.2 KiB)
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>
> [root@ipa vagrant]#
>
>
> Next the List of open ports
>
> [root@ipa vagrant]# netstat -napt
> Active Internet connections (servers and established)
> Proto Recv-Q Send-Q Local Address   Foreign Address
> State   PID/Program name
> tcp0  0 0.0.0.0:111 0.0.0.0:*
> LISTEN  1/systemd
> tcp0  0 0.0.0.0:22  0.0.0.0:*
> LISTEN  971/sshd
> tcp0  0 127.0.0.1:250.0.0.0:*
> LISTEN  1103/master
> tcp0  0 10.0.2.15:2210.0.2.2:40506
> ESTABLISHED 1887/sshd: vagrant
> tcp6   0  0 :::111  :::*
> LISTEN  1/systemd
> tcp6   0  0 :::22   :::*
> LISTEN  971/sshd
> tcp6   0  0 ::1:25  :::*
> LISTEN  1103/master
>
>
> can anyone please guide me in this
>
> --
> 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/230b2edf-5acc-4ece-a504-ed7bc3120bff%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/CAHqq0ewbApxWUWHWF7AtBWgJPHQ8TwXWbLofS2HMX-E%2BnB4CQQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] I am using vagrant + virtual box. Can vagrant select working network interfaces of host machine automatically?

[Alvaro Miranda Aguilera]

for public network + virtualbox you will be ask to choose

Can you share more information?

have you tried? what you see?

include vagrantfile also please

thanks


On Thu, Feb 1, 2018 at 10:20 AM, Emilbek Sulaymanov <
emilbeksulayma...@gmail.com> wrote:

> Can it pick right network interface of host machine itself?
>
> It will select itself, I am not saying about pointing right interface in
> Vagrantfile, vagrant will select itself.
>
>
> --
> 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/892982c9-964b-4e12-9c84-6e6f5625b7ed%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/CAHqq0eyxPp6GnaQmnwUioYuGNieqh1iojyjhOyeYASo1V1D3nw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] Configuration of the /etc/network/interfaces and /etc/dhcp/dhcpd.conf by Vagrantfile?

[Alvaro Miranda Aguilera]

hello

can we step back a bit?

What do you need to happen, then we can check on how we can make that to
happen.


By default vagrant provides one interface as Nat

on top of that you can add private (in a isolated network) or public
(bridged to some interface)

you can choose dhcp (default) or some fixed ip

That cover most of the use cases

if you need anything more complex you can use:

config.vm.network "public_network", auto_config: false


and Vagrant won't configure the interface and you can use a shell script if
you like.

So, what you want to do,? lets leave the how out for a bit

Alvaro

On Wed, Jan 31, 2018 at 5:34 AM, _nobody_ _nobody_ 
wrote:

> Hello to everyone,
>
>
> I have an interesting question here: Can I provide by Vagrantfile the
> configuration of /etc/network/interfaces, namely, can I add in the
> etc/network/interfaces the following:
>
>
> # The USB-Ethernet interface 2
> allow-hotplug eth2
> iface eth2 inet dhcp
>
>
> The another question is: can I define by Vagrantfile the following
> dhcpd.conf file?
> /etc/dhcp/dhcpd.conf : /etc/dhcp/dhcpd.conf
>
> I have set it like this:
>
>
> ## cat /etc/dhcp/dhcpd.conf
> ##
> ## DHCP Server Configuration file.
> ##   see /usr/share/doc/dhcp-server/dhcpd.conf.example
> ##   see dhcpd.conf(5) man page
> ##
>
> default-lease-time 600;
> max-lease-time 18000;
>
> subnet 192.168.15.0 netmask 255.255.255.0 {
> ##   interface enp0s25;
>range dynamic-bootp 192.168.15.100 192.168.15.200;
>option broadcast-address 192.168.15.255;
>next-server 192.168.15.2;
>option subnet-mask 255.255.255.0;
> }
>
> host bbb {
>hardware ethernet D0:5F:B8:FF:F8:69;
>fixed-address 192.168.15.20;
>filename "bbb-image";
> }
>
> host pdu {
>hardware ethernet 88:b6:27:01:62:43;
>fixed-address 192.168.15.21;
>filename "pdu-image";
> }
>
>
> Or I can import the files, written in some other languages (.xml, .json,
> .jinja2 or something else)?
>
>
> Any examples of the shelf for these cases?
>
>
> Thank you,
> Zoran (I use this account, since my primary account is on other three Open
> Source mailing lists)
>
>
> --
> 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/7b7a6c7b-4e85-4fb1-889c-e6e549196bbe%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/CAHqq0eyF9KExw9F79wNXdcL5mgXhS_oY3ma9pUEuOuoNuEQ2-Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] Laravel cannot make secure connection to server by domain name. Localhost:8000 works

[Alvaro Miranda Aguilera]

vagrant by default wouldnt set that

perhaps you had a plugin that now is gone?

hostmanager ?

On Tue, Jan 30, 2018 at 6:28 PM,  wrote:

> I am fairly new to web programming and have come into a tough problem. In
> the past I would be able to access a larvel site by running the command
> "vagrant up" in the homestead folder and then using the site name that I
> indicated in the "Homestead.yaml" file.
>
> Recently I updated my Mac to the latest version of High Sierra. I do not
> know if this is the main culprit, but for some reason now I am unable to
> reach the site by using the domain. I am however able to reach the laravel
> home page by going to localhost:8000.
>
> here is a list of things that I have done trying to fix the issue:
> I have tried uninstalling virtual box, homestead, and vagrant and
> reinstalling them but that has not fixed the issue.
> I tried running vagrant -provisions but that did not help the situation
> Here are my files:
>
> Homestead.yaml
>
> ip: "192.168.10.10"
> memory: 2048
> cpus: 1
> provider: virtualbox
>
> authorize: ~/.ssh/id_rsa.pub
>
> keys:
> - ~/.ssh/id_rsa
>
> folders:
> - map: ~/Code
>   to: /home/vagrant/Code
>
> sites:
> - map: hoomestead1.app
>   to: /home/vagrant/Code/Project1/public
> - map: lxa.app
>   to: /home/vagrant/Code/lxa/public
> - map: beerstreet.app
>   to: /home/vagrant/Code/beerstreet/public
> - map: blackbook.app
>   to: /home/vagrant/Code/blackbook/public
>
> databases:
> - homestead
>
> # blackfire:
> # - id: foo
> #   token: bar
> #   client-id: foo
> #   client-token: bar
>
> # ports:
> # - send: 5
> #   to: 5000
> # - send: 
> #   to: 777
> #   protocol: udp
>
>
> Host Files
>
> ##
> # Host Database
> #
> # localhost is used to configure the loopback interface
> # when the system is booting.  Do not change this entry.
> ##
> 127.0.0.1   localhost
> 255.255.255.255 broadcasthost
> ::1 localhost
>
> 192.168.10.10  homestead.app
> 192.168.10.10  hoomestead1.app
> 192.168.10.10  lxa.app
> 192.168.10.10  beerstreet.app
> 192.168.10.10  blackbook.app
>
> I really have no clue what the problem could be. It was working fine a day
> ago and now will not work. Can anyone please give me a suggestion on things
> I haven't tried yet and should?
>
> --
> 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/3aaacdd2-df71-4ec0-a6e9-192a4e8a7351%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/CAHqq0ezat9kV4dxnRkqrZ9A%3DhnmqTUkdZoNg-bVgv5SrO7Kmfg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] Re: SSH-2.0-OpenSSH - Protocol mismatch.

[Alvaro Miranda Aguilera]

hello

22 in the guest gets map to  on the host

the port 22 is ssh protocol so you can connect to the port  using a ssh
protocol client

a web browser is not an ssh client

you can use the web browser to talk to a web server

ssh is not the same as https

Alvaro.

On Tue, Jan 30, 2018 at 12:20 PM, Mohamed Hamed <moham...@motahidagroup.com>
wrote:

> Dear Srs,
>
> I have to install vagrant in centos 7.
>
> See attached image.
>
> When access http://127.0.0.1:/
>
> Return this message ...
>
> *SSH-2.0-OpenSSH_6.6.1p1 Ubuntu-2ubuntu2
> Protocol mismatch.*
>
>
> How to fix this problem?
>
>
> Best Regards,
>
>
>
> On Mon, Jan 29, 2018 at 8:04 PM, Alvaro Miranda Aguilera <
> kiki...@gmail.com> wrote:
>
>> you just reply to a 2015 email, i doubt the issue is near close
>>
>> can you send a new email and describe
>>
>> what you want to do
>> what is not working
>> what files are you using
>> what errors you get what do you see
>>
>> etc, any information that can help to understand
>>
>>
>> Thanks
>>
>>
>> On Mon, Jan 29, 2018 at 1:34 PM, Mohamed Hamed <
>> moham...@motahidagroup.com> wrote:
>>
>>> Dear Alvaro
>>>
>>> i have to install openio on vagrant so i have the same problem can you
>>> help me to solve this problem ..
>>>
>>> i don't know what is your meaning  can i Share your Vagrantfile 
>>>
>>>
>>> On Friday, September 18, 2015 at 6:07:25 AM UTC+2, Alvaro Miranda
>>> Aguilera wrote:
>>>>
>>>> Hello
>>>>
>>>> That happen when you use the wrong port in the browser.
>>>>
>>>>  usually is for SSH, so you can use ssh localhost 
>>>>
>>>> you need to create a port forward for http or https and use that
>>>> http/https port with the browser.
>>>>
>>>> Share your Vagrantfile and I can tell you if you are missing that or
>>>> not.
>>>>
>>>> Thanks
>>>> Alvaro.
>>>>
>>>> On Tue, Sep 15, 2015 at 10:10 PM, Gin Lance <gin.lanc...@gmail.com>
>>>> wrote:
>>>> > have you solved this problem?
>>>> >
>>>> > On Thursday, January 15, 2015 at 9:38:17 AM UTC+8, Marcelo Amorim
>>>> wrote:
>>>> >>
>>>> >> Dear Srs,
>>>> >>
>>>> >> I install vagrant in Windows 8.
>>>> >>
>>>> >> See attached image.
>>>> >>
>>>> >> When access http://127.0.0.1:/
>>>> >>
>>>> >> Return this message ...
>>>> >>
>>>> >> SSH-2.0-OpenSSH_6.6.1p1 Ubuntu-2ubuntu2
>>>> >> Protocol mismatch.
>>>> >>
>>>> >>
>>>> >> How to fix this problem?
>>>> >>
>>>> >>
>>>> >> Best Regards,
>>>> >>
>>>> >>
>>>> >> Marcelo Amorim
>>>> >
>>>> > --
>>>> > 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/52fc8b7a-aa7e-4
>>>> 4e1-ad8b-e5432ec719c1%40googlegroups.com.
>>>> > For more options, visit https://groups.google.com/d/optout.
>>>>
>>> --
>>> 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: #

Re: [vagrant-up] Extending a drive size using the vagrant vmware provider?

[Alvaro Miranda Aguilera]

better create a new VM thats fit for what you need.

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/CAHqq0eyb8kzjqr3G%2BszZXeuVsejSYdDi908Yp4q2ByXq-r8TyA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] Re: SSH-2.0-OpenSSH - Protocol mismatch.

[Alvaro Miranda Aguilera]

you just reply to a 2015 email, i doubt the issue is near close

can you send a new email and describe

what you want to do
what is not working
what files are you using
what errors you get what do you see

etc, any information that can help to understand


Thanks


On Mon, Jan 29, 2018 at 1:34 PM, Mohamed Hamed <moham...@motahidagroup.com>
wrote:

> Dear Alvaro
>
> i have to install openio on vagrant so i have the same problem can you
> help me to solve this problem ..
>
> i don't know what is your meaning  can i Share your Vagrantfile 
>
>
> On Friday, September 18, 2015 at 6:07:25 AM UTC+2, Alvaro Miranda Aguilera
> wrote:
>>
>> Hello
>>
>> That happen when you use the wrong port in the browser.
>>
>>  usually is for SSH, so you can use ssh localhost 
>>
>> you need to create a port forward for http or https and use that
>> http/https port with the browser.
>>
>> Share your Vagrantfile and I can tell you if you are missing that or not.
>>
>> Thanks
>> Alvaro.
>>
>> On Tue, Sep 15, 2015 at 10:10 PM, Gin Lance <gin.lanc...@gmail.com>
>> wrote:
>> > have you solved this problem?
>> >
>> > On Thursday, January 15, 2015 at 9:38:17 AM UTC+8, Marcelo Amorim
>> wrote:
>> >>
>> >> Dear Srs,
>> >>
>> >> I install vagrant in Windows 8.
>> >>
>> >> See attached image.
>> >>
>> >> When access http://127.0.0.1:/
>> >>
>> >> Return this message ...
>> >>
>> >> SSH-2.0-OpenSSH_6.6.1p1 Ubuntu-2ubuntu2
>> >> Protocol mismatch.
>> >>
>> >>
>> >> How to fix this problem?
>> >>
>> >>
>> >> Best Regards,
>> >>
>> >>
>> >> Marcelo Amorim
>> >
>> > --
>> > 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/52fc8b7a-aa7e-
>> 44e1-ad8b-e5432ec719c1%40googlegroups.com.
>> > For more options, visit https://groups.google.com/d/optout.
>>
> --
> 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/edeb7c18-7ceb-43db-8f16-13c780296416%40googlegroups.com
> <https://groups.google.com/d/msgid/vagrant-up/edeb7c18-7ceb-43db-8f16-13c780296416%40googlegroups.com?utm_medium=email_source=footer>
> .
> 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/CAHqq0ez%2B0tk0uQ3K4H3CKLQ7sEYoYZVyxv4EJkQ6EszT5%3D%3DHpg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] Debugging w/ PhpStorm

[Alvaro Miranda Aguilera]

the project you are using sets in the guest

from your host computer try to open a browser to  192.168.50.4

try to use phpstorm to  192.168.50.4



On Mon, Jan 29, 2018 at 4:52 PM, Clinton Gallagher <
clinton.s.gallag...@gmail.com> wrote:

> Don't understand what you are suggesting Alvaro. Where and what do you
> suggest I edit to use 192.168.50.4
>
> On Sat, Jan 27, 2018 at 2:40 AM, Alvaro Miranda Aguilera
> <kiki...@gmail.com> wrote:
> > how are you connecting?
> >
> > the project have a private network, try with  192.168.50.4
> >
> > --
> > 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 a topic in the
> > Google Groups "Vagrant" group.
> > To unsubscribe from this topic, visit
> > https://groups.google.com/d/topic/vagrant-up/SrW6RSKMZdE/unsubscribe.
> > To unsubscribe from this group and all its topics, 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/CAHqq0eyetnORLhU%
> 2BXJnMJb6Jspj6g1ySYqEBdzvcfTCtKhGn9A%40mail.gmail.com.
> >
> > For more options, visit https://groups.google.com/d/optout.
>
>
>
> --
> Clinton Gallagher
> tapABILITIES, LLC
> Wauwatosa, Milwaukee County, USA
> TEL   414-774-2557 Central
> CEL   414-243-8211
> WWW tapabilities.com
> @tapABILITIES
>
> --
> 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/CAH%3Ddq197G1fYUoEigbkUWEbMLp5Y2cY
> BjskW06QFWa-MiWAfnQ%40mail.gmail.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/CAHqq0ezWFvT-yFnrPzwas327MEnuRMSoMC5Ds-JHNj3HqVbYmg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] Debugging w/ PhpStorm

[Alvaro Miranda Aguilera]

how are you connecting?

the project have a private network, try with  192.168.50.4

-- 
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/CAHqq0eyetnORLhU%2BXJnMJb6Jspj6g1ySYqEBdzvcfTCtKhGn9A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] Password prompt on bringing up Vagrant although it is specified in Vagrantfile

[Alvaro Miranda Aguilera]

hello

thats new info. you should open an issue with then and check

thats a 3rd party plugin.

thanks
alvaro

On Thu, Jan 25, 2018 at 6:33 AM, Shashank Korada <shashank.kor...@gmail.com>
wrote:

> Hi Alvaro,
>
> Thanks for your reply.
> I think the ssh_settings that you are referring to is for accessing the
> VM. I was referring to accessing the remote server.
> As per plugin provider options this is what I found and tried to use
>
> https://github.com/vagrant-libvirt/vagrant-libvirt#provider-options
>
> Any idea if I am maybe still using it incorrectly ?
>
>
> On Thursday, January 25, 2018 at 8:21:55 AM UTC+5:30, Alvaro Miranda
> Aguilera wrote:
>>
>> hello
>>
>> seems you got the user/pass on the wrong block.
>>
>> https://www.vagrantup.com/docs/vagrantfile/ssh_settings.html
>>
>> config.ssh.username
>>
>> or
>> x.ssh.username
>>
>>
>>
>>
>> On Wed, Jan 24, 2018 at 7:23 AM, Shashank Korada <shashan...@gmail.com>
>> wrote:
>>
>>> Hello,
>>>
>>> I am trying to launch VMs on a remote server by specifying the
>>> username/password for the server in the Vagrantfile but on running "vagrant
>>> up" it still prompts me for the password.
>>> How do I avoid being prompted for the password?
>>>
>>> This is my current Vagrantfile:
>>>
>>> VAGRANTFILE_API_VERSION = "2"
>>> Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
>>>   config.ssh.forward_agent = true
>>>   config.vm.define "test-remote-vm-libvirt" do |x|
>>> x.vm.box = "ceph/ubuntu-xenial"
>>> x.vm.hostname = "test-remote-vm-libvirt"
>>> x.vm.network :private_network, ip: 10.0.10.100
>>> x.vm.provider :libvirt do |v|
>>>   v.driver = "kvm"
>>>   v.host = "10.73.40.52"
>>>   v.username = "skorada"
>>>   v.password = "mypassword"
>>>   v.connect_via_ssh = true
>>>   v.memory = 2
>>>   v.cpus = 2
>>>   v.nested = true
>>> end
>>>   end
>>> end
>>>
>>> Console logs on bringing up vagrant:
>>>
>>> skorada@test-server:~/home/vagrant/$ vagrant up
>>> Bringing machine 'test-remote-vm-libvirt' up with 'libvirt' provider...
>>>
>>> root@localhost's password:   ==>
>>> PASSWORD PROMPT
>>>
>>> ==> test-remote-vm-libvirt: Creating image (snapshot of base box volume).
>>> ==> test-remote-vm-libvirt: Creating domain with the following
>>> settings...
>>> ==> test-remote-vm-libvirt:  -- Name:
>>> master_test-remote-vm-libvirt
>>> ==> test-remote-vm-libvirt:  -- Domain type:   kvm
>>> ==> test-remote-vm-libvirt:  -- Cpus:  2
>>> ==> test-remote-vm-libvirt:  -- Feature:   acpi
>>> ==> test-remote-vm-libvirt:  -- Feature:   apic
>>> ==> test-remote-vm-libvirt:  -- Feature:   pae
>>> ==> test-remote-vm-libvirt:  -- Memory:6000M
>>> ==> test-remote-vm-libvirt:  -- Management MAC:
>>> ==> test-remote-vm-libvirt:  -- Loader:
>>> ==> test-remote-vm-libvirt:  -- Base box:  ceph/ubuntu-xenial
>>> ==> test-remote-vm-libvirt:  -- Storage pool:  default
>>> ==> test-remote-vm-libvirt:  -- Image:
>>>  /var/lib/libvirt/images/master_test-remote-vm-libvirt.img (301G)
>>> ==> test-remote-vm-libvirt:  -- Volume Cache:  default
>>> ==> test-remote-vm-libvirt:  -- Kernel:
>>> ==> test-remote-vm-libvirt:  -- Initrd:
>>> ==> test-remote-vm-libvirt:  -- Graphics Type: vnc
>>> ==> test-remote-vm-libvirt:  -- Graphics Port: 5900
>>> ==> test-remote-vm-libvirt:  -- Graphics IP:   127.0.0.1
>>> ==> test-remote-vm-libvirt:  -- Graphics Password: Not defined
>>> ==> test-remote-vm-libvirt:  -- Video Type:cirrus
>>> ==> test-remote-vm-libvirt:  -- Video VRAM:9216
>>> ==> test-remote-vm-libvirt:  -- Sound Type:
>>> ==> test-remote-vm-libvirt:  -- Keymap:en-us
>>> ==> test-remote-vm-libvirt:  -- TPM Path:
>>> ==> test-remote-vm-libvirt:  -- INPUT: type=mouse, bus=ps2
>>> ==> test-remote-vm-libvirt: Creating shared folders metadata...
>>> ==> test-remote-vm-libvirt: Starting domain.
>>> ==> test-remote-vm-libvirt: Waiting for domain to get an

Re: [vagrant-up] Debugging w/ PhpStorm

[Alvaro Miranda Aguilera]

screenshots of the errors?

can you share vagrant file?


On Thu, Jan 25, 2018 at 7:08 PM, Clinton Gallagher <
clinton.s.gallag...@gmail.com> wrote:

> Said no one on their death bed "I'll always remember the good times I had
> trying to configure @PhpStorm to use #Xdebug to debug @WordPress running on
> VVV/Vagrant @Ubuntu boxes installed on @VirtualBox VMs on #Windows10"
>
> I'm doing okay with Vagrant per se but debugging with PhpStorm is not
> going well at all. I really need help with this. PhpStorm just does not
> want me to learn to configure a remote server. Help!
>
> --
> 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/11a5da78-0840-4113-bf25-07987ff29b5d%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/CAHqq0ewzzUUiHdW0jXJxVPt%2BgUDJ7hqqFx68KV7CBf8Vk1SZMA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] How to add 2nd Hostonly private NIC in Vagrant box?

[Alvaro Miranda Aguilera]

hello

network is reset on each vagrant up.

the package box need to have the first interface confgured with dhcp

use the vagrant networking to add either private or public

you can add multiples interfaces this way

first nic / nat should be there since its what vagrant uses to configure
the guest

alvaro

On Wed, Jan 24, 2018 at 1:19 AM, Robert Wang 
wrote:

> Most of time we build Vagrant box without specific NIC, by default Vagrant
> add NAT NIC when launch vm using box,but sometime want to do pre-config on
> private network inside box.
>
> Tried it but when import box,found there is only NAT NIC there, seems
> private NIC removed when build box.
>
> Any idea is this for purpose or any solution I didn't know yet?
>
> Many thanks.
>
> BR/
> Robert
>
>
> --
> 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/8582fe86-44e3-4edf-929a-091bbcabd688%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/CAHqq0ewBWYoDDeNcB3ajsk6Vma77ST79zdCmi9TN1x%3Dr9YOPAA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] Password prompt on bringing up Vagrant although it is specified in Vagrantfile

[Alvaro Miranda Aguilera]

hello

seems you got the user/pass on the wrong block.

https://www.vagrantup.com/docs/vagrantfile/ssh_settings.html

config.ssh.username

or
x.ssh.username




On Wed, Jan 24, 2018 at 7:23 AM, Shashank Korada 
wrote:

> Hello,
>
> I am trying to launch VMs on a remote server by specifying the
> username/password for the server in the Vagrantfile but on running "vagrant
> up" it still prompts me for the password.
> How do I avoid being prompted for the password?
>
> This is my current Vagrantfile:
>
> VAGRANTFILE_API_VERSION = "2"
> Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
>   config.ssh.forward_agent = true
>   config.vm.define "test-remote-vm-libvirt" do |x|
> x.vm.box = "ceph/ubuntu-xenial"
> x.vm.hostname = "test-remote-vm-libvirt"
> x.vm.network :private_network, ip: 10.0.10.100
> x.vm.provider :libvirt do |v|
>   v.driver = "kvm"
>   v.host = "10.73.40.52"
>   v.username = "skorada"
>   v.password = "mypassword"
>   v.connect_via_ssh = true
>   v.memory = 2
>   v.cpus = 2
>   v.nested = true
> end
>   end
> end
>
> Console logs on bringing up vagrant:
>
> skorada@test-server:~/home/vagrant/$ vagrant up
> Bringing machine 'test-remote-vm-libvirt' up with 'libvirt' provider...
>
> root@localhost's password:   ==> PASSWORD
> PROMPT
>
> ==> test-remote-vm-libvirt: Creating image (snapshot of base box volume).
> ==> test-remote-vm-libvirt: Creating domain with the following settings...
> ==> test-remote-vm-libvirt:  -- Name:
> master_test-remote-vm-libvirt
> ==> test-remote-vm-libvirt:  -- Domain type:   kvm
> ==> test-remote-vm-libvirt:  -- Cpus:  2
> ==> test-remote-vm-libvirt:  -- Feature:   acpi
> ==> test-remote-vm-libvirt:  -- Feature:   apic
> ==> test-remote-vm-libvirt:  -- Feature:   pae
> ==> test-remote-vm-libvirt:  -- Memory:6000M
> ==> test-remote-vm-libvirt:  -- Management MAC:
> ==> test-remote-vm-libvirt:  -- Loader:
> ==> test-remote-vm-libvirt:  -- Base box:  ceph/ubuntu-xenial
> ==> test-remote-vm-libvirt:  -- Storage pool:  default
> ==> test-remote-vm-libvirt:  -- Image: /var/lib/libvirt/images/
> master_test-remote-vm-libvirt.img (301G)
> ==> test-remote-vm-libvirt:  -- Volume Cache:  default
> ==> test-remote-vm-libvirt:  -- Kernel:
> ==> test-remote-vm-libvirt:  -- Initrd:
> ==> test-remote-vm-libvirt:  -- Graphics Type: vnc
> ==> test-remote-vm-libvirt:  -- Graphics Port: 5900
> ==> test-remote-vm-libvirt:  -- Graphics IP:   127.0.0.1
> ==> test-remote-vm-libvirt:  -- Graphics Password: Not defined
> ==> test-remote-vm-libvirt:  -- Video Type:cirrus
> ==> test-remote-vm-libvirt:  -- Video VRAM:9216
> ==> test-remote-vm-libvirt:  -- Sound Type:
> ==> test-remote-vm-libvirt:  -- Keymap:en-us
> ==> test-remote-vm-libvirt:  -- TPM Path:
> ==> test-remote-vm-libvirt:  -- INPUT: type=mouse, bus=ps2
> ==> test-remote-vm-libvirt: Creating shared folders metadata...
> ==> test-remote-vm-libvirt: Starting domain.
> ==> test-remote-vm-libvirt: Waiting for domain to get an IP address...
> ==> test-remote-vm-libvirt: Waiting for SSH to become available...
> Pseudo-terminal will not be allocated because stdin is not a terminal.
> skorada@localhost's password:>
> PASSWORD PROMPT
> ==> test-remote-vm-libvirt: Setting hostname...
> ==> test-remote-vm-libvirt: Configuring and enabling network interfaces...
> ==> test-remote-vm-libvirt: Rsyncing folder: /home/vagrant/ => /vagrant
>
> skorada@localhost's password:   >
> PASSWORD PROMPT
>
>
> Am I missing any ssh config that is required? Also dont understand why I
> am being prompted for a password multiple times
> Any pointers would be helpful.
>
> Regards
>
> --
> 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/453f75a4-41b0-4a6e-ae22-79b8f86b5717%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 

Re: [vagrant-up] Re: Vagrant up virtual box boot error in windows 8

[Alvaro Miranda Aguilera]

you need to fix that error

is coming from virtualbox, not vagrant

On Wed, Jan 24, 2018 at 5:34 AM, <ve...@cityfashion.asia> wrote:

> I did same as you have mentioned.
> Previously and now also i am getting the same error.
> VM never went to power on state. it is always in Off state
> Please check and suggest me
>
>
> <https://lh3.googleusercontent.com/-MrW7rMANMPw/WmgM5fErRMI/AA0/UmUFivRewbMqhamqevA6mhryUecTYHMcgCLcBGAs/s1600/screenshot2.png>
>
>
> On Wednesday, January 24, 2018 00:57:00 UTC + 5: 30 Alvaro Miranda
> Aguilera wrote:
>>
>> hello
>>
>> open virtualbox, poweroff the VM, turn it on, see if you can connect
>>
>> user vagrant
>> password vagrant
>>
>>
>>
>> On Tue, Jan 23, 2018 at 4:07 PM, <ve...@cityfashion.asia> wrote:
>>
>>> Thanks for your reply.
>>> I did as you have mentioned but still i am getting same error.
>>> Please check and help me to fix
>>>
>>>
>>> <https://lh3.googleusercontent.com/-Jp5Mu92xiTk/WmdPqKFMmRI/AAg/VMZBbh8TsZYtnlyCf1fQvtAW9C4w5X6ewCLcBGAs/s1600/screenshot1.png>
>>>
>>>
>>> On Tuesday, January 23, 2018 17:17:27 UTC + 5:30 wrote ve ... @
>>> cityfashion.asia:
>>>>
>>>>
>>>> 0down votefavorite
>>>> <https://stackoverflow.com/questions/48400916/vagrant-up-virtual-box-boot-error-in-windows-8#>
>>>>
>>>>
>>>> <https://lh3.googleusercontent.com/-6SxFr7vMev8/Wmcgd5KPwhI/AAM/IW5p6bWhfGEBqt-k4RvJgC3Q2EAb7wUjwCLcBGAs/s1600/screenshot.png>
>>>>
>>>> I have installed vagrant (vagrant_2.0.1_x86_64.msi) and virtual box
>>>> (VirtualBox-4.3.12-93733-Win.exe, i also tried with
>>>> VirtualBox-5.2.6-120293-Win.exe) in windows 8 OS in my HP compaq latop
>>>> I have enabled virtualisation in BIOS But while executing 'vagrant up' i am
>>>> getting the below error  I googled for answers and none of them worked for
>>>> me. Please help me to fix this issue. I am trying to to setup
>>>> 'ubuntu/trusty64' box
>>>>
>>>> I am getting this error:
>>>>
>>>> ==> default: Waiting for machine to boot. This may take a few m The
>>>> guest machine entered an invalid state while waiting for it to boot. Valid
>>>> states are 'starting, running'. The machine is i 'poweroff' state. Please
>>>> verify everything is configured properly and try again.
>>>>
>>>> If the provider you're using has a GUI that comes with it, it is often
>>>> helpful to open that and watch the machine, since t GUI often has more
>>>> helpful error messages than Vagrant can retr For example, if you're using
>>>> VirtualBox, run vagrant up while VirtualBox GUI is open.
>>>>
>>>> The primary issue for this error is that the provider you're us is not
>>>> properly configured. This is very rarely a Vagrant issue
>>>>
>>>>
>>>> --
>>> 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/ms
>>> gid/vagrant-up/59d77798-176b-49d5-a12c-2eab337d2f21%40googlegroups.com
>>> <https://groups.google.com/d/msgid/vagrant-up/59d77798-176b-49d5-a12c-2eab337d2f21%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>> 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 receiv

Re: [vagrant-up] Re: Vagrant up virtual box boot error in windows 8

[Alvaro Miranda Aguilera]

hello

open virtualbox, poweroff the VM, turn it on, see if you can connect

user vagrant
password vagrant



On Tue, Jan 23, 2018 at 4:07 PM,  wrote:

> Thanks for your reply.
> I did as you have mentioned but still i am getting same error.
> Please check and help me to fix
>
>
> 
>
>
> On Tuesday, January 23, 2018 17:17:27 UTC + 5:30 wrote ve ... @
> cityfashion.asia:
>>
>>
>> 0down votefavorite
>> 
>>
>>
>> 
>>
>> I have installed vagrant (vagrant_2.0.1_x86_64.msi) and virtual box
>> (VirtualBox-4.3.12-93733-Win.exe, i also tried with
>> VirtualBox-5.2.6-120293-Win.exe) in windows 8 OS in my HP compaq latop I
>> have enabled virtualisation in BIOS But while executing 'vagrant up' i am
>> getting the below error  I googled for answers and none of them worked for
>> me. Please help me to fix this issue. I am trying to to setup
>> 'ubuntu/trusty64' box
>>
>> I am getting this error:
>>
>> ==> default: Waiting for machine to boot. This may take a few m The guest
>> machine entered an invalid state while waiting for it to boot. Valid states
>> are 'starting, running'. The machine is i 'poweroff' state. Please verify
>> everything is configured properly and try again.
>>
>> If the provider you're using has a GUI that comes with it, it is often
>> helpful to open that and watch the machine, since t GUI often has more
>> helpful error messages than Vagrant can retr For example, if you're using
>> VirtualBox, run vagrant up while VirtualBox GUI is open.
>>
>> The primary issue for this error is that the provider you're us is not
>> properly configured. This is very rarely a Vagrant issue
>>
>>
>> --
> 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/59d77798-176b-49d5-a12c-2eab337d2f21%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/CAHqq0ezw2szN7-COC8uQRiyecxydZik0Gx_N%2B8WL7AYY4b%3DH_A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] Vagrant up virtual box boot error in windows 8

[Alvaro Miranda Aguilera]

Hello

We need to separate tool and run time from boxes and projects

can you try with our box?

mkdir p64
cd p64
vagrant init -m hashicorp/precise64
vagrant up

does that work?



On Tue, Jan 23, 2018 at 12:47 PM,  wrote:

>
> 0down votefavorite
> 
>
>
> 
>
> I have installed vagrant (vagrant_2.0.1_x86_64.msi) and virtual box
> (VirtualBox-4.3.12-93733-Win.exe, i also tried with
> VirtualBox-5.2.6-120293-Win.exe) in windows 8 OS in my HP compaq latop I
> have enabled virtualisation in BIOS But while executing 'vagrant up' i am
> getting the below error  I googled for answers and none of them worked for
> me. Please help me to fix this issue. I am trying to to setup
> 'ubuntu/trusty64' box
>
> I am getting this error:
>
> ==> default: Waiting for machine to boot. This may take a few m The guest
> machine entered an invalid state while waiting for it to boot. Valid states
> are 'starting, running'. The machine is i 'poweroff' state. Please verify
> everything is configured properly and try again.
>
> If the provider you're using has a GUI that comes with it, it is often
> helpful to open that and watch the machine, since t GUI often has more
> helpful error messages than Vagrant can retr For example, if you're using
> VirtualBox, run vagrant up while VirtualBox GUI is open.
>
> The primary issue for this error is that the provider you're us is not
> properly configured. This is very rarely a Vagrant issue
>
>
> --
> 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/fc14a1ac-c4cb-4544-9c76-bfb126aba858%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/CAHqq0exYbfRDgSXNQBKJouCHWS%2BXEtfhE5vXNbcSsos%2B%3DCyCXQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] Packaging Vagrant as a deb?

[Alvaro Miranda Aguilera]

Hello

Have you seen this?

https://github.com/hashicorp/vagrant-installers


On Tue, Jan 23, 2018 at 2:12 AM, Jared Suttles  wrote:

> Hi all,
>
> Been using Vagrant for a while now, but have never had to consider
> building/distributing it before.  Wondering if there is documentation on
> how to build Vagrant into a deb for Ubuntu, or if there are guidelines for
> how to deploy some tweaks to local servers using ansible or the like?
>
> Ultimately we will probably wrap up our changes for upload to the general
> project, but for what we're doing we wanted to apply some changes to v1.9.5.
>
> Until now we've been just pushing new files over the top of the installed
> files on our servers, but that seems wrong... I was able to build a gem of
> my changes, but I dont fully understand the architecture of what I've
> installed for the v1.9.5 deb. :)
>
> Can anyone point me in a helpful direction?  Or tell me I'm really barking
> up the wrong tree? :)
>
> Thanks!
> Jared
>
> --
> 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/5d7e0518-cbeb-4fd4-89a9-6429d6d881f9%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/CAHqq0ewJv555EurKOi0YO7jZH1jfgSQ9yRAnFUEQRVMEmVFXYA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] OpenSSL SSL_read: SSL_ERROR_SYSCALL, errno 10054

[Alvaro Miranda Aguilera]

if possible can you try from a different network?



On Fri, Jan 19, 2018 at 6:52 PM, Ane Kuzmanovska 
wrote:

> Hello,
>
> I have been trying to install homestead and this error pops up every time:
>
> OpenSSL SSL_read: SSL_ERROR_SYSCALL, errno 10054
>
> I have already installed virtual box and vagrant, and I am using windows
> 10 prompt. I could use some assistance in this matter
>
> Thanks a lot!
>
> --
> 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/e782ee54-092b-4778-9903-7bb77616f4ab%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/CAHqq0exapinagtkmPagYXT14ei5Rr13edchE5UyuptenHWd3%2Bw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] Vagrant - Linux Host - Virtualbox Shared folders - Windows10 Pro Guest

[Alvaro Miranda Aguilera]

hello

can you put a simple Vagrantfile with a box available in Vagrant cloud to
reproduce?

Will be quicker if we can share the same box setup etc.

Thanks
Alvaro

On Thu, Jan 18, 2018 at 2:22 PM, Xavier Krantz  wrote:

> Hello there,
>
>
> I have a question regarding Virtualbox shared folders between a Linux host
> and a Windows10 Guest.
> I have searched the internet during 2 days now but I was unable to find
> any answer or possible workaround.
>
> * So by creating a VM manually in VBox GUI, the shared folders work.
> * By using Vagrant to define the state of the VM it does not.
>
>
> Any idea ?
>
>   # == Shared Folders
>   #
>   config.vm.synced_folder File.absolute_path(dir_name), "/Dir"
>   config.vm.synced_folder File.absolute_path(File.join(ENV['HOME'],
> 'Documents')), "/HOST_Documents"
>
> -> This does not work 
>
>
> Ubuntu 17.10
> Virtualbox 5.1.30
> Vargant: 2.0.1
>
>
> Thank you for your help !
>
> --
> 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/5e8953a9-32e4-4594-acbc-117dc79f09e8%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/CAHqq0ew52vxeN88KThX90qEnF0ZMgoiwhUAwS8TUt%2BfcLN7S3Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] Vagrant vmware-esxi plugin flag to enable hardware virtualization on the VM

[Alvaro Miranda Aguilera]

just to be sure

from this:

vi://10.73.40.19/

to this

vi://root:Password123@10.73.40.19/


On Thu, Jan 18, 2018 at 2:13 PM, Shashank Korada <shashank.kor...@gmail.com>
wrote:

> Thank you Alvaro.
>
> I just figured out 1. We could use the custom_vmx_settings and add what is
> required as a key value pair.
> Thanks for the second one, will try escaping the special characters
>
> -Shashank
>
> On Thursday, January 18, 2018 at 6:30:26 PM UTC+5:30, Alvaro Miranda
> Aguilera wrote:
>>
>> Hello
>>
>> for 1 you can contact the plugin person to see if he can add the conf part
>>
>> for 2 you can use vi://user:password@server
>>
>> if you got special characters you can escape them with the html codes ie
>> # -> %23 i think, by memory but giving you the idea.
>>
>> Thanks
>> Alvaro.
>>
>> On Wed, Jan 17, 2018 at 11:54 AM, Shashank Korada <shashan...@gmail.com>
>> wrote:
>>
>>> Hi,
>>>
>>> I am using the vagrant esxi plugin for my testing.
>>>
>>> Plugin: https://github.com/josenk/vagrant-vmware-esxi
>>>
>>> A couple of issues that I am facing.
>>>
>>> 1. For my testing I need to enable hardware virtualization on the VM
>>> that is brought up on the ESXI server. Is there a flag that I can enable in
>>> the vagrant file to support this.
>>> I am currently manually editing the vmx file on the VM by adding the
>>> following  : vhv.enable = "TRUE"'
>>>
>>> Is there a flag that I can use in my vagrant file that can be
>>> enabled to achieve this when the VM is brought up ?
>>>
>>> 2. For the plugin to work we need ovftool and when run vagrant to bring
>>> up the VM ovftool prompts for the password of the esxi server.
>>> Is there a way to change this config so as to not prompt for the
>>> password
>>>
>>> Log from console:
>>>VMware ovftool 4.2.0 (build-5965791)
>>>Opening VMX source: /home/sdptest/.vagrant.d/boxes
>>> /bento-VAGRANTSLASH-ubuntu-16.04/201801.02.0/vmware_desktop/
>>> _sdp-master-esxi-1.vmx
>>>Enter login information for target vi://10.73.40.19/
>>>Username: root
>>>Password: ** . => Manually entered. How
>>> can this be avoided?
>>>
>>>
>>> Vagrantfile:
>>>
>>> # Adjustable settings for Master Node
>>>
>>> CFG_MEMSIZE = "6000"  # max memory for each VM
>>> CFG_TZ = "US/Pacific" # timezone, like US/Pacific, US/Eastern, UTC,
>>> Europe/Warsaw, etc.
>>> CFG_CPU_NUM = "2"
>>>
>>> CFG_MASTER_NODE_NAME = "sdp-master-esxi-1"
>>>
>>> VAGRANTFILE_API_VERSION = "2"
>>> Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
>>>   config.ssh.forward_agent = true
>>>   config.vm.define CFG_MASTER_NODE_NAME do |x|
>>> x.vm.box = "bento/ubuntu-16.04"
>>> x.vm.provider :vmware_esxi do |v|
>>>   v.esxi_hostname = '10.73.40.11'
>>>   v.esxi_username = 'root'
>>>   v.esxi_password = 'password123'
>>>   v.vmname = CFG_MASTER_NODE_NAME
>>>   v.memsize = 6144
>>>   v.numvcpus = CFG_CPU_NUM
>>> end
>>>   end
>>> end
>>>
>>> --
>>> 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/ms
>>> gid/vagrant-up/996885d7-8393-4f18-abd9-a8b779c6d3b2%40googlegroups.com
>>> <https://groups.google.com/d/msgid/vagrant-up/996885d7-8393-4f18-abd9-a8b779c6d3b2%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> --
>> Alvaro
>>
>> --
> This mailing list is governe

Re: [vagrant-up] Vagrant vmware-esxi plugin flag to enable hardware virtualization on the VM

[Alvaro Miranda Aguilera]

Hello

for 1 you can contact the plugin person to see if he can add the conf part

for 2 you can use vi://user:password@server

if you got special characters you can escape them with the html codes ie #
-> %23 i think, by memory but giving you the idea.

Thanks
Alvaro.

On Wed, Jan 17, 2018 at 11:54 AM, Shashank Korada  wrote:

> Hi,
>
> I am using the vagrant esxi plugin for my testing.
>
> Plugin: https://github.com/josenk/vagrant-vmware-esxi
>
> A couple of issues that I am facing.
>
> 1. For my testing I need to enable hardware virtualization on the VM that
> is brought up on the ESXI server. Is there a flag that I can enable in the
> vagrant file to support this.
> I am currently manually editing the vmx file on the VM by adding the
> following  : vhv.enable = "TRUE"'
>
> Is there a flag that I can use in my vagrant file that can be enabled
> to achieve this when the VM is brought up ?
>
> 2. For the plugin to work we need ovftool and when run vagrant to bring up
> the VM ovftool prompts for the password of the esxi server.
> Is there a way to change this config so as to not prompt for the
> password
>
> Log from console:
>VMware ovftool 4.2.0 (build-5965791)
>Opening VMX source: /home/sdptest/.vagrant.d/
> boxes/bento-VAGRANTSLASH-ubuntu-16.04/201801.02.0/vmware_desktop/_sdp-
> master-esxi-1.vmx
>Enter login information for target vi://10.73.40.19/
>Username: root
>Password: ** . => Manually entered. How can
> this be avoided?
>
>
> Vagrantfile:
>
> # Adjustable settings for Master Node
>
> CFG_MEMSIZE = "6000"  # max memory for each VM
> CFG_TZ = "US/Pacific" # timezone, like US/Pacific, US/Eastern, UTC,
> Europe/Warsaw, etc.
> CFG_CPU_NUM = "2"
>
> CFG_MASTER_NODE_NAME = "sdp-master-esxi-1"
>
> VAGRANTFILE_API_VERSION = "2"
> Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
>   config.ssh.forward_agent = true
>   config.vm.define CFG_MASTER_NODE_NAME do |x|
> x.vm.box = "bento/ubuntu-16.04"
> x.vm.provider :vmware_esxi do |v|
>   v.esxi_hostname = '10.73.40.11'
>   v.esxi_username = 'root'
>   v.esxi_password = 'password123'
>   v.vmname = CFG_MASTER_NODE_NAME
>   v.memsize = 6144
>   v.numvcpus = CFG_CPU_NUM
> end
>   end
> end
>
> --
> 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/996885d7-8393-4f18-abd9-a8b779c6d3b2%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/CAHqq0ezvaTuoiDEoGEKyuVPuY%2B8F8A2uRc0cHMfASTaGBtia%3DA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] Can't download any vagrant box hosted by Vagrant Cloud

[Alvaro Miranda Aguilera]

can't say, but may be, corporate network (ids/dpi), they run some vpn, etc,
that may impact mtu and cause issues,  but difficult to say for sure

is there any proxy you can use?


On Wed, Jan 17, 2018 at 1:47 AM, Peter Henry <codingmadeeasyut...@gmail.com>
wrote:

> I tried on another network and it downloaded successfully. So it's
> definitely a network related issue but I can't figure out what could be
> causing the SSL error. Do you have any insight as to what the possible
> causes could be?
>
> On Tuesday, January 16, 2018 at 6:25:18 PM UTC-5, Alvaro Miranda Aguilera
> wrote:
>>
>> hello
>>
>> macos high sierra, over wifi.
>>
>>
>> *0*  $ time vagrant box add c9s/centos-stack
>>
>> *==> box: Loading metadata for box 'c9s/centos-stack'*
>>
>> box: URL: https://vagrantcloud.com/c9s/centos-stack
>>
>> *==> box: Adding box 'c9s/centos-stack' (v1.0.1) for provider: virtualbox*
>>
>> box: Downloading: https://vagrantcloud.com/c9s/b
>> oxes/centos-stack/versions/1.0.1/providers/virtualbox.box
>>
>> *==> box: Successfully added box 'c9s/centos-stack' (v1.0.1) for
>> 'virtualbox'!*
>>
>>
>> real 4m35.573s
>>
>> user 0m8.657s
>>
>> sys 0m5.386s
>>
>> *0*  $ uname -a
>>
>> Darwin Alvaros-MacBook-Pro.local 17.3.0 Darwin Kernel Version 17.3.0: Thu
>> Nov  9 18:09:22 PST 2017; root:xnu-4570.31.3~1/RELEASE_X86_64 x86_64
>>
>> *0*  $
>>
>>
>>
>> no issues at all
>>
>> On Wed, Jan 17, 2018 at 12:05 AM, Peter Henry <codingmad...@gmail.com>
>> wrote:
>>
>>> Hi,
>>>
>>> I've tried version 2.0.0 and 2.0.1, but I continuously get the same
>>> results. If I try to download a vagrant box that is hosted on vagrant cloud
>>> it fails to download and gives me the following error:
>>>
>>> "An error occurred while download the remote file. The error message,
>>> if any, is reproduced below. Please fix this error and try again.
>>>
>>> OpenSSL SSL_read: SSL_ERROR_SYSCALL, errno 54
>>>
>>> (Sometimes on OSX it says LIBRESSL instead of OPENSSL)"
>>>
>>> However if I try to download a vagrant box that is externally hosted
>>> such as "ubuntu/trusty64" then everything works fine.
>>>
>>> I've tried the following to get it working to no avail:
>>>
>>> Method 1: Vagrant up
>>>
>>> Method 2: vagrant box add c9s/centos-stack
>>>
>>> Method 3: vagrant box add --insecure -c c9s/centos-stack http://atlas.
>>> hashicorp.com/c9s/boxes/centos-stack
>>>
>>> I've tried with other vagrant boxes hosted on vagrant cloud such as
>>> laravel/homestead and they all have failed. Is there any reason why
>>> vagrantcloud.com gives me an SSL error? Is there any way that my team
>>> and I can get around this?
>>>
>>> Ps. On OSX I tried using wget and it failed as well.
>>>
>>> Thanks in advance for your assistance.
>>>
>>> --
>>> 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/ms
>>> gid/vagrant-up/5b93977e-5b34-4f31-8594-5c0f951383f2%40googlegroups.com
>>> <https://groups.google.com/d/msgid/vagrant-up/5b93977e-5b34-4f31-8594-5c0f951383f2%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>> 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.

Re: [vagrant-up] Can't download any vagrant box hosted by Vagrant Cloud

[Alvaro Miranda Aguilera]

hello

macos high sierra, over wifi.


*0*  $ time vagrant box add c9s/centos-stack

*==> box: Loading metadata for box 'c9s/centos-stack'*

box: URL: https://vagrantcloud.com/c9s/centos-stack

*==> box: Adding box 'c9s/centos-stack' (v1.0.1) for provider: virtualbox*

box: Downloading:
https://vagrantcloud.com/c9s/boxes/centos-stack/versions/1.0.1/providers/virtualbox.box

*==> box: Successfully added box 'c9s/centos-stack' (v1.0.1) for
'virtualbox'!*


real 4m35.573s

user 0m8.657s

sys 0m5.386s

*0*  $ uname -a

Darwin Alvaros-MacBook-Pro.local 17.3.0 Darwin Kernel Version 17.3.0: Thu
Nov  9 18:09:22 PST 2017; root:xnu-4570.31.3~1/RELEASE_X86_64 x86_64

*0*  $



no issues at all

On Wed, Jan 17, 2018 at 12:05 AM, Peter Henry  wrote:

> Hi,
>
> I've tried version 2.0.0 and 2.0.1, but I continuously get the same
> results. If I try to download a vagrant box that is hosted on vagrant cloud
> it fails to download and gives me the following error:
>
> "An error occurred while download the remote file. The error message, if
> any, is reproduced below. Please fix this error and try again.
>
> OpenSSL SSL_read: SSL_ERROR_SYSCALL, errno 54
>
> (Sometimes on OSX it says LIBRESSL instead of OPENSSL)"
>
> However if I try to download a vagrant box that is externally hosted such
> as "ubuntu/trusty64" then everything works fine.
>
> I've tried the following to get it working to no avail:
>
> Method 1: Vagrant up
>
> Method 2: vagrant box add c9s/centos-stack
>
> Method 3: vagrant box add --insecure -c c9s/centos-stack http://atlas.
> hashicorp.com/c9s/boxes/centos-stack
>
> I've tried with other vagrant boxes hosted on vagrant cloud such as
> laravel/homestead and they all have failed. Is there any reason why
> vagrantcloud.com gives me an SSL error? Is there any way that my team and
> I can get around this?
>
> Ps. On OSX I tried using wget and it failed as well.
>
> Thanks in advance for your assistance.
>
> --
> 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/5b93977e-5b34-4f31-8594-5c0f951383f2%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/CAHqq0ewXUQWyyU3zUL4UJQAQo33tBXui1qwwhRrO4jACk82ysg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] vagrant package: won't fork/clone/duplicate/generate a similar vagrant-up-able box/image

[Alvaro Miranda Aguilera]

is not a bug.

you need to make sure the box is ready to be used and include all thats
required.

1. use config.box.insert_key = false so the keys doesn't get overriden
2. use a tool that is made to build boxes like packer.io


Alvaro.


On Mon, Jan 15, 2018 at 6:00 PM, Ribamar Santarosa 
wrote:

>
> I am having a problem with vagrant package  (full description
> https://github.com/hashicorp/vagrant/issues/9362). It looks like a bug
> with vagrant ssh keys, does anybody have any insights?
>
> vagrant package --output mynew.box
>
>
> # 
>
> vagrant add mynewbox
>
> # ...
>
> vagrant up --provider=libvirt # full output at: 
> https://gist.github.com/ribamar-santarosa/7b98edacaada8fc1892140a2aabca0e1
> # ...
> # DEBUG wait_till_up: Searching for IP for MAC address: 52:54:00:19:76:79
> # 
> # ==> default: Waiting for domain to get an IP address...
> # ...
> #  INFO wait_till_up: Got IP address 192.168.121.65
> # ...
> #  INFO wait_till_up: Time for getting IP: 15.072947263717651
> # ...
> #  INFO ssh: SSH not up: # connection was reset! This usually happens when the machine is
> # ...
> # DEBUG ssh: == Net-SSH connection debug-level log END ==
> #  INFO ssh: SSH not up: # connection was reset! This usually happens when the machine is
> # ...
> # taking too long to reboot. First, try reloading your machine with
> # ...
>
> --
> 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/81a49bec-bfac-4bfb-8636-799b72ede3d2%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/CAHqq0ewaWVOiFGx3ihAkZ2NA76R7h5ekxiBFroH1YB0YFiVgTw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] Why vagrant creates two shared resources for one folder? Vagrant 2.0.1; laravel/homestead (hyperv, 5.0.1); Windows 10; SMB

[Alvaro Miranda Aguilera]

is not an issue

the current folder is mounted as /vagrant

on top of that does what you ask o do.

you can ignore /vagrant as its the default.

On Tue, Jan 16, 2018 at 7:49 AM, Alexander Radchenko <
radchenkosa...@gmail.com> wrote:

>
> I created new Laravel project `laravel new blog` at folder
> `~/Documents/Laravel`
>
> Changed folder to new Laravel project `cd blog`
>
> Add  laravel/homestead (hyperv, 5.0.1) to project
> `composer require laravel/homestead --dev`
> Then
> `vendor\\bin\\homestead make`
>
> Edit `Homestead.yaml` file to next:
> ```
> ip: 192.168.10.10
> memory: 2048
> cpus: 1
> provider: *hyperv*
> folders:
> -
> map: '*~/Documents/Laravel/blog*'
> to: /home/vagrant/code
> sites:
> -
> map: *blog.test*
> to: /home/vagrant/code/public
> databases:
> - homestead
> name: blog
> hostname: blog
> ```
>
> Created Hyper-V External virtual switch with name `External`
>
> Start vagrant `vagrant up` and select this `External` switch to attach to
> Hyper-V instance.
>
> And vagrant creates two  shared resources for `*~/Documents/Laravel/blog*`
> folder.
> The log is next:
> ```
> ==> blog: Preparing SMB shared folders...
> blog: You will be asked for the username and password to use for the
> SMB
> blog: folders shortly. Please use the proper username/password of your
> blog: Windows account.
> blog:
> blog: Username: Alex
> blog: Password (will be hidden):
> ==> blog: Setting hostname...
> ==> blog: Mounting SMB shared folders...
> blog: C:/Users/Alex/Documents/Laravel/blog => /home/vagrant/code
> blog: C:/Users/Alex/Documents/Laravel/blog => /vagrant
> ```
>
> Is it vagrant or homestead issue?
>
>
> --
> 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/716fb274-8feb-4332-89db-40b098012603%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/CAHqq0ewoCm6WrnSEQ%3Dt7c0r%3DjETr3Mu%3DFUsc1vz%2BejSrJQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] ubuntu-VAGRANTSLASH-xenial64 20180112 connection failed

[Alvaro Miranda Aguilera]

Hello

Those boxes are made by canonical. so perhaps you can skip this version


On Mon, Jan 15, 2018 at 12:38 AM, Taylor Ren  wrote:

> I have no problem up my Vagrant VM when using the 20180109 box. Today I
> updated this box to the newest 20180112 and the `vagrant up` command shows
> me the "Authentication failure. Retrying..." and finally the familiar
> "Timed out while waiting for the machine to boot. This means that Vagrant
> was unable to communicate with the guest machine within the configured
> ("config.vm.boot_timeout" value) time period."
>
> After this, I used `vagrant halt` and the following showed:
>
> ~~~
>  default: Attempting graceful shutdown of VM...
> default: Guest communication could not be established! This is usually
> because
> default: SSH is not running, the authentication information was
> changed,
> default: or some other networking issue. Vagrant will force halt, if
> default: capable.
> ==> default: Forcing shutdown of VM...
> ~~~
>
> If I delete the 0112 box and boot up with 0109, the VM booted
> successfully.
>
> Hope there could be a way for me to make it running...
>
> My OS: Windows 10 with latest patch
> Vagrant: 2.0.1
> Virtual Box: 5.2.4
>
> Thank you!
>
> --
> 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/aef9092a-d8a7-4572-96c7-dca5c249137d%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/CAHqq0exrQXQtywbNS7CP%3Ducn2dMxRjsLdCRGH2fmL3eRqj2q8g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] Vagrant up returns 'open' : Access is denied. (5) (ChildProcess:: Error)

[Alvaro Miranda Aguilera]

hello

this is strange:

C:/HashiCorp/Vagrant/embedded/gems/gems/childprocess-0.6.3/
lib/childprocess/windows/handle.rb:12:in `open': Access is denied. (5)
(ChildProcess::Error)


as normal user using cmd.exe try with vagrant up --debug

bug use our default box first

mkdir precise64
cd precise64
vagrant init -m hashicorp/precise64
vagrant up

if this fails too add --debug

if this works then share the vagrantfile you are using and run vagrant up
--debug and share the output


On Fri, Jan 12, 2018 at 6:59 PM, Chris Buck  wrote:

> I am looking to have my team at work start using Vagrant to spin up lab
> environments for testing certain tools. To that end a DevOps (Mac)
> colleague of mine wrote a vagrant configuration for me. Vagrant spins up
> the two machines on his Mac, Windows fails.
> My tech:
> Windows 10 Anniversary Update
> PowerShell 5
> Vagrant 2.0.1
> Virtualbox 5.2.2
> Git 2.15.1.2
> The etools Vagrant etc. were all installed using "Run as Administrator".
>
> Whether I attempt to execute *vagrant up* as admin or using normal
> permissions in CMD, vagrant reports:
>
> C:/HashiCorp/Vagrant/embedded/gems/gems/childprocess-0.6.3/
> lib/childprocess/windows/handle.rb:12:in `open': Access is denied. (5)
> (ChildProcess::Error)
> from C:/HashiCorp/Vagrant/embedded/gems/gems/childprocess-0.6.3/
> lib/childprocess/windows/process.rb:71:in `launch_process'
> from C:/HashiCorp/Vagrant/embedded/gems/gems/childprocess-0.6.3/
> lib/childprocess/abstract_process.rb:82:in `start'
> from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/
> vagrant/util/subprocess.rb:141:in `block in execute'
> from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/
> vagrant/util/safe_chdir.rb:26:in `block (2 levels) in safe_chdir'
> from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/
> vagrant/util/safe_chdir.rb:25:in `chdir'
> from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/
> vagrant/util/safe_chdir.rb:25:in `block in safe_chdir'
> from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/
> vagrant/util/safe_chdir.rb:24:in `synchronize'
> from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/
> vagrant/util/safe_chdir.rb:24:in `safe_chdir'
> from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/
> vagrant/util/subprocess.rb:140:in `execute'
> from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/
> vagrant/util/subprocess.rb:22:in `execute'
> from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/
> vagrant/util/powershell.rb:81:in `version'
> from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/
> vagrant/util/powershell.rb:95:in `validate_install!'
> from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/
> vagrant/util/powershell.rb:50:in `execute_cmd'
> from 
> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/util/platform.rb:73:in
> `block in windows_admin?'
> from 
> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/util/platform.rb:75:in
> `windows_admin?'
> from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/
> plugins/providers/hyperv/provider.rb:19:in `usable?'
> from 
> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/environment.rb:379:in
> `block in default_provider'
> from 
> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/registry.rb:49:in
> `block in each'
> from 
> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/registry.rb:48:in
> `each'
> from 
> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/registry.rb:48:in
> `each'
> from 
> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/environment.rb:365:in
> `default_provider'
> from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/
> vagrant/plugin/v2/command.rb:177:in `block in with_target_vms'
> from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/
> vagrant/plugin/v2/command.rb:204:in `block in with_target_vms'
> from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/
> vagrant/plugin/v2/command.rb:186:in `each'
> from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/
> vagrant/plugin/v2/command.rb:186:in `with_target_vms'
> from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/
> plugins/commands/up/command.rb:87:in `execute'
> from 
> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/cli.rb:42:in
> `execute'
> from 
> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/environment.rb:308:in
> `cli'
> from 
> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/bin/vagrant:138:in
> `'
>
> Almost laughably, when executing *vagrant up* from within PowerShell
> running as Admin, vagrant reports:
>
> The version of 

Re: [vagrant-up] Re: vagrant and ansible provisionning fails with INFO interface: error: The Ansible software could not be found! Please verify that Ansible is correctly installed on your host system.

[Alvaro Miranda Aguilera]

yeah no idea why, i tried localhost, change name etc, so i went for host:
all to get it running

On Thu, Jan 11, 2018 at 6:43 PM, Jean-Luc Pinardon 
wrote:

> Well... that's not what I wanted to do... But never mind, I tried with
> ansible_local.
> It automatically installs ansible on the guest and run it.
> Ok, ansible runs on the guest, but it fails with a :
>
> PLAY [Configure CI server] **
> ***
> skipping: no hosts matched
>
> error.
>
> It means that it actually try to run the playbook, but it can find the
> server where to run it.
> As it runs on the guest, I have tried to run the playbook directly on the
> guest.
> ==> Same error.
> So, I have changed the hosts line of the playbook to *hosts: localhost*.
> .
> Running it again *from the guest*, it worked !
> So far so good, I therefor changed to localhost within the playbook on the
> host and redo from scratch.
> But I retrieved the error again.
> ... and have no idea why...
>
> Thanks again for your help, and have a good evening.
> Best regards
> J.L.P.
>
> Le jeudi 11 janvier 2018 11:33:36 UTC+1, Jean-Luc Pinardon a écrit :
>>
>> Dear all,
>>
>> I am new to vagrant and ansible, and I am currently making some trials.
>> My host environment is a WIndows 7 machine (sorry) with cygwin64.
>> Ansible and Vagrant are both installed :
>> $ ansible --version  &&  vagrant --version
>> ansible 2.4.2.0
>>   config file = None
>>   configured module search path = ['/home/jeanlupi/.ansible/plug
>> ins/modules', '/usr/share/ansible/plugins/modules']
>>   ansible python module location = /usr/lib/python3.6/site-packages/
>> ansible
>>   executable location = /usr/bin/ansible
>>   python version = 3.6.3 (default, Oct 31 2017, 19:00:36) [GCC 6.4.0]
>> Vagrant 2.0.1
>>
>>
>> At the moment, I know how to create a Vagrantfile, have a brand new VM
>> automatically created with Vagrant, and access it through ssh.
>> Also, I succeed in using an ansible playbook to provision this new VM.
>> So, each vagrant and ansible can run correctly when launched one by one.
>>
>> Now, I want to make it to work together using config.vm.provider. But it
>> fails with the following trace :
>>  INFO provision: Writing provisioning sentinel so we don't provision
>> again
>>  INFO interface: info: Running provisioner: ansible...
>>  INFO interface: info: ==> default: Running provisioner: ansible...
>> ==> default: Running provisioner: ansible...
>>  INFO environment: Running hook: provisioner_run
>>  INFO runner: Preparing hooks for middleware sequence...
>>  INFO runner: 1 hooks defined.
>>  INFO runner: Running action: provisioner_run #> Vagrant::Action::Builtin::Provision#run_provisioner>
>>  INFO warden: Calling IN action: #> ashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/action/warden.rb:94
>> (lambda)>
>>  INFO subprocess: Starting process: ["C:/Program
>> Files/Oracle/VirtualBox/VBoxManage.exe", "showvminfo",
>> "2ace896f-293d-442b-9c62-bb8281960435", "--machinereadable"]
>>  INFO subprocess: Command not in installer, restoring original
>> environment...
>>  INFO subprocess: Starting process: ["C:/Program
>> Files/Oracle/VirtualBox/VBoxManage.exe", "showvminfo",
>> "2ace896f-293d-442b-9c62-bb8281960435", "--machinereadable"]
>>  INFO subprocess: Command not in installer, restoring original
>> environment...
>>  INFO interface: warn: Windows is not officially supported for the
>> Ansible Control Machine.
>> Please check https://docs.ansible.com/intro_installation.html#control-
>> machine-requirements
>>
>> Windows is not officially supported for the Ansible Control Machine.
>> Please check https://docs.ansible.com/intro_installation.html#control-
>> machine-requirements
>> ERROR ansible_host: Error while gathering the ansible version: The
>> Ansible software could not be found! Please verify
>> that Ansible is correctly installed on your host system.
>>
>> *So, it incorrectly says that "The Ansible software could not be found!*",
>> and I don't clearly understand why it claims that "Windows is not
>> officially supported for the Ansible Control Machine", though ansible
>> clearly runs correctly.
>>
>> For information :
>> The Vagrantfile is :
>> Vagrant.configure(2) do |config|
>>   config.vm.box = "geerlingguy/centos7"
>>   config.vm.network "forwarded_port", guest: 8080, host: 8080
>>   config.vm.synced_folder "../", "/var/data",create: true
>>   config.vm.provider "virtualbox" do |v|
>> # Add a name
>> v.name="CI_Env"
>> # Add enough memory
>> v.memory = 4048
>>   end
>>   config.vm.provision :ansible do |ansible|
>> ansible.playbook="../ansible/configure-ci-server.yml"
>> ansible.tags=["geerlingguy.java","git"]
>>   end
>> end
>>
>> And the directory tree is :
>> $ tree -d -L 3 .
>> .
>> ├── ansible
>> │   └── roles
>> │   ├── geerlingguy.java
>> │   ├── geerlingguy.jenkins
>> │   ├── git
>> │   └── LTS-2_89.jenkins
>> ├── 

Re: [vagrant-up] Re: vagrant and ansible provisionning fails with INFO interface: error: The Ansible software could not be found! Please verify that Ansible is correctly installed on your host system.

[Alvaro Miranda Aguilera]

you can use ansible_local that runs in the guest.

and there was couple of typos in one for the files..

https://github.com/JiElPe-Fr38/myKnowledge/pull/1

you can test mine here:
https://github.com/kikitux/myKnowledge

On Thu, Jan 11, 2018 at 3:15 PM, Jean-Luc Pinardon 
wrote:

> Ok, I put it there :
> https://github.com/JiElPe-Fr38/myKnowledge.git
>
> Note that I have sligthly modified the directory tree and the Vagrantfile
> according to this Vagrant documentation page
> ,
> and assuming that I needed to pass the same parameters as when running
> manually ansible.
>
> Thanks for your help.
> J-L
>
> Le jeudi 11 janvier 2018 11:33:36 UTC+1, Jean-Luc Pinardon a écrit :
>>
>> Dear all,
>>
>> I am new to vagrant and ansible, and I am currently making some trials.
>> My host environment is a WIndows 7 machine (sorry) with cygwin64.
>> Ansible and Vagrant are both installed :
>> $ ansible --version  &&  vagrant --version
>> ansible 2.4.2.0
>>   config file = None
>>   configured module search path = ['/home/jeanlupi/.ansible/plug
>> ins/modules', '/usr/share/ansible/plugins/modules']
>>   ansible python module location = /usr/lib/python3.6/site-packages/
>> ansible
>>   executable location = /usr/bin/ansible
>>   python version = 3.6.3 (default, Oct 31 2017, 19:00:36) [GCC 6.4.0]
>> Vagrant 2.0.1
>>
>>
>> At the moment, I know how to create a Vagrantfile, have a brand new VM
>> automatically created with Vagrant, and access it through ssh.
>> Also, I succeed in using an ansible playbook to provision this new VM.
>> So, each vagrant and ansible can run correctly when launched one by one.
>>
>> Now, I want to make it to work together using config.vm.provider. But it
>> fails with the following trace :
>>  INFO provision: Writing provisioning sentinel so we don't provision
>> again
>>  INFO interface: info: Running provisioner: ansible...
>>  INFO interface: info: ==> default: Running provisioner: ansible...
>> ==> default: Running provisioner: ansible...
>>  INFO environment: Running hook: provisioner_run
>>  INFO runner: Preparing hooks for middleware sequence...
>>  INFO runner: 1 hooks defined.
>>  INFO runner: Running action: provisioner_run #> Vagrant::Action::Builtin::Provision#run_provisioner>
>>  INFO warden: Calling IN action: #> ashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/action/warden.rb:94
>> (lambda)>
>>  INFO subprocess: Starting process: ["C:/Program
>> Files/Oracle/VirtualBox/VBoxManage.exe", "showvminfo",
>> "2ace896f-293d-442b-9c62-bb8281960435", "--machinereadable"]
>>  INFO subprocess: Command not in installer, restoring original
>> environment...
>>  INFO subprocess: Starting process: ["C:/Program
>> Files/Oracle/VirtualBox/VBoxManage.exe", "showvminfo",
>> "2ace896f-293d-442b-9c62-bb8281960435", "--machinereadable"]
>>  INFO subprocess: Command not in installer, restoring original
>> environment...
>>  INFO interface: warn: Windows is not officially supported for the
>> Ansible Control Machine.
>> Please check https://docs.ansible.com/intro_installation.html#control-
>> machine-requirements
>>
>> Windows is not officially supported for the Ansible Control Machine.
>> Please check https://docs.ansible.com/intro_installation.html#control-
>> machine-requirements
>> ERROR ansible_host: Error while gathering the ansible version: The
>> Ansible software could not be found! Please verify
>> that Ansible is correctly installed on your host system.
>>
>> *So, it incorrectly says that "The Ansible software could not be found!*",
>> and I don't clearly understand why it claims that "Windows is not
>> officially supported for the Ansible Control Machine", though ansible
>> clearly runs correctly.
>>
>> For information :
>> The Vagrantfile is :
>> Vagrant.configure(2) do |config|
>>   config.vm.box = "geerlingguy/centos7"
>>   config.vm.network "forwarded_port", guest: 8080, host: 8080
>>   config.vm.synced_folder "../", "/var/data",create: true
>>   config.vm.provider "virtualbox" do |v|
>> # Add a name
>> v.name="CI_Env"
>> # Add enough memory
>> v.memory = 4048
>>   end
>>   config.vm.provision :ansible do |ansible|
>> ansible.playbook="../ansible/configure-ci-server.yml"
>> ansible.tags=["geerlingguy.java","git"]
>>   end
>> end
>>
>> And the directory tree is :
>> $ tree -d -L 3 .
>> .
>> ├── ansible
>> │   └── roles
>> │   ├── geerlingguy.java
>> │   ├── geerlingguy.jenkins
>> │   ├── git
>> │   └── LTS-2_89.jenkins
>> ├── doc
>> ├── etc
>> ├── tools
>> ├── Vagrant
>>
>>
>> Thanks in advance for your help.
>> Best Regards
>> J-L
>>
>> --
> 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: 

Re: [vagrant-up] vagrant and ansible provisionning fails with INFO interface: error: The Ansible software could not be found! Please verify that Ansible is correctly installed on your host system.

[Alvaro Miranda Aguilera]

can you put this into a github repo and share?


On Thu, Jan 11, 2018 at 11:33 AM, Jean-Luc Pinardon 
wrote:

> Dear all,
>
> I am new to vagrant and ansible, and I am currently making some trials.
> My host environment is a WIndows 7 machine (sorry) with cygwin64.
> Ansible and Vagrant are both installed :
> $ ansible --version  &&  vagrant --version
> ansible 2.4.2.0
>   config file = None
>   configured module search path = ['/home/jeanlupi/.ansible/
> plugins/modules', '/usr/share/ansible/plugins/modules']
>   ansible python module location = /usr/lib/python3.6/site-packages/
> ansible
>   executable location = /usr/bin/ansible
>   python version = 3.6.3 (default, Oct 31 2017, 19:00:36) [GCC 6.4.0]
> Vagrant 2.0.1
>
>
> At the moment, I know how to create a Vagrantfile, have a brand new VM
> automatically created with Vagrant, and access it through ssh.
> Also, I succeed in using an ansible playbook to provision this new VM.
> So, each vagrant and ansible can run correctly when launched one by one.
>
> Now, I want to make it to work together using config.vm.provider. But it
> fails with the following trace :
>  INFO provision: Writing provisioning sentinel so we don't provision again
>  INFO interface: info: Running provisioner: ansible...
>  INFO interface: info: ==> default: Running provisioner: ansible...
> ==> default: Running provisioner: ansible...
>  INFO environment: Running hook: provisioner_run
>  INFO runner: Preparing hooks for middleware sequence...
>  INFO runner: 1 hooks defined.
>  INFO runner: Running action: provisioner_run # Vagrant::Action::Builtin::Provision#run_provisioner>
>  INFO warden: Calling IN action: # HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/action/warden.rb:94
> (lambda)>
>  INFO subprocess: Starting process: ["C:/Program 
> Files/Oracle/VirtualBox/VBoxManage.exe",
> "showvminfo", "2ace896f-293d-442b-9c62-bb8281960435", "--machinereadable"]
>  INFO subprocess: Command not in installer, restoring original
> environment...
>  INFO subprocess: Starting process: ["C:/Program 
> Files/Oracle/VirtualBox/VBoxManage.exe",
> "showvminfo", "2ace896f-293d-442b-9c62-bb8281960435", "--machinereadable"]
>  INFO subprocess: Command not in installer, restoring original
> environment...
>  INFO interface: warn: Windows is not officially supported for the Ansible
> Control Machine.
> Please check https://docs.ansible.com/intro_installation.html#
> control-machine-requirements
>
> Windows is not officially supported for the Ansible Control Machine.
> Please check https://docs.ansible.com/intro_installation.html#
> control-machine-requirements
> ERROR ansible_host: Error while gathering the ansible version: The Ansible
> software could not be found! Please verify
> that Ansible is correctly installed on your host system.
>
> *So, it incorrectly says that "The Ansible software could not be found!*",
> and I don't clearly understand why it claims that "Windows is not
> officially supported for the Ansible Control Machine", though ansible
> clearly runs correctly.
>
> For information :
> The Vagrantfile is :
> Vagrant.configure(2) do |config|
>   config.vm.box = "geerlingguy/centos7"
>   config.vm.network "forwarded_port", guest: 8080, host: 8080
>   config.vm.synced_folder "../", "/var/data",create: true
>   config.vm.provider "virtualbox" do |v|
> # Add a name
> v.name="CI_Env"
> # Add enough memory
> v.memory = 4048
>   end
>   config.vm.provision :ansible do |ansible|
> ansible.playbook="../ansible/configure-ci-server.yml"
> ansible.tags=["geerlingguy.java","git"]
>   end
> end
>
> And the directory tree is :
> $ tree -d -L 3 .
> .
> ├── ansible
> │   └── roles
> │   ├── geerlingguy.java
> │   ├── geerlingguy.jenkins
> │   ├── git
> │   └── LTS-2_89.jenkins
> ├── doc
> ├── etc
> ├── tools
> ├── Vagrant
>
>
> Thanks in advance for your help.
> Best Regards
> J-L
>
> --
> 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/37104476-637e-4190-9ad2-f603509b96b7%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Alvaro

-- 
This mailing list is governed under the HashiCorp Community Guidelines - 

Re: [vagrant-up] Can't get Vagrant Up

[Alvaro Miranda Aguilera]

hello

Vagrant is working fine.

upto here:

default: Configuring and enabling network interfaces...
==> default: Mounting shared folders...
default: /var/www => /Users/johnnyrains/Sites/phptutorial
==> default: Running provisioner: shell...



>From there the project you are using is doing things (running scripts)
that are breaking stuff


so, if you do


mkdir precise64

cd precise64

vagrant init -m hashicorp/precise64

vagrant up


your will notice it works.


I would suggest contact the person who handed that project to you and
get some support from there.


Alvaro.


On Mon, Jan 8, 2018 at 7:52 PM, John Ullyatt  wrote:

> Hi Antony
>
> Mac OSX High Sierra
>
> I am using the installer pkg from the dmg
>
> and here is a txt file of my errors:
>
> On Monday, January 8, 2018 at 3:08:29 AM UTC-7, Antony Stone wrote:
>>
>> On Monday 08 January 2018 at 03:20:20, John Ullyatt wrote:
>>
>> > I've installed and uninstalled Vagrant so many times, and I cannot get
>> this
>> > to work.  I have looked through this group, and I also cannot find the
>> > answer I am looking for.
>>
>> Well, at least tell us:
>>
>> a) which operating system you are trying to get this working on
>>
>> b) how you are installing Vagrant
>>
>> c) what goes wrong - show us some error messages.
>>
>>
>> Antony.
>>
>> --
>> "It would appear we have reached the limits of what it is possible to
>> achieve
>> with computer technology, although one should be careful with such
>> statements;
>> they tend to sound pretty silly in five years."
>>
>>  - John von Neumann (1949)
>>
>>Please reply to the
>> list;
>>  please *don't*
>> CC me.
>>
> --
> 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/8b065024-aea6-4a92-a335-18954aa41d40%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/CAHqq0ewap%3D6cxzz1vb-bX%2BQvo2TFQNUBE1cU7Z%2BsGEjU%2B_5WWg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] Vagrantfile: loop around shell

[Alvaro Miranda Aguilera]

Hello!

yes its confusing but not hard.


This is what your provision did:


*==> omg02: Running provisioner: shell...*

omg02: Running: inline script

omg02: hi

*==> omg02: Running provisioner: shell...*

omg02: Running: inline script

omg02: hi

*==> omg02: Running provisioner: shell...*

omg02: Running: inline script

omg02: hi

The reason is because vagrant is read top to bottom , outside to inside.

So you got a config 3 times.
The fix is to rename it to subconfig like all in that block.

So, I did update a bit and now:


*==> foo02: Running provisioner: shell...*

foo02: Running: inline script

foo02: stdin: is not a tty

foo02: hi

*==> bar02: Running provisioner: shell...*

bar02: Running: inline script

bar02: stdin: is not a tty

bar02: hi

*==> omg02: Running provisioner: shell...*

omg02: Running: inline script

omg02: stdin: is not a tty

omg02: hi

What I did change:

subconfig.vm.provision "shell", inline: <<-SHELL
echo hi
#/opt/puppetlabs/bin/puppet resource service puppet
ensure=running enable=true
SHELL

same for virtualbox if you want to apply all that to every subconfig

there is one nice thing is you can create a variable at define level like
this:
config.vm.define vm_name = "#{i}" do |subconfig|

and then you can use vm_name in that code

the whole thing now:

#BOX_IMAGE = "centos7-2018010301"
BOX_IMAGE = "hashicorp/precise64"

#ENV["BRIDGE"] = "eno1"
ENV["BRIDGE"] = "en0: Wi-Fi (AirPort)"

systems = {
'foo02' => '',
'bar02' => '',
'omg02' => '',
}

Vagrant.configure("2") do |config|
systems.each do |i,x|
config.vm.define vm_name = "#{i}" do |subconfig|
subconfig.vm.box = BOX_IMAGE
subconfig.ssh.username = "vagrant"
#subconfig.ssh.password = "lulz"
subconfig.vm.hostname = "#{i}"
subconfig.vm.network :public_network, auto_config: false,
bridge: "#{ENV['BRIDGE']}"
subconfig.vm.provision "shell", inline: <<-SHELL
echo hi from #{vm_name}
#/opt/puppetlabs/bin/puppet resource service puppet
ensure=running enable=true
SHELL
subconfig.vm.provider "virtualbox" do |v|
v.name = vm_name
v.customize ["modifyvm", :id, "--paravirtprovider", "kvm"]
v.customize ["modifyvm", :id, "--autostart-enabled", "on"]
end
end
end
end


Enjoy!
Alvaro


On Thu, Jan 4, 2018 at 10:46 PM, Kevin Kruzich  wrote:

>
> I have the Vagrantfile below. It may look funny but it gets the job done.
> I'm concerned about repeated runs of the provisioner.
>
> For the first host, foo02, this will print once. For bar02, it prints
> twice. For omg02, it prints thrice... and so forth
>
> ==> omg02: Running provisioner: shell...
> omg02: Running: inline script
> [ ... ]
>
>
> I realize this is probably due to the placement of 'config.vm.provision'
> but after moving it around a few places, the Vagrantfile either won't
> validate or there's some subsequent error.
>
> Can you help me understand the logic here and how the structure might be
> improved.
>
>
> BOX_IMAGE = "centos7-2018010301"
> ENV["BRIDGE"] = "eno1"
>
>
> systems = {
> 'foo02' => '',
> 'bar02' => '',
> 'omg02' => '',
> }
>
>
> Vagrant.configure("2") do |config|
>  systems.each do |i,x|
> config.vm.define "#{i}" do |subconfig|
>   subconfig.vm.box = BOX_IMAGE
>   subconfig.ssh.username = "vagrant"
>   subconfig.ssh.password = "lulz"
>   subconfig.vm.hostname = "#{i}"
>   subconfig.vm.network :public_network, auto_config: false, bridge:
> "#{ENV['BRIDGE']}"
> config.vm.provision "shell", inline: <<-SHELL
>  /opt/puppetlabs/bin/puppet resource service puppet ensure=running
> enable=true
> SHELL
>config.vm.provider "virtualbox" do |v|
>  v.name = "#{i}"
>  v.customize ["modifyvm", :id, "--paravirtprovider", "kvm"]
>  v.customize ["modifyvm", :id, "--autostart-enabled", "on"]
>end
> end
>  end
> end
>
> --
> 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/13ef6f00-01de-402b-8512-b32650c12778%40googlegroups.com
> 

Re: [vagrant-up] Re: Free IPA installation in vagrant

[Alvaro Miranda Aguilera]

hello

you can do this:

vagrant halt

then using virtualbox gui, turn the machine on

from there the machine will be 100% outside vagrant

if you came back with a list of requirements like scripts and ports to
forward we can help you to put those in the vagrantfile

but is out of the scope of the tool how to  things

hope you understand

Alvaro.

On Wed, Jan 3, 2018 at 10:03 AM,  wrote:

> i have successfully installed Free IPA but unable to access it in web gui
> when i try to add exception it shows unable to obtain identification status
> for this site.
>
> can you please help me
>
> my installation procedure was in vagrant (centos in that freeipa)
>
>
> On Wednesday, January 3, 2018 at 10:40:07 AM UTC+5:30, rang...@gmail.com
> wrote:
>>
>> Dear Team,
>>
>> Well need your humble guidance in order to install Free IPA in vagrant
>> and access its web GUI
>>
>> thank you
>>
> --
> 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/f6bf1b1a-b272-4004-be6e-b4f05f220a35%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/CAHqq0ewHaYce9fkDV9zAJB4H%2Bxpk5uze7nq%2BeTGCKAEP_0em5g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] ERR_CONNECTION_REFUSED: I think NFS based, possibly ...

[Alvaro Miranda Aguilera]

hello!

Sure thing, not a problem.

If you need any other help, just share it here

:)

Alvaro


On Wed, Jan 3, 2018 at 12:58 AM, Ian Robert Douglas <
ian.robert.doug...@gmail.com> wrote:

> LOL.
>
> That was it! Thank you, Alvaro!
>
> I had tried Safari, but now that I look more closely, it does the same
> thing as Chrome.
>
> Firefox works.
>
>
>
> On Jan 3, 2018, at 1:46 AM, Alvaro Miranda Aguilera <kiki...@gmail.com>
> wrote:
>
> google chrome forces https for .dev now
>
> site1.dev refused to connect.
> ERR_CONNECTION_REFUSED
>
> try other browser or other domain
>
> alvaro
>
> On Tue, Jan 2, 2018 at 11:36 PM, Ian Robert Douglas <
> ian.robert.doug...@gmail.com> wrote:
>
>> Hi,
>>
>> Need some help. I’m very poor with code.
>>
>> Something has gone wrong with my Vagrant-based Wordpress installs.
>>
>> I think it’s NFS based, but I’m not sure.
>>
>> Vagrant 2.0.1
>> Virtualbox 5.1.30
>> Macos High Sierra
>>
>>
>> Everything was working fine the last time I checked (I don’t do web
>> development work often).
>>
>> Meanwhile, I don’t know if this is relevant, but it may be:
>>
>> 1. Trying to set a home network so my kids can watch movies on their
>> iPads, I found only NFS would work to share movies via WIFI. SMB was
>> failing, for some reason.
>> 2. Part of this was installing a preferences pane that allowed for NFS
>> sharing of specific folders.
>>
>> When I tried vagrant up on one of my installs, I got a series of errors
>> reporting that my exports file contained entires to unmounted drives (these
>> were the movies drives I had earlier shared via NFS, that the preferences
>> pane had basically written to the exports file).
>>
>> As Vagrant is for the moment more important than movies (sorry, kids), I
>> disabled the preferences pane and manually emptied my exports file.
>>
>> Vagrant up no longer reported errors, but still couldn’t connect via my
>> browser:
>>
>> This site can’t be reached
>> site1.dev refused to connect.
>> ERR_CONNECTION_REFUSED
>>
>>
>> But I can ping the site.
>> And I can SSH into the VM
>>
>> I tried restarting Apache in the VM. No difference.
>> I tried flushing my DNS cache. No difference.
>> I turned file sharing off in my System preferences (I’d been using it for
>> sharing the movies). No difference.
>> Tried rebooting my machine. No difference.
>>
>>
>> After vagrant up I can see that my hosts file contains the right entry
>> for the vagrant install.
>> I checked my vagrantfile, which anyway hasn’t changed since I last had
>> the site up and running.
>> The exports file contains the right info, so far as I can tell.
>>
>>
>> So I’m out of ideas. But at present, I cannot access any of my vagrant
>> installs.
>>
>> I tried vagrant destroy followed by vagrant up. No difference.
>>
>> On vagrant up I get the usual Guest Additions errors, but I think it’s
>> not critical.
>>
>> Something else is not working.
>>
>>
>> I’d be so grateful if anyone with more expertise than I have can point me
>> in the right direction to a fix.
>>
>>
>> best wishes,
>> ian
>>
>> --
>> 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/ms
>> gid/vagrant-up/4F3DABE9-584D-484A-A3C0-44C1459B81D4%40gmail.com
>> <https://groups.google.com/d/msgid/vagrant-up/4F3DABE9-584D-484A-A3C0-44C1459B81D4%40gmail.com?utm_medium=email_source=footer>
>> .
>> 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/issue

Re: [vagrant-up] Free IPA installation in vagrant

[Alvaro Miranda Aguilera]

Hello

What you have tried and what questions you got?

if you are new to Vagrant, perhaps :
https://www.vagrantup.com/intro/getting-started/index.html

Thanks
Alvaro

On Wed, Jan 3, 2018 at 6:10 AM,  wrote:

> Dear Team,
>
> Well need your humble guidance in order to install Free IPA in vagrant and
> access its web GUI
>
> thank you
>
> --
> 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/f36fb60a-7116-4765-b08e-71e531fedac0%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/CAHqq0eyWozVb8z3dgpyJ9MQkZRmhWq-2qMRpG5j6-V111RUqjw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] NS_ERROR_FAILURE issue on MacOS High Sierra

[Alvaro Miranda Aguilera]

it seems not a vagrant issue

virtualbox forums like this:
https://forums.virtualbox.org/viewtopic.php?f=8=79515

blame things like external drivers no properly removed, or mac os upgrade
after virtualbox isntalls (?) and people try reboots / reinstalls

have the virtualbox removed and reinstalled here ?

alvaro

On Tue, Jan 2, 2018 at 11:20 PM, Ryan Langley  wrote:

> Hi Everyone,
>
> I'm having a strange issue with Vagrant + VBox on MacOS High Sierra.  I've
> created a custom Vagrant box for my team, and it works fine on Win10 and
> MacOS Sierra hosts.  However, one of my team members is on a newer Mac Pro
> laptop with MacOs High Sierra, and we get the following error when doing
> the same setup as the other hosts after "vagrant up":
>
> There was an error while executing `VBoxManage`, a CLI used by Vagrant
> for controlling VirtualBox. The command and stderr is shown below.
>
> Command: ["startvm", "a3c41dcb-841b-4395-9a04-28c50eea6781", "--type",
> "headless"]
>
> Stderr: VBoxManage: error: The virtual machine 'Vagrant_default_
> 1513972955067_49566' has terminated unexpectedly during startup with exit
> code 1 (0x1)
> VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component
> MachineWrap, interface IMachine
>
> This error gives very little to go on.  I've researched it for a few days
> via Google, and have tried multiple suggested fixes like vboxdrv setup,
> setting DISPLAY env var, verifying host-only network settings, removing and
> reinstalling vagrant and virtual box, removing ~/.vagrant.d and .vagrant,
> etc.  Everything gives the same error as above.  It does not even get to a
> point where it will create a vbox log file.
>
> One small glimmer of the issue is if I manually run:
>
> $ VBoxHeadless -s "vagrant_default"
>
> The VBox VM starts up as expected, however if I manually run:
>
> $ VBoxManage startvm "vagrant_default" --type headless
>
> The VBox VM fails to start with the same error as above.  Has anyone seen
> this issue before?  Is there a way to force vagrant to use VBoxHeadless
> instead of VBoxManage?
>
> Vagrant Version: 2.0.1
> VirtualBox Version: 5.2.4
>
> Any thoughts would be appreciated, I'm not sure what else to do at this
> point!
>
> Thanks,
>  - Ryan Langley
>
> --
> 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/6c664f00-2cd1-49d5-a7ea-42c424a7367e%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/CAHqq0exsAjW3qRVF%2BJh8YVfoSF1MDJHx2Ay-3wrvWWMNRx5Lrg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] ERR_CONNECTION_REFUSED: I think NFS based, possibly ...

[Alvaro Miranda Aguilera]

google chrome forces https for .dev now

site1.dev refused to connect.
ERR_CONNECTION_REFUSED

try other browser or other domain

alvaro

On Tue, Jan 2, 2018 at 11:36 PM, Ian Robert Douglas <
ian.robert.doug...@gmail.com> wrote:

> Hi,
>
> Need some help. I’m very poor with code.
>
> Something has gone wrong with my Vagrant-based Wordpress installs.
>
> I think it’s NFS based, but I’m not sure.
>
> Vagrant 2.0.1
> Virtualbox 5.1.30
> Macos High Sierra
>
>
> Everything was working fine the last time I checked (I don’t do web
> development work often).
>
> Meanwhile, I don’t know if this is relevant, but it may be:
>
> 1. Trying to set a home network so my kids can watch movies on their
> iPads, I found only NFS would work to share movies via WIFI. SMB was
> failing, for some reason.
> 2. Part of this was installing a preferences pane that allowed for NFS
> sharing of specific folders.
>
> When I tried vagrant up on one of my installs, I got a series of errors
> reporting that my exports file contained entires to unmounted drives (these
> were the movies drives I had earlier shared via NFS, that the preferences
> pane had basically written to the exports file).
>
> As Vagrant is for the moment more important than movies (sorry, kids), I
> disabled the preferences pane and manually emptied my exports file.
>
> Vagrant up no longer reported errors, but still couldn’t connect via my
> browser:
>
> This site can’t be reached
> site1.dev refused to connect.
> ERR_CONNECTION_REFUSED
>
>
> But I can ping the site.
> And I can SSH into the VM
>
> I tried restarting Apache in the VM. No difference.
> I tried flushing my DNS cache. No difference.
> I turned file sharing off in my System preferences (I’d been using it for
> sharing the movies). No difference.
> Tried rebooting my machine. No difference.
>
>
> After vagrant up I can see that my hosts file contains the right entry for
> the vagrant install.
> I checked my vagrantfile, which anyway hasn’t changed since I last had the
> site up and running.
> The exports file contains the right info, so far as I can tell.
>
>
> So I’m out of ideas. But at present, I cannot access any of my vagrant
> installs.
>
> I tried vagrant destroy followed by vagrant up. No difference.
>
> On vagrant up I get the usual Guest Additions errors, but I think it’s not
> critical.
>
> Something else is not working.
>
>
> I’d be so grateful if anyone with more expertise than I have can point me
> in the right direction to a fix.
>
>
> best wishes,
> ian
>
> --
> 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/4F3DABE9-584D-484A-A3C0-44C1459B81D4%40gmail.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/CAHqq0ey5VQR7ZGiYxmCozq24cZWyZfhrR8rxsbfrL27uMFRSGQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] Laravel / Homestead Proble

[Alvaro Miranda Aguilera]

hello

can you add --debug and try again ?

Please share a gist (gist.github.com) of the log

On Sun, Dec 31, 2017 at 6:07 PM, Rob Johnson 
wrote:

> Hi, I've seen several reference to this problem over the web but nothing
> that actually solves it.  Have installed Vagrant 2.0.1 (but have tried
> downgrading to solve the problem - no dice).  VirtualBox installed and
> seemingly OK:  Any vanguard command solicits the following.
>
> Don't know it seems obsessed with Ruby - I'm trying to install this - nor
> do I want it.  But I do want Laravel Homestead !  Can any one help - I'm
> pretty much stuck here.  fyi, I'm running W10 and accessing the Vagrant via
> Git Bash.
>
> Thanks
> Rob.
>
> rtjoh@XPS13 MINGW64 ~/Desktop
> $ vagrant box add laravel/homestead
> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/util/platform.rb:207:
> [BUG] Segmentation fault
> ruby 2.4.2p198 (2017-09-14 revision 59899) [x64-mingw32]
>
> -- Control frame information --
> -
> c:0009 p: s:0049 e:48 CFUNC  :open
> c:0008 p: s:0046 e:45 CFUNC  :entries
> c:0007 p:0016 s:0041 e:40 BLOCK  C:/HashiCorp/Vagrant/embedded/
> gems/gems/vagrant-2.0.1/lib/vagrant/util/platform.rb:207 [FINISH]
> c:0006 p: s:0037 e:36 CFUNC  :each
> c:0005 p:0163 s:0033 e:32 METHOD C:/HashiCorp/Vagrant/embedded/
> gems/gems/vagrant-2.0.1/lib/vagrant/util/platform.rb:206
> c:0004 p:0515 s:0026 e:25 METHOD C:/HashiCorp/Vagrant/embedded/
> gems/gems/vagrant-2.0.1/lib/vagrant/environment.rb:121 [FINISH]
> c:0003 p: s:0020 e:19 CFUNC  :new
> c:0002 p:0678 s:0015 E:000648 EVAL   C:/HashiCorp/Vagrant/
> embedded/gems/gems/vagrant-2.0.1/bin/vagrant:118 [FINISH]
> c:0001 p: s:0003 E:002570 (none) [FINISH]
>
> -- Ruby level backtrace information --
> --
> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/bin/vagrant:118:in
> `'
> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/bin/vagrant:118:in
> `new'
> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/environment.rb:121:in
> `initialize'
> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/
> vagrant/util/platform.rb:206:in `fs_real_path'
> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/
> vagrant/util/platform.rb:206:in `each'
> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/
> vagrant/util/platform.rb:207:in `block in fs_real_path'
> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/
> vagrant/util/platform.rb:207:in `entries'
> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/
> vagrant/util/platform.rb:207:in `open'
>
> -- C level backtrace information --
> -
> C:\WINDOWS\SYSTEM32\ntdll.dll(NtWaitForSingleObject+0x14)
> [0x7ffef227fec4]
> C:\WINDOWS\System32\KERNELBASE.dll(WaitForSingleObjectEx+0x9f)
> [0x7ffeee913b2f]
> C:\HashiCorp\Vagrant\embedded\mingw64\bin\x64-msvcrt-ruby240.dll(rb_print_backtrace+0x36)
> [0x67b02996]
> C:\HashiCorp\Vagrant\embedded\mingw64\bin\x64-msvcrt-
> ruby240.dll(rb_vm_bugreport+0x67) [0x67b02a07]
> C:\HashiCorp\Vagrant\embedded\mingw64\bin\x64-msvcrt-
> ruby240.dll(rb_bug_context+0x69) [0x679dda29]
> C:\HashiCorp\Vagrant\embedded\mingw64\bin\x64-msvcrt-
> ruby240.dll(rb_check_safe_obj+0x6cc) [0x67a9840c]
>  [0x00402388]
> C:\WINDOWS\SYSTEM32\ntdll.dll(_C_specific_handler+0x96)
> [0x7ffef2270f56]
> C:\WINDOWS\SYSTEM32\ntdll.dll(_chkstk+0x11d) [0x7ffef2284c3d]
> C:\WINDOWS\SYSTEM32\ntdll.dll(RtlWalkFrameChain+0x1518)
> [0x7ffef21fd1b8]
> C:\WINDOWS\SYSTEM32\ntdll.dll(KiUserExceptionDispatcher+0x2e)
> [0x7ffef2283b6e]
> C:\WINDOWS\System32\msvcrt.dll(memcmp+0x30) [0x7ffeef94b830]
> C:\HashiCorp\Vagrant\embedded\mingw64\bin\x64-msvcrt-
> ruby240.dll(rb_w32_read_reparse_point+0xfa) [0x67b1134a]
> C:\HashiCorp\Vagrant\embedded\mingw64\bin\x64-msvcrt-
> ruby240.dll(rb_w32_reparse_symlink_p+0x37) [0x67b11477]
> C:\HashiCorp\Vagrant\embedded\mingw64\bin\x64-msvcrt-
> ruby240.dll(rb_w32_reparse_symlink_p+0xafc) [0x67b11f3c]
> C:\HashiCorp\Vagrant\embedded\mingw64\bin\x64-msvcrt-
> ruby240.dll(rb_w32_uopendir+0x2c) [0x67b1205c]
> C:\HashiCorp\Vagrant\embedded\mingw64\bin\x64-msvcrt-
> ruby240.dll(ruby_set_debug_option+0x1d24) [0x679cb524]
> C:\HashiCorp\Vagrant\embedded\mingw64\bin\x64-msvcrt-
> ruby240.dll(ruby_set_debug_option+0x1e30) [0x679cb630]
> C:\HashiCorp\Vagrant\embedded\mingw64\bin\x64-msvcrt-
> ruby240.dll(rb_vm_invoke_proc+0x12b4) [0x67af73a4]
> C:\HashiCorp\Vagrant\embedded\mingw64\bin\x64-msvcrt-
> ruby240.dll(rb_check_funcall_with_hook+0xb67) [0x67af8fc7]
> C:\HashiCorp\Vagrant\embedded\mingw64\bin\x64-msvcrt-ruby240.dll(rb_funcallv+0x25)
> [0x67af9815]
> C:\HashiCorp\Vagrant\embedded\mingw64\bin\x64-msvcrt-
> ruby240.dll(ruby_set_debug_option+0x1b11) 

Re: [vagrant-up] Vendors supporting startup of multiple machines in parallel in Vagrant multi-machine environments

[Alvaro Miranda Aguilera]

Currently seems only docker.

Alvaro

On Thu, Dec 28, 2017 at 8:07 AM, Chiranga Alwis 
wrote:

> Which vendors support startup of multiple machines in parallel, in a
> multi-machine  environment
> when using Vagrant? It is known that Oracle VM VirtualBox does not support
> it, from here
> .
>
> --
> 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/cc150670-e715-4459-9217-763690078bcb%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/CAHqq0ewT0QiHVYn-87i6iUp7j0Bd%2BhKGDbByUMYo47dH0pPhAw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] Could not start Vagrant 2.0.1

[Alvaro Miranda Aguilera]

hello

very ugly error.

Whats your host OS ?

32 bit? 64 bit?

Can you un-install, and try 2.0.0 ?

Alvaro

On Tue, Dec 26, 2017 at 2:37 PM, Evgeny Alexandrovich <
evg...@alexandrovich.com> wrote:

> c:\m036>vagrant up
> C:/Program Files/HashiCorp/Vagrant/embedded/gems/gems/vagrant-
> share-1.1.9/lib/vagrant-share.rb:10: [BUG] Segmentation fault
> ruby 2.4.2p198 (2017-09-14 revision 59899) [i386-mingw32]
>
> -- Control frame information --
> -
> c:0013 p:0037 s:0088 e:87 TOPC:/Program Files/HashiCorp/Vagrant/
> embedded/gems/gems/vagrant-share-1.1.9/lib/vagrant-share.rb:10 [FINISH]
> c:0012 p: s:0085 e:84 CFUNC  :RGLoader_load
> c:0011 p:0207 s:0080 e:79 TOPC:/Program Files/HashiCorp/Vagrant/
> embedded/gems/gems/vagrant-share-1.1.9/lib/vagrant-share.rb:16 [FINISH]
> c:0010 p: s:0073 e:72 CFUNC  :require
> c:0009 p:0132 s:0068 e:67 METHOD C:/Program Files/HashiCorp/Vagrant/
> embedded/mingw32/lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55
> c:0008 p:0050 s:0056 e:55 BLOCK  C:/Program Files/HashiCorp/Vagrant/
> embedded/gems/gems/vagrant-2.0.1/lib/vagrant.rb:314 [FINISH]
> c:0007 p: s:0049 e:48 CFUNC  :each
> c:0006 p:0695 s:0045 E:0001e8 TOPC:/Program Files/HashiCorp/Vagrant/
> embedded/gems/gems/vagrant-2.0.1/lib/vagrant.rb:310 [FINISH]
> c:0005 p: s:0036 e:35 CFUNC  :require
> c:0004 p:0103 s:0031 e:30 RESCUE C:/Program Files/HashiCorp/Vagrant/
> embedded/mingw32/lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:133
> c:0003 p:0429 s:0027 e:26 METHOD C:/Program Files/HashiCorp/Vagrant/
> embedded/mingw32/lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:40
> c:0002 p:0241 s:0015 E:0026d4 EVAL   C:/Program Files/HashiCorp/Vagrant/
> embedded/gems/gems/vagrant-2.0.1/bin/vagrant:62 [FINISH]
> c:0001 p: s:0003 E:000580 (none) [FINISH]
>
> -- Ruby level backtrace information --
> --
> C:/Program 
> Files/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/bin/vagrant:62:in
> `'
> C:/Program Files/HashiCorp/Vagrant/embedded/mingw32/lib/ruby/2.4.
> 0/rubygems/core_ext/kernel_require.rb:40:in `require'
> C:/Program Files/HashiCorp/Vagrant/embedded/mingw32/lib/ruby/2.4.
> 0/rubygems/core_ext/kernel_require.rb:133:in `rescue in require'
> C:/Program Files/HashiCorp/Vagrant/embedded/mingw32/lib/ruby/2.4.
> 0/rubygems/core_ext/kernel_require.rb:133:in `require'
> C:/Program 
> Files/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant.rb:310:in
> `'
> C:/Program 
> Files/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant.rb:310:in
> `each'
> C:/Program 
> Files/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant.rb:314:in
> `block in '
> C:/Program Files/HashiCorp/Vagrant/embedded/mingw32/lib/ruby/2.4.
> 0/rubygems/core_ext/kernel_require.rb:55:in `require'
> C:/Program Files/HashiCorp/Vagrant/embedded/mingw32/lib/ruby/2.4.
> 0/rubygems/core_ext/kernel_require.rb:55:in `require'
> C:/Program Files/HashiCorp/Vagrant/embedded/gems/gems/vagrant-
> share-1.1.9/lib/vagrant-share.rb:16:in `'
> C:/Program Files/HashiCorp/Vagrant/embedded/gems/gems/vagrant-
> share-1.1.9/lib/vagrant-share.rb:16:in `RGLoader_load'
> C:/Program Files/HashiCorp/Vagrant/embedded/gems/gems/vagrant-
> share-1.1.9/lib/vagrant-share.rb:10:in `'
>
> -- C level backtrace information --
> -
> C:\Windows\SYSTEM32\ntdll.dll(KiFastSystemCallRet+0x0) [0x77ca6c74]
> C:\Windows\system32\kernel32.dll(WaitForSingleObjectEx+0x43) [0x76dbc533]
> C:\Windows\system32\kernel32.dll(WaitForSingleObject+0x12) [0x76dbc4e2]
> C:\Program Files\HashiCorp\Vagrant\embedded\mingw32\bin\msvcrt-
> ruby240.dll(rb_print_backtrace+0x40) [0x710f7e80]
> C:\Windows\SYSTEM32\ntdll.dll(EtwReplyNotification+0x366) [0x77cd793a]
>
> -- Other runtime information --
> -
>
> * Loaded script: C:/Program Files/HashiCorp/Vagrant/
> embedded/gems/gems/vagrant-2.0.1/bin/vagrant
>
> * Loaded features:
>
> 0 enumerator.so
> 1 thread.rb
> 2 rational.so
> 3 complex.so
> 4 C:/Program Files/HashiCorp/Vagrant/embedded/mingw32/lib/ruby/2.4.
> 0/i386-mingw32/enc/encdb.so
> 5 C:/Program Files/HashiCorp/Vagrant/embedded/mingw32/lib/ruby/2.4.
> 0/i386-mingw32/enc/trans/transdb.so
> 6 C:/Program Files/HashiCorp/Vagrant/embedded/mingw32/lib/ruby/2.4.
> 0/i386-mingw32/enc/iso_8859_8.so
> 7 C:/Program Files/HashiCorp/Vagrant/embedded/mingw32/lib/ruby/2.4.
> 0/unicode_normalize.rb
> 8 C:/Program Files/HashiCorp/Vagrant/embedded/mingw32/lib/ruby/2.4.
> 0/i386-mingw32/rbconfig.rb
> 9 C:/Program Files/HashiCorp/Vagrant/embedded/mingw32/lib/ruby/2.4.
> 0/rubygems/compatibility.rb
>10 C:/Program Files/HashiCorp/Vagrant/embedded/mingw32/lib/ruby/2.4.
> 0/rubygems/defaults.rb
>11 C:/Program Files/HashiCorp/Vagrant/embedded/mingw32/lib/ruby/2.4.
> 0/rubygems/deprecate.rb
>12 C:/Program 

Re: [vagrant-up] Understanding Vagrant disk space usage

[Alvaro Miranda Aguilera]

Hello

reply to 1. Open Virtualbox Settings, check the virtual machine directory,
you can change it.

then destroy and recreate will put the VM on the new path.

reply to 2.

dd with zeroes may not use much space, several layers are there that will
try to be smart. Filesystem, the Virtualbox disk, etc.

if you want to use space, you need to create files that are not zeroes, ie
put something big like an iso on on same directory of Vagrantfile, then on
the VM copy that multiples times.

Om the host the disk.vmdk will start growing if the VM start using it.


Vagrant is a tool that automate lots of things, but is good to know whats
happening under the hood, so please feel free to send all the questions you
have, and we will be more than happy to help.


Alvaro

On Mon, Dec 25, 2017 at 12:15 AM, Mohammed Ibrahim 
wrote:

> Hello,
> Just starting with Vagrant using the docs https://www.vagrantup.com,
> using Ubuntu server 16.04
> And now playing on my first box "hashicorp/precise64",
> Trying to understand the disk usage of vagrant:
>
> 1. Although i made a new partition for my 1st box, the new box is
> installed on "/root/VirtualBox VMs", how to change the destination of new
> box creation path?
>
> 2. I tried to create dummy sizes of 30 GB using "dd" on the box, but i
> didn't get where is that disk size located on the host server, as it is
> still the same for the host?!
>
> *disk sizes on box:*
> Filesystem   Size  Used Avail Use% Mounted on
> /dev/mapper/precise64-root   79G   32G   44G  43% /  *=> where is that
> disk usage located on the host server?*
> vagrant40G  2.1G   38G   6% /vagrant  *=>
> this is the host partition size of the vagrant box*
>
> *The .vmdk file size:*
> 1.3Gbox-disk1.vmdk
>
> Thanks in advance
>
> --
> 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/69c86747-f08b-4542-82b1-bb8f9a173a46%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/CAHqq0ez4tMka-dC1ihfJDTr%3DQg7%2BbbskyvRznaX1GB0Z%3DiawGw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] Re: How am I supposed to know which master VMs are not used (can be deleted?)

[Alvaro Miranda Aguilera]

what about checking Virtualbox gui?

Does that tells?

-- 
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/CAHqq0eysB_4%3DsxN1ZLyqeX%2BOpZEQgPVr1uJ8%3DUdM0LL3NHFkZA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] Error at vagrant up : Provider expected: vsphere while Provider of box: vmware_desktop

[Alvaro Miranda Aguilera]

check the documentation of the plugin, it wont take a local box

you need the dummy box and a source vm like this:

   # The template we're going to clone
#vsphere.template_name = 'ubuntu.template.dc.sw10.net'

Alvaro

On Fri, Dec 15, 2017 at 10:09 PM, cally725 via Vagrant <
vagrant-up@googlegroups.com> wrote:

> Hi,
>
> I am on Windows 10, with vmware workstation 14.0 installed, using packer
> 1.1.1 to build my box using type vmware.iso.
>
> My box gets created and complete with the following lines
>
> Build 'vmware-iso' finished.
> ==> Builds finished. The artifacts of successful builds are:
> --> vmware-iso: 'vmware' provider box: xtract-vmware-rhel-7.3.box
>
>
> When I try to do the vagrant up, using vagrant 1.9.6, I am getting the
> ERROR:
> Provider expected: vsphere
> Provider of box: vmware_desktop
>
> My vagrant file is:
> HOSTNAME = "exfo." + ENV['USERNAME'] + "-" + 
> File.basename(File.expand_path("..",
> Dir.pwd)).tr(" ", "").tr("_", "").tr(".", "")
> BOXNAME = "xtract-vmware-rhel-7.3"
> BOXURL = "file:///c:/Test/Xtract/Packer/xtract-rhel-esxi/" + BOXNAME +
> ".box"
> Vagrant.configure("2") do |config|
> config.ssh.insert_key = false
> config.vm.box = BOXNAME
> config.vm.box_url = BOXURL
> config.vm.network "public_network", ip: "xxx.xxx.xxx.xxx", netmask:
> "255.255.254.0", gateway: "xxx.xxx.xxx.xxx"
> config.vm.synced_folder('.', '/Vagrant', type: 'rsync')
> config.vm.provider :vsphere  do |vsphere|
>
> # The host we're going to connect to
> vsphere.host = 'Vcenter01.xxx.com'
> # The host for the new VM
> vsphere.compute_resource_name = 'xxx.xxx.xxx.xxx'
> # The resource pool for the new VM
> vsphere.resource_pool_name = 'Shared'
> # The template we're going to clone
> #vsphere.template_name = 'ubuntu.template.dc.sw10.net'
> # The name of the new machine
> vsphere.name = 'myvm'
> # vSphere login
> vsphere.user = 'xx'
> # vSphere password
> vsphere.password = 'xx'
> # If you don't have SSL configured correctly, set this to 'true'
> vsphere.insecure = true
> end
>
> config.vm.provision "shell", path: "scripts/xtract-start.sh", run:
> 'always'
> end
>
> --
> 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/9e93e168-a9f1-4620-b7ee-4842fd897f31%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/CAHqq0eyC%3DkF7V_GJzLDOD9oE16KBGqg%2B75Snry-zMDo6G2ex5g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] So how to actually setup vagrant with vmware and wsl?

[Alvaro Miranda Aguilera]

Hello

WSL information is here:
https://www.vagrantup.com/docs/other/wsl.html

It should work for VirtualBox, and let you use Docker with a DOCKER_HOST

But WSL + VMWare is not yet listed in the page.

Thanks
Alvaro.

On Fri, Dec 15, 2017 at 3:09 PM, Georgi  wrote:

> Hello everybody,
> so, Im using Windows 10 (version 1709), wsl, vmware workstation and
> vagrant.
>
> Vagrant is setup on the Windows with the vmware workstation plugin
> licensed and everything works fine. For example:
>
> 
> C:\WINDOWS\system32>vagrant plugin list
> vagrant-share (1.1.9, system)
>   - Version Constraint: > 0
> vagrant-vmware-workstation (5.0.4)
>   - Version Constraint: > 0
> 
>
> The default provider is set to vmware_workstation
> (i.e VAGRANT_DEFAULT_PROVIDER=vmware_workstation).
>
> Now, I want to use vagrant on wsl, so that I can do ansible provisionings.
> Now the fun stuff begins. I've installed
> the debian package as per documentation and then added the env variable,
> so that vagrant has access to the native Windows System.
>
> I cannot simply invoke vagrant, I need to use sudo everytime, otherwise if
> I use debug I got the following output (snippet):
>
> 
> DEBUG subprocess: Exit status: 0
>  INFO subprocess: Starting process: 
> ["/mnt/c/HashiCorp/Vagrant/bin/vagrant.exe",
> "version"]
>  INFO subprocess: Command not in installer, restoring original
> environment...
> DEBUG subprocess: Selecting on IO
> DEBUG subprocess: stderr: Vagrant failed to initialize at a very early
> stage:
>
> Failed to invoke the VMware utility task.
>
>   Cause: ERROR: Access is denied.
>
> Please address the issue above and try again. If
> this problem persists, please contact supp...@hashicorp.com
> 
>
>
> If I try to start a machine, vagrant complains, that it cannot find a
> provider, even if I specify per hand one:
>
> 
> ~/vagrant_test$ sudo vagrant up --provider=vmware_workstation
> The provider 'vmware_workstation' could not be found, but was requested to
> back the machine 'default'. Please use a provider that exists.
> 
>
> If I install and license the vmware_workstation provider on wsl, the
> vagrant
> complains that it cannot find a vmware installation (which is actually
> correct).
>
>  Any idea what am I doing wrong? I suppose installing and licensing the
> vmware_workstation provider
> on Windows and not WSL should be sufficient, but this does not work
> currently.
>
> Thank you in advance.
>
> --
> 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/f3a60a6f-37c8-4426-b111-398f067e96f5%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/CAHqq0ezKtE_HN-tvxO1Et61zSuHqSDDvK%2BvszO%2BzLd%3D5u2x-vg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] SSL Certificate Problem When Downloading Box Behind Websense

[Alvaro Miranda Aguilera]

You can add your proxy into the local certs being used
Try setting the variable SSL_CERT_FILE to a file that includes your proxy
certificate.

Alvaro.


On Thu, Dec 14, 2017 at 2:44 PM, Alex Drawbond  wrote:

> Hello,
>
> I am trying to run:
> vagrant box update --box ubuntu/trusty64
>
> from a macOS machine running behind Websense. I am taking the following
> error:
>
> There was an error while downloading the metadata for this box.
> The error message is shown below:
> SSL certificate problem: unable to get local issuer certificate
> More details here: https://curl.haxx.se/docs/sslcerts.html
> curl performs SSL certificate verification by default, using a "bundle"
> of Certificate Authority (CA) public keys (CA certs). If the default
> bundle file isn't adequate, you can specify an alternate file using the
> --cacert option. If this HTTPS server uses a certificate signed by a CA
> represented in the bundle, the certificate verification probably failed due
> to a problem with the certificate (it might be expired, or the name might
> not match the domain name in the URL). If you'd like to turn off curl's
> verification of the certificate, use the -k (or --insecure) option.
> HTTPS-proxy has similar options --proxy-cacert and --proxy-insecure.
>
> We assume the issue is that Websense is terminating SSL, inspecting the
> traffic and then injecting it's own certificate before passing the traffic
> along. Websense's certificate isn't recognized by curl and rejected. Using
> the --insecure option does resolve the problem. I would prefer to not use
> --insecure, and adding Websense's cert to the list of trusted certs isn't
> an option either. What I can do is have IP's whitelisted in Websense so
> that their SSL isn't interfered with. I am having a hard time tracking down
> all the IP's Vagrant is hitting behind scenes, and was hoping there was
> some documentation somewhere detailing which IP's need to be whitelisted to
> work with Websense?
>
> Thanks,
> Alex
>
> --
> 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/7ccf979c-ab52-4486-a724-762faa5fcf9a%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/CAHqq0ex3rC6sgfbQaJ0qMxKA3PaO9dR9p6oWcNsrmgXJXXL7wA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] some times Vagrant is failed to synching share folders to guest VM

[Alvaro Miranda Aguilera]

Hello

vsphere plugin is not native to vagrant

can you open an issue on the plugin repo?

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/CAHqq0ewj-_5J_2WE3KCrLgMXfNn1NP8hErudpEoWX4tWzeAFAw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] some times Vagrant is failed to synching share folders to guest VM

[Alvaro Miranda Aguilera]

hello

the box does and the host have all the needed to use smb?

how to reproduce? your vagrantfile says dummy for box

Alvaro

On Thu, Dec 14, 2017 at 7:25 AM, ashok vaddevalli  wrote:

> Vagrant version
>
> 2.0.1
> Host operating system
>
> Windows 7
> Guest operating system
>
> Windows 7
> Vagrantfile
>
> -*- mode: ruby -*-
> vi: set ft=ruby :
>
> #Author: Ashok Vaddevalli
>
> Vagrant.configure("2") do |config|
>
> config.vm.box = 'dummy'
> config.vm.box_url = 'dummy.box'
>
> #config.vm.network "private_network", ip: ENV["ip"]
>
> config.vm.communicator = "winrm"
> config.winrm.username = "admin"
> config.winrm.password = "admin@123"
> config.winrm.timeout = 1800
> config.vm.boot_timeout = 600
>
> config.vm.synced_folder "./src", "/src", type: "smb", smb_username:
> "administrator", smb_password: "admin@123"
>
> config.vm.synced_folder "./Result", "/Result", type: "smb", smb_username:
> "administrator", smb_password: "admin@123"
>
> config.vm.synced_folder ".", "/vagrant", disabled: true
>
> config.vm.provider :vsphere do |vsphere|
> vsphere.host = 'X.X.X.X'
> #vsphere.customization_spec_name = 'Win7-Custom_template'
> vsphere.compute_resource_name = 'X.X.X.X'
> vsphere.data_center_name = 'Demo'
> vsphere.template_name = 'Templates/InstallerAutomation'
> vsphere.name = 'InstallerAuto'
> vsphere.user = 'administrator@vsphere.local'
> vsphere.password = ENV["vsphere.password"]
> vsphere.insecure = true
> end
>
> config.vm.provision "shell", inline: "C:/src/setupandrunautomation.bat"
>
> end
> Expected behavior
>
> ==> default: Waiting for machine to boot. This may take a few minutes...
> default: WinRM address: X.X.X.X:5985
> default: WinRM username: admin
> default: WinRM execution_time_limit: PT2H
> default: WinRM transport: negotiate
> ==> default: Machine booted and ready!
> ==> default: Preparing SMB shared folders...
> ==> default: Mounting SMB shared folders...
> default: C:/InstallerAutomation/src => /src
> default: C:/InstallerAutomation/Result => /Result
> ==> default: Running provisioner: shell...
> default: Running: inline PowerShell script
> default: 1 file(s) moved.
> Actual behavior
>
> ==> default: Mounting SMB shared folders...
> default: C:/InstallerAutomation/src => /src
> The following WinRM command responded with a non-zero exit status.
> Vagrant assumes that this means the command failed!
>
> cmdkey /add:X.X.X.X /user:administrator /pass:admin@123
>
> Stdout from the command:
>
> Stderr from the command:
> Steps to reproduce
>
>1. Re run Vagrant up second time, it was synchronizing share folders,
>sometimes u can re run vagrant up multiple times for share folders
>synchronization.
>
> I am facing share folders synchronization recent only, last ten builds i
> have not seen this issue.
>
> --
> 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/98d802cd-6924-477b-a890-53548804314e%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/CAHqq0extDa70t0PFa2TMC2P2-A2YsRCYCANE%3DCW8-3JzbZXxVg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] Vagrant doesnt seem to want to mount /

[Alvaro Miranda Aguilera]

the best will be contact the people who builds that box, or use a different
box.

Alvaro.

On Wed, Dec 13, 2017 at 11:16 PM, Matthew Jonat 
wrote:

> So I use the vagrant scotchboxI was working away on a website with it
> which just stops working all of a sudden but there's nor errors anywhere.
>
> I do some digging and end up looking at the boot sequence with
> VirtualMachine as it happens and it stops at one point and just says:
>
> An error occured while mounting /
> Press S to Skip or M for manual recovery.
>
> So I press M and the system just reboots...fine I'll choose to skip...I
> then get this error:
>
> The disk drive for /tmp is not ready or not yet preset.
>
> Then it gives the same options as before.
>
> There is an error that comes before the first error message:
>
> EXT-4-fs (sda1): Couldn't remount RDWR because of unprocessed orphan inode
> list. Please unmount/remount instead.
>
> Im not sure if this is the right place to askbut I hope someone can help :)
>
> Thanks!
>
> Matt
>
> --
> 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/42319b10-81c3-469e-a19d-16c1203020ef%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/CAHqq0eydFZs8njwhK6vYacg7HcnX2uU%2BmV0fbZ%3D%2B%3DNnR0YruBQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] vagrant on windows behind proxy

[Alvaro Miranda Aguilera]

you know the proxy url?

you can set the variables http_proxy and https_proxy to the proxy address


That is for the vagrant tool

then inside the guest you need to setup the proxy again if you want to have
access to internet

git may work if the protocol is over https, not sure over ssh

Alvaro

On Mon, Dec 11, 2017 at 8:35 PM, Chris Smith  wrote:

> I'm running vagrant on a Win10 machine behind Websense.   When I try to
> download boxes from some URLs, they simply do not work. If I go to the URL
> directly in a browser, I can get there, but not from vagrant.
>
> I've sent pcap to my security team for troubleshooting.   I'm wondering,
> however, what mechanism does vagrant use to perform the download?.   Is it
> a wget thing, a git clone-y kind of thing, or something completely
> different?  If it's an external kind of thing like git, I could try the
> same command on my machine to see if that fails, too, and it would be
> something else I could pass along to my sec team.
>
> 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/2541ffee-bcfb-48e0-bdcd-bf6782e18521%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/CAHqq0eye%3DjPPfLDKEpGcgPbCC8b4BoUtDfhA1uecj6na3no6Wg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] Vagrant/Virtualbox fails on looking for network devices most of the time, and when it does actually boot it takes at least 15 minutes to do so.

[Alvaro Miranda Aguilera]

try a different box.

hashicorp/precise64

do yo have that private key?



On Mon, Dec 11, 2017 at 5:52 AM, CodeLyfe  wrote:

> My host is Windows 10 Home. (Fall Creators Update)
>
> When I run the `vagrant up` command I either can't get vagrant to boot
> into the machine or if it does eventually succeed and boot it takes 15
> minutes or more to do so.
>
> What can I do to fix this and have Vagrant & Virtualbox working together
> properly.
>
> Virtualbox version: 5.2.2
> Vagrant version: 2.0.1
>
> My box is just an Ubuntu 14.04 box for Ruby on Rails development. It works
> fine on other systems, (Mac, Linux).
>
> So far I've tried disabling the Firewall as well as disabling & enabling
> the Virtualbox Host-Only adapter.
>
> I have set vgui = true so I can see what is going on inside the VM.
>
> In the VM it tries to find the network device, then retries again after 10
> seconds, then again after 120 seconds. Then it "gave up" looking for the
> network device and runs an init. The network device appears immediately
> after the init. Then it spends about 5 minutes configuring the network
> interfaces. When it completed it booted into Ubuntu with a login prompt.
>
> Once the login prompt is shown, Vagrant stops retrying and shows Machine
> booted and ready. It then took another 10 minutes configuring and enabling
> network interfaces, then finally mounts the shared folder and gives me a
> command prompt.
>
> When it fails I get what you see below.
>
> Any help will be greatly appreciated!
>
> This is what I get when I run `vagrant up`:
>
> λ vagrant up
> Bringing machine 'default' up with 'virtualbox' provider...
> ==> default: Importing base box 'dev_box'...
> ==> default: Matching MAC address for NAT networking...
> ==> default: Setting the name of the VM: Dev_default_1512943736797_96012
> ==> default: Clearing any previously set network interfaces...
> ==> default: Preparing network interfaces based on configuration...
> default: Adapter 1: nat
> default: Adapter 2: bridged
> ==> default: Forwarding ports...
> default: 3000 (guest) => 3000 (host) (adapter 1)
> default: 22 (guest) =>  (host) (adapter 1)
> ==> default: Running 'pre-boot' VM customizations...
> ==> default: Booting VM...
> ==> default: Waiting for machine to boot. This may take a few minutes...
> default: SSH address: 127.0.0.1:
> default: SSH username: vagrant
> default: SSH auth method: private key
> default: Warning: Connection aborted. Retrying...
> default: Warning: Connection reset. Retrying...
> default: Warning: Connection aborted. Retrying...
> default: Warning: Connection reset. Retrying...
> default: Warning: Connection aborted. Retrying...
> default: Warning: Connection aborted. Retrying...
> default: Warning: Connection reset. Retrying...
> default: Warning: Connection aborted. Retrying...
> default: Warning: Connection reset. Retrying...
> default: Warning: Connection aborted. Retrying...
> default: Warning: Connection aborted. Retrying...
> default: Warning: Connection reset. Retrying...
> default: Warning: Connection aborted. Retrying...
> default: Warning: Connection reset. Retrying...
> default: Warning: Connection aborted. Retrying...
> default: Warning: Connection reset. Retrying...
> default: Warning: Connection aborted. Retrying...
> default: Warning: Connection reset. Retrying...
> default: Warning: Connection aborted. Retrying...
> default: Warning: Connection reset. Retrying...
> default: Warning: Connection aborted. Retrying...
> default: Warning: Connection reset. Retrying...
> default: Warning: Connection aborted. Retrying...
> default: Warning: Connection aborted. Retrying...
> default: Warning: Connection reset. Retrying...
> default: Warning: Connection aborted. Retrying...
> default: Warning: Connection reset. Retrying...
> default: Warning: Connection aborted. Retrying...
> default: Warning: Connection aborted. Retrying...
> default: Warning: Connection reset. Retrying...
> default: Warning: Connection aborted. Retrying...
> default: Warning: Connection reset. Retrying...
> default: Warning: Connection aborted. Retrying...
> default: Warning: Connection reset. Retrying...
> default: Warning: Connection aborted. Retrying...
> default: Warning: Connection reset. Retrying...
> default: Warning: Connection aborted. Retrying...
> default: Warning: Connection reset. Retrying...
> default: Warning: Connection aborted. Retrying...
> default: Warning: Connection reset. Retrying...
> default: Warning: Connection aborted. Retrying...
> default: Warning: Connection reset. Retrying...
> default: Warning: Connection aborted. Retrying...
> default: Warning: Remote connection disconnect. Retrying...
> default: Warning: Connection aborted. Retrying...
> default: Warning: Connection reset. 

Re: [vagrant-up] use nvidia docker as provider

[Alvaro Miranda Aguilera]

to give the docker container access to devices like /dev/<..> you may need
to use flags

so try to get that the comman line you need then you can tell vagrant to
use that.

https://www.vagrantup.com/docs/docker/configuration.html#cmd

Alvaro

On Sun, Dec 10, 2017 at 11:30 AM, Alvaro Miranda Aguilera <kiki...@gmail.com
> wrote:

> what happens if you replace
>
> d.image = "aia/dev"
>
> to the docker image you want to use?
>
> Alvaro.
>
> On Sun, Dec 10, 2017 at 6:35 AM, Nimrod Morag <nimrod.mo...@gmail.com>
> wrote:
>
>>
>>
>> On Friday, December 8, 2017 at 11:47:04 AM UTC+2, Alvaro Miranda Aguilera
>> wrote:
>>>
>>> helllo
>>>
>>> more info please.
>>>
>>> are you on a Linux host with docker installed?
>>>
>> Yes. Ubuntu 16
>>
>>
>>> Can you share a sample minimal Vagrantfile you use?
>>>
>>
>> Vagrant.configure(2) do |config|
>> config.vm.provider "docker" do |d|
>>  d.image = "aia/dev"
>>  d.has_ssh = true
>>  d.name = "vagrant_aia_dev"
>>  d.create_args = ["-dit"]
>> end
>>
>> config.vm.network "public_network"
>> config.ssh.forward_x11 = true
>> end
>>
>>
>>
>>
>>
>>
>>
>>
>>> Alvaro
>>>
>>> On Thu, Dec 7, 2017 at 1:50 PM, Nimrod Morag <nimrod...@gmail.com>
>>> wrote:
>>>
>>>> I'm part of a team developing a machine learning application.
>>>>
>>>> currently we're using Vagrant with a Docker provider as a uniform dev
>>>> environment.
>>>>
>>>> We want to utilize the GPUs on our computers when we play around during
>>>> development, and I found that Nvidia released nvidia-docker to enable that
>>>> without needing to map the devices seperately in each host.
>>>>
>>>> How can I use nvidia-docker as a provider for Vagrant?
>>>>
>>>> If not possible, how can I dynamically retreive the device names on the
>>>> host when running `vagrant up`?
>>>>
>>>>
>>>> (didn't specify versions because I will change to whatever version the
>>>> solution requires)
>>>>
>>>> --
>>>> 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/ms
>>>> gid/vagrant-up/90d488ac-897b-41cb-ae95-e56025e0fdb4%40googlegroups.com
>>>> <https://groups.google.com/d/msgid/vagrant-up/90d488ac-897b-41cb-ae95-e56025e0fdb4%40googlegroups.com?utm_medium=email_source=footer>
>>>> .
>>>> 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/ms
>> gid/vagrant-up/5bfe8b6c-f36b-4fa8-be6d-bee8208b72a1%40googlegroups.com
>> <https://groups.google.com/d/msgid/vagrant-up/5bfe8b6c-f36b-4fa8-be6d-bee8208b72a1%40googlegroups.com?utm_medium=email_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Alvaro
>
>


-- 
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/CAHqq0ez6G9eviBx5mfu4Q2ERtqvJ%2B6-jxKTSk9D3-%3DLccv04dA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] use nvidia docker as provider

[Alvaro Miranda Aguilera]

what happens if you replace

d.image = "aia/dev"

to the docker image you want to use?

Alvaro.

On Sun, Dec 10, 2017 at 6:35 AM, Nimrod Morag <nimrod.mo...@gmail.com>
wrote:

>
>
> On Friday, December 8, 2017 at 11:47:04 AM UTC+2, Alvaro Miranda Aguilera
> wrote:
>>
>> helllo
>>
>> more info please.
>>
>> are you on a Linux host with docker installed?
>>
> Yes. Ubuntu 16
>
>
>> Can you share a sample minimal Vagrantfile you use?
>>
>
> Vagrant.configure(2) do |config|
> config.vm.provider "docker" do |d|
>  d.image = "aia/dev"
>  d.has_ssh = true
>  d.name = "vagrant_aia_dev"
>  d.create_args = ["-dit"]
> end
>
> config.vm.network "public_network"
> config.ssh.forward_x11 = true
> end
>
>
>
>
>
>
>
>
>> Alvaro
>>
>> On Thu, Dec 7, 2017 at 1:50 PM, Nimrod Morag <nimrod...@gmail.com> wrote:
>>
>>> I'm part of a team developing a machine learning application.
>>>
>>> currently we're using Vagrant with a Docker provider as a uniform dev
>>> environment.
>>>
>>> We want to utilize the GPUs on our computers when we play around during
>>> development, and I found that Nvidia released nvidia-docker to enable that
>>> without needing to map the devices seperately in each host.
>>>
>>> How can I use nvidia-docker as a provider for Vagrant?
>>>
>>> If not possible, how can I dynamically retreive the device names on the
>>> host when running `vagrant up`?
>>>
>>>
>>> (didn't specify versions because I will change to whatever version the
>>> solution requires)
>>>
>>> --
>>> 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/ms
>>> gid/vagrant-up/90d488ac-897b-41cb-ae95-e56025e0fdb4%40googlegroups.com
>>> <https://groups.google.com/d/msgid/vagrant-up/90d488ac-897b-41cb-ae95-e56025e0fdb4%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>> 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/5bfe8b6c-f36b-4fa8-be6d-bee8208b72a1%40googlegroups.com
> <https://groups.google.com/d/msgid/vagrant-up/5bfe8b6c-f36b-4fa8-be6d-bee8208b72a1%40googlegroups.com?utm_medium=email_source=footer>
> .
> 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/CAHqq0exMBrXEc-iDWNm%3D85nfxFVe9ep%3DVNRe48fGRO_jWthLBw%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

if you run the vagrant command as administrator, maybe all those lost vms
are under the admin user

vagrant by default will create VMs on the default dir for each user.

Virtualbox uses   USER/VirtualBox VMs

C:\Users\Administrator\VirtualBox VMs

or maybe you can use that cmder thing to run Virtualbox and check the gui
under admin.

Alvaro

On Fri, Dec 8, 2017 at 1:50 AM, Charlie  wrote:

> Alvaro, Robert:
>
> I think I've tracked down the culprit. The non-vagrant virtualboxes were
> running at the time of the power down/reboot and survived with no problem -
> digging further in to this is what revealed the issue:
>
> I start all my vagrant machines with a command line emulator called Cmder
> and rarely pay attention to the VirtualBox Manager GUI.
>
> While doing some more debugging today I noticed that my non-vagrants were
> always present in the VirtualBox Manager GUI but the vagrant machines only
> sporadically showed up (and always showed as being powered off, even if
> running).
>
> I remembered I had set the Cmder emulator to run as administrator (for an
> unrelated reason, nothing to do with vagrant or this issue). As soon as I
> ran the emulator with normal privs and issued `vagrant up` the vagrant
> machines started surviving reboots with no issue.
>
> So I guess virtualbox and/or vagrant don't like communicating with each
> other if running under different user contexts. I don't think that's a bug
> (more like an implementation limitation/constraint) so, for me at least,
> the issue is marked 'solved' :)
>
> Charlie
>
>
>
>
>
> On Wednesday, December 6, 2017 at 3:53:05 PM UTC, Robert Lilly wrote:
>>
>> Charlie, just for clarification, were the non-Vagrant Virtualbox VMs
>> running at the time of the power down / reboot as well as the the Vagrant
>> ones?
>>
>> I have experienced this problem before on Windows 7 and 10, as well as OS
>> X / MacOS. I didn't take the time to troubleshoot, I just made a habit of
>> not leaving any VMs running when I was finished for the day.
>>
> --
> 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/831f9c40-ba2a-4de3-9555-88eba86e51e6%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/CAHqq0eyL05YaA%3D%3DygtvdWAEje0VTCCFznT%3Db9NK8C0o3-EiJOQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] Where can I find the `name` of vagrant ssh `name`?

[Alvaro Miranda Aguilera]

hello

vagrant status

by default the name is default

however, [] usually means [optional]

so vagrant ssh

or vagrant ssh default is the same

the name or id is needed if you want to connect to a vm without the default
name or some other vm just using the id

when you many multiple running you can use   vagrant global-status and then
use the id for vagrant commands

Alvaro

On Thu, Dec 7, 2017 at 6:52 PM, luo kan  wrote:

> I am using `Vagrant 2.0.1`,
> after running `vagrant up`,
> I run `vagrant ssh`,it didn't have a response,as follow:
>
> [![enter image description here][1]][1]
>
>
>
> the commond in docs is like this:  https://www.vagrantup.com/
> docs/cli/ssh.html
>
>
>
> vagrant ssh [name|id] [-- extra_ssh_args]
>
>
>
>
>
>
> **Question:**
> Does it need the parameter `name`?Where can I find the `name`?
>
>   [1]: https://i.stack.imgur.com/XhJKb.png
>
> --
> 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/09820907-9c8e-4758-a710-7f4f0b835509%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/CAHqq0ewbA3ainzUuJsGAzJCpf9eRWZk3cHfSiAURU0f8bR_G8w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] use nvidia docker as provider

[Alvaro Miranda Aguilera]

helllo

more info please.

are you on a Linux host with docker installed?

Can you share a sample minimal Vagrantfile you use?

Alvaro

On Thu, Dec 7, 2017 at 1:50 PM, Nimrod Morag  wrote:

> I'm part of a team developing a machine learning application.
>
> currently we're using Vagrant with a Docker provider as a uniform dev
> environment.
>
> We want to utilize the GPUs on our computers when we play around during
> development, and I found that Nvidia released nvidia-docker to enable that
> without needing to map the devices seperately in each host.
>
> How can I use nvidia-docker as a provider for Vagrant?
>
> If not possible, how can I dynamically retreive the device names on the
> host when running `vagrant up`?
>
>
> (didn't specify versions because I will change to whatever version the
> solution requires)
>
> --
> 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/90d488ac-897b-41cb-ae95-e56025e0fdb4%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/CAHqq0eziMVws1MpttSwFcoQH35J09NhiyBjVy8%3D7HzvcAJ3j9A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] No prompt in VM after Vagrant up - system just hangs

[Alvaro Miranda Aguilera]

does this happen on a new box?

ie

mkdir trusty64
cd trusty64
vagrant init -m ubuntu/trusty64
vagrant up

?

does happen with a different box? say hashicorp/precise64

Thanks
Alvaro

On Thu, Dec 7, 2017 at 1:02 PM, Nigel  wrote:

> Hi all,
>
> I'm running Vagrant 2.0.1 with VirtualBox 5.2.2 on a Windows 10 host,
> launching it from within Git Bash (part of Git for Windows 2.15.1.2)
> Previously, I had no problems spinning up the standard ubuntu/trusty64
> image. Without knowingly making any changes, when I now run vagrant ssh, I
> connect to the VM, but it hangs without showing the command prompt.
>
> I don't encounter this issue on my Linux host (Ubuntu 17.10 running the
> same versions of Vagrant and VirtualBox) with exactly the same Vagrant
> bootstrap provisioning files, so this looks like a Windows platform issue,
> but as I said, it's worked fine before.
>
> I've tried re-installing both Vagrant and VirtualBox, clearing out old
> config files left behind by both apps (excluding removing the actual box
> images in the box folder) without success.
>
> I would be very grateful for some advice, as I can't work in the
> Vagrant-managed VM anymore.
>
> Many thanks.
>
> Nigel
>
> --
> 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/c8c54605-241e-4d98-b430-67837da4%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/CAHqq0ewhGuAkc%3DJzp3cEnXpk-m%3DVf4vOyPEyv1uwfrnxYOvb7w%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]

Just did a PS script


cat test2.bat

echo "hello from bat in windows"

powershell C:\vagrant\test2.ps1

cat test2.ps1



$username = 'vagrant'

$password = 'vagrant'


$securePassword = ConvertTo-SecureString $password -AsPlainText -Force

$credential = New-Object System.Management.Automation.PSCredential
$username, $securePassword

Start-Process -Path "http://www.microsoft.com/"-Credential $credential

-- 
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/CAHqq0ex2B7-ZQ%2B3b-9YW%3DKeBpnGnqgsTwgdaqwULmo83yWTJ4A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] Trying to set up a virtual box with vagrant

[Alvaro Miranda Aguilera]

hello

please use your normal user, no need to use run-ad-admin

Alvaro.


On Wed, Dec 6, 2017 at 10:40 PM, Carlos Morales <
carlosmoralesdi...@gmail.com> wrote:

> I'm working with the admin  user and I'm working on  cmd.exe. Thanks
>
> El miércoles, 6 de diciembre de 2017, 22:35:32 (UTC+1), Alvaro Miranda
> Aguilera escribió:
>>
>> Hello
>>
>> There is this error:
>>
>>
>> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/machine.rb:333:in
>> `unlink': Permission denied @ unlink_internal - C:/Users/Carlos/Desktop/
>> Vagrant_base/.vagrant/machines/default/virtualbox/id (Errno::EACCES)
>>
>> what user are you using?
>>
>> are you in Windows over cmd.exe, powershell, wsl, some bash?
>>
>> Alvaro
>>
>> On Wed, Dec 6, 2017 at 12:40 PM, Carlos Morales <carlosmor...@gmail.com>
>> wrote:
>>
>>> I have a virtualbox 5.1.30 and I have vagrant 2.0.1 and I have this
>>> error after doing a vagrant up --provider=virtualbox:
>>>
>>> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/machine.rb:333:in
>>> `unlink': Permission denied @ unlink_internal -
>>> C:/Users/Carlos/Desktop/Vagrant_base/.vagrant/machines/default/virtualbox/id
>>> (Errno::EACCES)
>>> from C:/HashiCorp/Vagrant/embedded/
>>> gems/gems/vagrant-2.0.1/lib/vagrant/machine.rb:333:in `delete'
>>> from C:/HashiCorp/Vagrant/embedded/
>>> gems/gems/vagrant-2.0.1/lib/vagrant/machine.rb:333:in `id='
>>> from C:/HashiCorp/Vagrant/embedded/
>>> gems/gems/vagrant-2.0.1/lib/vagrant/machine.rb:146:in `initialize'
>>> from C:/HashiCorp/Vagrant/embedded/
>>> gems/gems/vagrant-2.0.1/lib/vagrant/vagrantfile.rb:79:in `new'
>>> from C:/HashiCorp/Vagrant/embedded/
>>> gems/gems/vagrant-2.0.1/lib/vagrant/vagrantfile.rb:79:in `machine'
>>> from C:/HashiCorp/Vagrant/embedded/
>>> gems/gems/vagrant-2.0.1/lib/vagrant/environment.rb:733:in `machine'
>>> from C:/HashiCorp/Vagrant/embedded/
>>> gems/gems/vagrant-2.0.1/lib/vagrant/plugin/v2/command.rb:180:in `block
>>> in with_target_vms'
>>> from C:/HashiCorp/Vagrant/embedded/
>>> gems/gems/vagrant-2.0.1/lib/vagrant/plugin/v2/command.rb:204:in `block
>>> in with_target_vms'
>>> from C:/HashiCorp/Vagrant/embedded/
>>> gems/gems/vagrant-2.0.1/lib/vagrant/plugin/v2/command.rb:186:in `each'
>>> from C:/HashiCorp/Vagrant/embedded/
>>> gems/gems/vagrant-2.0.1/lib/vagrant/plugin/v2/command.rb:186:in
>>> `with_target_vms'
>>> from C:/HashiCorp/Vagrant/embedded/
>>> gems/gems/vagrant-2.0.1/plugins/commands/up/command.rb:87:in `execute'
>>> from C:/HashiCorp/Vagrant/embedded/
>>> gems/gems/vagrant-2.0.1/lib/vagrant/cli.rb:42:in `execute'
>>> from C:/HashiCorp/Vagrant/embedded/
>>> gems/gems/vagrant-2.0.1/lib/vagrant/environment.rb:308:in `cli'
>>> from C:/HashiCorp/Vagrant/embedded/
>>> gems/gems/vagrant-2.0.1/bin/vagrant:138:in `'
>>>
>>>
>>> How can I solve it?. Thanks in advance
>>>
>>>
>>> --
>>> 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/ms
>>> gid/vagrant-up/5cbeee61-6b10-4fdd-ba08-1039ca622ac1%40googlegroups.com
>>> <https://groups.google.com/d/msgid/vagrant-up/5cbeee61-6b10-4fdd-ba08-1039ca622ac1%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>> 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: #va

Re: [vagrant-up] No response after "vagrant up" command in Git Bash

[Alvaro Miranda Aguilera]

hello

on a fresh install you should see a pop-up that ruby is asking for
permissions to add firewall access some networks (local/internet)

are you admin on the box?

can you cancel that, ensure there is not any unkown window open and try
again?

you should get the typical firewall windows pop up as long you are not in a
restricted setup where all is denied.

Alvaro.


On Wed, Dec 6, 2017 at 8:21 PM, Andy Carey  wrote:

> I am working in the Udacity course "Linux Command Line Basics". I have
> installed Git, and am running it fine. I have installed virtual box from
> here  for a windows host. And
> I have installed vagrant for a
> 64 bit OS. I got a VM configuration file (i have tried the one provided by
> the course, and the one downloaded from Vagrant). I navigatged to the
> directory i would be working in and typed in "vagrant up"... at that point
> my terminal stops producing anything. here is a screen shot of what i see -
> https://i.imgur.com/sMci4ik.png this has been like this since 9:00 AM CST
> today. Anybody have any suggestions?
>
> --
> 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/170512c6-3a9a-40d6-9f81-4de67db52862%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/CAHqq0ey%2BLVhSBO2F1rzG%2BQnGysWA1kSpcKT-8K-O2kU7DP%2Bixw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] Trying to set up a virtual box with vagrant

[Alvaro Miranda Aguilera]

Hello

There is this error:


C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/machine.rb:333:in
`unlink': Permission denied @ unlink_internal - C:/Users/Carlos/Desktop/
Vagrant_base/.vagrant/machines/default/virtualbox/id (Errno::EACCES)

what user are you using?

are you in Windows over cmd.exe, powershell, wsl, some bash?

Alvaro

On Wed, Dec 6, 2017 at 12:40 PM, Carlos Morales <
carlosmoralesdi...@gmail.com> wrote:

> I have a virtualbox 5.1.30 and I have vagrant 2.0.1 and I have this error
> after doing a vagrant up --provider=virtualbox:
>
> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/machine.rb:333:in
> `unlink': Permission denied @ unlink_internal - C:/Users/Carlos/Desktop/
> Vagrant_base/.vagrant/machines/default/virtualbox/id (Errno::EACCES)
> from 
> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/machine.rb:333:in
> `delete'
> from 
> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/machine.rb:333:in
> `id='
> from 
> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/machine.rb:146:in
> `initialize'
> from 
> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/vagrantfile.rb:79:in
> `new'
> from 
> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/vagrantfile.rb:79:in
> `machine'
> from 
> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/environment.rb:733:in
> `machine'
> from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/
> vagrant/plugin/v2/command.rb:180:in `block in with_target_vms'
> from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/
> vagrant/plugin/v2/command.rb:204:in `block in with_target_vms'
> from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/
> vagrant/plugin/v2/command.rb:186:in `each'
> from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/
> vagrant/plugin/v2/command.rb:186:in `with_target_vms'
> from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/
> plugins/commands/up/command.rb:87:in `execute'
> from 
> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/cli.rb:42:in
> `execute'
> from 
> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/environment.rb:308:in
> `cli'
> from 
> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/bin/vagrant:138:in
> `'
>
>
> How can I solve it?. Thanks in advance
>
>
> --
> 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/5cbeee61-6b10-4fdd-ba08-1039ca622ac1%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/CAHqq0ezc0gCrwGiD45-OfH0ZJhvRN6LihCgeUX0isc3knNNRCw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] Does not execute PHP files only shows the content

[Alvaro Miranda Aguilera]

that means the webserver is not processing php.

perhaps open an issue in puphpet?

Alvaro

On Tue, Dec 5, 2017 at 10:50 PM, Giannino Di Tizio A. 
wrote:

> Hello,
> I'm new to this vagrant.
>
> After having downloaded vagrant ver. 2.0.1 and having generated with
> puphpet a machine for VirtualBox with Ubuntu 16.04, Apache, PHP 5.6 and
> MySql 5.7.
> Up to here everything ok, the localhost runs well.
>
> but when trying to execute scripts file in PHP, it does not run and only
> shows the content of the script on the screen.
>
> a file as basic as: infophp.php
>
> phpinfo ();
> ?>
>
> it does not run. and it only shows the content of the script.
>
> Any ideas of what is left to do?
>
>
> --
> 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/7b0e8a6a-d4de-4063-acb4-9f90b2bd6f4e%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/CAHqq0ezLkYhhof%3Dn3yXKoQ-oSu72Bu8%2B5L-OoO%2B%3DgQAg1qSUbQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] 'vagrant up' error: another VM with that name already exists

[Alvaro Miranda Aguilera]

hello

do vagrant destroy

then open virtualbox and delete a vm if there

then go to virtual media manager, hdd and delete any disk that is there
then go to this directory:
C:\Users\snarl\VirtualBox VMs\

and delete whats there.

specially if there is this:
C:\Users\snarl\VirtualBox VMs\sites_3d45f90d3b8

Alvaro

On Tue, Dec 5, 2017 at 7:46 PM, Carl Gross  wrote:

> Hello.  I am encountering an error with vagrant up:  "another VM with that
> name already exists" (see full text below).  How can I resolve this issue?
> Here is some more information.
>
> I am trying to setup Vagrant for the first time on this computer (Win 10,
> x64).  I recently carried out the installation steps, up through the
> initial *vagrant up*.  That step completed, but it could not write to the
> hosts file (due to a permissions issue), so I tried to start over from
> scratch.  I uninstalled Vagrant and Oracle VM from my computer.  But when I
> re-installed them and ran *vagrant up* again, I encountered this issue.
>
> I'm not sure if this is related or not, but I noticed that even after I
> uninstall Vagrant and Oracle VM from my computer, several folders are still
> leftover:  VirtualBox VMs, .vagrant.d, and .VirtualBox.  Am I free to
> manually delete these folders and their files?
>
> Here is the full output from *vagrant up*:
>
> $ vagrant up
> -f was unexpected at this time.
> __   ___   ___   __
> \ \ / \ \ / \ \ / / Varying Vagrant Vagrants
>  \ V / \ V / \ V /  v2.2.0-
>   \_/   \_/   \_/   
>
> Docs:   https://varyingvagrantvagrants.org/
> Contribute: https://github.com/varying-vagrant-vagrants/vvv
> Dashboard:  http://vvv.test
>
> Bringing machine 'default' up with 'virtualbox' provider...
> ==> default: Importing base box 'ubuntu/trusty64'...
> ==> default: Matching MAC address for NAT networking...
> ==> default: Checking if box 'ubuntu/trusty64' is up to date...
> ==> default: Setting the name of the VM: sites_3d45f90d3b8
> The name of your virtual machine couldn't be set because VirtualBox
> is reporting another VM with that name already exists. Most of the
> time, this is because of an error with VirtualBox not cleaning up
> properly. To fix this, verify that no VMs with that name do exist
> (by opening the VirtualBox GUI). If they don't, then look at the
> folder in the error message from VirtualBox below and remove it
> if there isn't any information you need in there.
>
> VirtualBox error:
>
> VBoxManage.exe: error: Could not rename the directory
> 'C:\Users\snarl\VirtualBox VMs\ubuntu-cloudimg-trusty-
> vagrant-amd64_1512498932320_30519' to 'C:\Users\snarl\VirtualBox
> VMs\sites_3d45f90d3b8' to save the settings file (VERR_ALREADY_EXISTS)
> VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component
> SessionMachine, interface IMachine, callee IUnknown
> VBoxManage.exe: error: Context: "SaveSettings()" at line 3093 of file
> VBoxManageModifyVM.cpp
>
> --
> 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/448abf3d-d2fd-4dc4-989c-bc5ec7726021%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/CAHqq0ey%3DrLzbA1k6rJcjWZFrJiUU_5i_yHEejAai%2BFOT9iArWg%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]

to try to repro this.

you have multiple vagrant projects that were provisioned
you did cut the power
started, the machins gone.

what host OS?

Alvaro.

On Tue, Dec 5, 2017 at 5:32 PM, Charlie <charlie.orf...@gmail.com> wrote:

> Hi Alvaro
>
> After simulating an unplanned host reboot (i.e. forcibly turning the
> laptop off and then on), this is what happens:
>
> 1. The machine dirs and files under ".vagrant/machines" (in the directory
> where the Vagrant file is) remain as they were
> 2. Running `vagrant global-status` shows the machines (although I think
> this is cached info as the warning message suggests)
> 3. Running `vagrant status` lists all the machines but their status is
> marked as "not created"
> 4. After running `vagrant status`, all the files in the machine dirs
> (under ".vagrant/machines/machine_name/vagrant" in the project directory
> with the Vagrant file) disappear
> 5. Running `VBoxManage list vms` no longer shows the machines
> 6. Despite this, the virtualbox files and vmdks for each machine all still
> exist under C:\Users\Charlie\VirtualBox VMs
> 7. Running `vagrant up` re-creates all the machines and re-provisions them
> (effectively duplicating the virtualbox machine files and vmdks that were
> already present in C:\Users\Charlie\VirtualBox VMs)
>
> It's not clear to me if the issue is with vagrant losing the associations
> after a reboot or with Virtualbox losing track of the VMs after a reboot
> and causing vagrant to assume they don't exist. If the latter, I don't
> understand why virtualbox doesn't also lose track of other non-vagrant VMs
> I have created. They continue to exist and work as normal after a reboot.
>
> Charlie
>
> On Tuesday, December 5, 2017 at 7:33:09 AM UTC, Alvaro Miranda Aguilera
> wrote:
>>
>> 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 <charlie...@gmail.com> 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+...@googlegroups.com.
>>> To view this discussion on the web visit https://groups.google.com/d/ms
>>> gid/vagrant-up/700b6dca-b73a-4cb8-8c4c-fb9853fd7361%40googlegroups.com
>>> <https://groups.google.com/d/msgid/vagrant-up/700b6dca-b73a-4cb8-8c4c-fb9853fd7361%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>> 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 Go

Re: [vagrant-up] public_network and gateway

[Alvaro Miranda Aguilera]

hello

vagrant wont setup gw in that fixed ip setup, better tell vagrant not
configure and do it over a provision script. you can add run: "always" to
have it run all the time.

Alvaro.

On Tue, Dec 5, 2017 at 2:37 PM, Mathew Abraham 
wrote:

> Hi guys,
>
> I got a setup for public_network with static IP
>
>  c.vm.network :public_network, ip: n[0], netmask: '255.255.255.0'
>
> However When the last bit is executed i.e. "Configuring and enabling
> network interfaces.."  it clears my manual GATEWAY entry in ifcfg-enp0s8
> because of this other servers cannot ping my VM. Is there any way to
>
> a) Configure gateways for interface via vagrant?
> b)or tell vagrant  not to delete gateway configs ?
>
> VirtualBox Guest Additions: Starting.
> Redirecting to /bin/systemctl start vboxadd.service
> Redirecting to /bin/systemctl start vboxadd-service.service
> Unmounting Virtualbox Guest Additions ISO from: /mnt
> ==> wcs_local_env: Checking for guest additions in VM...
> ==> wcs_local_env: Setting hostname...
> *==> wcs_local_env: Configuring and enabling network interfaces...*
> wcs_local_env: SSH address: 127.0.0.1:2200
> wcs_local_env: SSH username: vagrant
> wcs_local_env: SSH auth method: private key
> ==> wcs_local_env: Mounting shared folders...
> wcs_local_env: /vagrant => C:/disc/vagrant
> ==> wcs_local_env: Machine already provisioned. Run `vagrant provision` or
> use the `--provision`
> ==> wcs_local_env: flag to force provisioning. Provisioners marked to run
> always will still run.
>
> Thanks,
> Mathew
>
> --
> 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/c2103655-0ab1-4f0e-8211-2e60786d9b9f%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/CAHqq0eyzCLXq4mfi8rnR6Wqzy%2B_7kLqaqTbnD5Y0%3D_JZ8T7Kog%40mail.gmail.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.

Re: [vagrant-up] change nic name ?

[Alvaro Miranda Aguilera]

if you disable the new predictable naming you can end with eth0/eth1 etc

you may need to repackage the box or create one from iso.

check about net.ifnames=0 on boot kernel parameter.



On Sun, Dec 3, 2017 at 9:40 PM, Mathew Abraham 
wrote:

> Hi Alvaro,
>>
>
> Thanks, I was trying to keep the  nic name same for all the developers as
> my Ansible job configure the VM system  based on the nic name provided. If
> it differs for each VM then I have to make is as a parameter via data vars.
> I was just trying to reduce that parameter if possible.
>
> Thanks,
> Mathew
>
> --
> 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/0274468b-314c-4de3-b5ff-a1ec1c9bafdc%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/CAHqq0eyvj93mefZH4yQYeFwCOdhgArBQROhR15HOid71rkcr2Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] dynamically change the sshd port in guest

[Alvaro Miranda Aguilera]

hello

vagrant expect the ssh to be in the port 22
I think you better using an intermediate tool to do that changes before
vagrant.

if you are using virtualbox, have a look at packer virtualbox-ovf

that can start from an existing vm, however change the port yes may work,
you build them in 2 steps.

step 1, from existing vm with sshd on port 22, change it to 222, poweroff
step 2, existing vm with sshd on port 222 install the app that uses port
22, poweroff create vagrant box with vagrant file that says use port 222


but in all is not a normal use case for vagrant, so i think the best is to
build boxes that are ready to use for vagrant.

you can use packer to build from an iso, so there are options.

for vagrant itself i think is a bit hard

Alvaro.

On Sat, Dec 2, 2017 at 11:03 PM, Marcin Dulak <marcin.du...@gmail.com>
wrote:

> 1. I have an official box that uses sshd on port 22, that could be
> https://app.vagrantup.com/centos/ https://app.vagrantup.com/fedora/
> https://app.vagrantup.com/ubuntu, anything
> 2. I start guest using that box with Vagrant and reconfigure sshd on the
> guest to listen on a different port (222). This is for example due to
> starting another service on port 22 on the guest. The new service on port
> 22 does not need to exposed to the Vagrant host.
> 3. I want now Vagrant to know about this change after I reload the same
> box, by passing environment variables to Vagrantfile or some other way
> 4. After creating a set of scripts that configure my box (ansible, puppet,
> docker, ...) this way, I can now use them on a physical host, VM not
> managed by Vagrant, or a VM managed by Vagrant, all having sshd on port 222
>
> I think I'm clear enough, if not try my Vagrantfile.
>
> Best regards,
>
> Marcin
>
> On Saturday, December 2, 2017 at 4:41:37 PM UTC+1, Alvaro Miranda Aguilera
> wrote:
>>
>> Vagrant will create a local port say on  for the first box
>>
>> When tries for the 2nd port, will try  used? Then 2223 or other
>>
>> So still not clear whats the benefit or requirement on doing this.
>>
>> Is this really needed? Why?
>>
>> And what are those boxes you mention?
>>
>> 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/23c69ff1-0157-419d-b548-fddabaa2b876%40googlegroups.com
> <https://groups.google.com/d/msgid/vagrant-up/23c69ff1-0157-419d-b548-fddabaa2b876%40googlegroups.com?utm_medium=email_source=footer>
> .
>
> 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/CAHqq0exkaJcpJJ2hfw6rBVeM5GBzm%2BruszBXPKENaE3DXBYE3w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] Downloading boxes from atlas.hashicorp.com is very slow

[Alvaro Miranda Aguilera]

Hello

that box is externally hosted, so you should contact canonical. Is not
hosted in vagrant cloud/hashicorp

the box is a redirect from:

Location:
https://app.vagrantup.com/ubuntu/boxes/trusty64/versions/20171128.0.0/providers/virtualbox.box


to:


Location:
http://cloud-images.ubuntu.com/vagrant/trusty/current/trusty-server-cloudimg-amd64-vagrant-disk1.box



virtualbox Externally hosted (cloud-images.ubuntu.com)



On Sun, Dec 3, 2017 at 7:23 AM, Christopher Carr <
christopher.c...@pdxwebguy.com> wrote:

> This seems to still be a frequent problem 3 years later. I'm not getting
> over 200Kb/s downloading https://vagrantcloud.com/ubuntu/boxes/trusty64/
> versions/20171128.0.0/providers/virtualbox.box
>
> Run into a bandwidth limit and being throttled, or something? Shouldn't
> have to wait 90+ minutes after 'vagrant up'.
>
> On Wednesday, December 17, 2014 at 2:45:15 PM UTC-8, Mitchell Hashimoto
> wrote:
>>
>> Frank,
>>
>> The location of these boxes hasn't changed in nearly a year. I'd say
>> that this is probably just due to transient issues.
>>
>> Best,
>> Mitchell
>>
>> On Wed, Dec 17, 2014 at 2:43 PM, Frank Patz-Brockmann
>>  wrote:
>> > After month I've returned to using vagrant and find downloading base
>> boxes
>> > like hashicorp/precise32 extremely slow.
>> > It literally takes hours, where it took just minutes a while ago. I am
>> sure
>> > it's not my internet connection, other downloads
>> > work as expected. Is there some bandwidth throttling at work? Waiting
>> hours
>> > makes "Getting Started" really hard ...
>> >
>> > --
>> > 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/d/optout.
>>
> --
> 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/27447da2-643e-4682-add0-25e330b91d39%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/CAHqq0exBopJP-s%3DefcUfrjO1RcHLH5eQh9hFVvht0sCVvhL9iA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

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

[Alvaro Miranda Aguilera]

Hello

vbox extension on the host need to be installed.

this works for me:

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

  config.vm.box = "hashicorp/precise64"

  config.vm.provider "virtualbox" do |v|

v.customize ["modifyvm", :id, "--vrde", "on"]

v.customize ["modifyvm", :id, "--vrdeport", "3389-3389"]

  end

end


no need to ssh into the VM if you have direct access, just rdp to the
hostip:port

enjoy!
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/CAHqq0eysSSY-cQd0PoBrafAAYc9dN88eNU-ZAr4kvxXfXihKVA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] New Vagrant Setup

[Alvaro Miranda Aguilera]

Hello

At some point you or someone did configure a proxy in the machine you are
using.

I don't have all the information.

usually is a variable like

http_proxy=
https_proxy=

the value to test:

http://connsvr.abcdcom:8080 <https://connsvr.abcdcom:8080/>

On Sun, Dec 3, 2017 at 5:41 AM, Rajasekhar Reddy <rajredd...@gmail.com>
wrote:

> can you tell me how do i do that ?
>
> On Sat, Dec 2, 2017 at 7:39 AM, Alvaro Miranda Aguilera <kiki...@gmail.com
> > wrote:
>
>> Hello
>>
>> Here is the error:
>> URL: ["https://vagrantcloud.com/nrel/CentOS-6.5-x86_64;]
>> Error: Unsupported proxy 'https://connsvr.abcdcom:8080', libcurl is
>> built without the HTTPS-proxy support.
>>
>> Can you try to set the proxy var to be http instead of https ?
>>
>> Alvaro.
>>
>>
>> On 1 Dec 2017, at 21:18, Rajasekhar Reddy Anumula <rajredd...@gmail.com>
>> wrote:
>>
>> URL: ["https://vagrantcloud.com/nrel/CentOS-6.5-x86_64;]
>> Error: Unsupported proxy 'https://connsvr.abcdcom:8080', libcurl is
>> built without the HTTPS-proxy support.
>>
>>
>> --
>> 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 a topic in the
>> Google Groups "Vagrant" group.
>> To unsubscribe from this topic, visit https://groups.google.com/d/to
>> pic/vagrant-up/TXWsPecleII/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> vagrant-up+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit https://groups.google.com/d/ms
>> gid/vagrant-up/746A2BC3-BD36-41C4-96CC-F4B8DE137965%40gmail.com
>> <https://groups.google.com/d/msgid/vagrant-up/746A2BC3-BD36-41C4-96CC-F4B8DE137965%40gmail.com?utm_medium=email_source=footer>
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Cheers,
>
> Rajasekhar Reddy.A
>
> --
> 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/CACYbpTm3p9VA2%3DQyJ6wfxQGWRePvu-
> dMBQgEvF5Wnk9%3Dpn3a5w%40mail.gmail.com
> <https://groups.google.com/d/msgid/vagrant-up/CACYbpTm3p9VA2%3DQyJ6wfxQGWRePvu-dMBQgEvF5Wnk9%3Dpn3a5w%40mail.gmail.com?utm_medium=email_source=footer>
> .
> 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/CAHqq0ewh-ibYi84jTueJgT6VRg7EVf%3DiZjmkYh%2BSkW0uqwzDVg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] Vagrant with Virtualbox 5.2.2

[Alvaro Miranda Aguilera]

Hello Carlos

Please try with Virtualbox 5.1.30


5.2 is not ready yet.

Thanks
Alvaro

On Sun, Dec 3, 2017 at 12:07 PM, Carlos Morales <
carlosmoralesdi...@gmail.com> wrote:

> Hello,
>
> I have Vagrant 2.0.1 and Virtualbox 5.2.2 and I have this mistake:
>
> Bringing machine 'default' up with 'virtualbox' provider...
>
> ==> default: Checking if box 'ubuntu/xenial64' is up to date...
>
> ==> default: A newer version of the box 'ubuntu/xenial64' is available!
> You currently
>
> ==> default: have version '20171109.0.0'. The latest is version
> '20171201.0.0'. Run
>
> ==> default: `vagrant box update` to update.
>
> ==> default: Clearing any previously set forwarded ports...
>
> ==> default: Clearing any previously set network interfaces...
>
> ==> default: Preparing network interfaces based on configuration...
>
> default: Adapter 1: nat
>
> default: Adapter 2: hostonly
>
> ==> default: Forwarding ports...
>
> default: 80 (guest) => 8080 (host) (adapter 1)
>
> default: 22 (guest) =>  (host) (adapter 1)
>
> ==> default: Running 'pre-boot' VM customizations...
>
> ==> default: Booting VM...
>
> There was an error while executing `VBoxManage`, a CLI used by Vagrant
>
> for controlling VirtualBox. The command and stderr is shown below.
>
> Command: ["startvm", "4942eee0-9109-4694-8aa4-c414453ebc34", "--type",
> "headless"]
>
> Stderr: VBoxManage.exe: error: The virtual machine
> 'Vagrant_base_default_1510557259464_65915' has terminated unexpectedly
> during startup with exit code 1 (0x1). More details may be available in
> 'C:\Users\cmoralesdiego\VirtualBox VMs\Vagrant_base_default_15105
> 57259464_65915\Logs\VBoxHardening.log'
>
> VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component
> MachineWrap, interface IMachine
>
>
> What can I do?, with the previous virtualbox I could work but now nothing.
>
> --
> 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/937b7642-264b-4752-a26b-753520b43f9d%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/CAHqq0eyzkmitzMVuxxLi5o6Swri1z9GcEm_NTewFbEmUpzx6oQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] New Vagrant Setup

[Alvaro Miranda Aguilera]

Hello

Here is the error:
URL: ["https://vagrantcloud.com/nrel/CentOS-6.5-x86_64 
"]
Error: Unsupported proxy 'https://connsvr.abcdcom:8080 
', libcurl is built without the HTTPS-proxy 
support.

Can you try to set the proxy var to be http instead of https ?

Alvaro.


> On 1 Dec 2017, at 21:18, Rajasekhar Reddy Anumula  
> wrote:
> 
> URL: ["https://vagrantcloud.com/nrel/CentOS-6.5-x86_64 
> "]
> Error: Unsupported proxy 'https://connsvr.abcdcom:8080 
> ', libcurl is built without the HTTPS-proxy 
> support.

-- 
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/746A2BC3-BD36-41C4-96CC-F4B8DE137965%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] change nic name ?

[Alvaro Miranda Aguilera]

hello

Why you need that?

The nic name is generated by linux based on thinks like pci port.

What requirement you have that relies on the nic name?

alvaro.


> On 1 Dec 2017, at 13:07, Mathew Abraham  wrote:
> 
> Hi guys,
> 
> Is it possible to change the nic name to custom one using vagrantfile ?  i.e 
> instead of  'enp0s8'  could I specify 'ens100' ?
> 
>   c.vm.network :public_network, ip: 192.17.28.180 , netmask: 
> '255.255.255.0'
> 
> 
> [vagrant@ansible ~]$ ifconfig
> enp0s3: flags=4163  mtu 1500
> inet 10.0.2.15  netmask 255.255.255.0  broadcast 10.0.2.255
> inet6 xxx  prefixlen 64  scopeid 0x20
> ether 09:00:30:1f:gc:83  txqueuelen 1000  (Ethernet)
> RX packets 45752  bytes 63057452 (60.1 MiB)
> RX errors 0  dropped 0  overruns 0  frame 0
> TX packets 7547  bytes 558118 (545.0 KiB)
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
> 
> enp0s8: flags=4163  mtu 1500
> inet 192.17.28.180  netmask 255.255.255.0  broadcast 192.17.28.255
> inet6 xx  prefixlen 64  scopeid 0x20
> ether 09:00:30:gc:dc:92  txqueuelen 1000  (Ethernet)
> RX packets 86  bytes 8543 (8.3 KiB)
> RX errors 0  dropped 0  overruns 0  frame 0
> TX packets 55  bytes 8108 (7.9 KiB)
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
> 
> Thanks,
> Mathew
> 
> -- 
> 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/dfda4d37-4f2f-427b-abc0-d0ad5eda9ba7%40googlegroups.com
>  
> .
> For more options, visit https://groups.google.com/d/optout 
> .

-- 
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/52EBA1E0-FBE0-44AF-A2C7-BA4B9397431B%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] Vagrant Reload after config file change

[Alvaro Miranda Aguilera]

some of them yes.

networking is one that come to my mind that happens every time.

each halt/up or reload all the networking gets deleted and created again,
so if you add/remove/reload a network i think should dissapear.

but other won't be overriden.

Alvaro.


Virusvrij.
www.avast.com

<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Mon, Nov 27, 2017 at 11:55 AM, Makrand  wrote:

> So attributes or values once applied will remain effective unless you
> override them or destroy the environment.
>
> --
> 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/7567550c-e1c5-495d-adce-8f0004e6d5f7%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/CAHqq0ezLxm7DkAxGK2EH8Wny0wfRaLVQ_PDaO1r4bzd_fn__tw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] Vagrant Error on Configuring nic

[Alvaro Miranda Aguilera]

hello

can you open virtualbox gui and create and boot a VM 64 bits?


not sure from where the error is coming from, so after you confirm you can
create and boot a vm please do this.

mkdir precise64
cd precise64
vagrant init -m hashicorp/precise64
vagrant up

if there are errors do this:


vagrant destroy
vagrant version
vagrant plugin list
vagrant up --debug

and share the output  and the generated Vagrantfile for review

Thanks
Alvaro

On Wed, Nov 22, 2017 at 3:45 PM, Private Info  wrote:

> I have been trying to install Vagrant on Windows 10 for a few days and
> finally isolated the issue to a nic configuration problem...
>
> Stderr: VBoxManage.exe: error: Failed to open/create the internal network
>> 'HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter #2'
>> (VERR_SUPDRV_COMPONENT_NOT_FOUND).
>> VBoxManage.exe: error: Failed to attach the network LUN
>> (VERR_SUPDRV_COMPONENT_NOT_FOUND)
>> VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component
>> ConsoleWrap, interface IConsole
>
>
> This is just a Dell T3500 Xeon system with a gigabit Broadcom adapter, PC
> has two, one is not in use. I had Vbox and HyperV running. HyperV was
> removed from windows config. Vbox was removed from PC along with supporting
> folders.
>
> Vagrant version 1.9.6
>
> I could use some help on how to get past this error.
>
> thank you,
>
>
> --
> 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/661b4ccf-e5b9-4022-adf9-581032a03306%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/CAHqq0ezMvKzLNNhK47Y%2Bxdyw%3DLT9Rez0etpfaz6bo0%2BHbg7ENQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] Vagrant config

[Alvaro Miranda Aguilera]

hello

yes

1. you can open virtualbox GUI, go to settings and replace the default
location for vms.

2. you can update the vagrantfile to modify the VM to adjust memory and CPU
count.

ghz not sure, say your machine is 2ghz you can set some sort of cpu caps on
utilization


cpu cap:
https://www.vagrantup.com/docs/virtualbox/configuration.html#vboxmanage-customizations


memory and cpu:

config.vm.provider "virtualbox" do |v|
  v.memory = 1024
  v.cpus = 2end


Thanks
Alvaro

On Wed, Nov 22, 2017 at 1:38 PM, Makrand  wrote:

> Hello,
>
> Getting started with vagrant.
>
> Right now I am playing with *hashicorp/precise64 box*
>
> The only thing I defined in vagrant file is name of box and kept rest file
> (created with vagrant init) as is. The VM is getting launched by default
> into /home/user/Virtualbox VMs folder. (Since this folder in on SSD, do not
> want to use if for testing purposes)
>
> 1) Is there any way can force VM to be launched into particular folder??
> say /media/mount/VMs.
>
> 2) Where can I define the cpu core/ghz and root disk size parameters for
> VM?
>
> Already looked at below:- https://www.vagrantup.
> com/docs/vagrantfile/machine_settings.html
>
> --
> 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/fa8f1e76-762e-4e1d-aa23-8eb57c194853%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/CAHqq0exBpTs%3D-59-DPSwVae4h3avAm65%2Bf0FwNFeNnrrrug%2BNw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] Vagrant code to build a 2-node Oracle RAC cluster in VirtualBox

[Alvaro Miranda Aguilera]

hello

Vagrant is written in ruby, and Vagrantfile use ruby as a lang.

The code I did share it works.

I build a shared disk setup for clusters and oracle rac too.

Alvaro.


On Tue, Nov 21, 2017 at 2:21 PM, <faber1...@gmail.com> wrote:

> Thank You Alvaro.
>  I am new to vagrant.
>  Is there a way I could check the code for syntax errors before I execute
> the code?
>
>  My only programming knowledge is on Oracle PL/SQL where IF statements end
> with an END IF as shown below in Courier New font.
>  But vagrant's IF statements end with just an "end" keyword which can be
> confusing if not intended very clearly.
>
>  if condition then
>--statements
> elseif condition then
> -- more statements
> ...
> else
> -- other statements;
> end if;
>
>
>
>
> On Tuesday, November 21, 2017 at 6:41:49 AM UTC+8, Alvaro Miranda Aguilera
> wrote:
>>
>> for the disk part you can use something like this:
>>
>> https://gist.github.com/anonymous/a3a7832904e13ac1f222baa911d33024
>>
>> Alvaro
>>
>> On Mon, Nov 20, 2017 at 2:59 PM, <fabe...@gmail.com> wrote:
>>
>>> Vagrant version : 2.0.1
>>> Guest OS : Oracle Linux 7.4
>>>
>>>
>>> I have an Oracle Linux 7.4 vagrant base box. I would like to build a
>>> 2-node Oracle RAC cluster. I want to build 2 RAC VMs and attach shared
>>> disks (for ASM) to both of these VMs.
>>> Where can I find the vagrant code for this requirement ??
>>>
>>> --
>>> 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/ms
>>> gid/vagrant-up/a9132a38-ab27-4bd5-8977-015d4b8d3452%40googlegroups.com
>>> <https://groups.google.com/d/msgid/vagrant-up/a9132a38-ab27-4bd5-8977-015d4b8d3452%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>> 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/e8c7d345-cb4a-454b-852a-d77dcd6b8029%40googlegroups.com
> <https://groups.google.com/d/msgid/vagrant-up/e8c7d345-cb4a-454b-852a-d77dcd6b8029%40googlegroups.com?utm_medium=email_source=footer>
> .
> 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/CAHqq0ey-3nwDixvfiEbBvrqRafqVKkzxeZ%3Di3h6SeONVW%3DqdJA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] Bridged network with vmware workstation, windows guest

[Alvaro Miranda Aguilera]

Hello

Missed the vmware part from your message, but I can see it now in the
vagrantfile, I just took a bit from it didn't copy paste all.

So for VMWare, it also works:

kikitux@alvaro MINGW64 ~/Downloads/vagrant_bridge_eth0_vmware
$ vagrant up
Bringing machine 'default' up with 'vmware_workstation' provider...
==> default: Cloning VMware VM: 'hashicorp/precise64'. This can take some
time...
==> default: Checking if box 'hashicorp/precise64' is up to date...
==> default: Verifying vmnet devices are healthy...
==> default: Preparing network adapters...
WARNING: The VMX file for this box contains a setting that is automatically
overwritten by Vagrant
WARNING: when started. Vagrant will stop overwriting this setting in an
upcoming release which may
WARNING: prevent proper networking setup. Below is the detected VMX setting:
WARNING:
WARNING:   ethernet0.pcislotnumber = "32"
WARNING:
WARNING: If networking fails to properly configure, it may require this VMX
setting. It can be manually
WARNING: applied via the Vagrantfile:
WARNING:
WARNING:   Vagrant.configure(2) do |config|
WARNING: config.vm.provider :vmare_workstation do |vmware|
WARNING:   vmware.vmx["ethernet0.pcislotnumber"] = "32"
WARNING: end
WARNING:   end
WARNING:
WARNING: For more information:
https://www.vagrantup.com/docs/vmware/boxes.html#vmx-whitelisting
==> default: Starting the VMware VM...
==> default: Waiting for the VM to receive an address...
==> default: Forwarding ports...
default: -- 22 => 
==> default: Waiting for machine to boot. This may take a few minutes...
default: SSH address: 0:22
default: SSH username: vagrant
default: SSH auth method: private key
default:
default: Vagrant insecure key detected. Vagrant will automatically
replace
default: this with a newly generated keypair for better security.
default:
default: Inserting generated public key within guest...
default: Removing insecure key from the guest if it's present...
default: Key inserted! Disconnecting and reconnecting using new SSH
key...
==> default: Machine booted and ready!
==> default: Configuring network adapters within the VM...
==> default: Waiting for HGFS to become available...
==> default: Enabling and configuring shared folders...
default: -- C:/Users/kikitux/Downloads/vagrant_bridge_eth0_vmware:
/vagrant

kikitux@alvaro MINGW64 ~/Downloads/vagrant_bridge_eth0_vmware
$ vagrant ssh -c 'ifconfig ; route -n'
eth0  Link encap:Ethernet  HWaddr 00:0c:29:1f:47:89
  inet addr:10.0.15.89  Bcast:10.0.115.255  Mask:255.255.252.0
  inet6 addr: fe80::20c:29ff:fe1f:4789/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:1469 errors:0 dropped:0 overruns:0 frame:0
  TX packets:497 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:224165 (224.1 KB)  TX bytes:70375 (70.3 KB)

loLink encap:Local Loopback
  inet addr:127.0.0.1  Mask:255.0.0.0
  inet6 addr: ::1/128 Scope:Host
  UP LOOPBACK RUNNING  MTU:16436  Metric:1
  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0
  RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse
Iface
0.0.0.0 10.0.12.1  0.0.0.0 UG10000 eth0
10.0.12.0  0.0.0.0 255.255.252.0   U 0  00 eth0
Connection to 10.0.115.89 closed.

kikitux@alvaro MINGW64 ~/Downloads/vagrant_bridge_eth0_vmware
$


This one requires less tricks since VMware works bit differently:

$ cat Vagrantfile
# -*- mode: ruby -*-
# vi: set ft=ruby :

Vagrant.configure("2") do |config|
  config.vm.box = "hashicorp/precise64"
  config.vm.network "public_network", adapter: 0, auto_config: false
  config.vm.provider :vmware_workstation do |v|
v.gui = true
  end
end

let me know if works.

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/CAHqq0ey_LjEbeV0D6bAzhT7PTyGtiSZX7S-k1p52HxJ5-%3DDz2A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] Bridged network with vmware workstation, windows guest

[Alvaro Miranda Aguilera]

WARNING:
> WARNING: For more information: https://www.vagrantup.com/
> docs/vmware/boxes.html#vmx-whitelisting
> ==> default: Starting the VMware VM...
> ==> default: Waiting for the VM to receive an address...
> ==> default: Forwarding ports...
> default: -- 3389 => 3389
> default: -- 22 => 
> default: -- 5985 => 55985
> default: -- 5986 => 55986
> ==> default: Waiting for machine to boot. This may take a few minutes...
> ==> default: Stopping the VMware VM...
> ==> default: Deleting the VM...
> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/
> plugins/communicators/winrm/helper.rb:41:in `winrm_info_invalid?':
> undefined method `start_with?' for 0:Integer (NoMethodError)
> from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/
> plugins/communicators/winrm/helper.rb:36:in `winrm_address'
> from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/
> plugins/communicators/winrm/helper.rb:21:in `winrm_info'
> from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/
> plugins/communicators/winrm/communicator.rb:37:in `block in
> wait_for_ready'
> from 
> C:/HashiCorp/Vagrant/embedded/mingw64/lib/ruby/2.4.0/timeout.rb:93:in
> `block in timeout'
> from 
> C:/HashiCorp/Vagrant/embedded/mingw64/lib/ruby/2.4.0/timeout.rb:33:in
> `block in catch'
> from 
> C:/HashiCorp/Vagrant/embedded/mingw64/lib/ruby/2.4.0/timeout.rb:33:in
> `catch'
> from 
> C:/HashiCorp/Vagrant/embedded/mingw64/lib/ruby/2.4.0/timeout.rb:33:in
> `catch'
> from 
> C:/HashiCorp/Vagrant/embedded/mingw64/lib/ruby/2.4.0/timeout.rb:108:in
> `timeout'
> from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/
> plugins/communicators/winrm/communicator.rb:31:in `wait_for_ready'
> from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/
> vagrant/action/builtin/wait_for_communicator.rb:16:in `block in call'
> from C:/HashiCorp/Vagrant/embedded/gems/gems/logging-2.2.2/lib/
> logging/diagnostic_context.rb:474:in `block in
> create_with_logging_context'
>
> Did you ever actually got this working in practice, or is that a case of
> "should work in principle"?
>
> Cheers,
> Andrew
>
> On Monday, 20 November 2017 22:47:42 UTC+13, Alvaro Miranda Aguilera wrote:
>>
>> the first nic is by default.
>>
>> So you don't want to add a new nic, you can override the first one.
>>
>> have a look at this:
>> https://superuser.com/questions/957631/how-to-force-vagrant-
>> to-have-a-single-bridged-network-interface
>>
>> Alvaro
>>
>>
>> On Mon, Nov 20, 2017 at 1:55 AM, <andr...@gmail.com> wrote:
>>
>>> When I add this line to my vagrantfile:
>>>
>>> config.vm.network "public_network", bridge: "vmnet0"
>>>
>>> vagrant creates *second* adapter which is bridged.
>>> Both primary and secondary adaters seems to work fine in this
>>> configuration.
>>> I do not want second adapter I want the primary one to be bridged.
>>>
>>> How do I configure this?
>>>
>>> Vagrantfile to test:
>>>
>>> # -*- mode: ruby -*-
>>> # vi: set ft=ruby :
>>>
>>> Vagrant.configure("2") do |config|
>>>   config.vm.box = "StefanScherer/windows_2016_docker"
>>>
>>>   config.vm.network "public_network"
>>>   config.vm.provider :vmware_workstation do |v|
>>> v.gui = true
>>>   end
>>> end
>>>
>>>
>>>
>>> Cheers,
>>> Andrew
>>>
>>> --
>>> 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/ms
>>> gid/vagrant-up/f564595c-48f5-4dc3-ae48-067f09b2da0f%40googlegroups.com
>>> <https://groups.google.com/d/msgid/vagrant-up/f564595c-48f5-4dc3-ae48-067f09b2da0f%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>> For more opt

Re: [vagrant-up] Vagrant code to build a 2-node Oracle RAC cluster in VirtualBox

[Alvaro Miranda Aguilera]

for the disk part you can use something like this:

https://gist.github.com/anonymous/a3a7832904e13ac1f222baa911d33024

Alvaro

On Mon, Nov 20, 2017 at 2:59 PM,  wrote:

> Vagrant version : 2.0.1
> Guest OS : Oracle Linux 7.4
>
>
> I have an Oracle Linux 7.4 vagrant base box. I would like to build a
> 2-node Oracle RAC cluster. I want to build 2 RAC VMs and attach shared
> disks (for ASM) to both of these VMs.
> Where can I find the vagrant code for this requirement ??
>
> --
> 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/a9132a38-ab27-4bd5-8977-015d4b8d3452%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/CAHqq0ezL0G_0J8%2BiPs84OCLjiRd2GK7OpDd1jwZpVweLFsyMXQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] Broken routes with changed default router on macOS

[Alvaro Miranda Aguilera]

there is not enough information to help.

should it connect over private_network?

what are the output of

route -n
ip addr show

can you ping 8.8.8.8 ?

perhaps you need to replace the dns?

can be many reasons why doesnt work, if you could share a repo over github
to reproduce will be easier to have a look.

Alvaro.

On Mon, Nov 20, 2017 at 11:26 AM, <mich...@kinvolk.io> wrote:

>
>
> On Monday, November 20, 2017 at 10:44:56 AM UTC+1, Alvaro Miranda Aguilera
> wrote:
>>
>>
>> are you doing a macOS guest and you want to override the default gw there?
>>
>
> The guest is a Linux VM. The relevant part of my provision script is:
>
> route add default gw 192.168.222.1
> eval "$(route -n | awk '{ if ($8 =="enp0s3" && $2 != "0.0.0.0") print "route
> del default gw " $2; }')"
>
> 192.168.222.1 is the host IP address. The guest uses a private network;
> from the Vagrant file:
>
> c.vm.network "private_network", ip: "192.168.222.10"
>
> This all works on a Linux host. On a macOS host the guest is not able to
> connect to the internet after the default gw was changed.
>
>
>
> --
> 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/e31e7b26-0713-4b69-b749-d27c82d50b08%40googlegroups.com
> <https://groups.google.com/d/msgid/vagrant-up/e31e7b26-0713-4b69-b749-d27c82d50b08%40googlegroups.com?utm_medium=email_source=footer>
> .
> 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/CAHqq0ezpDC8Mwy_76vdB_iXsGeCcjhKC18t3UFA0J49Zms8qMw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] Bridged network with vmware workstation, windows guest

[Alvaro Miranda Aguilera]

the first nic is by default.

So you don't want to add a new nic, you can override the first one.

have a look at this:
https://superuser.com/questions/957631/how-to-force-vagrant-to-have-a-single-bridged-network-interface

Alvaro


On Mon, Nov 20, 2017 at 1:55 AM,  wrote:

> When I add this line to my vagrantfile:
>
> config.vm.network "public_network", bridge: "vmnet0"
>
> vagrant creates *second* adapter which is bridged.
> Both primary and secondary adaters seems to work fine in this
> configuration.
> I do not want second adapter I want the primary one to be bridged.
>
> How do I configure this?
>
> Vagrantfile to test:
>
> # -*- mode: ruby -*-
> # vi: set ft=ruby :
>
> Vagrant.configure("2") do |config|
>   config.vm.box = "StefanScherer/windows_2016_docker"
>
>   config.vm.network "public_network"
>   config.vm.provider :vmware_workstation do |v|
> v.gui = true
>   end
> end
>
>
>
> Cheers,
> Andrew
>
> --
> 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/f564595c-48f5-4dc3-ae48-067f09b2da0f%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/CAHqq0ezWPozZ42754SoeEweDbiko-pmpWyjPvy3QqMiYzhjhgA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] Broken routes with changed default router on macOS

[Alvaro Miranda Aguilera]

Hello

the documentation is just an example, different OS will require a different
route.

are you doing a macOS guest and you want to override the default gw there?

The first point will be check the documentation and came with the commands
you need

once you get the commands, Vagrant can run them for you. but came with the
commands require some trial try/error.

Alvaro.

On Mon, Nov 20, 2017 at 9:40 AM,  wrote:

> Hello,
>
> I change the default route in a VM as described here:
> https://www.vagrantup.com/docs/networking/public_
> network.html#default-router (i.e. `route add default gw  && route
> del default gw `).
>
> This works fine on Linux but not for macOS users: they loose connectivity
> to the internet with the change (host and guest can still connect though).
>
> Somebody knows the problem and a solution?
>
> Thanks,
> Michael
>
> --
> 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/d03310ea-a817-407c-a525-997cbed904c9%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/CAHqq0ezV%2BqK1VV5aK0ZW0JZgoeOpqBQDDX3_NdV3wd2gkA%3DXUQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] Re: Can't install vagrant-vmware-workstation 5.0.3

[Alvaro Miranda Aguilera]

Hello

Chris has been working hard on getting all the issues related to windows
solved.

We were able to replicate some of them on win10/win2016 domain, but some
others weren't possible to replicate at all.

so maybe are still some that we are working hard to catch up.

alvaro



On Thu, Nov 16, 2017 at 10:08 PM, Eric Beach <ebe...@gmail.com> wrote:

> So, I don't know what changed with 5.0.4, but this seems to have fixed the
> issue.  I was able to successfully install the plugin and it appears to be
> functioning normally.
>
> Thanks again!
>
> On Wednesday, November 15, 2017 at 2:53:26 PM UTC-5, Eric Beach wrote:
>>
>> Hey Alvaro,
>>
>> Thanks for getting back.
>>
>> I was re-running the command to provide a new debug for you and it
>> appears that 5.0.4 has released as well. It took a long time (with no
>> verbose output), but it appears the plugin finally installed with 5.0.4.
>>
>> I'll do some testing and see what happens.
>>
>> Thanks!
>>
>> On Wednesday, November 15, 2017 at 3:52:28 AM UTC-5, Alvaro Miranda
>> Aguilera wrote:
>>>
>>> Hello
>>>
>>> We haven't been able to reproduce this particular error.
>>>
>>> We did release 5.0.3 that includes the fix for the machine on the
>>> domain, but I am able to install and run VMs with either local user or
>>> domain user.
>>>
>>> Does the error happens at install time of the plugin or after the
>>> install on the vagrant commands?
>>>
>>> Can you share a verbose error? (just add --debug to the command)
>>>
>>> Also, some information.
>>>
>>> I am testing with win10 pro, english lang. windows 2016 AD domain.
>>>
>>> Thanks
>>> Alvaro
>>>
>>> On Tue, Nov 14, 2017 at 4:01 PM, Eric Beach <ebe...@gmail.com> wrote:
>>>
>>>> Unfortunately, no, not yet.   I was able to install with a local
>>>> account, but not with a domain account logged in.
>>>>
>>>> --
>>>> 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/ms
>>>> gid/vagrant-up/7e71859f-e16c-41c0-84dd-482be9571082%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/e7897e15-306c-49c9-b922-2a525a39ba3a%40googlegroups.com
> <https://groups.google.com/d/msgid/vagrant-up/e7897e15-306c-49c9-b922-2a525a39ba3a%40googlegroups.com?utm_medium=email_source=footer>
> .
> 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/CAHqq0eza9SzehOAG38ApALuOoVBe6tG7z%2B4UTxb54x6Y8QYc%3DA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] Configuring secondary network adapters through VMware on Windows is not yet supported

[Alvaro Miranda Aguilera]

Hello

is the VM a windows OS?

The message is this:

==> default: Configuring secondary network adapters through VMware  on
Windows is not yet supported.
==> default: You will need to manually configure the network adapter.

The idea is to tell windows os users that Vagrant will create the network
interface, but won't try to configure it with static info if present.

I think I see what you mean, I created this:
https://github.com/hashicorp/vagrant/issues/9192

Thanks
Alvaro.



On Thu, Nov 16, 2017 at 7:04 AM,  wrote:

> When I do `vagrant up`, I'm getting this:
>
> ==> default: Configuring network adapters within the VM...
> ==> default: Configuring secondary network adapters through VMware
> ==> default: on Windows is not yet supported. You will need to manually
> ==> default: configure the network adapter.
>
> *Can someone explain the meaning to me?*
>
> I don't think I *have *a secondary adapter. The VM seems to work as
> expected not problem.
>
> *Is it possible to switch off the warning?*
>
> Vagrantfile
>
> # -*- mode: ruby -*-
> # vi: set ft=ruby :
>
> Vagrant.configure("2") do |config|
>
>   config.vm.box = "E:\\mybox-0.1.0.box"
>
>   config.vm.provider :vmware_workstation do |v, override|
> v.gui = true
> v.vmx["ethernet0.addresstype"] = "generated"
> v.vmx["ethernet0.linkstatepropagation.enable"] = "FALSE"
> v.vmx["ethernet0.vnet"] = "vmnet8"
> v.whitelist_verified = true
>   end
> end
>
>
> mybox.vmx
>
> .encoding = "UTF-8"
> bios.bootorder = "hdd,CDROM"
> checkpoint.vmstate = ""
> cleanshutdown = "FALSE"
> config.version = "8"
> displayname = "TEST: default"
> ehci.pcislotnumber = "-1"
> ehci.present = "FALSE"
> ethernet0.addresstype = "generated"
> ethernet0.connectiontype = "nat"
> ethernet0.linkstatepropagation.enable = "FALSE"
> ethernet0.pcislotnumber = "192"
> ethernet0.present = "TRUE"
> ethernet0.virtualdev = "vmxnet3"
> ethernet0.vnet = "vmnet8"
> extendedconfigfile = "mybox.vmxf"
> filesearchpath = 
> ".;G:\.vagrant.d\boxes\E-VAGRANTCOLON-\Sources\packer\Templates\Vagrant
> VMWare Windows\box\vmware\mybox-0.1.0.box\0\vmware_desktop"
> floppy0.present = "FALSE"
> guestos = "windows9srv-64"
> gui.fitguestusingnativedisplayresolution = "FALSE"
> gui.fullscreenatpoweron = "FALSE"
> gui.viewmodeatpoweron = "windowed"
> hgfs.linkrootshare = "TRUE"
> hgfs.maprootshare = "TRUE"
> ide1:0.clientdevice = "TRUE"
> ide1:0.devicetype = "cdrom-raw"
> ide1:0.filename = "auto detect"
> ide1:0.present = "TRUE"
> isolation.tools.hgfs.disable = "FALSE"
> memsize = "8192"
> migrate.hostlog = ".\windows-2016-base-8bd188b6.hlog"
> monitor.phys_bits_used = "42"
> msg.autoanswer = "true"
> numa.autosize.cookie = "20001"
> numa.autosize.vcpu.maxpervirtualnode = "2"
> numvcpus = "2"
> nvram = "mybox.nvram"
> pcibridge0.pcislotnumber = "17"
> pcibridge0.present = "TRUE"
> pcibridge4.functions = "8"
> pcibridge4.pcislotnumber = "21"
> pcibridge4.present = "TRUE"
> pcibridge4.virtualdev = "pcieRootPort"
> pcibridge5.functions = "8"
> pcibridge5.pcislotnumber = "22"
> pcibridge5.present = "TRUE"
> pcibridge5.virtualdev = "pcieRootPort"
> pcibridge6.functions = "8"
> pcibridge6.pcislotnumber = "23"
> pcibridge6.present = "TRUE"
> pcibridge6.virtualdev = "pcieRootPort"
> pcibridge7.functions = "8"
> pcibridge7.pcislotnumber = "24"
> pcibridge7.present = "TRUE"
> pcibridge7.virtualdev = "pcieRootPort"
> policy.vm.mvmtid = ""
> powertype.poweroff = "soft"
> powertype.poweron = "soft"
> powertype.reset = "soft"
> powertype.suspend = "soft"
> proxyapps.publishtohost = "FALSE"
> remotedisplay.vnc.enabled = "false"
> remotedisplay.vnc.ip = "127.0.0.1"
> remotedisplay.vnc.key = "redacted"
> remotedisplay.vnc.password = "redacted"
> remotedisplay.vnc.port = "5900"
> replay.filename = ""
> replay.supported = "FALSE"
> scsi0.pcislotnumber = "160"
> scsi0.present = "TRUE"
> scsi0.saswwid = "50 05 05 69 2b 39 4c 70"
> scsi0.virtualdev = "lsisas1068"
> scsi0:0.filename = "disk-cl3.vmdk"
> scsi0:0.present = "TRUE"
> scsi0:0.redo = ""
> sharedfolder.maxnum = "1"
> softpoweroff = "FALSE"
> sound.startconnected = "FALSE"
> svga.guestbackedprimaryaware = "TRUE"
> tools.synctime = "TRUE"
> tools.upgrade.policy = "upgradeAtPowerCycle"
> usb.pcislotnumber = "-1"
> usb.present = "FALSE"
> uuid.action = "create"
> uuid.bios = "56 4d 21 59 2b 39 4c 79-ad f9 36 1a 34 a4 89 e1"
> uuid.location = "56 4d 21 59 2b 39 4c 79-ad f9 36 1a 34 a4 89 e1"
> vc.uuid = ""
> virtualhw.productcompatibility = "hosted"
> virtualhw.version = "11"
> vmci0.id = "1861462627"
> vmci0.pcislotnumber = "35"
> vmci0.present = "TRUE"
> vmotion.checkpointfbsize = "4194304"
> vmotion.checkpointsvgaprimarysize = "33554432"
> ethernet0.generatedAddress = "00:0c:29:a4:89:e1"
> ethernet0.generatedAddressOffset = "0"
> vm.genid = "4365688414994605568"
> vm.genidX = "6290051713079307348"
> unity.wasCapable = "TRUE"
> sharedFolder0.present = "TRUE"
> sharedFolder0.enabled = "TRUE"
> sharedFolder0.readAccess = "TRUE"
> 

Re: [vagrant-up] vagrantfile in boxes

[Alvaro Miranda Aguilera]

Hello

lets say your user is home is /home/user

and you have a project like this

/home/user/myproject

Vagrant home directory will be

/home/user/.vagrant.d

The box or your setup can include multiples Vagrantfiles that are all read
and joined in memory

/home/user/myproject/Vagrantfile  # this is your local project Vagrantfile,
things here are used only is this local project

/home/user/.vagrant.d/boxes///Vagrantfile  # this is
your box Vagrantfile , will be used in all the projects that use this box.

/home/user/.vagrant.d/Vagrantfile  # this is your global Vagrantfile , will
be used in all the projects


https://www.vagrantup.com/docs/vagrantfile/#lookup-path


Seems you are right that the box one is not in the documentation.
Will check and came back with something.



When a box includes a Vagrantfile, its to set something at box level, say
you don't want to use Virtualbox shared folder and want to use/force rsync.


Thats the one that packer can include.

ie:

$ find ~/.vagrant.d/boxes/ -name Vagrantfile
/c/Users/kikitux/.vagrant.d/boxes/bento-VAGRANTSLASH-ubuntu-16.04/201708.22.0/virtualbox/Vagrantfile
/c/Users/kikitux/.vagrant.d/boxes/centos-VAGRANTSLASH-7/1611.01/virtualbox/Vagrantfile
/c/Users/kikitux/.vagrant.d/boxes/ferventcoder-VAGRANTSLASH-win2012r2-x64-nocm/1.0.0/virtualbox/Vagrantfile
/c/Users/kikitux/.vagrant.d/boxes/hashicorp-VAGRANTSLASH-precise64/1.1.0/virtualbox/Vagrantfile
/c/Users/kikitux/.vagrant.d/boxes/iseo_tech-VAGRANTSLASH-CentOS-7-x86_64-DVD-1503-01/7.1.1/virtualbox/Vagrantfile
/c/Users/kikitux/.vagrant.d/boxes/oraclelinux7/0/virtualbox/Vagrantfile
/c/Users/kikitux/.vagrant.d/boxes/ubuntu-VAGRANTSLASH-trusty64/20171026.0.0/virtualbox/Vagrantfile



example of utilization:

$ cat
/c/Users/kikitux/.vagrant.d/boxes/centos-VAGRANTSLASH-7/1611.01/virtualbox/Vagrantfile
Vagrant.configure("2") do |config|
  config.vm.base_mac = "525400225b53"
  config.vm.synced_folder ".", "/vagrant", type: "rsync"
end






Alvaro.

On Thu, Nov 16, 2017 at 6:26 AM,  wrote:

> This page  on vagrant
> file format tells us:
>
> Today, there are three different components:
>>
>>-
>>
>>Box File - This is a compressed (tar, tar.gz, zip) file that is
>>specific to a single provider and can contain anything. Vagrant core does
>>not ever use the contents of this file. Instead, they are passed to the
>>provider. Therefore, a VirtualBox box file has different contents from a
>>VMware box file and so on.
>>-
>>
>>Box Catalog Metadata - This is a JSON document (typically exchanged
>>during interactions with HashiCorp's Vagrant Cloud
>>) that specifies the
>>name of the box, a description, available versions, available providers,
>>and URLs to the actual box files (next component) for each provider and
>>version. If this catalog metadata does not exist, a box file can still be
>>added directly, but it will not support versioning and updating.
>>-
>>
>>Box Information - This is a JSON document that can provide additional
>>information about the box that displays when a user runs vagrant box
>>list -i. More information is provided here
>>.
>>
>> Note, how vargrantfile is not mentioned anywhere in this description or
> elsewhere on the page.
>
> Yet, if we read this page
>  from packer
> documentation we can read:
>
> vagrantfile_template
>> 
>>  (string)
>> - Path to a template to use for the Vagrantfile that is packaged with the
>> box.
>
>
> This implies that a vagrantfile can indeed be packaged with the box.
>
> How does this work? Why one includes vagrantfile with a box and how this
> vagrantfile is used and how it interact with the normal vagrantfile which
> we are using with `vagrant up`?
>
> --
> 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/0248837a-7d7d-484d-8786-e8664b3e8eff%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Alvaro

-- 
This mailing list is governed under the 

Re: [vagrant-up] Detecting machine state in Vagrantfile

[Alvaro Miranda Aguilera]

Hello

There was an old email once that used ruby magic to detect if the id of the
vm existed, but i don't think is needed.

check for a local file, if doesn't exist, set those values.

and in a provision script, just do `touch /vagrant/.provisioned` or similar.

will be more easy to read.

My 2 cents

alvaro.

On Wed, Nov 15, 2017 at 3:42 PM, Sam Kaplan <stkap...@gmail.com> wrote:

> Not quite...I'm not worried about provisioning scripts in this case.
>
> I have a block in my Vagrantfile like:
>
>   config.vm.provider "virtualbox" do |vb|
> vb.cpus = ENV["VAGRANT_CPU"] || "2"
> vb.memory = ENV["VAGRANT_MEM"] || "2048"
>   end
>
> so you can specify cpu and memory size in environment variables. But this
> also means you have to specify them every time you boot the machine, or
> they will get overwritten by the defaults. If I had a way to detect that
> the machine was already created, then I could avoid setting the config
> values in that case.
>
> Thanks,
> Sam
>
> On Wednesday, November 15, 2017 at 3:46:37 AM UTC-5, Alvaro Miranda
> Aguilera wrote:
>>
>> Hello
>>
>> By default provisioning scripts only run at creation time.
>>
>> Next time you do vagrant up/reload the provisioning doesn't run at all.
>>
>> If there are some provisioning you want to have always to run, you can
>> add
>>
>> ,run: "always"
>>
>>
>> Does this helps?
>> Alvaro
>>
>> On Mon, Nov 13, 2017 at 9:50 PM, Sam Kaplan <stka...@gmail.com> wrote:
>>
>>>
>>> Hi,
>>>
>>> In a Vagrantfile, is it possible to detect whether a machine is already
>>> created? I'm trying to run a block of code only if "vagrant up" is creating
>>> a new box (and not when re-booting an existing one).
>>>
>>> Even a provider-specific method would be helpful -- I'm only using
>>> Virtualbox.
>>>
>>> Thanks,
>>> Sam
>>>
>>> --
>>> 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/ms
>>> gid/vagrant-up/c3ef20a6-5ef1-4253-a076-43d381bda8fe%40googlegroups.com
>>> <https://groups.google.com/d/msgid/vagrant-up/c3ef20a6-5ef1-4253-a076-43d381bda8fe%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>> 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/824fbc3f-d644-4230-bc95-a425543aca49%40googlegroups.com
> <https://groups.google.com/d/msgid/vagrant-up/824fbc3f-d644-4230-bc95-a425543aca49%40googlegroups.com?utm_medium=email_source=footer>
> .
>
> 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/CAHqq0eysO_gcTMrQX3rzqSAoxm8MpmxEsBU6wSHWTeMDaLC_CA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] Exec error: fork/exec /opt/vagrant/embedded/bin/ruby: no such file or directory

[Alvaro Miranda Aguilera]

hello

is anything in that path?

which vagrant
find  /opt/vagrant/embedded



On Wed, Nov 15, 2017 at 10:12 AM, Kelio  wrote:

>
> Hi,
>
>
> I have installed version 2.0.1-1 of vagrant on linux manjaro via Octopi.
>
> Any "vagrant" command give an error :
>
> Exec error: fork/exec /opt/vagrant/embedded/bin/ruby: no such file or
> directory
>
> I uninstall and reinstall but nothing is working.
>
> Thanks you for your help.
>
> --
> 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/7b74ec8d-33c0-4df4-a1b6-b6752860df04%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/CAHqq0ewKs0qhkXgSnrmCkpT-nXPx2DiSVOCVuDZjY%3D542fJhrA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] Re: Can't install vagrant-vmware-workstation 5.0.3

[Alvaro Miranda Aguilera]

Hello

We haven't been able to reproduce this particular error.

We did release 5.0.3 that includes the fix for the machine on the domain,
but I am able to install and run VMs with either local user or domain user.

Does the error happens at install time of the plugin or after the install
on the vagrant commands?

Can you share a verbose error? (just add --debug to the command)

Also, some information.

I am testing with win10 pro, english lang. windows 2016 AD domain.

Thanks
Alvaro

On Tue, Nov 14, 2017 at 4:01 PM, Eric Beach  wrote:

> Unfortunately, no, not yet.   I was able to install with a local account,
> but not with a domain account logged in.
>
> --
> 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/7e71859f-e16c-41c0-84dd-482be9571082%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/CAHqq0eyFn4bnehF5VzH%2Bn4JgOiyW8z%2Bpkxjbm7mZpjr8Q8PR%2BA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] Re: Can't install vagrant-vmware-workstation 5.0.3

[Alvaro Miranda Aguilera]

can you email supp...@hashicorp.com with a description on your setup?

Thanks
Alvaro

On Tue, Nov 14, 2017 at 8:07 AM, Arvind Prabhakar 
wrote:

> Did you get any solution to this issue? I'm having similar issue.
>
>
> On Friday, November 10, 2017 at 12:11:44 AM UTC+5:30, Eric Beach wrote:
>>
>> Attempting to install the plugin on a domain-joined computer with a
>> domain account fails.  I was able to install to the same computer running a
>> local account.
>>
>> PS C:\> vagrant plugin install vagrant-vmware-workstation
>> Installing the 'vagrant-vmware-workstation' plugin. This can take a few
>> minutes...
>> Fetching: vagrant-share-1.1.9.gem (100%)
>> Fetching: vagrant-vmware-workstation-5.0.3.gem (100%)
>> Building native extensions.  This could take a while...
>> Administator failed to take ownership of install directory
>> Bundler, the underlying system Vagrant uses to install plugins,
>> reported an error. The error is shown below. These errors are usually
>> caused by misconfigured plugin installations or transient network
>> issues. The error from Bundler is:
>>
>> ERROR: Failed to build gem native extension.
>>
>> current directory: C:/Users//.vagrant.d/gems/
>> 2.4.2/gems/vagrant-vmware-workstation-5.0.3/ext/vagrant-vmware-desktop
>> C:/HashiCorp/Vagrant/embedded/mingw64/bin/ruby.exe -r
>> ./siteconf20171109-5712-114qzcn.rb extconf.rb
>>
>> Folder: \
>> TaskName Next Run Time  Status
>>  ==
>> ===
>> vagrant-vmware-desktop--N/AReady
>> A subdirectory or file C:\ProgramData\HashiCorp\VagrantVMware\-\bin
>> already exists.
>> A subdirectory or file 
>> C:\ProgramData\HashiCorp\VagrantVMware\-\UserData
>> already exists.
>> 1 file(s) copied.
>> 1 file(s) moved.
>> processed file: C:\ProgramData\HashiCorp\VagrantVMware\-\UserData
>> Successfully processed 1 files; Failed processing 0 files
>> No mapping between account names and security IDs was done.
>> Successfully processed 0 files; Failed processing 0 files
>> 'Administrator"' is not recognized as an internal or external command,
>> operable program or batch file.
>> *** extconf.rb failed ***
>> Could not create Makefile due to some reason, probably lack of necessary
>> libraries and/or headers.  Check the mkmf.log file for more details.  You
>> may
>> need configuration options.
>>
>> Provided configuration options:
>> --with-opt-dir
>> --without-opt-dir
>> --with-opt-include
>> --without-opt-include=${opt-dir}/include
>> --with-opt-lib
>> --without-opt-lib=${opt-dir}/lib
>> --with-make-prog
>> --without-make-prog
>> --srcdir=.
>> --curdir
>> --ruby=C:/HashiCorp/Vagrant/embedded/mingw64/bin/$(RUBY_BASE
>> _NAME)
>>
>> extconf failed, exit code 1
>>
>> Gem files will remain installed in C:/Users//.vagrant.d/gems/
>> 2.4.2/gems/vagrant-vmware-workstation-5.0.3 for inspection.
>> Results logged to C:/Users//.vagrant.d/gems/
>> 2.4.2/extensions/x64-mingw32/2.4.0/vagrant-vmware-workstatio
>> n-5.0.3/gem_make.out
>>
> --
> 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/fe0ce4db-b45c-448a-912f-1167559987bd%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/CAHqq0exUmXochaVw4quudbd9ypoq7RefZP2AKm2g25pG9fUBeg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] Detecting machine state in Vagrantfile

[Alvaro Miranda Aguilera]

Hello

By default provisioning scripts only run at creation time.

Next time you do vagrant up/reload the provisioning doesn't run at all.

If there are some provisioning you want to have always to run, you can add


,run: "always"


Does this helps?
Alvaro

On Mon, Nov 13, 2017 at 9:50 PM, Sam Kaplan  wrote:

>
> Hi,
>
> In a Vagrantfile, is it possible to detect whether a machine is already
> created? I'm trying to run a block of code only if "vagrant up" is creating
> a new box (and not when re-booting an existing one).
>
> Even a provider-specific method would be helpful -- I'm only using
> Virtualbox.
>
> Thanks,
> Sam
>
> --
> 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/c3ef20a6-5ef1-4253-a076-43d381bda8fe%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/CAHqq0ex1tghQPwe0SZSKs0OcbvfsbPUD9F3Pv_%2Bz%2B0jozJYEpg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] 'vagrant up' is failing with the following errors--how can I troubleshoot?

[Alvaro Miranda Aguilera]

Hello

Try to use Virtualbox gui, and turn on/off/on VMs you see there.

The error is coming from VirtualBox, so Vagrant here is just failing.

If you can skip Vagrant you  may find what the issue is.

Which virtualbox version are you using?

Thanks
Alvaro

On Tue, Nov 14, 2017 at 6:18 PM, Carl Gross  wrote:

> Hello.  I recently had to re-install many programs on my computer (Win 10,
> x64), and VirtualBox was one of them.  I re-installed without issue, but am
> now encountering an error when running 'vagrant up' (Vagrant version
> 1.8.6).  The console output is:
>
> *$ vagrant up*
> *Bringing machine 'default' up with 'virtualbox' provider...*
> *==> default: Checking if box 'ubuntu/trusty64' is up to date...*
> *==> default: Clearing any previously set forwarded ports...*
> *==> default: Clearing any previously set network interfaces...*
> *==> default: Preparing network interfaces based on configuration...*
> *default: Adapter 1: nat*
> *default: Adapter 2: hostonly*
> *==> default: Forwarding ports...*
> *default: 22 (guest) =>  (host) (adapter 1)*
> *==> default: Running 'pre-boot' VM customizations...*
> *==> default: Booting VM...*
> *There was an error while executing `VBoxManage`, a CLI used by Vagrant*
> *for controlling VirtualBox. The command and stderr is shown below.*
>
> *Command: ["startvm", "09fb1b27-94cb-4eb8-9735-9c0dd82f5b49", "--type",
> "headless"]*
>
> *Stderr: VBoxManage.exe: error: The virtual machine 'sites' has terminated
> unexpectedly during startup with exit code 1 (0x1).  More details may be
> available in 'C:\Users\snarl\VirtualBox VMs\sites\Logs\VBoxHardening.log'*
> *VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component
> MachineWrap, interface IMachine*
>
> Per the suggestion, I opened VBoxHardening.log.  The last several lines
> are as follows:
>
> *2950.1f98: supR3HardenedMonitor_LdrLoadDll: pName=C:\Program
> Files\Oracle\VirtualBox\VBoxRT.dll (rcNtResolve=0xc0150008) *pfFlags=0x0
> pwszSearchPath=0001: [calling]*
> *2950.1f98: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0
> hMod=7ff8ab0c 'C:\Program Files\Oracle\VirtualBox\VBoxRT.dll'*
> *2950.1f98: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0
> hMod=7ff8ab0c 'C:\Program Files\Oracle\VirtualBox\VBoxRT.dll'*
> *2950.1f98: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0
> hMod=7ff8ab0c 'C:\Program Files\Oracle\VirtualBox\VBoxRT.dll'*
> *2950.1f98: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0
> hMod=7ff8ab0c 'C:\Program Files\Oracle\VirtualBox\VBoxRT.dll'*
> *2950.1f98: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0
> hMod=7ff8e68e 'C:\WINDOWS\system32\Wintrust.dll'*
> *2950.1f98: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0
> hMod=7ff8e4d8 'C:\WINDOWS\system32\rsaenh.dll'*
> *2950.1f98: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0
> hMod=7ff8e5be 'C:\WINDOWS\System32\crypt32.dll'*
> *2950.1f98: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0
> hMod=7ff8e4d8 'C:\WINDOWS\system32\rsaenh.dll'*
> *2950.1f98: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0
> hMod=7ff8e5be 'C:\WINDOWS\System32\crypt32.dll'*
> *2950.1f98: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0
> hMod=7ff8e5be 'C:\WINDOWS\system32\crypt32.dll'*
> *2950.1f98: Error -1912 in supR3HardenedMainInitRuntime! (enmWhat=4)*
> *2950.1f98: RTR3InitEx failed with rc=-1912*
> *2850.1818: supR3HardNtChildWaitFor[2]: Quitting: ExitCode=0x1
> (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 504 ms, the end);*
> *a80.26f4: supR3HardNtChildWaitFor[1]: Quitting: ExitCode=0x1
> (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 929 ms, the end);*
>
> Can anyone shed some light on this *Error -1912*?  Do I have any options
> other than uninstalling/re-installing Vagrant?
>
> Thanks in advance.
>
> --
> 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/466114b2-7a6a-41d2-95f4-c16be5c8fcda%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 

Re: [vagrant-up] SSH: * The following settings shouldn't exist: paranoid

[Alvaro Miranda Aguilera]

Please share the Vagrant file.

Or try this.

mkdir precise64
cd precise64
vagrant init -m hashicorp/precise64
vagrant up

if there are issues, do this

vagrant destroy

vagrant version
vagrant plugin list
vagrant up --debug

and share the output of the last 3 commands.

Thanks
alvaro

On Fri, Nov 10, 2017 at 5:37 PM, Gavin Power  wrote:

> Hi all,
>
> Can anyone help with this one? I have a default Vagrantfile (just with the
> base Vagrant image name changed). When I 'vagrant up' it downloads the
> required box and fails with this message:
>
>  INFO interface: error: There are errors in the configuration of this
> machine. Please fix
> the following errors and try again:
>
> SSH:
> * The following settings shouldn't exist: paranoid
>
> Not sure what is causing this. I have tried a few different base images
> and get the same message. Reinstalled vagrant, openssh-server and
> virtualbox but no change. Any ideas what is causing this?
>
> Kind regards
> Gavin
>
> --
> 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/dc5a4864-14b2-4282-b8ba-78b2bdb9a458%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/CAHqq0ewANA6FhC5zYapujFmn374U-JXxkxJBTPKV-p2Z%2Bhso3A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] Any google group on Packer?

[Alvaro Miranda Aguilera]

Hello

Yes, listed here:

https://www.packer.io/community.html

On Fri, Nov 10, 2017 at 8:04 PM, Joaquin Menchaca 
wrote:

>
> I just started getting into building vagrant boxes with packer.  Is there
> a google group for Packer?
>
> --
> 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/aa273474-741e-4956-b18d-6917f875a195%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/CAHqq0exY_rnmw%3DxOgLqbmXsP6CfTD72FR-PuDkM4HFw39u3sVQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] VMware Workstation plugin and Foreman Forklift vms all giving 1 GB of ram

[Alvaro Miranda Aguilera]

it seems you can use some configuration file and set memory values.

If the documentation is not clear, perhaps you can open a issue there and
ask for a working example?

https://github.com/theforeman/forklift/blob/master/boxes.yaml.example#L15

alvaro

On Wed, Nov 8, 2017 at 4:18 PM,  wrote:

> Hi,
>
> I use this to spin up boxes for testing foreman
> https://github.com/theforeman/forklift and im using vmware-workstation as
> the plugin, all the vms are getting built with 1gb of ram so it fails to
> install. What Vagrantfile would I add the vmx options too
> if I use the gem one it does nothing and when I add it to the box or the
> file they provide I get undefined method configure
>
> --
> 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/96f4d5c9-3fc8-4d22-aa9a-fbe08b22e485%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/CAHqq0eygVNiLGOx5%3DHT96B9Mc92GoO93JUUguEZF%2BEB4u8O-Rg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] Is there a way to programmatically take snapshots of my VM from the Vagrantfile?

[Alvaro Miranda Aguilera]

Hello

Perhaps you can use vagrant triggers? it will allow you run commands on
host before/after etc.


Have a look at the snapshot recipe here, it may need adjustment since
snapshot is now an internal feature so commands can be different:

https://github.com/emyl/vagrant-triggers/wiki/Trigger-recipes

Alvaro

On Wed, Nov 8, 2017 at 9:23 PM, Niko  wrote:

> Hello,
>
> I am trying to take a snapshot of my VM automatically before and after
> provisioning my box. Is there a way to do this without using a top level
> script?
>
> --Niko
>
> --
> 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/5106810d-50e7-494a-8bd9-41494a2ddaca%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/CAHqq0ew5%3DdYbScrt6m5FpYVQc0AuhR3UOidO3qvT1FK1_F%3D46g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.