I am in the middle of an upgrade of our clusters from vSphere 4.1 to vSphere 5.
On all vSphere 4.1 hosts we had vShield Endpoint 3.0.8-308978 installed (epsec_vfile).
On the first cluster, to perform the upgrade, I left all VMs on a single vSphere 4.1 host and rebuilt the remaining hosts manually via ISO to ESXi v5 and applied a patch to upgrade ESXi to v5.0.0 build 474610.
I then installed the vShield Manager v5 appliance and deployed vShield Endpoint v5 to all the vSphere 5 hosts.
My issue is I cannot vmotion or power on any of the VMs from the remaining vSphere 4 host to the vSphere 5 hosts. Because we had installed the epsec_vfile filter (Endpoint v3) on all hosts, all VMs have had their .vmx file updated, which is expected. What isn't expected is that I cannot power on these VMs on vSphere 5 hosts with Vshield Endpoint v5 installed. I get the following errors:
Power On virtual machine:Module DevicePowerOn power on failed.
An unexpected error was received from the ESX host while powering on VM vm-266.
Module DevicePowerOn power on failed.
Unable to create virtual SCSI device for scsi0:0, '/vmfs/volumes/4efb7a66-5903dc3b-22b1-0025b5010116/PDC1ADG002/PDC1ADG002.vmdk'
Failed to attach filter 'VFILE' to scsi0:0: Not found (195887107).
As per KB1030463, If I remove the following two lines from the .vmx file, the VMs power on fine:
This is also expected, but should not be necessary. This is the recommended workaround if you want to power on a VM after it has been powered on, on an ESXi host with vShield Endpoint v3 installed.
On vShield Endpoint v3 the .vmx file is updated on power on, if the above lines are not present. On vShield Endpoint v5 it does not appear to be updating the .vmx files of the VMs after I have removed them.
I have logged into the hosts via SSH and confirmed the epsec filter is installed:
2012-01-28T01:39:27.128917+00:00: The following VIBs are
installed:
epsec-mux 5.0.0-447150