Cfxtrjtrk

The following worked for me:

VBoxManage modifyhd YOUR_HARD_DISK.vdi --resize SIZE_IN_MB

However, I understand how mileage can vary :-) As far as resizing the partition, in Windows 7, I was able to resize at the screen you showed by right clicking on the
C: drive in the bottom panel and selecting extend volume.

Wim, I think you'll need to unregister it from Vbox first. File, Media Manager, Click on you hdd, and unregister it. Then try it again.

After resizing and not being able to view the resizing on my windows XP guest machine, I had to

1. clone it


2. resize it with
   "VBoxManage modifyhd winxppro Clone.vdi --resize 30720"
   and everything worked

I saw in other forums that snapshots can interfere for resizing and not being able to remove all snapshots for different errors I got, the only found solution for me was to clone it to remove the snapshots and then resize it, and everything worked. For resizing outside windows, a gparted boot cd that can be found here can help

You can also do it using the VirtualBox menu:

Select File -> Virtual Media Manager ...

A window will open:

Select your disk, and select Properties. Now just move the slider at the bottom.

After you start the virtual machine, windows will not recognize the new space.

In windows, open Computer Management (search for it in the start menu), select Storage -> Disk Management in the left menu. Select your partition (probably C:), right click on it and select Extend Volume .... Now just click through the wizard and you're done.

I had the same problem where I had moved a disk, and replaced the original with a symlink. This works OK afterwards, but you run into problems with the 'modifyhd' command, as that apparently canonicalizes the path to the vdi-file when working with it. This makes it looks like you're trying to add a new disk with the same UUID but on a different path - or something like that.

There was two problems:

1. The disk had to be removed from the VM that used it, but then also "from the VirtualBox list of hdds". This was fixed with 'closemedium' command, which removes it from that list.




2. The disk to be resized was a "fixed disk" instead of "dynamic", and only dynamic disks can be resized. That was fixed with a 'clone' command (the clone is dynamic), and then resize the resulting disk.

This is my log for how it was done. Do notice that I am not at any point running as root, except when I afterwards do the resize of the partition and filesystem.

REMOVE THE ASSOCIATION TO THE DISK FROM VM.

PROBLEM STILL PERSISTS:

virt_box@TestBox:~/VirtualBox VMs/TestInception 64 bit$ VBoxManage modifyhd TestInception 64 bit.vdi --resize 8192

VBoxManage: error: Cannot register the hard disk '/datadisk/VirtualBox VMs/TestInception 64 bit/TestInception 64 bit.vdi' {6cd99209-e4db-4178-a6c2-53f9581b1fad} because a hard disk '/home/virt_box/VirtualBox VMs/TestInception 64 bit/TestInception 64 bit.vdi' with UUID {6cd99209-e4db-4178-a6c2-53f9581b1fad} already exists

VBoxManage: error: Details: code NS_ERROR_INVALID_ARG (0x80070057), component VirtualBox, interface IVirtualBox, callee nsISupports

VBoxManage: error: Context: "OpenMedium(Bstr(pszFilenameOrUuid).raw(), enmDevType, enmAccessMode, fForceNewUuidOnOpen, pMedium.asOutParam())" at line 178 of file VBoxManageDisk.cpp

Ah, the disk is still "in the system":

virt_box@TestBox:~/VirtualBox VMs/TestInception 64 bit$ VBoxManage list hdds

UUID:        ba58276a-bbe1-4354-8ae5-246bdac390c8

Parent UUID: base

Format:      VDI

Location:    /home/virt_box/VirtualBox VMs/TestInception 32 bit/TestInception.vdi

State:       locked write

Type:        normal

Usage:       TestInception 32 bit (UUID: a693ac62-7caa-4f11-9d00-51d3a149f5f7)



UUID:        6cd99209-e4db-4178-a6c2-53f9581b1fad

Parent UUID: base

Format:      VDI

Location:    /home/virt_box/VirtualBox VMs/TestInception 64 bit/TestInception 64 bit.vdi

State:       created

Type:        normal

Remove/delete the disk from the VirtualBox disk list ("closemedium"):

virt_box@TestBox:~/VirtualBox VMs/TestInception 64 bit$ VBoxManage closemedium disk 6cd99209-e4db-4178-a6c2-53f9581b1fad

virt_box@TestBox:~/VirtualBox VMs/TestInception 64 bit$ VBoxManage list hdds

UUID:        ba58276a-bbe1-4354-8ae5-246bdac390c8

Parent UUID: base

Format:      VDI

Location:    /home/virt_box/VirtualBox VMs/TestInception 32 bit/TestInception.vdi

State:       locked write

Type:        normal

Usage:       TestInception 32 bit (UUID: a693ac62-7caa-4f11-9d00-51d3a149f5f7)

Try the resize again:

virt_box@TestBox:~/VirtualBox VMs/TestInception 64 bit$ VBoxManage modifyhd TestInception 64 bit.vdi --resize 8192

0%...

Progress state: VBOX_E_NOT_SUPPORTED

VBoxManage: error: Resize hard disk operation for this format is not implemented yet!

DAMN, "fixed-size" DOESN'T WORK! 'clonehd' to the rescue, as that leaves a 'dynamically allocated' cloned disk:

virt_box@TestBox:/datadisk/VirtualBox VMs/TestInception 64 bit$ VBoxManage clonehd TestInception 64 bit.vdi TestInception 64 bit-cloned.vdi

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

Clone hard disk created in format 'VDI'. UUID: 8e237500-173b-401a-9e63-9e64da110da9

NOW DO THE RESIZE (instantanious):

virt_box@TestBox:/datadisk/VirtualBox VMs/TestInception 64 bit$ VBoxManage modifyhd --resize 8192 TestInception 64 bit-cloned.vdi 

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

THEN ATTACH TO SOME VM, FOR RESIZING. This is done as root. Assumes that you only have one partition and possibly swap.

# fdisk /dev/sdb  # <- The extra disk, just attached to be resized

// The procedure looks like this:

// m - print help

// p - print table

// d ... - delete partition (delete both if you have root and swap)

// n - new partition (create root/first partition starting on exact same sector as before, typically 2048, but ends on last, or last minus swap)

//  ... n.. (.. then add the swap partition. Calculate how many sectors using original table)

// t - change type of partition (swap partition, if any, to 82 - not 83 which is "normal Linux").

// w - write partition table (write out, with the resized partition)



# e2fsck -f /dev/sdb1



e2fsck 1.42.5 (29-Jul-2012)

Pass 1: Checking inodes, blocks, and sizes

Pass 2: Checking directory structure

Pass 3: Checking directory connectivity

Pass 4: Checking reference counts

Pass 5: Checking group summary information

/dev/sdb1: 99918/122160 files (0.3% non-contiguous), 471032/487936 blocks



# resize2fs /dev/sdb1



resize2fs 1.42.5 (29-Jul-2012)

Resizing the filesystem on /dev/sdb1 to 1965824 (4k) blocks.

The filesystem on /dev/sdb1 is now 1965824 blocks long.

This worked for me with Virtualbox 5.2.6 installed on Ubuntu 16.04 Host Machine and Windows 10 Guest:
open Virtualbox Manager, click on Global Tools (upper right corner) and choose Virtual Media Manager.
Click on the Hard Disk Tab and select your Guest OS. At the bottom of the box click on the Attributes Tab. At the bottom you can see the size of the Virtual Disk, and with the slider you can increase the size to your liking. (You can only increase, not decrease the size with this method). Click on Apply.
Start your Windows Guest OS, open Computer Management, right click on the C: Drive, and select Extend Volume to extend the file system with the unallocated part.

That’s all I had to do, works perfectly for me.

A sure-proof way is to do it the same as moving to a larger hard drive that's not running in a VM. First use ccleaner or similiar program in XP to clean up all junk files that it can. Then create a secondary virtual HDD of the size you want. Boot with the clonezilla ISO in your virtual ODD drive and clone over along with the 'resize to new partition size' option selected. Then set the new Virtual HDD as primary, and don't delete the old one until you know it worked.

I received the same error until I used sudo to run the command, then worked perfect, still need to have partition grown from within the guest to use additional space.

Make sure you are logged in as user with write permissions to the disk image file. Then run

VBoxManage modifyhd YOUR_HARD_DISK.vdi --resize SIZE_IN_MB  

Worked for me at first time of asking

If your host machine is windows, then you can run the following command to increase or decrease the vdi disk size in virtual box:

"C:Program FilesOracleVirtualBoxVBoxManage.exe" modifyhd "C:Usersyour_user_nameVirtualBox VMsUbuntu18LTSUbuntu18LTS.vdi" --resize 20000

In the above command replace your_user_name with the real windows user and 20000 is MB size of disk.

As a matter of fact, it seems that modifyhd alone doesn't do you any good in some cases. I actually expanded my WinXP vdi by cloning the image after expansion.

Here's the complete step-by-step guide that worked for me a couple of weeks ago: http://libtronics.com/2011/07/resize-virtualbox-disk-for-winxp-guest/

Here's a way to resize your VirtualBox disk, regardless of whether it is a fixed format or dynamic format disk. Specifically, it prevents this error:

Progress state: VBOX_E_NOT_SUPPORTED

VBoxManage: error: Resize hard disk operation for this format is not implemented yet!

⚠️ Backup the virtual disk. You never know what might go wrong.

On your host:

1. 
   

   Open a terminal window.

   
   
   

   
   

   On Windows: Open the command prompt cmd.

   
   

   
   


2. 
   

   Go to the directory with the virtual disk you want to resize. For example:

   
   
   

   cd "My VMs"
   
   

   
   


3. 
   

   Create a new VirtualBox disk with your desired filename, size (in megabytes) and format (either Standard (dynamic) or Fixed). For example, to create a 50 GB fixed-format disk called MyNewDisk.vdi:

   
   
   

   VBoxManage createmedium --filename "MyNewDisk.vdi" --size 50000 --variant Fixed
   
   

   
   
   

   
   

   If VBoxManage is not recognized as a command, specify the full path to it. It can be found in the VirtualBox installation directory. On Windows the above command would become:

   
   
   

   "C:Program FilesOracleVirtualBoxVBoxManage.exe" createmedium
   
       --filename "MyNewDisk.vdi" --size 50000 --variant Fixed
   
   

   
   

   
   


4. 
   

   Copy the original disk to the new disk.

   
   
   

   VBoxManage clonemedium "MyOriginalDisk.vdi" "MyNewDisk.vdi" --existing
   
   

   
   


5. 
   

   The resize is done! You can check the properties of the new disk if you want:

   
   
   

   VBoxManage showmediuminfo "MyNewDisk.vdi"
   
   

   
   



6. Change the virtual machine to use the new disk instead.

Next, on your guest OS you need to resize the partitions to use the newly available space.

For those who have Windows on a VHD, like I did, first convert to VDI by cloning with the following Linux command. (Note, Windows VM powered off.)

VBoxManage clonehd Windows10.vhd Windows10.vdi --format vdi

This will duplicate the vhd.

Then the VDI can be resized with the following. Note the VDI won't actually grow until it is used.

VBoxManage modifyhd Windows10.vdi --resize 80000

After fixing up the storage mounting in the VM host software, and powering on the VM, Windows boots, but the partition will still be the same size. Google for a Windows tool that can resize the C drive partition. I used EaseUs Partition Master to grow the C drive partition to my new size.

Finally, the VHD can be deleted.