{"id":201,"date":"2021-06-18T17:43:02","date_gmt":"2021-06-18T17:43:02","guid":{"rendered":"https:\/\/systemsmedic.net\/?p=201"},"modified":"2023-02-17T18:59:39","modified_gmt":"2023-02-17T18:59:39","slug":"vmotion-issue-stucks-at-14-operation-timed-out","status":"publish","type":"post","link":"https:\/\/systemsmedic.net\/index.php\/2021\/06\/18\/vmotion-issue-stucks-at-14-operation-timed-out\/","title":{"rendered":"vMotion issue stucks at 14% operation timed out"},"content":{"rendered":"\n

ESXi 5.5 \/ vCenter 5.5<\/p>\n\n\n\n

Today I was asked to put one host in maintained mode and shutdown the ESXi server. Prior to this I had to relocate the VMs in to different ESXi servers in same cluster. After the checking the DRS setting, I just put server in maintained mode. Most of the VMs were migrated successfully except one VM. What I did is cancel the maintained task from the vCenter task list and try to manually migrate this VM. After the manual migration initiated below issues and error messages were appeared.<\/p>\n\n\n\n

Experienced symptoms<\/strong><\/p>\n\n\n\n

vMotion task stucks at 14%<\/em><\/strong><\/p>\n\n\n\n

After few min later task was canceled saying Operation timed out<\/em><\/strong><\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n
\"\"<\/figure>\n\n\n\n
\"\"<\/figure>\n\n\n\n

After I checked the vMotion network and everything related but nothing wrong with the settings because all other VMs were migrated successfully. After I decide to perform a storage vMotion to verify is this only related with host vMotion but unfortunately, it\u2019s given different error. <\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Finally I searched through google and found this VMware KB<\/a>  which has been describe the same issue as mine one. Thanks for the VMware.<\/p>\n\n\n\n

As per the KB article there should be two .vswp files in VM directory. Normally there are only one vswp file must be there. As VMware says I could see two files as below screen shot.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

VMware recommend powering down the VM to fix this issue, but I tried to minimize the down time of the production VM. So, I tried to find the lock outsource of the duplicate vswp<\/strong> file by using VMKSFSTOOL<\/em><\/strong> command in ESXi shell.<\/p>\n\n\n\n

Eg: vmkfstool -D \u201cpath to vswp file\u201d<\/strong><\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

As per the above screen shot it was locked by one of the ESXi servers in the cluster. I tried restarting that host but unfortunately lock has been moved to different ESXi server. So finally, I had to coordinate the downtime with application team and shut the VM. Once power down I was able to vMotion the VM and finally performed a storage vMotion and duplicate vswp<\/strong> file disappeared.<\/p>\n\n\n\n

Thanks for reading. Stay safe!!!<\/strong><\/p>\n","protected":false},"excerpt":{"rendered":"

ESXi 5.5 \/ vCenter 5.5 Today I was asked to put one host in maintained mode and shutdown the ESXi server. Prior to this I had to relocate the VMs in to different ESXi servers in same cluster. After the checking the DRS setting, I just put server in maintained mode. Most of the VMs […]<\/p>\n","protected":false},"author":1,"featured_media":388,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[21],"tags":[],"class_list":["post-201","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-centos"],"_links":{"self":[{"href":"https:\/\/systemsmedic.net\/index.php\/wp-json\/wp\/v2\/posts\/201","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/systemsmedic.net\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/systemsmedic.net\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/systemsmedic.net\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/systemsmedic.net\/index.php\/wp-json\/wp\/v2\/comments?post=201"}],"version-history":[{"count":1,"href":"https:\/\/systemsmedic.net\/index.php\/wp-json\/wp\/v2\/posts\/201\/revisions"}],"predecessor-version":[{"id":207,"href":"https:\/\/systemsmedic.net\/index.php\/wp-json\/wp\/v2\/posts\/201\/revisions\/207"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/systemsmedic.net\/index.php\/wp-json\/wp\/v2\/media\/388"}],"wp:attachment":[{"href":"https:\/\/systemsmedic.net\/index.php\/wp-json\/wp\/v2\/media?parent=201"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/systemsmedic.net\/index.php\/wp-json\/wp\/v2\/categories?post=201"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/systemsmedic.net\/index.php\/wp-json\/wp\/v2\/tags?post=201"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}