fresh install on Windows results in bento box doesn't support provider

[thecommonthread]

What was The Command Used To Provision

vagrant up --provision

What Kind of VVV Provision Was This

This was a fresh install of everything on a new computer and it threw an error saying bento/ubuntu-24.04 doesn't support the provider I'm using.

Steps to Reproduce (for bugs)

install virtualbox, vagrant, and VVV, then vagrant up

Your Environment

Operating System: Windows 11 Home
Vagrant 2.4.9
VVV 3.15.1
Intel Core 7 240H

__ __ __ __
\ V\ V\ V / v3.16.0 Ruby:3.3.8, Path:"C:/Users/tomor/vvv2/VVV"
 \_/\_/\_/  git::develop(8ee0d24f)

Platform: mingw32 windows  HasWinAdminPriv  vagrant-goodhosts monochrome-terminal shared_db_folder_disabled
Vagrant: v2.4.9, virtualbox: v7.2.4

Docs:       https://varyingvagrantvagrants.org/
Contribute: https://github.com/varying-vagrant-vagrants/vvv
Dashboard:  http://vvv.test

Bringing machine 'default' up with 'virtualbox' provider...
==> default: Box 'bento/ubuntu-24.04' could not be found. Attempting to find and install...
    default: Box Provider: virtualbox
    default: Box Version: >= 0
==> default: Loading metadata for box 'bento/ubuntu-24.04'
    default: URL: https://vagrantcloud.com/api/v2/vagrant/bento/ubuntu-24.04
The box you're attempting to add doesn't support the provider
you requested. Please find an alternate box or use an alternate
provider. Double-check your requested provider to verify you didn't
simply misspell it.

If you're adding a box from HashiCorp's Vagrant Public Registry, make sure the box is
released.

Name: bento/ubuntu-24.04
Address: https://vagrantcloud.com/api/v2/vagrant/bento/ubuntu-24.04
Requested provider: virtualbox```

[tomjn]

bento/ubuntu-24.04 does appear to have a virtualbox build acording to https://portal.cloud.hashicorp.com/vagrant/discover/bento/ubuntu-24.04, do you have anything in config.yml that you've added around boxes and box versions? Does this happen on newer versions of the develop branch? ( Current develop should show as 3.16 )

HashiCorp Cloud Platform

[tomjn]

Next steps to try:

1. Update to the latest develop branch as you're on an older commit, it should read 3.16
2. Try again, sometimes vagrant cloud takes a moment to update and it might have fixed itself
3. There's a config parameter similar to specifying the box, but for the box version. Try pinning it to a version that vagrant cloud says there is definitely an amd64 box for. ( 202510.26.0 looks like what you want )

Since you mentioned an Intel core cpu I can rule out that you're actually on Arm Windows, I'm not sure if Windows 11 home is a factor since you're not using Hyper-V but I believe in newer versions that shouldn't be an issue either.

[thecommonthread]

Sorry, I reported 3.15.1 from when I tested the stable branch, but if you look at the terminal output I pasted, you'll see what I provided from the 3.16.0 develop branch. I did a git pull just to make sure and it said it was already up to date.

I gave it another provision attempt, which resulted in the same output.

Is this config option you're referring supposed to be in the VVV config.yml file or in the Vagrantfile? I want to assume you're referring to the override.vm.box_version option in the Vagrantfile, which I changed from 202502.21.0 to 202510.26.0.

Is Windows 11 Home not typically used for dev environments or with VVV? I realize I did not consider much the ramifications of not buying a computer with Windows Pro on it for dev work.

I don't think Hyper-V is actually supposed on Windows 11 Home (which I didn't realize until I just looked it up). I tried checking Hyper-V status using the Dism /online /Get-FeatureInfo /FeatureName:HypervisorPlatform command:

Deployment Image Servicing and Management tool
Version: 10.0.26100.5074

Image Version: 10.0.26200.7462

Feature Information:

Feature Name : HypervisorPlatform
Display Name : Windows Hypervisor Platform
Description : Enables virtualization software to run on the Windows hypervisor
Restart Required : Possible
State : Disabled

Custom Properties:

(No custom properties found)

...and when I used command (gcim Win32_ComputerSystem).HypervisorPresent, it output True. But the Get-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V command returned no output, so I want to believe that Hyper-V is not installed, since all I see installed is Windows Hypervisor Platform (not the same as Hyper-V nor an alternative hypervisor).

[tomjn]

Is this config option you're referring supposed to be in the VVV config.yml file or in the Vagrantfile? I want to assume you're referring to the override.vm.box_version option in the Vagrantfile, which I changed from 202502.21.0 to 202510.26.0.

It's in config.yml, modifying the vagrantfile would just mess up updating to newer versions. If you've never touched it then that isn't the cause. In config.yml under vm_config: you can specify both a box: parameter and a box_version parameter, e.g.

vm_config:
  box_version: 202510.26.0

Is Windows 11 Home not typically used for dev environments or with VVV? I realize I did not consider much the ramifications of not buying a computer with Windows Pro on it for dev work.

Plenty of people do but it's good to rule out various causes, and it looks like you've done that. If you had enabled Hyper-V you could have used it as a provider, and virtualbox would secretly use it behind the scenes. I believe Home supports it now as the feature was needed for certain security features, but was previously an enterprise grade feature.

Something else you could do is find the amd64 box and manually install the box file with vagrant box commands, but you shouldn't need to do this. I've not checked the bento github yet to see if anyone else has reported similar issues though

[thecommonthread]

Thanks, I plugged that config setting in and ran into the same:

__ __ __ __
\ V\ V\ V / v3.16.0 Ruby:3.3.8, Path:"C:/Users/tomor/vvv2/VVV"
 \_/\_/\_/  git::develop(8ee0d24f)

Platform: mingw32 windows  HasWinAdminPriv  vagrant-goodhosts monochrome-terminal shared_db_folder_disabled
Vagrant: v2.4.9, virtualbox: v7.2.4

Docs:       https://varyingvagrantvagrants.org/
Contribute: https://github.com/varying-vagrant-vagrants/vvv
Dashboard:  http://vvv.test

Bringing machine 'default' up with 'virtualbox' provider...
==> default: Box 'bento/ubuntu-24.04' could not be found. Attempting to find and install...
    default: Box Provider: virtualbox
    default: Box Version: 202510.26.0
==> default: Loading metadata for box 'bento/ubuntu-24.04'
    default: URL: https://vagrantcloud.com/api/v2/vagrant/bento/ubuntu-24.04
The box you're attempting to add doesn't support the provider
you requested. Please find an alternate box or use an alternate
provider. Double-check your requested provider to verify you didn't
simply misspell it.

If you're adding a box from HashiCorp's Vagrant Public Registry, make sure the box is
released.

Name: bento/ubuntu-24.04
Address: https://vagrantcloud.com/api/v2/vagrant/bento/ubuntu-24.04
Requested provider: virtualbox

I did a separate fresh install also and got the exact same output. Then I tried to add the box and that didn't work either:

> vagrant box add bento/ubuntu-24.04
==> box: Loading metadata for box 'bento/ubuntu-24.04'
    box: URL: https://vagrantcloud.com/api/v2/vagrant/bento/ubuntu-24.04
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/api/v2/vagrant/bento/ubuntu-24.04
Constraints: >= 0
Available versions:

I then just tried to install the bento box on its own separate from VVV and it couldn't be found there either:

> vagrant init bento/ubuntu-24.04 --box-version 202510.26.0
A `Vagrantfile` has been placed in this directory. You are now
ready to `vagrant up` your first virtual environment! Please read
the comments in the Vagrantfile as well as documentation on
`vagrantup.com` for more information on using Vagrant.
> vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Box 'bento/ubuntu-24.04' could not be found. Attempting to find and install...
    default: Box Provider: virtualbox
    default: Box Version: 202510.26.0
==> default: Loading metadata for box 'bento/ubuntu-24.04'
    default: URL: https://vagrantcloud.com/api/v2/vagrant/bento/ubuntu-24.04
The box you're attempting to add doesn't support the provider
you requested. Please find an alternate box or use an alternate
provider. Double-check your requested provider to verify you didn't
simply misspell it.

If you're adding a box from HashiCorp's Vagrant Public Registry, make sure the box is
released.

Name: bento/ubuntu-24.04
Address: https://vagrantcloud.com/api/v2/vagrant/bento/ubuntu-24.04
Requested provider: virtualbox

So I really don't know what the issue is, but to me this doesn't look like an issue with VVV.

[tomjn]

Can you try with the provider and architecture flags?

❯ vagrant box add bento/ubuntu-24.04 --provider=virtualbox --architecture=amd64
==> box: Loading metadata for box 'bento/ubuntu-24.04'
    box: URL: https://vagrantcloud.com/api/v2/vagrant/bento/ubuntu-24.04
==> box: Adding box 'bento/ubuntu-24.04' (v202510.26.0) for provider: virtualbox (amd64)
    box: Downloading: https://vagrantcloud.com/bento/boxes/ubuntu-24.04/versions/202510.26.0/providers/virtualbox/amd64/vagrant.box
==> box: Successfully added box 'bento/ubuntu-24.04' (v202510.26.0) for 'virtualbox (amd64)'!

Note that I ran that on MacOS so I can't use that box but it should work the same for you. I'm assuming as well that you're running a 64bit OS ( I don't think Windows 11 come in a 32bit flavor? )

[thecommonthread]

That did work to download the box so that's cool:

> vagrant box add bento/ubuntu-24.04 --provider=virtualbox --architecture=amd64
==> box: Loading metadata for box 'bento/ubuntu-24.04'
    box: URL: https://vagrantcloud.com/api/v2/vagrant/bento/ubuntu-24.04
==> box: Adding box 'bento/ubuntu-24.04' (v202510.26.0) for provider: virtualbox (amd64)
    box: Downloading: https://vagrantcloud.com/bento/boxes/ubuntu-24.04/versions/202510.26.0/providers/virtualbox/amd64/vagrant.box
==> box: Box download is resuming from prior download progress
    box:
==> box: Successfully added box 'bento/ubuntu-24.04' (v202510.26.0) for 'virtualbox (amd64)'!

But then when trying to vagrant up it continues to say it doesn't support the provider requested:

> vagrant up --provision --provider=virtualbox
__ __ __ __
\ V\ V\ V / v3.16.0 Ruby:3.3.8, Path:"C:/Users/tomor/dev/vvv3/VVV"
 \_/\_/\_/  git::develop(8ee0d24f)

Platform: mingw32 windows  missingWinAdminPriv  vagrant-goodhosts monochrome-terminal shared_db_folder_disabled
Vagrant: v2.4.9, virtualbox: v7.2.4

Docs:       https://varyingvagrantvagrants.org/
Contribute: https://github.com/varying-vagrant-vagrants/vvv
Dashboard:  http://vvv.test

Bringing machine 'default' up with 'virtualbox' provider...
==> default: Box 'bento/ubuntu-24.04' could not be found. Attempting to find and install...
    default: Box Provider: virtualbox
    default: Box Version: 202510.26.0
==> default: Loading metadata for box 'bento/ubuntu-24.04'
    default: URL: https://vagrantcloud.com/api/v2/vagrant/bento/ubuntu-24.04
The box you're attempting to add doesn't support the provider
you requested. Please find an alternate box or use an alternate
provider. Double-check your requested provider to verify you didn't
simply misspell it.

If you're adding a box from HashiCorp's Vagrant Public Registry, make sure the box is
released.

Name: bento/ubuntu-24.04
Address: https://vagrantcloud.com/api/v2/vagrant/bento/ubuntu-24.04
Requested provider: virtualbox

[thecommonthread]

I added this issue to the bento github, but haven't had a response. 🙁

[tomjn]

I get the feeling there's something glaringly obvious that's too simple for us to spot, e.g. if the provider is actually " virtualbox" or something as silly as that.

Something I've not tried before, there's a CLI at https://github.com/Varying-Vagrant-Vagrants/cli and it has a doctor subcommand that runs a number of tests and checks, if you'd like to give that a go? You'll need to make sure your working directory is your VVV folder so it picks it up rather than looking for vvv-local in your main user folder.

In the meantime can you share a copy of your config/config.yml? And does removing your .vagrant folder help at all?

GitHub

GitHub - Varying-Vagrant-Vagrants/cli: Beta VVV CLI application

Beta VVV CLI application. Contribute to Varying-Vagrant-Vagrants/cli development by creating an account on GitHub.