Additional disks not working for VirtualBox provider in Vagrant

[kri5]

What happened?

When configuring vagrant to provision additional disks AND using the VirtualBox provider, no additional disks is provisionned.

What did you expect to happen?

Additional disks should be provisionned regardless of the VM provider

How can we reproduce it (as minimally and precisely as possible)?

use a vagrant/config.rb with
kube_node_instances_with_disks = true

By default, it is set to false, setting it to true would provision 2 additional disks per VM, 20GB each (current default values for kube_node_instances_with_disks_number and kube_node_instances_with_disks_size in the Vagrantfile)

OS

Linux 5.15.133.1-microsoft-standard-WSL2 x86_64
PRETTY_NAME="Ubuntu 22.04.4 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.4 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=jammy

Version of Ansible

ansible [core 2.16.5]
config file = /<private_path>/ansible/kubespray/ansible.cfg
configured module search path = ['/<private_path>/ansible/kubespray/library']
ansible python module location = /<private_path>/ansible/venv/lib/python3.10/site-packages/ansible
ansible collection location = /home/kri5/.ansible/collections:/usr/share/ansible/collections
executable location = /<private_path>/ansible/venv/bin/ansible
python version = 3.10.12 (main, Nov 20 2023, 15:14:05) [GCC 11.4.0] (/<private_path>/ansible/venv/bin/python)
jinja version = 3.1.2
libyaml = True

Version of Python

Python 3.10.12

Version of Kubespray (commit)

8919901

Network plugin used

cilium

Full inventory with variables

Default vagrant variable for inventory is being used

Command used to invoke ansible

vagrant up --provider virtualbox

Output of ansible run

Not Relevant

Anything else we need to know

No response