Error: "com.vmware.vim.binding.vim.fault.VmValidateMaxDevice vCenter Server task failed..." when reconfiguring or powering on a VM

Products

• VMware Cloud Director

Issue/Introduction

When attempting to upgrade a vGPU profile for a virtual machine in VMware Cloud Director, the task fails. You may also encounter errors when changing CPU configurations, such as the number of cores per socket.

• com.vmware.vim.binding.vim.fault.VmValidateMaxDevice vCenter Server task failed - '2' of device 'vmiop' was found. Only '1' allowed.

• The number of cores per socket can only be changed for the virtual machine when powered off.

Environment

VMware Cloud Director 10.6.x

Cause

Virtual hardware limitations and power state restrictions cause this issue:

The target vGPU profile attempts to add a second vmiop device. The underlying system is restricted to a maximum of one such device for the current VM configuration.

VMware Cloud Director cannot modify the CPU Cores per Socket configuration while the virtual machine is in a Powered On state.

Due to the VM's hard limit on CPUs (e.g., 8 CPUs), the new profile cannot be allocated the required higher number of CPUs.

Resolution

To resolve this issue, you must align the VM state and hardware configuration with the requirements of the new vGPU profile:

1. Ensure the virtual machine is completely powered off before attempting to change the vGPU profile or CPU topology.

2. In vCenter, verify that the VM hardware version supports the required number of CPUs and that no manual limits are preventing the expansion to X number of CPUs.

3. If the Higher Specification vGPU profile is not strictly required, roll back to the previously used vGPU profile.

4. For profiles requiring multiple vmiop devices, consider deploying a new VM instance configured specifically for multi-vGPU support.