Estoy empezando a migrar de wamp a la caja vagabunda de laravel homestead, sin embargo, me quedé perplejo a la hora de iniciar la caja. Descargué y configuré todos los activos y ejecuté vagrant up para iniciar la caja; sin embargo, aquí está el resultado de vagrant up:
$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'laravel/homestead' is up to date...
==> 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: Adapter 2: hostonly
==> default: Forwarding ports...
default: 80 => 8000 (adapter 1)
default: 3306 => 33060 (adapter 1)
default: 5432 => 54320 (adapter 1)
default: 22 => 2200 (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:2200
default: SSH username: vagrant
default: SSH auth method: private key
default: Warning: Connection timeout. Retrying...
default: Warning: Connection timeout. Retrying...
default: Warning: Connection timeout. Retrying...
default: Warning: Connection timeout. Retrying...
default: Warning: Connection timeout. Retrying...
default: Warning: Connection timeout. Retrying...
default: Warning: Connection timeout. Retrying...
default: Warning: Connection timeout. Retrying...
default: Warning: Connection timeout. Retrying...
default: Warning: Connection timeout. Retrying...
default: Warning: Connection timeout. Retrying...
default: Warning: Connection timeout. Retrying...
default: Warning: Connection timeout. Retrying...
default: Warning: Connection timeout. Retrying...
default: Warning: Connection timeout. Retrying...
default: Warning: Connection timeout. Retrying...
default: Warning: Connection timeout. Retrying...
default: Warning: Connection timeout. Retrying...
default: Warning: Connection timeout. Retrying...
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.
Aquí está el resultado de la parada vagabunda:
$ vagrant halt
==> default: Attempting graceful shutdown of VM...
default: Guest communication could not be established! This is usually because
default: SSH is not running, the authentication information was changed,
default: or some other networking issue. Vagrant will force halt, if
default: capable.
==> default: Forcing shutdown of VM...
Parece que el problema puede estar al abrir SSH. Las respuestas aquíhttps://stackoverflow.com/questions/22575261/vagrant-stuck-connection-timeout-retryingNo ayudó a pesar de que parece ser un problema similar.
Estoy ejecutando Windows 8.1.
Respuesta1
El tiempo de espera de la conexión SSH durante la fase de arranque puede ocurrir por diferentes motivos, como:
- El sistema espera la interacción del usuario (p. ej.la partición compartida no está lista),
sshdmala configuración,- mala configuración del firewall (en caso de que no sea local),
- falta de coincidencia de su clave privada,
- el proceso de arranque lleva demasiado tiempo (intente aumentar
config.vm.boot_timeout), - compruebe si la virtualización está habilitada en el BIOS (segúncomentario).
Para depurar el problema, ejecútelo como:
VAGRANT_LOG=debug vagrant up
Si no hay nada obvio, intente conectarse desde otro terminal, mediante vagrant ssho mediante:
vagrant ssh-config > vagrant-ssh; ssh -F vagrant-ssh default
Si SSH aún falla, vuelva a ejecutarlo conuna interfaz gráfica de usuario(p.ej config.gui = true).
Si no es así, verifique los procesos en ejecución (por ejemplo, mediante: vagrant ssh -c 'pstree -a') o verifique su sshd_config.
Si es una máquina virtual desechable, siempre puedes destroyusarla una y upotra vez. También considere actualizar su Vagrant y Virtualbox.