Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

"Deployed an OVF with NVRAM is not supported" error deploying an OVF in vSphere 6.7 (67724)

Last Updated: 4/7/2021Categories: TroubleshootingTotal Views: 29236Language:
Chinese (Simplified)JapaneseEnglish

46 like this article

Subscribe to get an email
newsletter with new updates

46 people found this helpful Please provide article feedback:

Learn how VMware Skyline Advisor and Skyline Health Diagnostics work together to provide proactive intelligence and self-service log analysis.

Use Skyline Advisor to avoid issues before they occur across VCF, vSphere, vSAN, NSX, vROps & Horizon. Skyline Findings are based on top KBs, VMSAs/CVEs and design best practices.

Use Skyline Health Diagnostics to root cause vSphere & vSAN logs when an issue occurs. Skyline Health Diagnostic Findings are based on top KBs and VMSA/CVEs. You can use the Skyline Health Diagnostics tool in online or offline mode.

If you require additional help from technical support, please use Skyline Advisor to initiate a Log Assist to reduce time to upload logs. TSEs can also initiate logs to reduce effort.

Symptoms

Deploying an OVF located in a VMware Content Library fails in:

6.7 environment

6.5 environment or using the 6.7 vSphere Web

In the vSphere Web Client, you see entries similar to:

Deployed an OVF with NVRAM is not supported (incompatible vCenter version).

Using the OVFtool, in the ovftool.log file, you see entries similar to:

2019-02-12T16:15:31.101Z verbose OVFTool[70000E045000] [Originator@6876 sub=Default] Bad return code from POST request: 500
2019-02-12T16:15:31.108Z verbose OVFTool[109AE45C0] [Originator@6876 sub=Default] Exception thrown:
N5boost16exception_detail10clone_implINS0_19error_info_injectorI16OvfToolExceptionEEEE(Bad response code (500) from POST request)"

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Cause

An OVF exported from a virtual machine from a 6.7 environment now contains four types of files:

NVRAM

OVF

VMDK

MF

OVF files exported from a 6.5 environment does not generate a NVRAM file. Only the 6.7 HTML5 client recognizes the NVRAM file during import.

Resolution

This is expected behavior.

OVF templates created in a 6.7 environments can only be deployed into 6.7 environments with the vSphere Client (HTML5) as it supports OVF files that contains an NVRAM file.

Workaround

To work around this issue:

Export the OVF from the 6.7 environment.

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"/>

Notes: 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.

How to use ovftool:

Download the  ovftool

Open a Windows command prompt with administrator privileges (cmd.exe)

Navigate to the directory where you installed ovftool (by default: cd “<C:\Program Files\VMware\VMware> OVF Tool”)

To deploy VM from OVF template run this command:

ovftool.exe --X:logLevel=trivia --X:logToConsole --skipManifestCheck --datastore=datastorename "<path file of ovf>" "vi://administrator:Password@<vCenter FQDN or IP>/Datacenter/host/Cluster/<Host IP or FQDN>"

For example:
C:\Program Files\VMware\VMware OVF Tool>  ovftool.exe --X:logLevel=trivia --X:logToConsole --skipManifestCheck --datastore=iSCI_1 "C:\vcenter_ovf" "vi://administrator:Password@[email-masked]/DC_1/ESXI_1/CL_1/ESXi_1"

Notes:

These flags enable trivia logging and output to command prompt which assists with troubleshooting if ovftool fails:.--X:logLevel=trivia --X:logToConsole

Some additional flags may be required in order to successfully export or deploy:

--skipManifestCheck
--disableVerification
--X:skipContentLength
--noSSLVerify
--acceptAllEulas

For further information on what the above flags refer to, see the following document: OVT Tool User's Guide Command-Line Options

For more information on the OVF Tool, see  OVF Tool Documentation.

Related Information

Cannot Import OVF file from vCenter 6.7 to 6.5 communities post

"PostNFCData failed : IO error" when deploying virtual machine from OVF template through host client

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere Web Client

VMware vSphere

VMware vCenter Server

Related Versions:

VMware vSphere Web Client 6.7.x

VMware vSphere Web Client 6.5.x

VMware vCenter Server 6.7.x

Take Our Survey

Support Assistant