For what it's worth, I just started having this problem as well. I try to
post that debug output tomorrow if no one beats me to it. Yay Microsoft
QA...
On Thursday, March 16, 2017 at 3:47:18 PM UTC-4, Alvaro Miranda Aguilera
wrote:
>
> hello
>
> try this
>
> vagrant halt
>
> then go to virtualbox gui, and try to start the vm from there
>
> it may help as will give you more information
>
> From vagrant side try this
>
> vagrant version
> vagrant plugin list
> mkdir precise64
> cd precise64
> vagrant init -m hashicorp/precise64
> set VAGRANT_LOG=debug
> vagrant up
>
> and share all the generated verbose output
>
> thanks
>
> Alvaro
>
> On Thu, Mar 16, 2017 at 10:48 AM, Tony Toth <tonyto...@gmail.com
> <javascript:>> wrote:
>
>> Hello,
>> I recently updated my windows 10, vagrant and virtualbox and my vagrant
>> won't boot anymore.
>> The warning I get is:
>> "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.
>>
>> If you look above, you should be able to see the error(s) that
>> Vagrant had when attempting to connect to the machine. These errors
>> are usually good hints as to what may be wrong.
>>
>> If you're using a custom box, make sure that networking is properly
>> working and you're able to connect to the machine. It is a common
>> problem that networking isn't setup properly in these boxes.
>> Verify that authentication configurations are also setup properly,
>> as well.
>>
>> If the box appears to be booting properly, you may want to increase
>> the timeout ("config.vm.boot_timeout") value."
>> I also tried to increase the boot_timeout but it doesn't work.
>> Can anyone help me with 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+...@googlegroups.com <javascript:>.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/vagrant-up/157f3159-abfe-4b10-bcec-dec4b92689f4%40googlegroups.com
>>
>> <https://groups.google.com/d/msgid/vagrant-up/157f3159-abfe-4b10-bcec-dec4b92689f4%40googlegroups.com?utm_medium=email&utm_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/023d79e7-b7d6-469a-8d80-5ae1daca6022%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
