Re: CoresPerSocket

I never found a way to do this within the build profile in advance of building the machine, so as a workaround, I dropped my profile's vCPU count to 4 to meet the license restriction, then altered the CPU configuration via a PostOutputCreation step, along the lines of that posted here: http://communities.vmware.com/thread/431997

My resulting script looks like this:

                                <vadk:Script vadk:name="Virtual Hardware Fix" vadk:enabled="true">                                # Avaya specific script that will:                                #   Update any vmx-07 entry to vmx-08                                #   Rebuild the manifest                                # Move to the OVF directory                                cd `dirname $1`                                # Update Virtual Hardware Type                                sed -i -e &quot;s/vmx-07/vmx-08/&quot; $1                                # Update the CPU configuration to 8 cores with 4 cores per socket
sed -i -e &quot;/ResourceType&gt;3&lt;/ {
N
s/VirtualQuantity&gt;4/VirtualQuantity&gt;8/
a\        &lt;vmw:CoresPerSocket ovf:required=\&quot;false\&quot;&gt;4&lt;/vmw:CoresPerSocket&gt;
}&quot; $1                                # Rebuild the manifest file                                sha=`sha1sum $1 | awk &apos;{print $1}&apos;`                                ovf=$(basename $1)                                shafile=$(basename $1 .ovf).mf                                sed -i -e &quot;s/^SHA1($ovf)=.*/SHA1($ovf)=$sha/&quot; $shafile                                </vadk:Script>

Hopefully somebody may find this helpful!