VMware: Fedora 23 box builds but can't connect

[juliandunn]

Per discussion with @cheeseplus both of us have experienced a problem with the Fedora 23 VMWare Fusion/Workstation box; it can be built from the definitions here, but will never start in Vagrant. Capturing the issue here.

[edude03]

I just ran into this today as well. Surprised it's been happening since January.

[cheeseplus]

Example failure via test-kitchen

-----> Cleaning up any prior instances of <default-fedora-23-vmware-fusion>
-----> Destroying <default-fedora-23-vmware-fusion>...
       Finished destroying <default-fedora-23-vmware-fusion> (0m0.00s).
-----> Testing <default-fedora-23-vmware-fusion>
-----> Creating <default-fedora-23-vmware-fusion>...
       Bringing machine 'default' up with 'vmware_fusion' provider...
       ==> default: Box 'bento-fedora-23' could not be found. Attempting to find and install...
           default: Box Provider: vmware_desktop, vmware_fusion, vmware_workstation
           default: Box Version: >= 0
       ==> default: Box file was not detected as metadata. Adding it directly...
       ==> default: Adding box 'bento-fedora-23' (v0) for provider: vmware_desktop, vmware_fusion, vmware_workstation
           default: Unpacking necessary files from: file:///usr/local/var/buildkite-agent/builds/titan.local-1/chef/bento/builds/fedora-23-2.2.6.git.ae400746e31910493d31f6bf37b1f0154944cfac_dirty.vmware.box
==> default: Successfully added box 'bento-fedora-23' (v0) for 'vmware_desktop'!
       ==> default: Cloning VMware VM: 'bento-fedora-23'. This can take some time...
       ==> default: Verifying vmnet devices are healthy...
       ==> default: Preparing network adapters...
       ==> default: Starting the VMware VM...
       ==> default: Waiting for machine to boot. This may take a few minutes...
       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.
-----> Destroying <default-fedora-23-vmware-fusion>...
       Finished destroying <default-fedora-23-vmware-fusion> (0m0.00s).