Comment 8 for bug 1898871

Hi John Chittum,
 > Does VMWare provide guidance on editing OVF files outside of booting an image, making a change, and exporting?

 I try the following steps and it works.

 1) extract ubuntu-impish-21.10-cloudimg.ova, we will see three files ubuntu-impish-21.10-cloudimg.ovf, ubuntu-impish-21.10-cloudimg.mf and ubuntu-impish-21.10-cloudimg.vmdk

 2) edit file ubuntu-impish-21.10-cloudimg.ovf and change "<rasd:AutomaticAllocation>true</rasd:AutomaticAllocation>" to "<rasd:AutomaticAllocation>false</rasd:AutomaticAllocation>" for the element serial0 as described in #5

 3) produce the SHA256 for modified file ubuntu-impish-21.10-cloudimg.ovf with the command
    shasum -a 256 ubuntu-impish-21.10-cloudimg.ovf

 4) edit file ubuntu-impish-21.10-cloudimg.mf to update the SHA256 value of file ubuntu-impish-21.10-cloudimg.ovf

 5) repack ubuntu-impish-21.10-cloudimg.ova with the command:
    tar cf ubuntu-impish-21.10-cloudimg.ova ubuntu-impish-21.10-cloudimg.ovf ubuntu-impish-21.10-cloudimg.mf ubuntu-impish-21.10-cloudimg.vmdk

 6) (optional) deploy the repacked ubuntu-impish-21.10-cloudimg.ova in ESXi and I don't hit previous warning message when VM is powered on.

Thanks
Yuhua Zou