Why does vagrant up hang on SSH auth method: private key?

Question

virtual box

When running the vagrant up command at the SSH auth method: private key stage, it hangs and after a while gives the
Timed out while waiting for the machine to boot error. 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 set up properly in these boxes.
Verify that authentication configurations are also set up properly,
as well.
If the box appears to be booting properly, you may want to increase
the timeout ("config.vm.boot_timeout") value.
windows 7
virtualbox 6.0
vagrant 2.2.3
collected all the settings with puphpet
How can I solve this problem?

Answer 1

Faced the same issue on Windows 10 Pro. Perhaps someone will help. Everything was solved with one command to disable the hypervisor:
bcdedit /set hypervisorlaunchtype off

Answer 2

tried as it advised you - increase in Vagrantfile for example up to 10 minutes?

Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
... другие настройки

  config.vm.boot_timeout = 600

what does the instance say when it loads?
some xenials had a delay in initializing the network device for the first time (not every time, so I can't quote the error exactly). increasing timeout is the easiest way. or switch back to trusty (if you have ubuntu

Answer 3

There was the same problem, the solution turned out to be that one of the CPU Configuration parameters had to be included in the BIOS ( https://itremont.info/programmnoe-obespechenie/16-...