Vagrantup does not progress from Connection timeout.Retrying...

I'm trying to launch vccw with "$vagrant up", but I can't proceed with "Connection timeout. Retrying..."

$vagrantup
Bringing machine 'default' up with 'virtualbox' provider...
==>default: Importing base box 'centos'...
==>default:Matching MAC address for NAT networking...
==>default:Setting the name of the VM:vagrant-wataca_default_1435643479833_86344
==>default: Clearing any previously set forwarded ports...
==>default: Fixed port collision for 22=>2222.Now on port 2200.
==>default: Clearing any previously set network interfaces...
==>default:Preparing network interfaces based on configuration...
default:Adapter 1:nat
==>default: Forwarding ports...
default:22=>2200(adapter1)
==>default: Booting VM...
==>default: Waiting for machine to boot. This may take a new minutes...
default:SSH address:127.0.0.1:2200
default:SSH username:vagrant
default:SSH auth method:private key
default:Warning:Connection timeout.Retrying...
default:Warning:Connection timeout.Retrying..

The error statements are as follows:

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 always good hits as to what may be wrong.

If you're using a custom box, make sure that networking is proper
working and you're able to connect to the machine.It is a common
problem that networking isn't setup proper in these boxes.
Verify that authentication configurations are also setup proper,
as well.

If the boxappears to be booting properly, you may want to increase
the timeout("config.vm.boot_timeout") value.

Rewriting config.vm.boot_timeout to 10 seconds → 120 seconds changed the message to the following:

The guest machine entered an invalid state while waiting for it
to boot.Valid states are 'starting, running'.The machine is in the
'poweroff' state.Please verify everything is configured
property and try again.

If the provider you're using has a GUI that comes with it,
It is helpful to open that and watch the machine, since the
GUI often has more helpful error messages than Vagrant can retrieve.
For example, if you're using VirtualBox, run vagrant up while the
VirtualBox GUI is open.

You cannot connect with "vagrant ssh" after "vagrant up".

Other Vagrant files are experiencing similar problems, so

I'm wondering if the SSH configuration is missing around VirtualBox, but I'm at a loss as to how to look into it in the future.

I think it's quite a basic mistake, but I'd appreciate it if you could give me some advice.