Search the VMware Knowledge Base (KB)
View by Article ID

Performing vMotion or powering on a virtual machine being protected by vShield Endpoint fails (1030463)

  • 8 Ratings

Symptoms

  • Powering on a virtual machine fails with the error:

    Module DevicePowerOn power on failed.
    Unable to create virtual SCSI device for scsi0:0, '/vmfs/volumes/datastorename/VirtualMachineHome/VirtualMachineDisk.vmdk'
    Failed to attach filter 'VFILE' to scsi0:0: Not found (195887107).

  • Performing a vMotion on a powered on virtual machine fails at 78% or 82%
    • You see the vCenter Server error:

      Failed to resume on destination

    • The vmware.log file contains entries similar to:

      <YYYY-MM-DD>T<TIME>.314: vmx| Msg_Post: Error Nov 05 17:37:18.315: vmx| [msg.scsi.esx.filterAttachmentFailed] Failed to attach filter 'VFILE' to scsi0:0: Not found (195887107).
      <YYYY-MM-DD>T<TIME>.315: vmx| [msg.scsi.esx.virtualDevFailed] Unable to create virtual SCSI device for scsi0:0, '<path to vmdk>'
      <YYYY-MM-DD>T<TIME>.315: vmx| [msg.moduletable.powerOnFailed] Module DevicePowerOn power on failed.
      <YYYY-MM-DD>T<TIME>.315: vmx| ----------------------------------------
      <YYYY-MM-DD>T<TIME>.331: vmx| VMX_PowerOn: ModuleTable_PowerOn = 0 Nov 05 <YYYY-MM-DD>T<TIME>.332: vmx| MigrateSetStateFinished: type=2 new state=11 <YYYY-MM-DD>T<TIME>.332: vmx| MigrateSetState: Transitioning from state 10 to 11.
      <YYYY-MM-DD>T<TIME>.333: vmx| Migrate_SetFailure: The VM failed to resume on the destination during early power on.
      <YYYY-MM-DD>T<TIME>.333: vmx| Msg_Post: Error Nov 05 17:37:18.334: vmx| [msg.migrate.resume.fail] The VM failed to resume on the destination during early power on.
      <YYYY-MM-DD>T<TIME>.334: vmx| ----------------------------------------

    • The vmkernel.log file contains entries similar to:

      <YYYY-MM-DD>T<TIME> <vmname>vmkernel: 0:20:35:19.090 cpu2:6670)VMotionSend: 3836: 1288978553136411 S: Sent all modified pages to destination (network bandwidth ~53.890 MB/s)
      <YYYY-MM-DD>T<TIME> <vmname> vmkernel: 0:20:35:20.571 cpu2:6671)WARNING: Migrate: 296: 1288978553136411 S: Failed: Failed to resume VM (0xbad0044) @0x418034c13cec
      <YYYY-MM-DD>T<TIME> <vmname> vmkernel: 0:20:35:20.602 cpu2:4609)WARNING: Migrate: 4249: 1288978553136411 S: Migration considered a failure by the VMX. It is most likely a timeout, but check the VMX log for the true error.


      Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment. 


Resolution

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.
  1. Locate the virtual machine configuration (.vmx) file. For more information, see Tips for editing a .vmx file (1714).
  2. Open the .vmx file using a text editor.
  3. In the file, you see entries similar to:

    VFILE.globaloptions = "svmip=A.B.C.D svmport=abcd"
    scsi0:0.filters = "VFILE
    "

  4. Delete these entries and then save the .vmx file.
  5. 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.

See Also

Update History

01/25/2013 - Minor formatting corrections.

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 8 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)




Please enter the Captcha code before clicking Submit.
  • 8 Ratings
Actions
KB: