Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

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

Clone operation using a Template to VM or a VM to VM would fail with error "An error occurred while communicating with remote host" with Tegile Storage on ESXi 6.7 (59258)

Last Updated: 8/6/2020Categories: TroubleshootingTotal Views: 7398Language:
English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

1) Storage vMotion of a VM from Tegile storage to Tegile storage would fail with error "An error occurred while communicating with remote host"
2) Storage vMotion of a VM from Tegile storage to local datastore would complete and vice versa would also complete successfully.
3) Clone of a VM from Tegile storage to Tegile storage would fail with error "An error occurred while communicating with remote host"
4) Clone of a VM from Tegile storage to local datastore would complete and vice versa would also complete successfully.
5) Issue would start only after upgrading ESXi to 6.7 as the Tegile plugin version 1.0-15.53 is not compatible with ESXi 6.7

Note: During above failure scenarios the vpxa agent on host would crash with vpxa dump file causing the host to temporarily disconnect from the vCenter, however the host will reconnect automatically.

Purpose

This article provides the information on why the clone operation fails because of the tegile vaail plugin (version 1.0-15.53)

Cause

The tegile vaai plugin in the ESXi causes the vpxa to crash, which disconnects the ESXi from vCenter momentarily resulting the clone operation to fail.

[root@ESXi4:~] esxcli software vib list | grep tgl
tgl-vaai-nas-diskplugin        1.0-15.53                             Tegile                 VMwareAccepted    2018-09-13

vpxd.log:
2018-09-24T19:17:24.871Z info vpxd[04470] [Originator@6876 sub=VmProv opID=48c9016f-8a4a-4088-92f0-b65de4d5e48a-237620-auto-237621-h5c:70015914-7f-01] Starting Datastore changing Local-VC Clone of poweredOff vm Server2016 on vim.HostSystem:host-90(x.x.x.x) with ds ds:///vmfs/volumes/cafeafb4-369f4b12/ to vim.HostSystem:host-90(x.x.x.x) with ds ds:///vmfs/volumes/fb200226-e484902a/

Above line explains the clone task being initiated with the source and destination datastore details.

2018-09-24T19:18:14.516Z warning vpxd[04470] [Originator@6876 sub=OCM opID=48c9016f-8a4a-4088-92f0-b65de4d5e48a-237620-auto-237621-h5c:70015914-7f-01] Encountered host communication error when attempting to finish operation! Waiting for up to one hour for the host to reconnect.

2018-09-24T19:19:14.613Z info vpxd[04470] [Originator@6876 sub=Default opID=48c9016f-8a4a-4088-92f0-b65de4d5e48a-237620-auto-237621-h5c:70015914-7f-01] [VpxLRO] -- ERROR lro-1938778 --  -- VmprovWorkflow: vmodl.fault.HostCommunication:
--> Result:
--> (vmodl.fault.HostCommunication) {
-->    faultCause = (vmodl.MethodFault) null,
-->    faultMessage = <unset>
-->    msg = ""
--> }
--> Args:
-->

============================

vmkernel.log:
2018-09-24T19:17:25.169Z cpu29:2281985)User: 3143: vpxa-worker: wantCoreDump:vpxa-worker signal:6 exitCode:0 coredump:enabled
2018-09-24T19:17:25.325Z cpu24:2281985)UserDump: 3098: vpxa-worker: Dumping cartel 2281965 (from world 2281985) to file /var/core/vpxa-zdump.003 ...
2018-09-24T19:18:14.447Z cpu17:2281985)UserDump: 3246: vpxa-worker: Userworld(vpxa-worker) coredump complete.

Above lines explains that the vpxa has crashed and created a dump file.

============================

hostd.log:
2018-09-24T19:19:14.547Z info hostd[2188008] [Originator@6876 sub=Libs opID=48c9016f-8a4a-4088-92f0-b65de4d5e48a-237620-auto-237621-h5c:70015914-7f-01-48-f557 user=vpxuser:D91_DOMAIN\BodiEric] OBJLIB-LIB:  Failed to get VCFS root path for '/vmfs/volumes/fb200226-e484902a/LFiche1_Temp': No such file or directory (131076).
2018-09-24T19:19:14.549Z warning hostd[2188008] [Originator@6876 sub=Vmsvc opID=48c9016f-8a4a-4088-92f0-b65de4d5e48a-237620-auto-237621-h5c:70015914-7f-01-48-f557 user=vpxuser:D91_DOMAIN\BodiEric] Could not retrieve canonical path for /vmfs/volumes/fb200226-e484902a/LFiche1_Temp/LFiche1_Temp.vmx
2018-09-24T19:19:14.550Z info hostd[2188008] [Originator@6876 sub=vm opID=48c9016f-8a4a-4088-92f0-b65de4d5e48a-237620-auto-237621-h5c:70015914-7f-01-48-f557 user=vpxuser:D91_DOMAIN\BodiEric] VigorOffline_Init: Failed to initialize VIGOR offline: Cannot open file "/vmfs/volumes/fb200226-e484902a/LFiche1_Temp/LFiche1_Temp.vmx": No such file or directory.
2018-09-24T19:19:14.550Z info hostd[2188008] [Originator@6876 sub=Libs opID=48c9016f-8a4a-4088-92f0-b65de4d5e48a-237620-auto-237621-h5c:70015914-7f-01-48-f557 user=vpxuser:D91_DOMAIN\BodiEric]

2018-09-24T19:19:14.565Z info hostd[2188008] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/fb200226-e484902a/LFiche1_Temp/LFiche1_Temp.vmx opID=48c9016f-8a4a-4088-92f0-b65de4d5e48a-237620-auto-237621-h5c:70015914-7f-01-48-f557 user=vpxuser:D91_DOMAIN\BodiEric] State Transition (VM_STATE_INITIALIZING -> VM_STATE_INVALID_LOAD)

2018-09-24T19:19:14.566Z info hostd[2188008] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/fb200226-e484902a/LFiche1_Temp/LFiche1_Temp.vmx opID=48c9016f-8a4a-4088-92f0-b65de4d5e48a-237620-auto-237621-h5c:70015914-7f-01-48-f557 user=vpxuser:D91_DOMAIN\BodiEric] State Transition (VM_STATE_INVALID_LOAD -> VM_STATE_UNREGISTERING)
2018-09-24T19:19:14.566Z warning hostd[2188008] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/fb200226-e484902a/LFiche1_Temp/LFiche1_Temp.vmx opID=48c9016f-8a4a-4088-92f0-b65de4d5e48a-237620-auto-237621-h5c:70015914-7f-01-48-f557 user=vpxuser:D91_DOMAIN\BodiEric] Null _cachedLayoutEx in force unbind
2018-09-24T19:19:14.566Z info hostd[2188008] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/fb200226-e484902a/LFiche1_Temp/LFiche1_Temp.vmx opID=48c9016f-8a4a-4088-92f0-b65de4d5e48a-237620-auto-237621-h5c:70015914-7f-01-48-f557 user=vpxuser:D91_DOMAIN\BodiEric] State Transition (VM_STATE_UNREGISTERING -> VM_STATE_GONE)
2018-09-24T19:19:14.566Z info hostd[2188008] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/fb200226-e484902a/LFiche1_Temp/LFiche1_Temp.vmx opID=48c9016f-8a4a-4088-92f0-b65de4d5e48a-237620-auto-237621-h5c:70015914-7f-01-48-f557 user=vpxuser:D91_DOMAIN\BodiEric] Virtual machine object cleanup

Above lines explain that the clone operation created the respective files, however the path for the vmx file was not available, since it failed to find the path it marked the file as invalid and unregistered, hence we will not be able to see the cloned disks in the destination datastore.

Impact / Risks

Reboot of ESXi required as the plugin updated.

Resolution

Upgrade the tegile vaai plugin to the latest plugin version "1.0-15.70" as per the hardware compatibility guide.

Ref: https://www.vmware.com/resources/compatibility/detail.php?deviceCategory=san&productid=37941&releaseid=369&deviceCategory=san&details=1&partner=423&pFeaturesCat=9&isSVA=0&page=1&display_interval=10&sortColumn=Partner&sortOrder=Asc

Workaround

Disable Tegile VAAI plugin.

Ref: https://kb.vmware.com/s/article/1033665

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

sVmotion_Tegile to Tegile.PNG

clone.png

Additional Resources

KB
•
针对 vSphere 6.x 的产品服务 (2109507)

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

KB
•
Windows 2008 R2 磁盘卷变为只读并且引导失败 (2001611)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

VMware vCenter Server

Related Versions:

VMware vSphere ESXi 6.7

VMware vCenter Server 6.7.x

Take Our Survey

Support Assistant