VMware Cloud Community
ganesh_patwardh
Contributor
Contributor
Jump to solution

Issue during OVF template deployment (ESXI 5.5)

Hi,

     I created a VM with default settings and exported OVF template out of it and deployed new VM with this template. Every thing works fine.

     But if I change some of the CPU and other options in my VM and create OVF template.. creation works fine but this template refuses to deploy properly.

     These are the change I did in VM settings, not sure which change is causing the issue.

      cores per socket :4 , 

       cpu reservation : 2.4GHz*4, 

       HT: None,

       CPU/MMU virtualization : Hardware CPU and MMU

        Low Latency: High, 

        SMBIOS.reflectHost = TRUE


I found below lines in OVF file generated with above change , these could be causing the issue


<vmw:CpuCompatibilitySection>

      <Info>CPU compatibility constraints</Info>

      <vmw:Level vmw:level="-2147483647"/>

      <vmw:Level vmw:level="-2147483647" vmw:vendor="amd"/>

    </vmw:CpuCompatibilitySection>

.

.

.

<rasd:Reservation>9576</rasd:Reservation>

        <rasd:ResourceType>3</rasd:ResourceType>

        <rasd:VirtualQuantity>4</rasd:VirtualQuantity>

        <vmw:CoresPerSocket ovf:required="false">4</vmw:CoresPerSocket>


Please help me to understand what could have went wrong!!  (If I delete these lines in ovf file then deployment works fine)

0 Kudos
1 Solution

Accepted Solutions
ganesh_patwardh
Contributor
Contributor
Jump to solution

Looks like a bug.. reference  to AMD is added when  "Advanced" option is just clicked and no change is done  (for CPU mask).

This causes compatibility issue during ovf template deployment.

View solution in original post

0 Kudos
1 Reply
ganesh_patwardh
Contributor
Contributor
Jump to solution

Looks like a bug.. reference  to AMD is added when  "Advanced" option is just clicked and no change is done  (for CPU mask).

This causes compatibility issue during ovf template deployment.

0 Kudos