ich meine Microsoft Windows 10 aktualisiert haben, und versucht, die virtuelle Maschine laufen zu lassen, aber es hielt mich thrownig den gleichen Fehler an, wie oft ‚Zeitüberschreitung beim für die Maschine warten die Möglichkeiten zu booten‘, habe alles, was ich versuche, gui ermöglicht, den Timeout-Wert zu erhöhen und sogar die vagabundierende und Virtual BoxVagabund ‚Zeitüberschreitung beim für die Maschine warten zu starten‘ 10 in den Fenstern
C:\Users\tmsfi\fullstack-nanodegree-vm\vagrant>vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'bento/ubuntu-16.04-i386' is up to date...
==> default: There was a problem while downloading the metadata for your box
==> default: to check for updates. This is not an error, since it is usually
due
==> default: to temporary network problems. This is just a warning. The
problem
==> default: encountered was:
==> default:
==> default: Could not resolve host: vagrantcloud.com
==> default:
==> default: If you want to check for box updates, verify your network
connection
==> default: is valid and try again.
==> 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: 8000 (guest) => 8000 (host) (adapter 1)
default: 8080 (guest) => 8080 (host) (adapter 1)
default: 5000 (guest) => 5000 (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.
C:\Users\tmsfi\fullstack-nanodegree-vm\vagrant>vagrant ssh
ssh_exchange_identification: read: Connection reset by peer
mir aktualisiert Bitte helfen, dieses Problem zu lösen, Vielen Dank im Voraus
Meghana
Mögliche Duplikat [Get Nachricht Zeit, wenn vagrant bis auf Windows 10 zu tun versuchen - aber keine Fehler] (https://stackoverflow.com/questions/36569157/get-time- out-message-when-versuchen-to-do-Vagabund-up-on-Fenster-10-aber-nicht-Fehler) –
Dank @DanilaSmirnov –