virtualbox.org

Now I have booted from Gparted but not able to extend it any more to use the unalocated space. Please suggest

Why are you not able to extend it?

Screenshot

You need to move the swap area to the end of the partition table.
Personally I find it easier to delete the swap and then extend the first partition and make sure to leave enough at the end to add the swap back.

If you are not familiar with this and since it can cause real damage to the guest. Be sure you have backed up the guest. Also if you are using snapshots this will not work for you anyway.

I can delete and create the swap again but what about the boot partition next to it ?
If I delete it might not boot at all, can it be re-created ?

OK you might be better off just creating a new guest with the proper size.

Yay ... I think I solved it.
There was no boot partition in the original hard disk (I had posted the screenshot of the Copied one). I deleted the swap and re-created at the end of it after expanding.
I think boot is taken care by the primary partition's boot section itself. Thanks so much for your help. I saved all my settings without having to go for a new installation.

neil@neil-VirtualBox:~$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda1 19G 6.6G 12G 37% /
udev 874M 8.0K 874M 1% /dev
tmpfs 353M 756K 352M 1% /run
none 5.0M 0 5.0M 0% /run/lock
none 881M 1.1M 880M 1% /run/shm
SH 82G 55G 27G 68% /media/sf_SH

I had the same error, but I misunderstood its working. I used the following command :
and got the error. I thought the command was extending the current size, but the '30000' argument is the new size. In my case, the new size was smaller then the current one which was 81920 (discovered with "VBoxManage showhdinfo KPN.FOW.vdi"). This command worked :

I am running VirtualBox on a windows machine via docker and I am executing the command from command prompt "vboxmanage modify C:\Users\KBT2\.docker\machine\machines\default\disk.vdi --resize 100000"
However, the following error is displayed "Resize medium operation for this format is not implemented yet!"

Vasanti, this is a dead thread, despite the previous poster's attempt to resurrect it.

Please post in a new thread, and please enter the exact command you type and the exact error message you receive. (clue that exactness wasn't attempted is the posted command "vboxmanage modify". There is no "vboxmanage modify". There is a "vboxmanage modifymedium disk", though.)

Yes, time to lock this one. People are quite obviously not reading it all - all two pages of it.