Power-on failure
The virtual machine power-on operation fails with this error when the virtual machine that was earlier protected by vShield Endpoint is either moved or copied to a host that is not protected by the vShield Endpoint security solution.
To resolve this issue, VMware recommends you to move the virtual machine to a host that is protected by vShield Endpoint.
To work around this issue when you no longer want to protect this virtual machine using vShield Endpoint, but want to power on the virtual machine:
Note: Create a backup copy of the configuration file (.vmx) before proceeding.
- Locate the virtual machine configuration (.vmx) file. For more information, see Tips for editing a .vmx file (1714).
- Open the .vmx file using a text editor.
- In the file, you see entries similar to:
VFILE.globaloptions = "svmip=A.B.C.D svmport=abcd"
scsi0:0.filters = "VFILE"
- Delete these entries and then save the .vmx file.
- Power on the virtual machine.
vMotion failure
For vMotion to work with vShield Endpoint the Endpoint LKM must be installed on the ESX/ESXi hosts to which you are trying to vMotion the virtual machine.
When you install the vShield Endpoint security solution, you go into the vShield Manager web console, point to the ESX/ESXi host you want to protect, then click Install. This installs a vmkernel module on the host that is called VFILE. For virtual machines to be able to vMotion from one ESX/ESXi host to another ESX/ESXi host in a cluster, all of the ESX/ESXi hosts in the cluster must have the LKM installed.
To install the vShield Endpoint LKM, go to the vShield Manager web interface and install the Endpoint LKM on the host to which you are trying to vMotion the virtual machine.
For more information on preparing an ESX/ESXi host for the vShield functionality, see
Prepare All ESX Hosts section in the
vShield Quick Start Guide.