Timeout error when vagrant up

[carma12]

Debug output

https://gist.github.com/carma12/996816f66affb0296b2fc936d6a5dd0d

Expected behavior

The VM with the given configuration should be up with no errors at the end of vagrant up execution.

Actual behavior

VM throws a timeout error when executing vagrant up with a given configuration (replacing the config.vm.box by fedora/40-cloud-base). Vagrant and VboxManage dependencies contain latest versions (Vagrant 2.4.6 and 7.1.10r169112 respectively).

Reproduction information

Vagrant version

Vagrant 2.4.6

Host operating system

Fedora 42

Guest operating system

fedora/40-cloud-base

Steps to reproduce

1. Do vagrant up with the Vagrantfile described below

Vagrantfile

Simplified version of the original Vagrantfile (fails on both):

# -*- mode: ruby -*-
# vi: set ft=ruby :

Vagrant.configure("2") do |config|
  config.vm.hostname = "server.ipa.demo"
  config.vm.box = "fedora/40-cloud-base"
end

[carma12]

After a failed execution, this is the output from vagrant ssh-config command:

Host default
  HostName 127.0.0.1
  User vagrant
  Port 2222
  UserKnownHostsFile /dev/null
  StrictHostKeyChecking no
  PasswordAuthentication no
  IdentityFile /home/carlmart/.vagrant.d/insecure_private_keys/vagrant.key.ed25519
  IdentityFile /home/carlmart/.vagrant.d/insecure_private_keys/vagrant.key.rsa
  IdentitiesOnly yes
  LogLevel FATAL
  PubkeyAcceptedKeyTypes +ssh-rsa
  HostKeyAlgorithms +ssh-rsa

[taru-garg-hashicorp]

Hi @carma12,

Thanks for the detailed report on the issue, I can confirm using an amd64 based Windows 11 I am able to reproduce this issue.

Since, ssh triggered during provision step from vagrant up command was failing I loaded the Virtualbox UI and I was able to then login using username as vagrant and password as vagrant, checking the ssh.d service status, it seems the virtual machine reports that it is up and running, but even with that Vagrant isn't able to ssh, I tried directly ssh'ing into the machine using ssh [email protected] -p 2222 even that seems to be failing, so I have a suspicion that somehow the port-forwarding is not working. I will investigate further and let you know, but in the meantime if you want you can use the machine directly via the UI once Vagrant has downloaded it.

Update: The issue seems with the box itself, I tested another box from fedora - fedora/41-cloud-base (with a static ip and public network) that seems to come up fine. Can you try changing the box to the newer ( fedora/41-cloud-base ) and see if it works ? I also tried installing net-tools on the box, and then connecting to it via the local ip the machine was assigned with ssh [email protected] -p 22, that also seems to work correctly, so I think my initial suspicion of somehow port forwarding not working is correct, although when running VBoxManage showvminfo <VM-Name> I do see that according to Virtual Box at least the port forwarding has been setup correctly. I also found this StackOverflow answer which hints at port forwarding not working, although I haven't tried the solution recommend there.

Update: I was also able to test with bento/fedora-40 machine and that works perfectly, so in case changing the version is not possible I would recommend using the bento/fedora-40 box.

Thanks!

[taru-garg-hashicorp]

Hi! I am closing this issue, as there hasn't been any activity on it, please feel free to open a new issue in case the behaviour noticed earlier persists with other boxes as well.

Cheers!