Loading

×Sorry to interrupt
CSS Error

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

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

Last Updated: 12/15/2015Categories: TroubleshootingTotal Views: 17288Language:
Chinese (Simplified)JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

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).
</time><YYYY-MM-DD>T<time></time>.315: vmx| [msg.scsi.esx.virtualDevFailed] Unable to create virtual SCSI device for scsi0:0, '<path to vmdk>'
<YYYY-MM-DD>T<time></time>.315: vmx| [msg.moduletable.powerOnFailed] Module DevicePowerOn power on failed.
<YYYY-MM-DD>T<time></time>.315: vmx| ----------------------------------------
<YYYY-MM-DD>T<time></time>.331: vmx| VMX_PowerOn: ModuleTable_PowerOn = 0 Nov 05 <YYYY-MM-DD>T<time></time>.332: vmx| MigrateSetStateFinished: type=2 new state=11 <YYYY-MM-DD>T<time></time>.332: vmx| MigrateSetState: Transitioning from state 10 to 11.
<YYYY-MM-DD>T<time></time>.333: vmx| Migrate_SetFailure: The VM failed to resume on the destination during early power on.
<YYYY-MM-DD>T<time></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></time>.334: vmx| ----------------------------------------

The vmkernel.log file contains entries similar to:

<YYYY-MM-DD>T<time></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></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></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.

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.

Related Information

Tips for editing a .vmx file
vShield Endpoint で保護されている仮想マシンで vMotion の実行またはパワーオンに失敗する
执行 vMotion 或打开受 vShield Endpoint 保护的虚拟机的电源失败

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vShield Endpoint

VMware vCenter Lab Manager

Related Versions:

VMware vShield Endpoint 5.1.x

VMware vShield Endpoint 5.0.x

VMware vShield Endpoint 1.0.x

VMware vCenter Lab Manager 4.0.x

Take Our Survey

Support Assistant