OPERATIONAL DEFECT DATABASE
...
...
Deploying OVF template from the content library fails with the error similar to: "The operation failed due to Invalid configuration for device 8" In the /var/log/vpxd.log file, you see the entries similar to: 2017-08-23T21:33:59.340Z info vpxd[7F5D2265F700] [Originator@6876 sub=Default opID=4768a78d-f7bb-4c50-a9ff-e90f7e72a24a-2370-ngc-25-b2-7c-91-79-7b-57] [VpxLRO] -- ERROR task-internal-10643 -- -- VmprovWorkflow: vim.fault.InvalidDeviceSpec:--> Result:--> (vim.fault.InvalidDeviceSpec) {--> faultCause = (vmodl.MethodFault) null,--> property = "VirtualVideoCard.graphicsMemorySizeInKB",--> deviceIndex = 8,--> msg = "Invalid configuration for device '8'."--> }--> Args:--> Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.
This issue occurs because ESXi 6.0 does not take value -1 while it can take null value if it is unknown from the source virtual machine, and set the default value.
This issue is resolved in VMware ESXi 6.0 Patch Release ESXi600-201807001, available at VMware Patch Downloads.
To work around this issue, remove the vmw:value="-1" from the OVF descriptor: Download the exported OVF template from content library.Edit the OVF descriptor and makethe following changes: <vmw:Config ovf:required="false" vmw:value="-1" vmw:key="graphicsMemorySizeInKB"/> to <vmw:Config ovf:required="false" vmw:key="graphicsMemorySizeInKB"/> Upload the OVF template back to content library.
Click on a version to see all relevant bugs
VMware Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
