I started creating placeholder VMs for otherwise occupied spots in the infrastructure invisible (without Operations and NSX and all that) to vSphere. It's much faster than checking IPAM and efficient since there's no server in machine or process dedicated to the task.
These machines have the real bare minimums of what they can have, 4 megabytes of memory, no disk, no network, 1 CPU only because there's no such thing as a fractional CPU—maybe in containers.
Just now I was cloning one of these and noticed it allocated more than a gigabyte for the machine:
A gigabyte isn't really much, plus, allocated as I understand doesn't mean written. but rather some combination of resources if the machine were to be turned on (it hasn't—there aren't any temporary files, swap, logs, anything), memory for instance for the…um… I want to say the balloon? I don't remember exactly but I did the math, that's over 300 times the memory.
I'm curious, what does this allocation involve? I've read about it in the documentation but memory and disk are explicitly referenced, one isn't there, and the other is almost non-existent in this case.
it is overhead of the VMFS filesystem. if you go to the commandline, you can do an "ls -lah" and you will see the files which take up the space in the VM folder. Just as an example, see the below, this is an empty VM with more or less the same config you created.
[root@w4-hs4-i1505:/vmfs/volumes/vsan:528674a7398e2ef8-ff7ab0d84b18adaa/aa6db162-4451-7eae-7950-0c42a162f588] ls -lah
drwxr-xr-t 1 root root 72.0K Jun 21 07:05 .
drwxr-xr-x 1 root root 512 Jun 21 07:14 ..
-r-------- 1 root root 4.3M Jun 21 07:05 .fbb.sf
-r-------- 1 root root 128.6M Jun 21 07:05 .fdc.sf
-r-------- 1 root root 256.2M Jun 21 07:05 .jbc.sf
-r-------- 1 root root 16.1M Jun 21 07:05 .pb2.sf
-r-------- 1 root root 64.0K Jun 21 07:05 .pbc.sf
-r-------- 1 root root 1.0G Jun 21 07:05 .sbc.sf
drwx------ 1 root root 68.0K Jun 21 07:05 .sdd.sf
On a newly created datastore the hidden .sf metafiles require about 1.5 GB. On a heavily used datastore the metafiles will grow. Especially the .sbc.sf can reach sizes of 30 GB and more.