I have installed and uninstalled Vshield on a esx host. However, I can't boot vm's on the esx host. They all give the error below.
Even if I vmotion the vm's towards an other esx host where there is no vshield ever installed on it I will get this error.
I also made a new VM and attached the drives to it. Also this didn't work and gave the same error.
Event Details:
Type: info
Time: 21-9-2010 9:39:15
Task Details:
Description: Power On virtual machine
Error Stack:
Module DevicePowerOn power on failed.
Unable to create virtual SCSI device for scsi0:0, '/vmfs/volumes/....-dc9a65e0-867a-00215aa6ce42/Eurotech../Eurotech....vmdk'
Failed to attach filter 'VFILE' to scsi0:0: Not found (195887107).
Additional Event Details:
Type ID: Info
Target Object Type: ClusterComputeResource
DataCenter Object Type: Datacenter
Host Object Type: HostSystem
Host Build: 260247
VirtualMachine Object Type: VirtualMachine
ChainId: 64288
Additional Task Details:
VC Build: 258902
Task Id: Task
Cancelable: False
Cancelled: False
Description Id: Drm.ExecuteVmPowerOnLRO
Event Chain Id: 64288
I'm getting the identical error. Did you resolve?
Ian
The only Solution was a reinstall of the esx host.
Greetings Ruud
Op 3 nov. 2010 om 20:05 heeft "iforbes" <communities-emailer@vmware.com> het volgende geschreven:
,
A new message was posted in the thread "[Vshield] Vfile error":
http://communities.vmware.com/message/1640668#1640668
Author : iforbes
Email : ian.forbes@scalar.ca
Profile : http://communities.vmware.com/people/iforbes
Message:
If you install and uninstall vShield Endpoint, it can leave entries
in the .vmx file which until removed will cause the VM to become unstart
(or resumeable).
eg:
VFILE.globaloptions = “svmip=169.254.50.39 svmport=8888″
scsi0:0.filters = “VFILE”
ESX4.1 gives this error:
Module DevicePowerOn power on failed.
Unable to create virtual SCSI device for scsi0:0, ‘/vmfs/volumes/4b451286-80fef9f2-6a13-18a90544f4fe/VMNAME/VMNAME-000002.vmdk’
Failed to attach filter ‘VFILE’ to scsi0:0: Not found (195887107).
The solution is to remove those two lines and re-power on the VM.
Cheers - Chris
Had the same error today, you can also get around it by editing this line:
scsi0:0.filters = “VFILE”
in the "Edit Settings - Options - General - Configuration Parameters" via the VI Client.