<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic ovftool generated ova share value not adhered when it is deployed through vSphere UI in VMware vSphere™ Discussions</title>
    <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/ovftool-generated-ova-share-value-not-adhered-when-it-is/m-p/2984898#M45996</link>
    <description>&lt;P class=""&gt;We have a test VM with ‘&lt;STRONG&gt;Shares&lt;/STRONG&gt;’&lt;SPAN class=""&gt;&amp;nbsp; &lt;/SPAN&gt;configures as &lt;STRONG&gt;High&lt;/STRONG&gt; 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 ‘&lt;STRONG&gt;Shares&lt;/STRONG&gt;’ values are not honoured and the default ‘Share’ value ‘Normal’ is applied for both CPU and Disk.&lt;/P&gt;&lt;P class=""&gt;For the same VM, if we export OVA through vSphere UI and import , then the shares values are honoured.&lt;/P&gt;&lt;P class=""&gt;On exploring further, we found that OVF attributes generated for ‘&lt;STRONG&gt;Share&lt;/STRONG&gt;’ level by OVFtool and vSphere UI is varying.&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;With&amp;nbsp;OVF&amp;nbsp;tool, it generates the shares value and level attributes as VMWare custom attribute.&lt;/SPAN&gt;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;&amp;lt;vmw:Config ovf:required="false" vmw:key="cpuAllocation.shares.shares" vmw:value="64000"/&amp;gt;

&amp;lt;vmw:Config ovf:required="false" vmw:key="cpuAllocation.shares.level" vmw:value="high"/&amp;gt;
&lt;/LI-CODE&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;But where as when we export ova from vSphere UI, shares value&lt;STRONG&gt;(rasd:Weight)&lt;/STRONG&gt; is generated as per specification.&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class=""&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;&amp;lt;rasd:Weight&amp;gt;64000&amp;lt;/rasd:Weight&amp;gt;
&amp;lt;vmw:Config ovf:required="false" vmw:key="sharesLevel" vmw:value="high"/&amp;gt;
&lt;/LI-CODE&gt;&lt;P class=""&gt;Is there known limitation around this share value attribute ? Is there any workaround to address this behaviour ?&lt;/P&gt;&lt;P class=""&gt;&lt;STRONG&gt;vSphere version: vSphere 7.0 U3&lt;/STRONG&gt;&lt;/P&gt;</description>
    <pubDate>Thu, 31 Aug 2023 16:56:30 GMT</pubDate>
    <dc:creator>vperiyasamy</dc:creator>
    <dc:date>2023-08-31T16:56:30Z</dc:date>
    <item>
      <title>ovftool generated ova share value not adhered when it is deployed through vSphere UI</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/ovftool-generated-ova-share-value-not-adhered-when-it-is/m-p/2984898#M45996</link>
      <description>&lt;P class=""&gt;We have a test VM with ‘&lt;STRONG&gt;Shares&lt;/STRONG&gt;’&lt;SPAN class=""&gt;&amp;nbsp; &lt;/SPAN&gt;configures as &lt;STRONG&gt;High&lt;/STRONG&gt; 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 ‘&lt;STRONG&gt;Shares&lt;/STRONG&gt;’ values are not honoured and the default ‘Share’ value ‘Normal’ is applied for both CPU and Disk.&lt;/P&gt;&lt;P class=""&gt;For the same VM, if we export OVA through vSphere UI and import , then the shares values are honoured.&lt;/P&gt;&lt;P class=""&gt;On exploring further, we found that OVF attributes generated for ‘&lt;STRONG&gt;Share&lt;/STRONG&gt;’ level by OVFtool and vSphere UI is varying.&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;With&amp;nbsp;OVF&amp;nbsp;tool, it generates the shares value and level attributes as VMWare custom attribute.&lt;/SPAN&gt;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;&amp;lt;vmw:Config ovf:required="false" vmw:key="cpuAllocation.shares.shares" vmw:value="64000"/&amp;gt;

&amp;lt;vmw:Config ovf:required="false" vmw:key="cpuAllocation.shares.level" vmw:value="high"/&amp;gt;
&lt;/LI-CODE&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;But where as when we export ova from vSphere UI, shares value&lt;STRONG&gt;(rasd:Weight)&lt;/STRONG&gt; is generated as per specification.&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class=""&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;&amp;lt;rasd:Weight&amp;gt;64000&amp;lt;/rasd:Weight&amp;gt;
&amp;lt;vmw:Config ovf:required="false" vmw:key="sharesLevel" vmw:value="high"/&amp;gt;
&lt;/LI-CODE&gt;&lt;P class=""&gt;Is there known limitation around this share value attribute ? Is there any workaround to address this behaviour ?&lt;/P&gt;&lt;P class=""&gt;&lt;STRONG&gt;vSphere version: vSphere 7.0 U3&lt;/STRONG&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 31 Aug 2023 16:56:30 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/ovftool-generated-ova-share-value-not-adhered-when-it-is/m-p/2984898#M45996</guid>
      <dc:creator>vperiyasamy</dc:creator>
      <dc:date>2023-08-31T16:56:30Z</dc:date>
    </item>
  </channel>
</rss>

