Why doesn't it look different?

Resize a Fedora, CentOS, or Windows Dynamic Guest Virtual Disk (VDI) in VirtualBox in 3 Easy Steps 7


Here’s the scenario: you’ve set up Dynamically Allocated Storage for the hard drive on your Guest VM in VirtualBox and you’ve run out of space — even though your Actual Size is smaller than the Virtual Size (this happened to me recently when my Virtual Size was 10 GB, and the Actual Size was only 5.55 GB… but my Guest OS was complaining that I didn’t have enough disk space to do an update.)

You thought that as long as the Actual Size was smaller than the Virtual Size, that still meant you have room on the disk… but you’d be wrong. That’s kind of like believing that as long as you have checks in your checkbook, you’ve still got money in the bank. Ok, it’s not actually like that, and there are a lot of boring reasons why this happens… but you don’t really care about those. You just want to increase your disk space and get back to work.

Just follow these three easy steps to resize your Dynamic VDI.

Assumptions

  1. First, we’re assuming that you’ve backed up your data, if it’s important. Remember, there are two types of data: data that’s backed up, and data that’s waiting to be lost. Backup your .vdi file before going any further.
  2. We’re assuming that your Guest OS is either Fedora or RHEL/CentOS (which have additional steps for LVM below) or Windows. For any other setup, these instructions will probably still be helpful, but those are the two Guest systems that this specifically applies to.
  3. We’re assuming that you set up your VDI with Dynamically Allocated Storage. This will not work with fixed drives.
  4. If your Guest OS has Snapshots, we’re assuming you’re running a version of VirtualBox that is 4.3.* or later. This will not work with Snapshots prior to that release. I used version 4.3.12 when I wrote this.
  5. We’re assuming that if you hose this up royally, you don’t know where I live… and that even if you do hose it up royally, you’ve followed Assumption #1. Seriously. Back it up, yo!

For this example, I’ll expand an older Fedora 18 VDI I have on my system (because I already used these instructions to expand my Fedora 20 VDI… and therefore can’t take screenshots as I do it).

Note that we’re starting out with a Virtual Size of 20.00 GB and an Actual Size of 12.00 GB:

Starting Virtual Size for this VDI is 20.00 GB.

Starting Virtual Size for this VDI is 20.00 GB.

 

Before You Start: Shut Down your VM

You can’t do this process with the VM running. Shut it down so that its status appears as “Powered Off” in your VirtualBox Manager.

Make sure your VM is Powered Off, and not just Stopped.

Make sure your VM is Powered Off, and not just Stopped.

Step 1: Enlarge the Virtual Disk from the Command Line with VBoxManage

Now that your VM powered is off, go to the command line on your Host machine (mine is a Windows box) and change into your VirtualBox directory (these examples are for Windows, but adjust accordingly if your host OS is Linux).

cd "C:\Program Files\Oracle\VirtualBox"

Decide what you’d like the new upper limit for your dynamically allocated VDI to be. Again, this won’t be the actual size of the VDI file on your Host’s drive (it will grow dynamically as you use more space in your Guest). Since mine started out at 20 GB, I didn’t want to deal with this problem again for a long time (if ever), so I chose 40 GB. You can choose anything you like.

Now you’re ready to use the VBoxManage command to modify the max size of your virtual disk to 40 GB (40 x 1024 = 40960 MB) with:

VBoxManage modifyhd "C:\Users\Steve\VirtualBox VMs\Fedora 18\Fedora 18.vdi" --resize 40960

Make sure you use two dashes before the resize flag.

You’ll see progress output like this:

0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%

Those folder names I used above are the default, but this screenshot shows that this works even if you keep your program and data files in non-default locations (like I do). Just launch the VBoxManage command from the folder where VirtualBox is installed, and know the location of your VDI, and you’ll be fine.

VBoxManage command resizes your VDI

VBoxManage command resizes your VDI

The first part is done! You’ve just increased the virtual disk size, but your original partition is still the same size, so the next step is to expand your existing partition into the space you just created.

Step 2: Expand Your Existing Partition with GParted

If you’re the hard-core Linux command line type, there are ways to do this with fdisk, but I love me some GParted, so that’s how I recommend you do it, too.

If you don’t have it already (and you really should), download the GParted Live CD and save the .iso file somewhere on your Host’s hard drive.

Next, go into your VirtualBox Manager, select the VM, press Settings, then Storage, then find the IDE Controller and press the icon for Add CD/DVD Device.

Add a CD device to your IDE Controller

Add a CD device to your IDE Controller

Then press Choose disk.

Choose disk

Choose disk

then select the GParted .iso file on your hard drive. When it appears in the Storage Tree, select it and press the Live CD/DVD option under Attributes.

GParted Live CD is ready to boot!

GParted Live CD is ready to boot!

Hit OK, and now you’re ready to fire up your VM. It should boot from the GParted Live CD .iso.

GParted Boot Screen

GParted Boot Screen

Just hit enter to choose all the default GParted boot options when they present themselves. Eventually, the desktop will appear and GParted will launch automagically.

GParted Interface

GParted Interface

On a Windows system,  you’ll likely a small NTFS boot partition on /dev/sda1 and a larger NTFS partition on /dev/sda2.

With a default Fedora install (shown above), you’ll see a smallish (500MB is default) ext4 boot partition on /dev/sda1 and a larger LVM partition on /dev/sda2.

In both cases, you’ll see a bunch of unallocated space (which you created in Step 1) to the right of your data partition (which is almost certainly /dev/sda2). Select your data partition with your mouse, then click the Resize/Move button in the toolbar.

Select the partition and press Resize/Move

Select the partition and press Resize/Move

A new dialog box will open, where you can position your mouse near the black arrow on the side of the partition:

GParted Resize dialog

GParted Resize dialog

…then drag all the way to the right to  the size of the partition all the way to the right until it takes up all the available space.

My, what a large partition you have!

My, what a large partition you have!

Press the Resize/Move button in that dialog, which will return you to the main GParted window and show you the resized partition, and “1 operation pending” at the bottom of the window.

Resize operation is ready to be applied.

Resize operation is ready to be applied.

Click the Apply button on the toolbar, which will pop up a very scary dialog that warns you all about the nasty stuff that can happen, including LOSS of DATA. It also advises you to backup your data before proceeding, but you don’t need to worry about that… because you already listened to me in Assumption #1 and backed it up, right? RIGHT?!?!?!?!?

You're feeling pretty fly because your data is already backed up.

You’re feeling pretty fly because your data is already backed up.

Press the Apply to confirm, then you’ll get this dialog box that shows you the progress. It says it could take a long time, but it shouldn’t.

Operations completed!

Operations completed!

Hit the Close button, then quit GParted by selecting the QParted menu item and Quit:

I quit you, GParted!

I quit you, GParted!

Then double-click hit the red Exit button on the desktop, choose Shutdown, and OK. Press ENTER when it prompts to halt the system, which will power off the VM.

Now you’re ready for the last step!

Step 3: Remove the GParted .iso and Restart Your Guest OS

From the VirtualBox Manager, go back into your VM’s settings, go to Storage, right-click the GParted .iso disk, then select Remove Attachment.

Remove the GParted disk

Remove the GParted disk

Confirm with Remove when it asks if you’re sure.

Now go back out and restart your virtual machine. It should boot back into the Guest OS.

If you’re running a Windows Guest, the file system should automatically recognize the larger partition on boot and run an automatic check on the file system to make sure everything is kosher. Don’t skip this check. When it’s done, you should be able to use all your new space!

If you’re running a Fedora Guest, however, you have one more step. But since I promised only 3 easy steps, we’ll call it Step 3-And-A-Half.

Step 3-And-A-Half: Extend the Logical Volume into the Resized Partition (LVM Users Only)

By default, recent versions of Fedora and RHEL use LVM (logical volume manager), which requires an additional nudge to take advantage of your resized partition. From the Fedora command line, as root, you can verify that the OS can see the resized partition by doing:

pvscan

You can see here that our resized partition is almost 40 GB:

Fedora sees the resized partition... kinda...

Fedora sees the resized partition… kinda…

but doing a df -h shows the /dev/mapper/fedora-root logical volume as 16 GB:

Hmm... something's not right here...

Hmm… something’s not right here…

Take note of your logical volume’s location (/dev/mapper/fedora-root in this example) when you do df -h, then force the LVM volume to take up 100% of the available space on the partition with:

lvextend -l +100%FREE /dev/mapper/fedora-root

You should get a success message like this:

Logical volume extended!

Logical volume extended!

Boom! You did it! Now do another df -h and see if you notice any difference:

Why doesn't it look different?

Why doesn’t it look different?

Wait a minute… that looks decidedly un-different! Did we do something wrong? No, you just need one more step. Run resize2fs on the fedora-root location with:

resize2fs -p /dev/mapper/fedora-root

You should get a success message that says something like:

Filesystem at /dev/mapper/fedora-root is mounted on /; on-line resizing required
old_desc_blocks=1, new_desc_blocks=5
The filesystem on /dev/mapper/fedora-root is now XXXXXXX(Xk) blocks long.

Now do a df -h again and you should see the increased size of the root partition. Do a quick reboot and you should be all set!

And if you go back out and check the Storage settings of the VM in the VirtualBox Manager, we’ll see that the Virtual Size has now been doubled to 40.00 GB, which is exactly what we set out to do:

Virtual size doubled!

Virtual size doubled!

Congratulations!

Way to go. You just successfully increased the size of a dynamically allocated VDI on your VirtualBox VM!

Feel free to post your success stories in the comments below. But if you run into any problems, you  don’t need to worry… because you totally backed up your data. 🙂

  • Hey Steve! It looks like for step 1 you accidentally pasted your options for the Fedora 20 modifyhd command.

    I enjoy reading your wide array of blog articles. They closely match with much of what I do and am interested in. 🙂

    • Hi, Greg. Doh! You’re right. That was from when I had just previously expanded my F20 VM. Fixed now. Nice catch! And glad you enjoy the blog. I enjoy writing it! 🙂

  • DanyC

    Hey Steve, nice post.

    Fyi i’ve followed the steps but i had to run resize2fs -p /dev//

    Without it it didn’t work regardless of the setting on VM storage disk.

    • Thanks, DanyC. Between you and Steve I finally got this working.

  • Darren

    good job boys that worked resize2fs -p /dev/mapper/fedora-root sorted it out df -h reflected correctly and a restart did the final blow. velly velly nice

  • Siddhartha

    Thanks! This was spot on!