Comment 4 for bug 1751858

@jam, i haven't found many use cases for wanting disk.EnableUUID to be 0. I found this:

https://blogs.vmware.com/kb/2013/03/setting-disk-enableuuidtrue-in-vmware-data-protection.html

That's pretty old, but basically, if the option was 0 (false) and an operator enabled it while the VM was running, snapshots would fail because the current config doesn't match the config from when the VM was started.

And also this:

https://kb.vmware.com/s/article/2146204

Apparently the Volume Snapshot Service (VSS) is tied to disk.EnableUUID; if you wanted a quiesced snapshot that doesn't interact with VSS, you might want to set the option to 0 (false).

The reason we want control over this setting is for persistent vsphere storage in kubernetes. You can't have it without disk.EnableUUID=true on the VMs:

https://vmware.github.io/vsphere-storage-for-kubernetes/documentation/existing.html#step-3-enable-disk-uuid-on-node-virtual-machines

So if we do end up supporting this with model config, perhaps the safe thing to do is default it to false to match current behavior, yet allow ops to turn it on when required.