VDI Migrate Fail

SchaffnerOnline

Migrating VM disks from one SR to another SR.

Select the VM that I want to migrate and then goto the "Disk" tab and on the disk, click on the "Migrate VDI". Select the Destination SR and click on "OK". The migration runs to 100% but then errors out at the end.

If I migrate the VM to a new host in the pool along with migrating the Disks to a new SR then it works fine.

Here is the log from when it fails to migrate the VDI only:

{
  "id": "0mhdtmn5s",
  "properties": {
    "method": "vdi.migrate",
    "params": {
      "id": "2be3f81f-7731-4f48-8755-d46d596cbf61",
      "sr_id": "6b100387-35a3-df36-9e98-3062ede35c02"
    },
    "name": "API call: vdi.migrate",
    "userId": "b57e5662-a787-411e-9db7-cd94c09714bd",
    "type": "api.call"
  },
  "start": 1761852735425,
  "status": "failure",
  "updatedAt": 1761852959800,
  "end": 1761852959799,
  "result": {
    "code": "INTERNAL_ERROR",
    "params": [
      "Xenops_interface.Xenopsd_error([S(Internal_error);S(Sys_error(\"Connection reset by peer\"))])"
    ],
    "task": {
      "uuid": "7a4d41c7-b092-eaea-0d4a-fdda9a3e8bc4",
      "name_label": "Async.VDI.pool_migrate",
      "name_description": "",
      "allowed_operations": [],
      "current_operations": {},
      "created": "20251030T19:32:15Z",
      "finished": "20251030T19:35:59Z",
      "status": "failure",
      "resident_on": "OpaqueRef:2f3535a2-2119-4b72-a35f-c9bfbd128ad7",
      "progress": 1,
      "type": "<none/>",
      "result": "",
      "error_info": [
        "INTERNAL_ERROR",
        "Xenops_interface.Xenopsd_error([S(Internal_error);S(Sys_error(\"Connection reset by peer\"))])"
      ],
      "other_config": {},
      "subtask_of": "OpaqueRef:NULL",
      "subtasks": [],
      "backtrace": "(((process xapi)(filename ocaml/xapi/helpers.ml)(line 1882))
((process xapi)(filename ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml)(line 24))
((process xapi)(filename ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml)(line 39))
((process xapi)(filename ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml)(line 24))
((process xapi)(filename ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml)(line 39))
((process xapi)(filename ocaml/xapi/message_forwarding.ml)(line 144))
((process xapi)(filename ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml)(line 24))
((process xapi)(filename ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml)(line 39))
((process xapi)(filename ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml)(line 24))
((process xapi)(filename ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml)(line 39))
((process xapi)(filename ocaml/xapi/rbac.ml)(line 229))
((process xapi)(filename ocaml/xapi/rbac.ml)(line 239))
((process xapi)(filename ocaml/xapi/server_helpers.ml)(line 78)))"
    },
    "message": "INTERNAL_ERROR(Xenops_interface.Xenopsd_error([S(Internal_error);S(Sys_error(\"Connection reset by peer\"))]))",
    "name": "XapiError",
    "stack": "XapiError: INTERNAL_ERROR(Xenops_interface.Xenopsd_error([S(Internal_error);S(Sys_error(\"Connection reset by peer\"))]))\n
    at Function.wrap (file:///opt/xo/xo-builds/xen-orchestra-202510240854/packages/xen-api/_XapiError.mjs:16:12)\n
    at default (file:///opt/xo/xo-builds/xen-orchestra-202510240854/packages/xen-api/_getTaskResult.mjs:13:29)\n
    at Xapi._addRecordToCache (file:///opt/xo/xo-builds/xen-orchestra-202510240854/packages/xen-api/index.mjs:1073:24)\n
    at file:///opt/xo/xo-builds/xen-orchestra-202510240854/packages/xen-api/index.mjs:1107:14\n
    at Array.forEach (<anonymous>)\n
    at Xapi._processEvents (file:///opt/xo/xo-builds/xen-orchestra-202510240854/packages/xen-api/index.mjs:1097:12)\n
    at Xapi._watchEvents (file:///opt/xo/xo-builds/xen-orchestra-202510240854/packages/xen-api/index.mjs:1270:14)"
  }
}

Forza

@SchaffnerOnline we have the exact same issue.

olivierlambert

Can you reproduce the issue with xe CLI?

SchaffnerOnline

@olivierlambert ran it from command line and got the same results

xe vdi-pool-migrate uuid=00133568-52c8-4f70-b329-c3e92cfec7dd sr-uuid=6b100387-35a3-df36-9e98-3062ede35c02The server failed to handle your request, due to an internal error. The given message may give details useful for debugging the problem.
message: Xenops_interface.Xenopsd_error([S(Internal_error);S(Sys_error("Connection reset by peer"))])

Forza

@olivierlambert said in VDI Migrate Fail:

Can you reproduce the issue with xe CLI?

We have a ticket open with your team about this. They could also not find a quick work around.

olivierlambert

So first, it's not an XO issue, which helps to diagnose it. Then, it might be a subtle XCP-ng bug indeed.