XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login
    1. Home
    2. SchaffnerOnline
    3. Best
    S
    Offline
    • Profile
    • Following 0
    • Followers 0
    • Topics 2
    • Posts 13
    • Groups 0

    Posts

    Recent Best Controversial
    • VDI Migrate Fail

      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)"
        }
      }
      
      posted in XCP-ng
      S
      SchaffnerOnline
    • RE: Create VM from Template not creating VM

      So I've been doing some more work to see if I can figure out this issue. And so far no luck.

      I'm running a 3 Host environment, that all 3 hosts are identical, HP EliteDesk 800 G3 SFF, Intel i7-7700 CPUs, 64GB memory in each. There is QNAP NAS that is providing NFS storage for the VMs and an NFS ISO storage location. My XCP-NG hosts are running version 8.3 Beta 2

      My XO is running on a Mini PC, XO is compiled from sources, and updated today to commit 1b515.

      When I create any Windows VM and then convert it to a template. When I then try to create a new VM from that template, instead of creating a VM, it creates another template. What I have found interesting, is that when I try to create this new VM and I give the Disk a new name, when it completes and has created template instead, the name of the disk is the same as the source template and not the new disk name that I gave it when I was filling out the info for the new VM.

      When I create a Windows VM from the template I made, but using the "Fast Clone", then it seems to be working correctly. Its creating a VM and the disk name is the new disk name I wanted for the new VM.

      I think, but I can't confirm that I think this issue may have started with the changes from this issue:
      https://github.com/vatesfr/xen-orchestra/pull/7388

      If someone can confirm using the same XCP-NG version and an updated XO from sources, or some guidance on where to look in logs that may tell me why instead of a VM being created from the template, its creating another template.

      julien-f opened this pull request in vatesfr/xen-orchestra

      closed Fix clone #7388

      posted in Management
      S
      SchaffnerOnline