Skip to content

Instantly share code, notes, and snippets.

@xypnox
Created March 4, 2019 14:04
Show Gist options
  • Save xypnox/bebd876544e0d3d75ead0d9448a60ffc to your computer and use it in GitHub Desktop.
Save xypnox/bebd876544e0d3d75ead0d9448a60ffc to your computer and use it in GitHub Desktop.
Vagrant output for suspend followed by up
xypnox-xps in ~/Submitty ⟩
(19:26:35) ⟨master → origin ✓⟩ ⟩ vagrant suspend
==> ubuntu-18.04: Saving VM state and suspending execution...
==> ubuntu-16.04: VM not created. Moving on...
==> debian: VM not created. Moving on...
xypnox-xps in ~/Submitty ⟩
(19:26:53) ⟨master → origin ✓⟩ ⟩ vagrant up
Bringing machine 'ubuntu-18.04' up with 'virtualbox' provider...
==> ubuntu-18.04: Checking if box 'bento/ubuntu-18.04' is up to date...
==> ubuntu-18.04: Resuming suspended VM...
==> ubuntu-18.04: Booting VM...
==> ubuntu-18.04: Waiting for machine to boot. This may take a few minutes...
ubuntu-18.04: SSH address: 127.0.0.1:2222
ubuntu-18.04: SSH username: vagrant
ubuntu-18.04: 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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment