Page 1 of 1
Failed to resize medium
Posted: 12. Feb 2022, 19:18
by Axell
Hi there!!!
Still resizing of vdi don't work for me.
Input:
Host - Win 10 Pro x64;
VM Box - 6.1.32 r14920 (Qt5.6.2)
VM - WS2019, virtua drive - WS2019.vdi
I have NO snapshots
VDI size = 20 Gb, try to resize for example to 30 Gb (30*1024 = 30720)
Type of my Virt hard disk is: Normal
My commands are:
Code: Select all
cd "C:\Program Files\Oracle\VirtualBox\"
.\VBoxManage.exe modifymedium 'E:\VMs\WS2019\WS2019.vdi' --resize 30720
Screen 1 from console:

- 1.jpg (47.85 KiB) Viewed 3150 times
Screen 2 from GUI:

- 2.jpg (76.6 KiB) Viewed 3150 times
What is the problem there???
Re: Failed to resize medium
Posted: 12. Feb 2022, 19:59
by scottgus1
For the first command line attempt, the path to the file is very strange:
Could not get the storage format of the medium 'C:\Program Files\Oracle\VirtualBox\'E:\VMs\WS2019\WS2019.vdi' '
I think that's because of the .\ behind Vboxmanage.exe. That .\ does not need to be there if the command window is operating in 'C:\Program Files\Oracle\VirtualBox\'.
For the GUI attempt, could it be possible that the .vdi is a fixed size .vdi? Only Dynamically expanding .vdi's can be increased.
Please provide the text output of this command:
vboxmanage showmediuminfo E:\VMs\WS2019\WS2019.vdi
Re: Failed to resize medium
Posted: 13. Feb 2022, 08:44
by Axell
1. I was surprized i think i just repost this....
viewtopic.php?t=103633 (cant insert full path)
2. I think there is no metter:
Code: Select all
.\VBoxManage.exe modifymedium 'C:\dev\VirtualBox VMs\PRJ\PRJ-disk001.vdi' --resize 81920
or
Code: Select all
VBoxManage.exe modifymedium 'C:\dev\VirtualBox VMs\PRJ\PRJ-disk001.vdi' --resize 81920
.\ just shown current folder. But yes seems it is no need in our situation, thanks.
I try it and have the same error.
Seems like it is really fixed. But i create VM with default options and don't know about this moments...
Now try to modify it with some manuals.

- 3.jpg (116.24 KiB) Viewed 3068 times
Re: Failed to resize medium
Posted: 13. Feb 2022, 09:35
by Axell
The steps are here:
1. Check all of our disks
2. Create a copy of disk with new name and new type - dynamic with this in my case
Code: Select all
VBoxManage.exe clonemedium disk "E:\VMs\WS2019\WS2019.vdi" "E:\VMs\WS2019\WS2019dyn.vdi" -variant Standard
I really don't undestand why dymamic disk is called: Standart....

- bandicam 2022-02-13 10-00-55-192.jpg (82.48 KiB) Viewed 3054 times
3. Remove our drive from GUI

- bandicam 2022-02-13 09-59-17-808.jpg (86.6 KiB) Viewed 3054 times
4. Remove our old VDI disk from disk list (
but in my case i remove old and new disk because it was an error while additing a new one)
Code: Select all
VBoxManage.exe closemedium OLD_DISK_UUID --delete
Where OLD_DISK_UUID is UUID number of an old disk
5. Rename a new diks with the name of old, in my case WS2019dyn.vdi to WS2019.vdi
6. Add disk to VM

- add disk to VM.jpg (23.3 KiB) Viewed 3054 times
7. Resize our disk C (in my case) with standart
Computer Management GUI
Re: Failed to resize medium
Posted: 13. Feb 2022, 09:37
by Axell
7. Resize our disk C (in my case) with standart Computer Management GUI

- bandicam 2022-02-13 10-21-47-801.jpg (59.57 KiB) Viewed 3054 times
Re: Failed to resize medium
Posted: 13. Feb 2022, 09:39
by Axell
Tell me pls is dynamic volume not a default volume while VM creation?
I just want everytime create only dynamic volumes to my new VMs.
Re: Failed to resize medium
Posted: 13. Feb 2022, 12:03
by mpack
Axell wrote:Tell me pls is dynamic volume not a default volume while VM creation?
The default is dynamic VDI, but you are offered a dialog every time a VM is created in which you can pick the exact disk container type you want. I recommend that you choose dynamic VDI every time.
I don't know what options are offered on import - I rarely use the export/import feature. From memory however you are given an option to convert the VMDK to a VDI, and I would assume that also means dynamic VDI.
Re: Failed to resize medium
Posted: 13. Feb 2022, 13:36
by Axell
Thanks a lot. Try to create a new VM and clearly look at options.