Hi all, On Friday, I was trying to bring up the GPII Windows vagrant VM but was getting stuck and hitting a timeout.
Details: - Vagrant: 1.97 - VirtualBox: 5.1.22 - Host OS: Ubuntu 16.04 - Vagrantfile: https://github.com/GPII/windows/blob/master/Vagrantfile - Box: inclusivedesign/windows10-eval-x64-Apps - Box versions: 2017.05.05 and 2017.07.15 I was getting stuck at this point: ==> default: Booting VM... ==> default: Waiting for machine to boot. This may take a few minutes... default: WinRM address: 127.0.0.1:5985 default: WinRM username: vagrant default: WinRM execution_time_limit: PT2H default: WinRM transport: negotiate 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. I tried increasing the timeout, but after 30mins it was still stuck at this point. I noticed that where I'm currently working, I have an IPv6 network address and wondered if that could be a factor. I disconnected from the network and then brought up the box -- I was able to get past the point where I was stuck. I wasn't able to actually provision, of course, as I didn't have network but it looks like there's an issue making the WinRM connection with an IPv6 network address. I'm seeing this with both the 2017.05.05 and 2017.07.15 versions of inclusivedesign/windows10-eval-x64-Apps. Perhaps related: https://github.com/mitchellh/vagrant/issues/8759 Simon _______________________________________________ Architecture mailing list [email protected] http://lists.gpii.net/mailman/listinfo/architecture
