@Hakan On Mon, 2022-09-12 at 10:48 +0300, Hakan Bayındır wrote:
To run these VMs, please put the relevant Vagrantfiles to their own folder and run "vagrant up". The rest should be automagic.
Do you have hint for me? My installation on Ubuntu 20.04.5 LTS as host with VirtualBox 6.1 and vagrant 2.2.6 hangs here despite the VM is running and waiting at the login screen (see screen shot with VM and console). I have already tried to manually "cable connect" the network adapter 1 and 2, install vagrant-vbguest plugin and edit the Vagrant file like described here etc.: https://stackoverflow.com/questions/38463579/vagrant-hangs-at-ssh-auth-metho... BTW: How do I continue a broken installation, just via "vagrant up"? Thanks a lot :-) Jürgen config.vm.synced_folder '/host/path', '/guest/path', SharedFoldersEnableSymlinksCreate: false ==> default: Clearing any previously set network interfaces... ==> default: Preparing network interfaces based on configuration... default: Adapter 1: nat default: Adapter 2: hostonly ==> default: Forwarding ports... 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 default: Warning: Authentication failure. Retrying... default: Warning: Authentication failure. Retrying... default: Warning: Authentication failure. Retrying... ... x times ... 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. ~/vagrant >
