VMware Crash when trying to install vSRX on WMware Workstation Pro

[#1]

When opening a OVA file (vSRX JUNIPER), just after accepting the licence terms, WMware Workstation Crash with error:

FATAL APPLICATION ERROR: Invalid vector <T> subscript (class std::out_of_range).

Add infos:
I installed another VM without pb.
OVA file integrity check ok
VM requirements OK

[#2]

Having the same problem here. Did you ever get anywhere with this?

[#3]

I started facing this issue with VMware workstation 14.x , after rolling back to Workstation 12.x ova file is working fine. 

Thanks , 

Mahdy

[#4]

Hey

I managed to fix this if your interested.

If you use 7zip to extract the OVA you can edit the OVF using notepad. <-- this whole section below:

         <!--<DeploymentOptionSection>
           <Info>vSRX RAM Deployment Options</Info>
           
           <Configuration ovf:id="Default" ovf:default="true">
               <Label>Default</Label>
               <Description>
               2 CPUs
               </Description>
           </Configuration>
           <Configuration ovf:id="3GvRAM">
               <Label>3G vRAM</Label>
               <Description>
               3G Memory (recommended if UTM and/or IDP are enabled)
               </Description>
           </Configuration>
           


           <Configuration ovf:id="4GvRAM">
               <Label>4G vRAM</Label>
               <Description>
               4G Memory
               </Description>
           </Configuration>
                      <Configuration ovf:id="1GvRAM">
               <Label>1G vRAM</Label>
               <Description>
               1G Memory
               </Description>
           </Configuration>
           

           </DeploymentOptionSection>
            -->

You need to then delete the .cert, .mf and .pem file from the folder.

Go back to VMware Workstation > Open > Browse to extracted folder and open the new OVF with the changes and it imports fine. Running three on version 14.1.1 at the moment.

Hope this helps.

[#5]

Need to change some addition content in ovf file as @Charles_Juniper's mentions and:

<!--
<Item ovf:configuration="4GvRAM">
<rasd:AllocationUnits>byte * 2^20</rasd:AllocationUnits>
<rasd:Description>Memory Size</rasd:Description>
<rasd:ElementName>Memory</rasd:ElementName>
<rasd:InstanceID>%iid%</rasd:InstanceID>
<rasd:ResourceType>4</rasd:ResourceType>
<rasd:VirtualQuantity>4096</rasd:VirtualQuantity>

</Item>
<Item ovf:configuration="3GvRAM">
<rasd:AllocationUnits>byte * 2^20</rasd:AllocationUnits>
<rasd:Description>Memory Size</rasd:Description>
<rasd:ElementName>Memory</rasd:ElementName>
<rasd:InstanceID>%iid%</rasd:InstanceID>
<rasd:ResourceType>4</rasd:ResourceType>
<rasd:VirtualQuantity>3072</rasd:VirtualQuantity>
</Item>
<Item ovf:configuration="1GvRAM">
<rasd:AllocationUnits>byte * 2^20</rasd:AllocationUnits>
<rasd:Description>Memory Size</rasd:Description>
<rasd:ElementName>Memory</rasd:ElementName>
<rasd:InstanceID>%iid%</rasd:InstanceID>
<rasd:ResourceType>4</rasd:ResourceType>
<rasd:VirtualQuantity>1024</rasd:VirtualQuantity>
</Item>
-->

And again, thanks to @Charles_Juniper 🙂

[#6]

Thanks, it works .

1. Commenting tags :
   <DeploymentOptionSection>
   <Item ovf:configuration="XGvRAM"> | X is the RAM ammount

[#7]

Hi,

What actually you chnaged ?

All the content is the same as in orignal file ?

Same as for the eralier reply as well ?

What actually you huys changed?

[#8]

You need to change some things as mentioned in the first post of this thread or the first reply.

It is applicable to vSRX 12.x and VMWare Workstation 14.x. That I tested. Can work well for VMWare Workstation 15.x. If you use vSRX 15.x it is not necessary any more.

[#9]

Hi,

1. the issue still occurs with workstation 15.0.1 and I updated my "report" to VMware with that information at https://communities.vmware.com/message/2816761

2. workaround is still the same as before

- edit .ovf file and remove the DeploymentOptionSection

- further edit the .ovf file so that "<Item ovf:configuration="4GvRAM">" reads just "<Item>"

- remove the .mf manifest file as the signature for the .ovf file obviously doesn't match anymore

Regards

Ulf

[#10]

Thanks for this!

Only problem I had (Workstation v14, vSRX Eval 18.2) was that the image booted into Wind River OS. Problem is that the default interface on WS is not vmxnet3.

You also need to go into the VMX-file and replace the Virtualdeve statements with  ethernet*.virtualDev = "vmxnet3"  wher the * is the interface number for each of the Ethernet adapters