Welcome to the Linux Foundation Forum!

Vagrant timeout

Hello I am trying to launch the VM on Mac OS X High Sierra 10.13.6 with vagrant version 2.2.2 and virtualbox version 6.0 but I keep getting the following error even though i increased the boot timeout to 15 minutes.

  1. ~/fabric-fundamentals > vagrant up
  2. Bringing machine 'default' up with 'virtualbox' provider...
  3. ==> default: Importing base box 'fabric-fundamentals'...
  4. ==> default: Matching MAC address for NAT networking...
  5. ==> default: Setting the name of the VM: fabric-fundamentals_default_1546978822486_40874
  6. ==> default: Clearing any previously set network interfaces...
  7. ==> default: Preparing network interfaces based on configuration...
  8. default: Adapter 1: nat
  9. ==> default: Forwarding ports...
  10. default: 3000 (guest) => 3000 (host) (adapter 1)
  11. default: 3333 (guest) => 3333 (host) (adapter 1)
  12. default: 8080 (guest) => 8080 (host) (adapter 1)
  13. default: 22 (guest) => 2222 (host) (adapter 1)
  14. ==> default: Running 'pre-boot' VM customizations...
  15. ==> default: Booting VM...
  16. ==> default: Waiting for machine to boot. This may take a few minutes...
  17. default: SSH address: 127.0.0.1:2222
  18. default: SSH username: vagrant
  19. default: SSH auth method: private key
  20. Timed out while waiting for the machine to boot. This means that
  21. Vagrant was unable to communicate with the guest machine within
  22. the configured ("config.vm.boot_timeout" value) time period.
  23.  
  24. If you look above, you should be able to see the error(s) that
  25. Vagrant had when attempting to connect to the machine. These errors
  26. are usually good hints as to what may be wrong.
  27.  
  28. If you're using a custom box, make sure that networking is properly
  29. working and you're able to connect to the machine. It is a common
  30. problem that networking isn't setup properly in these boxes.
  31. Verify that authentication configurations are also setup properly,
  32. as well.
  33.  
  34. If the box appears to be booting properly, you may want to increase
  35. the timeout ("config.vm.boot_timeout") value.

Welcome!

It looks like you're new here. Sign in or register to get started.
Sign In

Comments

  • I was able to get it working by downgrading virtualbox version to 5.2.2

  • Hi All,

    Just wanted to drop a note that I was having the same issues and browsed a bunch of different resources trying to find what the issue was. I downgraded my virtualbox from 6.0.x to 5.2.2 as well and was able to boot my VM with no issues. I also had my Windows firewall disabled, but I don't think that played a role. This was on Windows 10.

  • I had same issue, downgrading virtualbox to 5.2 solved it for me. The course guidelines should be updated as this is not intuitive to understand by oneself.

  • Posts: 4

    Hello,
    I am having the same issue.
    I was able to solve it from switching VirtualBox version back from 6.1.10 to 5.2.42.

    It would be really helpful to mention that in the guidelines. So I have wasted much time.

  • Posts: 4
    edited September 2020

    Same for me, downgrading Virtualbox 6 to 5 did the trick. Please update your Lab 1 material and mention this!

Welcome!

It looks like you're new here. Sign in or register to get started.
Sign In

Welcome!

It looks like you're new here. Sign in or register to get started.
Sign In

Categories

Upcoming Training