bento/ubuntu-24.04 sometimes times out on boot

[alexkart]

Version

'bento/ubuntu-24.04' version '202502.21.0'

Environment

Windows 11, VirtualBox 7.1.6 r167084 (Qt6.5.3), Vagrant 2.4.3

Vagrant.configure("2") do |config|
  config.vm.box = "bento/ubuntu-24.04"
  config.vm.network "forwarded_port", guest: 22, host: 2255, host_ip: "127.0.0.1"
  config.vm.network "forwarded_port", guest: 5432, host: 5432, host_ip: "127.0.0.1"
  config.vm.network "forwarded_port", guest: 8080, host: 8080, host_ip: "127.0.0.1"
  config.vm.network "forwarded_port", guest: 5173, host: 5173, host_ip: "127.0.0.1"
  config.vm.network "private_network", ip: "192.168.250.35"
  config.vm.synced_folder "../ubuntu2404_data", "/vagrant_data"
  config.vm.synced_folder '.', '/vagrant', disabled: true
  config.vm.provider "virtualbox" do |vb|
    vb.memory = "8192"
	vb.cpus = "4"
  end
  config.vm.provision :shell, path: "_vagrant/bootstrap.sh"
  config.vm.hostname = "vagrant-ubuntu2404"
end

Scenario

Provision a VM once and use up and halt to boot and shut down the machine

Steps to Reproduce

Run vagrant up and vagrant halt to boot and shut down the machine

Expected Result

The VM boots without issues

Actual Result

Sometimes the VM boots OK, but sometimes it stalls during the boot on this stage:

Before this, I used ubuntu/jammy64, and it worked correctly, and the issue appeared after switching to bento/ubuntu-24.04.

[hunleyd]

I have this issue as well

[alexkart]

It looks like setting vb.customize ["modifyvm", :id, "--cpuexecutioncap", "90"] helps a bit.

[obrunofilipe]

I'm having the same issue. Has anyone found a solution for this?

[Stromweld]

new boxes have been released version 202508.03. Can anyone confirm they are still seeing this issue with the latest version.

[obrunofilipe]

I've tested with the new box (version 202508.03) and I'm still seeing this issue

[konstruktoid]

I use the following when running my lab boxes (https://github.com/konstruktoid/hardened-images/blob/master/build_box.sh#L38-L41), and haven't noticed the issue. Hopefully it helps someone.

  config.vm.provider "virtualbox" do |vb|
    vb.customize ["modifyvm", :id, "--cableconnected1", "on"]
    vb.customize ["modifyvm", :id, "--uart1", "0x3F8", "4"]
    vb.customize ["modifyvm", :id, "--uartmode1", "file", File::NULL]
  end

[giner]

I'm experiencing the same issue regularly after switching from ubuntu/jammy64 to bento/ubuntu-24.04

[giner]

Here is how to reproduce

mkdir repro-issue
cd repro-issue
vagrant init bento/ubuntu-24.04
while vagrant up; do vagrant destroy -f; done

The while loop will stop when vagrant up fails.

[giner]

It doesn't always get stuck on the same step

This is from one run

This is from another run

[giner]

One more input point which might help, I can't reproduce the issue with cloud-image/ubuntu-24.04 image which comes with minimal to no changes (claimed) from the official cloud images.

[Stromweld]

unfortunately it's not easy for me to test. I have mac and do not see this issue with arm version of bento/ubuntu-24.04.

I also just released new version 202510.26 built on virtualbox 7.2.4. On another chef product we use virtualbox on ubuntu-24.04 host in github actions. That about 2-3 weeks ago started having a similar issue but with all bento boxes it's using for testing not just ubuntu-24.04 here.

I'm not sure if it's a virtualbox issue, an box image issue, or possibly combo that can be fixed with vagrantfile template modification to the vbox settings.