How to resize a Virtual Drive

[Perryg]

Resize a virtual HDD

First resizing does not work if the guest has snapshots (prior to version 4.3.*) nor will it work on Fixed drives.
Secondly when doing anything that could prove as destructive as this should you make a mistake, backup the *.vdi file before you start.

Increasing the drive does not increase the primary partition so this is a two step process.

Step 1: Increase the size of the drive.
Note: if the path has spaces in it you will need to wrap the path in quotes.

Use the following command to increase the size of the drive:


Code: Select all   Expand viewCollapse view

VBoxManage modifyhd <absolute path to file> --resize <size in MB>


Example: I have a 10GB drive that I want to be 20GB the command would be.


Code: Select all   Expand viewCollapse view

VBoxManage modifyhd <absolute path including the name and extension> --resize 20480

Step 2: Extend the primary partition to include the new drive space.

Download the Gparted live cd or what ever partition manager program you wish and mount it to the guests virtual CD and boot the guest.
From here you can expand the primary partition to use the new space.

Windows Vista and newer guests can use the Disk Management to expand the primary partition.

You can download the Gparted Live CD from HERE.


Note 1: The only step that VirtualBox is concerned with is step 1. After that you need to seek additional information on the partition manager you wish to use from the vendor of the partition manager.

Note 2: You can not shrink a guest drive with VirtualBox due to the inherent danger of loosing data or making the guest non-bootable.

Note 3: In 4.3.0 the devs fixed a bug which had previously made it impossible to resize a snapshot. Since then it is possible, but not recommended for non-experts.

[mpack]

What if I used Fixed Disks, or VMDK?

As the advice above states, resizing of fixed VDIs or VHDs is not directly supported, nor is resizing of formats other than VHD/VDI. Nor is it easy to resize disks which are part of a snapshot chain.

However, all of these problems are easily addressed if you clone the disk to a supported format first, using :-
(fields in brackets are placeholders which should be replaced with actual filenames, the brackets are not literal)

Code: Select all   Expand viewCollapse view

VBoxManage clonehd <infilename or UUID> <outfilename> --format VDI --variant Standard


You can then resize the resulting dynamic VDI using "VBoxManage modifyhd" as described in the previous message.

If a snapshot chain is involved then <infilename> should be the name of the latest snapshot VDI in the "Snapshots" subfolder. Do not make the rookie mistake of cloning the base VDI. In this case "clonehd" will create a merged clone and it's important that you not incorporate this back into a VM which is still expecting a chain of difference disk images. Either build a new VM around the clone, or delete all the snapshot markers from the original VM, then replace the disk file. If the VM did not use difference images (no immutable drive, linked clone or snapshot) then you can use the Storage settings panel to remove the old disk and replace with the new one.

[mpack]

What if my VM uses Snapshots?

If you are intent on keeping the snapshot structure then you are supposed to enlarge all members of the snapshot chain, which is a risky business. Or you can enlarge only the latest snapshot, but that is even more risky (think about future complications when snapshot elements are removed).

The best thing is to delete all the snapshots using the UI, before enlarging the current state. Be sure to make a backup of the VM before starting this.

You can also use the "clone VM, then enlarge" trick from the previous post. In particular see the paragraph on merging a snapshot chain into a single disk using VBoxManage clonehd. This would be an easy way to dispense with snapshots, making it a trivial matter to enlarge the disk.