Re: [vagrant-up] Vagrant update to 1.92 timeout after windows update

2017-03-23 Thread Mike Thomsen
I have tried the latest, the 5.14 and the last stable build of 5.0. It's clearly not an issue with just having an old version because they all work the same way here. On Wednesday, March 22, 2017 at 3:40:08 PM UTC-4, Alvaro Miranda Aguilera wrote: > > ensure you are on latest virtualbox > > On

Re: [vagrant-up] Synced Folders not created

2017-03-23 Thread Alvaro Miranda Aguilera
Hello, I can't even start the VM. Does this happen only with box? kikitux@alvaro MINGW64 ~/iseo $ vagrant up Bringing machine 'default' up with 'virtualbox' provider... ==> default: Importing base box 'iseo_tech/CentOS-7-x86_64-DVD-1503-01'... ==> default: Matching MAC address for NAT

Re: [vagrant-up] Synced Folders not created

2017-03-23 Thread Chantal Tremblay
Hi, 1. Yes the folder exist on the host 2. Here's a part of the code I have in the vagrant file: config.vm.box = "iseo_tech/CentOS-7-x86_64-DVD-1503-01" config.vm.provider "virtualbox" do |vb| vb.customize ["modifyvm", :id, "--name", "mysite", "--memory", "2048"] vb.customize ["modifyvm", :id,

Re: [vagrant-up] Vagrant hangs when bringing up hosts in parallel.

2017-03-23 Thread Alvaro Miranda Aguilera
hello did you try this? http://stackoverflow.com/questions/28864603/specify-no-parallel-flag-inside-vagrantfile Virusvrij. www.avast.com

Re: [vagrant-up] Re: Wrong folder path for default synced vagrant dir for windows 7

2017-03-23 Thread Arkadiusz Bicz
Thank you very much Alvaro, I confirm it is working fine with virtualbox 5.1.18 On Wed, Mar 22, 2017 at 8:37 PM, Alvaro Miranda Aguilera wrote: > hi, check you are on latest virtualbox 5.1.18 or 5.1.14, it seems there is > an issue on .16 > > >

[vagrant-up] Vagrant hangs when bringing up hosts in parallel.

2017-03-23 Thread Krist van Besien
Hello, If I do this: vagrant up gluster-{1..5} the boxes are brought up in parallel, and this almost always ends up hanging somewhere, usually during provisioning of one of the machines, or waiting for ssh If I do: for h in gluster-{1..5}; do vagrant up $h ; done the hosts all get booted