Vagrant installer for 5.0.4-r1 is not working on Windows 10

[cdw9]

We are testing the installer to make sure it works for anyone that wants to try it out at PyCon. Our QA engineer ran into the following problems:

vagrant up hangs:

C:\Users\clsha\Projects\plonedev.vagrant-master>cd plonedev.vagrant-master

C:\Users\clsha\Projects\plonedev.vagrant-master\plonedev.vagrant-master>vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'ubuntu/trusty32'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'ubuntu/trusty32' is up to date...
==> default: Setting the name of the VM: plonedevvagrant-master_default_1461950087258_41522
==> 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: Forwarding ports...
    default: 8080 (guest) => 8080 (host) (adapter 1)
    default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> 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: private key
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.

vagrant ssh doesn't work:

C:\Users\clsha\Projects\plonedev.vagrant-master\plonedev.vagrant-master>vagrant ssh
ssh_exchange_identification: read: Connection reset by peer

vagrant global-status shows:

C:\Users\clsha\Projects\plonedev.vagrant-master\plonedev.vagrant-master>vagrant global-status
id       name    provider   state   directory
------------------------------------------------------------------------------------------------------------
539199a  default virtualbox running C:/Users/clsha/Projects/plonedev.vagrant-master/plonedev.vagrant-master

[smcmahon]

It looks like your guest machine is not even booting. So, it's not even getting to the Plone provisioning. Have you tried simply bringing up a clean Vagrant box?

In a new directory:

vagrant init ubuntu/trusty32 vagrant up

[clshaw01]

Both hang when they reach:

==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 127.0.0.1:2200
    default: SSH username: vagrant
    default: SSH auth method: private key

[smcmahon]

That problem has to be solved first. If Vagrant isn't running, we can't use it to run Plone :)