Warning! This feature is experimental and may break or change in between releases. Use at your own risk. It currently is not officially supported or functional.
This feature currently reqiures the experimental flag to be used. To explicitly enable this feature, you can set the experimental flag to:
Please note that
VAGRANT_EXPERIMENTAL is an environment variable. For more
information about this flag visit the Experimental docs page
for more info. Without this flag enabled, any disks defined will not be configured.
Vagrant currently only supports VirtualBox version 5.x and newer for configuring and attaching disks.
Because of how VirtualBox handles disk management, a Vagrant guest must be powered
off for any changes to be applied to a guest. If you make a configuration change
with a guests disk, you will need to
vagrant reload the guest for any changes
to be applied.
When new disks are defined to be attached to a guest, Vagrant will attach disks to a particular storage controller based on the type of disk configured:
- For the
:disktype, Vagrant will use the storage controller containing the boot disk. It will also create the disk if necessary.
- For the
:dvdtype, Vagrant will attach the disk to the storage controller that comes earliest in the machine's boot order. For example, if a VM has a SATA controller and an IDE controller, the disk will be attached to the IDE controller.
Vagrant will not be able to configure disks of a given type if the associated storage controller does not exist. In this case, you may use provider-specific customizations to add a required storage controller.
It should also be noted that storage controllers have different limits for the number of disks that can be attached. Attempting to configure more than the maximum number of disks for a storage controller type will result in a Vagrant error.