Please publish new versions of bento/ubuntu-24.04 that include the Virtualbox provider, like version 202404.26.0 did

[mig5]

Describe the problem

The last two versions of the bento/ubuntu24.04 image, were not built for the virtualbox provider (or others).

https://portal.cloud.hashicorp.com/vagrant/discover/bento/ubuntu-24.04/versions/202407.23.0
https://portal.cloud.hashicorp.com/vagrant/discover/bento/ubuntu-24.04/versions/202407.22.0

The older image from April 2024 was built with many otther providers such as virtualbox, libvirt, qemu etc

https://portal.cloud.hashicorp.com/vagrant/discover/bento/ubuntu-24.04/versions/202404.26.0

Would it be possible to publish another image that was built for all the providers originally covered by that of version 202404.26.0?

Software Version

Packer v1.11.2
Debian 12.8

Replication Case

Try to run vagrant box add "bento/ubuntu-24.04" --box-version "202407.23.0" --provider virtualbox

Stacktrace

The box you're attempting to add has no available version that
matches the constraints you requested. Please double-check your
settings. Also verify that if you specified version constraints,
that the provider you wish to use is available for these constraints.

Box: bento/ubuntu-24.04
Address: https://vagrantcloud.com/bento/ubuntu-24.04
Constraints: 202407.23.0
Available versions: 202404.26.0, 202407.22.0, 202407.23.0

[carlosefr]

I second this. Is there a reason why builds for VirtualBox were stopped?

[Stromweld]

Due to updates of providers like virtualbox, vmwas, and parallels, along with packer plugin updates for those platforms things are not in a stable state and have been tough to get certain combinations of builds to works.

[skyscooby]

Due to updates of providers like virtualbox, vmwas, and parallels, along with packer plugin updates for those platforms things are not in a stable state and have been tough to get certain combinations of builds to works.

Maybe consider freeze/pin the versions of packer+plugins+vagrant that you used for older OS/providers.. it seems like a real time sink going back and trying to fix new issues that pop up in legacy / old OS's due to recent changes.. especially given the reason to rebuild these older images, I assume, is likely just to refresh the base package set installed most of the time. Does Vagrant brake the interface to the box files in ways that require rebuilding with newer versions?