config.vm.box_check_update = false
--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/bb4907db-8145-46d2-b44a-9c429649b075%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
DEBUG command: Finding machine that match name: buildINFO loader: Set :root = ["#<Pathname:C:/work/projects/swr-puppet/control-repo-ssdc/Vagrantfile>"]DEBUG loader: Populating proc cache for #<Pathname:C:/work/projects/swr-puppet/control-repo-ssdc/Vagrantfile>DEBUG loader: Load procs for pathname: C:/work/projects/swr-puppet/control-repo-ssdc/VagrantfileINFO loader: Loading configuration in order: [:home, :root]DEBUG loader: Loading from: root (evaluating)DEBUG loader: Configuration loaded successfully, finalizing and returningDEBUG push: finalizingINFO loader: Set "36435876_machine_build" = ["[\"2\",#<Proc:0x3271848@C:/work/projects/swr-puppet/control-repo-ssdc/Vagrantfile:138>]"]DEBUG loader: Populating proc cache for ["2",#<Proc:0x3271848@C:/work/projects/swr-puppet/control-repo-ssdc/Vagrantfile:138>]INFO loader: Loading configuration in order: [:home, :root, "36435876_machine_build"]DEBUG loader: Loading from: root (cache)DEBUG loader: Loading from: 36435876_machine_build (evaluating)DEBUG loader: Configuration loaded successfully, finalizing and returningDEBUG push: finalizing***HANGS HERE***
DEBUG base: Windows, checking for VBoxManage on PATH firstINFO base: VBoxManage path: C:/Program Files/Oracle/VirtualBox/VBoxManage.exeINFO subprocess: Starting process: ["C:/Program Files/Oracle/VirtualBox/VBoxManage.exe", "--version"]INFO subprocess: Command not in installer, restoring original environment...DEBUG subprocess: Selecting on IODEBUG subprocess: stdout: 5.1.10r112026DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000DEBUG subprocess: Exit status: 0
helloAss this and check if helps:config.vm.box_check_update = false
if not, try to setup verbose loggingset VAGRANT_LOG=debugorexport VAGRANT_LOG=debugand do a Vagrant up on vpnThanksAlvaro
On Fri, Mar 24, 2017 at 9:12 PM, William Saxton <sax...@gmail.com> wrote:
When I connect into my company VPN (which lives behind a proxy) and do "vagrant up" on one of my VM's, there is a long delay (couple minutes) before the:Bringing machine 'example' up with 'virtualbox' provider...appears. I'm guessing vagrant tries to do something "networky" and eventually has to time out before proceeding. Any idea what this could be? I'm wondering if there is something I can configure in my Vagrantfile to stop this from happening.Its just a slight nuisance.
--
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/bb4907db-8145-46d2-b44a-9c429649b075%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--Alvaro