Disk size problem with vmware convert 3.0.3

[dwchan]

Not that big of a deal, but want to know if anyone experience this problem with the latest version of vmware converter 3.0.3 When I go ahead and resize a disk (usually lower it size) to some whole value. When the migration is complete, it is always few megabytes extra. For example, when I say I want a 9.0GB C drive, when the migration is done, inside esx it report the drive being 9.0124 G versus 9.0. Weird

[K-MaC]

I am no expert but I would attribute it to the difference between KB and KiB 1000 vs 1024. Hope this helps.

1 byte (B, b): (2^0 bytes, iow 1 byte)

1 kilobyte (KB, kib): (2^10 bytes, iow 1024 bytes)

1 megabyte (MB, Mib): (2^20 bytes, iow 1 048 576 bytes, 1024 kib)

1 gigabyte (GB, Gib): (2^30 bytes, iow 1 073 741 824 bytes, 1 048 576 kib, 1024 Mib)

1 terrabyte (TB, Tib): (2^40 bytes, iow 1 099 511 627 776 bytes, 1 073 741 824 kib, 1 048 576 Mib, 1024 Gib)

Message was edited by: K-MaC Spacing

[theanykey · Accepted solution]

I actually reproduced this a couple of months back. Here is the scoop.

When asking for a 10.00GB .vmdk file ... you get ...

ESX/VC will create a disk of 9.98GB within a .vmdk filename of 10.00GB.

Converter will create a disk of 10.00GB within a .vmdk filename of 10.02GB.

What you are seeing is roughly 0.02GB which is required when building a virtual disk within a .vmdk file. When using ESX or VC you will not notice this because you get a .vmdk file specific to the size requested. But when converting, it sets the requested filesize to the size of the resulting disk/partition and as a result, 0.02GB gets tacked on for the .vmdk file.