website/content/docs/disks/virtualbox/index.mdx
⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️
[!IMPORTANT]
Documentation Update: Product documentation previously located in/websitehas moved to thehashicorp/web-unified-docsrepository, where all product documentation is now centralized. Please make contributions directly toweb-unified-docs, since changes to/websitein this repository will not appear on developer.hashicorp.com. ⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️
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:
:disk type, Vagrant will use the storage controller containing the
boot disk. It will also create the disk if necessary.:dvd type, 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.
For more information on how to use VirtualBox to configure disks for a guest, refer to the general usage and configuration guide for more information.