Looking at the output of vagrant ssh-config reveals a major difference between the two though:įor the working Xenial / Bionic VMs, the private key file used is one created at the project level: vagrant ssh-config The timeout ("config.vm.boot_timeout") value.īut doing the same process with xenial and bionic works fine, I can start the VMs and SSH into them just fine. If the box appears to be booting properly, you may want to increase Verify that authentication configurations are also setup properly, Problem that networking isn't setup properly in these boxes. Working and you're able to connect to the machine. If you're using a custom box, make sure that networking is properly These errorsĪre usually good hints as to what may be wrong. Vagrant had when attempting to connect to the machine. If you look above, you should be able to see the error(s) that The configured ("config.vm.boot_timeout" value) time period. Vagrant was unable to communicate with the guest machine within Timed out while waiting for the machine to boot. => default: Running 'pre-boot' VM customizations. => default: Preparing network interfaces based on configuration.ĭefault: 22 (guest) => 2205 (host) (adapter 1) => default: Clearing any previously set network interfaces. => default: Fixed port collision for 22 => 2222. => default: Checking if box 'ubuntu/focal64' version '20200720.0.0' is up to date.
=> default: Matching MAC address for NAT networking. => default: Importing base box 'ubuntu/focal64'.
When I try to bring the focal VM up with vagrant up the process gets stuck on the default: SSH auth method: private key and eventually times out: vagrant upīringing machine 'default' up with 'virtualbox' provider. nfigure(VAGRANTFILE_API_VERSION) do |config| Xenial and Bionic VMs are created fine and I can SSH into them, but I can't SSH into Focal ones. I need to run VMs with different versions of Ubuntu: 16.04 (xenial), 18.04 (bionic) and 20.04 (focal). I'm running Vagrant 2.2.9 using Virtualbox 6.1.12.
0 kommentar(er)
