Hello, It will help to have ssh sooner on first boot, so vagrant up won't error.
Alvaro. On Thu, Mar 17, 2016 at 9:09 PM, Bryan Berry <[email protected]> wrote: > Tks for your quick response Alvaro, > > I'm not sure changing services to delayed start would help. I can ssh into > the windows long before `vagrant up` times out. in fact, i only have to > wait a minute or two after startup whereas `vagrant up` takes ~ 10 minutes > to time out. > > On Thu, Mar 17, 2016 at 3:05 PM, Alvaro Miranda Aguilera < > [email protected]> wrote: > >> Hello, >> >> In Windows server, change all the services from Start to Delayed Start. >> >> That will be start the non-essential services after the boot. >> >> That will cut down the time to get ssh working, and Vagrant should boot >> just fine after that. >> >> If the service is essential, it won't allow you put it as delayed, so you >> can be confident changing as many services as possible. >> >> Alvaro. >> >> >> On Thu, Mar 17, 2016 at 8:22 PM, Bryan Berry <[email protected]> >> wrote: >> >>> Folks, >>> >>> I have an odd issue when executing `vagrant up` for a windows server >>> 2012 guest using SSH as the communicator. The guest UI boots up fine but >>> `vagrant up` hangs and ultimately fails w/ the error: >>> >>> hitman@localhost:~/tmp/cycle-vbox/tmp$ vagrant up >>> Bringing machine 'default' up with 'virtualbox' provider... >>> ==> 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) => 2222 (host) (adapter 1) >>> ==> default: Booting VM... >>> ==> default: Waiting for machine to boot. This may take a few minutes... >>> default: SSH address: 127.0.0.1:2222 >>> default: SSH username: vagrant >>> default: SSH auth method: password >>> INFO interface: Machine: error-exit ["Vagrant::Errors::VMBootTimeout"] >>> 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 fails, i can successfully execute `vagrant ssh` to get a >>> login shell into the same machine. I can also ssh into it (using port 2222) >>> using the ssh command directly. However, >>> vagrant halt and vagrant reload do nothing. >>> >>> `vagrant up` works when I change the communicator to winrm >>> >>> here are the details of my setup >>> >>> - host: mac os x 10.9.5 >>> - virtualbox 5.0.16 >>> - vagrant 1.8.1 >>> - guest os windows server 2012 R2 eval >>> - bitvise SSH server in guest >>> >>> The bitvise SSH server shows my host connected to the guest while >>> `vagrant up` hangs >>> >>> >>> Here are the important bits in my Vagrantfile >>> >>> >>> Vagrant.configure(2) do |config| >>> config.vm.guest = :windows >>> config.vm.box = "cycle-win2k12" >>> # config.vm.communicator = >>> "ssh" >>> >>> config.vm.communicator = "winrm" >>> config.ssh.insert_key = false >>> config.ssh.username = 'vagrant' >>> config.ssh.password = 'vagrant' >>> >>> config.vm.provision "shell", inline: 'echo hello world' >>> >>> end >>> >>> >>> I realize that this is likely a virtualbox error. For that reason, I >>> have tried reinstalling virtualbox and rebooted, to no success. I also see >>> no errors in the VBox.log for my machine >>> >>> >>> Any suggestions folks have would be most appreciated. >>> >>> >>> -- >>> 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 [email protected]. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/vagrant-up/eba201c0-f61a-4a4f-be39-cccbea0e1bf8%40googlegroups.com >>> <https://groups.google.com/d/msgid/vagrant-up/eba201c0-f61a-4a4f-be39-cccbea0e1bf8%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> 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 a topic in the >> Google Groups "Vagrant" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/vagrant-up/oFvBvjNoH04/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/vagrant-up/CAHqq0ewadsRrNkwLvyxdkW7EXG2jezmn0qh60U_z-GbujiAD6Q%40mail.gmail.com >> <https://groups.google.com/d/msgid/vagrant-up/CAHqq0ewadsRrNkwLvyxdkW7EXG2jezmn0qh60U_z-GbujiAD6Q%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> >> 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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/vagrant-up/CANsX4xSj1j%3Dg2MbiO7zx9uTFE4jE8X1c4a317r%3Daog33QwKpKg%40mail.gmail.com > <https://groups.google.com/d/msgid/vagrant-up/CANsX4xSj1j%3Dg2MbiO7zx9uTFE4jE8X1c4a317r%3Daog33QwKpKg%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CAHqq0ey4XaXFOJZNQQV8YmDD11c-rG0rQDD9FBgxOnEc51W6UQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
