We have a test VM with ‘Shares’ configures as High for CPU and Disk. We have exported this VM as OVA file using the ovftool. When we import the ovftool generated OVA using vSphere UI, the ‘Shares’ v...
See more...
We have a test VM with ‘Shares’ configures as High for CPU and Disk. We have exported this VM as OVA file using the ovftool. When we import the ovftool generated OVA using vSphere UI, the ‘Shares’ values are not honoured and the default ‘Share’ value ‘Normal’ is applied for both CPU and Disk. For the same VM, if we export OVA through vSphere UI and import , then the shares values are honoured. On exploring further, we found that OVF attributes generated for ‘Share’ level by OVFtool and vSphere UI is varying. With OVF tool, it generates the shares value and level attributes as VMWare custom attribute. <vmw:Config ovf:required="false" vmw:key="cpuAllocation.shares.shares" vmw:value="64000"/>
<vmw:Config ovf:required="false" vmw:key="cpuAllocation.shares.level" vmw:value="high"/>
But where as when we export ova from vSphere UI, shares value(rasd:Weight) is generated as per specification. <rasd:Weight>64000</rasd:Weight>
<vmw:Config ovf:required="false" vmw:key="sharesLevel" vmw:value="high"/>
Is there known limitation around this share value attribute ? Is there any workaround to address this behaviour ? vSphere version: vSphere 7.0 U3
