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

"Invalid configuration for device" error deploying vApp or Deploying VMs from OVF in vSphere 6.7 (65205)

Last Updated: 8/17/2023Categories: TroubleshootingTotal Views: 41664Language:
Chinese (Simplified)JapaneseEnglish

15 like this article

Subscribe to get an email
newsletter with new updates

15 people found this helpful Please provide article feedback:

Symptoms

In vSphere 6.7, you are unable to deploy OVF templates.

In vCloud Director that is backed by a vSphere 6.7 environment, you are unable to add a vApp from OVF.

In the vSphere Web Client, you see a similar error:

Invalid configuration for device '2'.

Note: The above device number may be different from '2'

In /var/log/vpxa.log on the host that attempts the OVF/OVA import, you may see a similar message:

2018-12-21T14:27:36.624Z info vpxd[16006] [Originator@6876 sub=Default opID=<VCD_UUID>;activity=urn:uuid:<ACTIVITY_UUID>] [VpxLRO] -- ERROR lro-72155 --  -- VmprovWorkflow: vim.fault.InvalidDeviceSpec:
--> Result:
--> (vim.fault.InvalidDeviceSpec) {
-->    faultCause = (vmodl.MethodFault) null,
-->    faultMessage = <unset>,
-->    property = "VirtualVideoCard.videoRamSizeInKB",
-->    deviceIndex = 2
-->    msg = "Invalid configuration for device '2'."
--> }

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

Cause

This issue occurs because vSphere 6.7 incorrectly attempts to validate that the Video Memory does not exceed 128 MB in size. However, with hardware versions 14 and later, the SVGA device raised the maximum value for svga.vramSize to allow guests to set modes using up to 256MB of video memory.

Hardware Features Available with Virtual Machine Compatibility Settings

Resolution

This issue is resolved in vSphere 6.7 Update 1 available from VMware Downloads.

Workaround

If you are unable to upgrade at this time you can work around this issue by editing the VM or OVF configuration file.

Edit the virtual machine

Connect to the ESXi hos the virtual machine (VM) resides on.

Navigate to were the VM is located

Open the VM configuration file with this command: vi vm_name.vmx

Look for the svga.vramSize entry and increase the available memory.

Example: svga.vramSize = "134217728"

Save and close the file.

Edit the OVF file

Edit the OVF file in a plain text editor and make the following change:

Original value:

Item ovf:required="false">

<rasd:AutomaticAllocation>false</rasd:AutomaticAllocation>

<rasd:ElementName>video</rasd:ElementName>

<rasd:InstanceID>10</rasd:InstanceID>

<rasd:ResourceType>24</rasd:ResourceType>

<vmw:Config ovf:required="false" vmw:key="videoRamSizeInKB" vmw:value="262144"/>

<vmw:Config ovf:required="false" vmw:key="enable3DSupport" vmw:value="true"/>

</Item>

New Value:

<vmw:Config ovf:required="false" vmw:key="videoRamSizeInKB" vmw:value="128000"/>

<vmw:Config ovf:required="false" vmw:key="enable3DSupport" vmw:value="true"/>

</Item>

Related Information

Deploying a new virtual machine from a template fails with the error: Invalid configuration for device "1"

"The operation failed due to Invalid configuration for device 8" during OVF deployment from Content Library

Cloning a virtual machine fails with the error: Invalid configuration for device device_number

"Invalid Configuration for Device 0" error powering on / Cloning virtual machine

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

VMware Cloud Director for Service Provider

VMware Cloud Director

Related Versions:

VMware vSphere ESXi 6.7

VMware Cloud Director for Service Provider 9.x

VMware Cloud Director for Service Provider 8.20.x

Take Our Survey

Support Assistant