VirtualBox

Changes between Initial Version and Version 1 of Ticket #16311, comment 4


Ignore:
Timestamp:
01/21/2017 10:42:19 AM (4 months ago)
Author:
mpack
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #16311, comment 4

    initial v1  
    44 
    55It seems that when the container type is VHD then the sanity check code sees the old disk size as 0MB. This means that the size multiplier for the new size is always >1000 times 0MB, hence I guess it is now impossible to resize VHDs using --resize. As a workaround, --resizebytes still works. 
     6 
     7Wait... belay that. He says VHD, but the commands he enters say VDI. Still, ''something'' weird is going on - it still gets 0MB for the old disk size, how? I guess that's the bit which needs explaining. 

www.oracle.com
ContactPrivacy policyTerms of Use