Hi André, many thanks for the quick reply!
In my case it's not to be strictly 2GB, but after some empirical tests I figured I'm not really in control of the maximum size of disk chunks and files still grow much larger than the desired size.
Both articles you referred to confirm what I experienced so far.
I copied vmware-vdiskmanager from an old system with Fusion 5.
Alas, although it behaves differently, chunks also grow way beyond 2GB.
So I think it's save to say VMware changed the behaviour of vmware-vdiskmanager after Fusion 3.0.2 earliest, but v 5.0.3 latest.
So, after getting 1023856-vdiskmanager-3.0.2.zip from the aforementioned KB-article does the trick.
FWIW, the older the versions of Fusion/vmware-vdiskmanager the smaller the maximum disk size:
| Fusion 8.5.10 / vmware-vdiskmanager build 7527438 | ide/scsi adapter : [1MB, 8192.0GB] / buslogic adapter : [1MB, 2040.0GB] |
| Fusion 5.0.3 / vmware-vdiskmanager build 1040386 | ide adapter : [1MB, 2040.0GB] / scsi adapter: [1MB, 2040.0GB] |
| Fusion 3.0.2 / vmware-vdiskmanager build 232708 | ide adapter : [1MB, 950.0GB] / scsi adapter: [1MB, 950.0GB] |
(according to the internal help of this versions I have at hands)
BTW, better late than never, I just discovered macOS Finder shows real Gigabytes and not Gibibytes for sizes.
Hence the 2GB we talk about (2*2^30 Bytes) chunk is listed as rounded to 2,15GB (as in metric Gigabytes) and not 2,0GB.
Thanks a lot - Michael.