Workaround:
Once exported, edit the OVF file and remove all the NVRAM entries
<File ovf:id=“file3″ ovf:href=“<VM Name>.nvram“ ovf:size=“8684″/>
<vmw:ExtraConfig ovf:required=“false“ vmw:key=“nvram“ vmw:value=“ovf:/file/file3″/>
If using the OVFtool make sure to use the –skipManifestCheck this allows the OVF to be created after removing the references to NVRAM without this command the OVF Tool would not be able to confirm the manifest file and will return an error
E:\PC_SAVE\VMwareESXi-Backup>C:\“Program Files\VMware\VMware OVF Tool\ovftool.exe“ –datastore=“HDD500GB“ –diskMode=thin –name=VA-DB-I-029 –skipManifestCheck F:\PC_SAVE\VMwareESXi-Backup\medico27SystemWorkshopTemplate\VA-DB-I-029\VA-DB-I-029.ovf vi://root:<password>@192.168.1.143
Opening OVF source: F:\PC_SAVE\VMwareESXi-Backup\medico27SystemWorkshopTemplate\VA-DB-I-029\VA-DB-I-029.ovf
The manifest does not validate
Opening VI target: vi://root@192.168.1.143:443/
Deploying to VI: vi://root@192.168.1.143:443/
Transfer Completed
Warning:
– The manifest is present but user flag causing to skip it
Completed successfully
This entry was posted on Samstag, Juli 3rd, 2021 at 20:33 and is filed under Administration, VMware vSphere 7. You can follow any responses to this entry through the RSS 2.0 feed.
You can leave a response, or trackback from your own site.