Error Message

[4752] xxxx-xx-xxT14:57:01.534 [fsys\vmvcb] - SymVmTools: CreateVmExAPI: OK
[4752] xxxx-xx-xxT14:57:01.818 [fsys\vmvcb] - SymVmTools: WaitForTaskComplete: reached Error!
[4752] xxxx-xx-xxT14:57:01.818 [fsys\vmvcb] - SymVmTools: WaitForTaskComplete: Invalid virtual machine configuration. <292>
[4752] xxxx-xx-xxT14:57:01.819 [fsys\vmvcb] - SymVmTools: WaitForTaskComplete: Starting SoapFault dump.
[4752] xxxx-xx-xxT14:57:01.819 [fsys\vmvcb] - SymVmTools:
msg.hostd.configSpec.vnuma.onlyCpuHotaddVirtual NUMA cannot be configured when CPU hotadd is enabled.
configSpec.virtualNum
[4752] xxxx-xx-xxT14:57:01.819 [fsys\vmvcb] - SymVmTools: a
[4752] xxxx-xx-xxT14:57:01.819 [fsys\vmvcb] - SymVmTools: WaitForTaskComplete: Completed SoapFault dump.
[4752] xxxx-xx-xxT14:57:01.819 [fsys\vmvcb] - SymVmTools: WaitForTaskComplete: SYM_VMC_ERROR: TASK_REACHED_ERROR_STATE
[4752] xxxx-xx-xxT14:57:01.820 [fsys\vmvcb] - SymVmTools: WaitForTaskComplete: returning 0X24
[4752] xxxx-xx-xxT14:57:01.822 [fsys\vmvcb] - SymVmTools: CreateVm: SYM_VMC_ERROR: TASK_REACHED_ERROR_STATE
[4752] xxxx-xx-xxT14:57:01.822 [fsys\vmvcb] - SymVmTools: CreateVirtualMachineExAPI: SYM_VMC_ERROR: TASK_REACHED_ERROR_STATE
[4752] xxxx-xx-xxT14:57:01.822 [fsys\vmvcb] - VM_VCBPROXY_FS::CreateVirtualMachine: failed, result = 0X24
[4752] xxxx-xx-xxT14:57:01.823 [fsys\vmvcb] - VM_VCBPROXY_FS::CreateVirtualMachine: vmcCreateVirtualMachineEx reported: Invalid virtual machine configuration., <0X124>
[4752] xxxx-xx-xxT14:57:01.823 [fsys\vmvcb] - VM_VCBPROXY_FS::createVM() Could not create the VM 'xxxxxxxx'

vNUMA is disabled if vCPU hotplug is enabled:
https://kb.vmware.com/s/article/2040375

When the VM is powered on, the vCenter will set some of the vNUMA configuration.  

• The workaround to this issue is to disable the CPU hotplug on the VMs being backed up -OR- to restore the VMs to a vSphere 7.x datastore. 

A supported hotfix has been made available for this issue. Please contact Veritas Technical Support to obtain this fix. This hotfix has not yet gone through any extensive Q&A testing. Consequently, if you are not adversely affected by this problem and have a satisfactory temporary workaround in place, we recommend that you wait for the public release of this hotfix.

Veritas Technologies LLC currently plans to address this issue by way of a patch or hotfix to the current version of the software. Please note that Veritas Technologies LLC reserves the right to remove any fix from the targeted release if it does not pass quality assurance tests. Veritas’ plans are subject to change and any action taken by you based on the above information or your reliance upon the above information is made at your own risk.