Was mem.hotadd deprecated but not mentioned in the release notes?

[IamTHEvilONE]

Trying to deploy an ovf fails due to an extra config where mem.hotadd is disabled on the example OVF/OVA and I'm using OVFTool 4.3.

OVFTool 4.2 does not error in the same fashion, using the same syntax (--allowExtraConfigs).

The two configs I see in the VM are:

<vmw:Config ovf:required="true" vmw:key="memoryHotAddEnabled" vmw:value="false"/>
<vmw:ExtraConfig ovf:required="true" vmw:key="mem.hotadd" vmw:value="false"/>

[dgold]

The extaconfig is redundant as the regular config shown above maps to mem.hotadd in vmx.

[IamTHEvilONE]

Understood that it is, but both are usually done for backward compatibility for when the it was only an extraConfig.  I can't remember when that was, but my point was more about informing users/developers of a change in functionality in the tools we use and VMware implements.

If something is no longer supported of fully deprecated, then mention that in some public documentation.

[dgold]

I totally agree.  It might be(not sure) probably buried somewhere deep in one of the release notes.