From 0aa8a517c4c56e99d5aa6126e4d11d098c655560 Mon Sep 17 00:00:00 2001 From: Brian Cain Date: Tue, 28 Jan 2020 13:11:15 -0800 Subject: [PATCH] Add note about resizing VMDK disks --- .../docs/disks/virtualbox/common-issues.html.md | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/website/source/docs/disks/virtualbox/common-issues.html.md b/website/source/docs/disks/virtualbox/common-issues.html.md index 09de55e16..c6b5ba9c2 100644 --- a/website/source/docs/disks/virtualbox/common-issues.html.md +++ b/website/source/docs/disks/virtualbox/common-issues.html.md @@ -26,7 +26,16 @@ SATA Controllers can only support up to **30 disks** per guest. Therefore if you to define and attach more than 30, it will result in an error. This number _includes_ the primary disk for the guest. -## Applying Changes to Guests +## Resizing VMDK format disks + +VMDK disks cannot be resized in their current state, so Vagrant will automatically +convert these disks to VDI, resize the disk, and convert it back to its original format. +Many Vagrant boxes default to using the VMDK disk format, so resizing disks for +many users will require Vagrant to convert these disks. Generally, this will be transparent +to the user. However if Vagrant crashes or if a user interrupts Vagrant during the +cloning process, there is a chance that you might lose your data. + +## Applying Vagrant disk configuration changes to guests Due to how VirtualBox works, you must reload your guest for any disk config changes to be applied. So if you update your Vagrantfile to update or even remove disks, make