Caution about vShield Endpoint

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.

Advertisements

2 Responses to Caution about vShield Endpoint

  1. JediMasterMero says:

    i have seen this issue after removing trend micro deep security 7.5 VA and vshield endpoint from my ESX 4.1 however it is happening only with some VMs, i can’t understand y, meanwhile i had another doubt how does vshield edit the VMX file while the machine is powered on? is that related to FSR(fast suspend and resume)

  2. Fu Yong says:

    According to the following article from geeksilver,

    http://geeksilver.wordpress.com/2010/12/15/vmware-vsphere-vshield-1-0-design-flaw-with-vcenter-as-vm/

    The editing of the VMX file is done by vCenter, which will potentially cause some network issue when vCenter is temporarily unavailable (e.g. during vMotion)

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: