After all, isn't this what Virtual Hardware Versions are for? Why is this NVRAM configuration included when Virtual Hardware Version is set to 13 (or less), when this configuration is only compatible with vSphere 6.7 (Virtual Hardware Version 14)? I would like to hear an explanation why this NVRAM configuration is allowed by ovftool 4.3.0 to be exposed to vSphere 6.5 when a known incompatibility exists. the ovf is successfully imported to vSphere 6.5. ovf template (and deleting the manifest file which should be recalculated in production): After making the following changes to the. Neither error message suggests the underlying cause of the issue, which is an incompatibility with NVRAM-containing.
- vSphere 6.5 Tasks View: The task was cancelled by a user.
- ovftool: Bad response code (500) from POST request.
- We observed similar behaviour using ovftool 4.3.0 which even boasts of improved support for vSphere 6.7 and NVRAM. I consider this a bug which VMware should be accountable for.
VMware needs to add an option to export templates with support of UEFI or no support of UEFI so those of us without 6.7 in all our environments can still use a 6.7 environment to manage templates. I've even sent them links (like this thread) to others with the same issue. While this workaround isn't a major issue, it's frustrating that I've been trying to explain this to VMware Support for 2 weeks now without success. This is great IF all your environments are 6.7, but most of us aren't that lucky, so because I've upgraded by internal cluster that I use for Template mangement to 6.7, I can no longer import any of our templates into a pre 6.7 environment without manually removing the NVRAM entry from the VMX file.
To me it looks like 6.7 now supports UEFI Templates and due to that (I read this a few weeks ago but can't seem to fine the link now where I read it, so hopefully I'm correct with this.), when a template/VM is exported from 6.7 it includes the NVRAM file as well as a line in the vmx for the NVRAM location.
I have the same issue and have been trying to get VMware Support to understand what the problem is but I can't seem to make them grasp what's going on.