When i try start a VM with ubuntu/focal64, it fail with error
boby@sok-01:/mnt/data/sites/learn/vagrant/2020-09-13-ubuntu-20.04$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'ubuntu/focal64'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'ubuntu/focal64' version '20200910.0.0' is up to date...
==> default: Setting the name of the VM: 2020-09-13-ubuntu-2004_default_1599985318716_1017
==> default: Fixed port collision for 22 => 2222. Now on port 2201.
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
==> default: Forwarding ports...
default: 22 (guest) => 2201 (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:2201
default: SSH username: vagrant
default: SSH auth method: private key
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.
boby@sok-01:/mnt/data/sites/learn/vagrant/2020-09-13-ubuntu-20.04$
I am using Ubuntu 18.04, Vagrant 2.2.10 and Virualbox 6.1.14 r140239.
Hi there!
There is a confirmed bug that causes some of the newer Ubuntu boxes to boot slowly, which is causing the SSH timeout in this case.
You can work around this by adding the following customizations to your Vagrantfile:
config.vm.provider :virtualbox do |v|
v.customize ["modifyvm", :id, "--uart1", "0x3F8", "4"]
v.customize ["modifyvm", :id, "--uartmode1", "file", File::NULL]
end
please help
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.
still the problem
my Vagrantfile is
-- mode: ruby --
vi: set ft=ruby :
All Vagrant configuration is done below. The “2” in Vagrant.configure
configures the configuration version (we support older styles for
backwards compatibility). Please don’t change it unless you know what
you’re doing.
Vagrant.configure(“2”) do |config|
config.vm.provider :virtualbox do |v|
v.customize [“modifyvm”, :id, “–uart1”, “0x3F8”, “4”]
v.customize [“modifyvm”, :id, “–uartmode1”, “file”, File::NULL]
end
The most common configuration options are documented and commented below.
For a complete reference, please see the online documentation at
Thanks for the workaround snippet! I added it to my Vagrantfile:
Vagrant.configure("2") do |config|
config.vm.box = "ubuntu/focal64"
config.vm.provider "virtualbox" do |vb|
vb.memory = "1024"
vb.customize ["modifyvm", :id, "--uart1", "0x3F8", "4"]
vb.customize ["modifyvm", :id, "--uartmode1", "file", "./ttyS0.log"]
end
end
but still can’t get Ubuntu focal to boot up:
C:\Users\ChrisEich\Documents\repos\hub-system>vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'ubuntu/focal64'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'ubuntu/focal64' version '20210927.0.0' is up to date...
==> default: Setting the name of the VM: hub-system_default_1632871817992_15800
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
==> 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
[hangs here]
By way of comparison, hashicorp/bionic64 works fine…
I spoke too soon; the boot continued after almost 45 minutes, and I was able to vagrant ssh after that. I changed the timeout to 3600 and tried vagrant reload. This time it took just over 3 minutes. The kernel messages indicate “detected stall” on one vCPU, and later on, “soft lockup” on both vCPUs:
