VM Migration error within XCP 7.6 pool using NFS storage

[racecar]

First post here, so I apologize if I miss some crucial details. I'd be happy to provide any additional details / logs.

Attempting to migrate VM within a pool running XCP 7.6. Storage is NFS and connected to all hosts in pool. A different VM migrated successfully yesterday with the same source and destination host, on the same NFS storage. Successful VM is Win10, failing VM is Server 2019; both have management tools freshly installed.

Error:

vm.migrate
{
  "vm": "aea94893-d254-fca1-fce7-4f55dce51bc4",
  "targetHost": "89e4c7b4-85a6-4d36-81cd-8d69cdc52b54"
}
{
  "code": 21,
  "data": {
    "objectId": "aea94893-d254-fca1-fce7-4f55dce51bc4",
    "code": "CANNOT_CONTACT_HOST"
  },
  "message": "operation failed",
  "name": "XoError",
  "stack": "XoError: operation failed
    at operationFailed (/usr/local/lib/node_modules/xo-server/node_modules/xo-common/src/api-errors.js:21:32)
    at file:///usr/local/lib/node_modules/xo-server/src/api/vm.mjs:567:15
    at Xo.migrate (file:///usr/local/lib/node_modules/xo-server/src/api/vm.mjs:553:3)
    at Api.#callApiMethod (file:///usr/local/lib/node_modules/xo-server/src/xo-mixins/api.mjs:417:20)"
}

[racecar]

Live migration of a different VM from the same source host to the same destination host was successful.
Restarted toolstack on source host and tried live migration of this failing VM again, failed again.
Cold migration of another VM (same source/destination) also worked fine. Ideally, a live migration would be better to minimize downtime, but I'll try it cold if nothing else works.

[olivierlambert]

Warm migration is an alternative you should try when you have issues See https://xen-orchestra.com/blog/warm-migration-with-xen-orchestra/

[racecar]

@olivierlambert Thank you!

I read the blog post you linked and it sounds perfect for me. It looks like it will come in handy as I work to get my VMs migrated off older versions of Citrix and XCP to modern, cohesive hosts.