To resolve this issue, reload the virtual machine's .vmx configuration file.
Note: Configuration changes through the .vmx file require the virtual machine to be powered off.
To reload the virtual machine's .vmx configuration file, perform one of these options:
Option 1 - reload the .vmx configuration file from the command line
- SSH to the ESXi host via root
- Obtain the Inventory ID (Vmid) for the virtual machine:
vim-cmd vmsvc/getallvms
Note: The output shows virtual machines which are registered on the ESXi host. Command output will be similar to:
Vmid Name File Guest OS Version Annotation
10 ExampleVM [datastore] ExampleVM/ExampleVM.vmx windows8Server64Guest vmx-08
In the above example, the Vmid is 10.
- Reload the .vmx file:
vim-cmd vmsvc/reload <Vmid>
Option 2 - reload the configuration file of all the virtual machines on the ESXi host using a script
- SSH to the ESXi host via root
- Reload all virtual machine's configuration files registered to the host:
for a in $(vim-cmd vmsvc/getallvms 2>&1 |grep invalid |awk '{print $4}'|cut -d \' -f2);do vim-cmd vmsvc/reload $a;done