Top contributor

Private

Posts

  • RE: Unclear errors

    i forgot how i got VM_BAD_POWER_STATE.
    Probably need to choose multiple VMs from different pools and do a batch migration.

  • Unclear errors

    Many errors don't explain the cause or lead you down the wrong path. For example:

    • if enabled
      изображение.jpeg
    vm.migrate
    {
      "vm": "a6f6d2ec-17fd-338f-16f5-cdbcfa3e23de",
      "mapVifsNetworks": {
        "c5825de5-4b88-1794-5381-b9ded8fde08b": "12612d2e-9490-185d-5056-d848db1a754f"
      },
      "migrationNetwork": "d6492be1-f89e-e4fe-f6e0-1cbaad111581",
      "sr": "43daf4a2-ff01-e974-0db7-bb68765e5f73",
      "targetHost": "2444db2d-8701-475e-9191-c0b0417b3c51"
    }
    {
      "code": "OPERATION_BLOCKED",
      "params": [
        "OpaqueRef:63424fd1-95b1-8518-9a82-faee73bbd427",
        "true"
      ],
      "task": {
        "uuid": "9120561b-99a6-6677-6e8a-cd4432410aa1",
        "name_label": "Async.VM.migrate_send",
        "name_description": "",
        "allowed_operations": [],
        "current_operations": {},
        "created": "20260914T09:52:49Z",
        "finished": "20260914T09:52:49Z",
        "status": "failure",
        "resident_on": "OpaqueRef:e455b3a6-4d05-6d86-2f7a-c4cdba26e120",
        "progress": 1,
        "type": "<none/>",
        "result": "",
        "error_info": [
          "OPERATION_BLOCKED",
          "OpaqueRef:63424fd1-95b1-8518-9a82-faee73bbd427",
          "true"
        ],
        "other_config": {},
        "subtask_of": "OpaqueRef:NULL",
        "subtasks": [],
        "backtrace": "(((process xapi)(filename ocaml/xapi/xapi_vm_lifecycle.ml)(line 758))((process xapi)(filename ocaml/xapi/xapi_vm_helpers.ml)(line 1657))((process xapi)(filename fun.ml)(line 33))((process xapi)(filename fun.ml)(line 38))((process xapi)(filename ocaml/xapi/helpers.ml)(line 1825))((process xapi)(filename ocaml/xapi/xapi_vm_helpers.ml)(line 1656))((process xapi)(filename ocaml/xapi/message_forwarding.ml)(line 2654))((process xapi)(filename ocaml/xapi/rbac.ml)(line 228))((process xapi)(filename ocaml/xapi/rbac.ml)(line 238))((process xapi)(filename ocaml/xapi/server_helpers.ml)(line 78)))"
      },
      "message": "OPERATION_BLOCKED(OpaqueRef:63424fd1-95b1-8518-9a82-faee73bbd427, true)",
      "name": "XapiError",
      "stack": "XapiError: OPERATION_BLOCKED(OpaqueRef:63424fd1-95b1-8518-9a82-faee73bbd427, true)
        at XapiError.wrap (file:///opt/xo/xo-builds/xen-orchestra-202609011557/packages/xen-api/_XapiError.mjs:16:12)
        at default (file:///opt/xo/xo-builds/xen-orchestra-202609011557/packages/xen-api/_getTaskResult.mjs:13:29)
        at Xapi._addRecordToCache (file:///opt/xo/xo-builds/xen-orchestra-202609011557/packages/xen-api/index.mjs:1329:24)
        at file:///opt/xo/xo-builds/xen-orchestra-202609011557/packages/xen-api/index.mjs:1363:14
        at Array.forEach (<anonymous>)
        at Xapi._processEvents (file:///opt/xo/xo-builds/xen-orchestra-202609011557/packages/xen-api/index.mjs:1353:12)
        at Xapi._watchEvents (file:///opt/xo/xo-builds/xen-orchestra-202609011557/packages/xen-api/index.mjs:1560:14)"
    }
    
    • VM migration into current pool.
    vm.migrate
    {
      "migrationNetwork": "d6492be1-f89e-e4fe-f6e0-1cbaad111581",
      "targetHost": "2444db2d-8701-475e-9191-c0b0417b3c51",
      "vm": "5579297f-c843-9b13-a418-864db48196b5"
    }
    {
      "code": "VM_BAD_POWER_STATE",
      "params": [
        "OpaqueRef:3d062b96-e098-69c3-b77b-db727c06505f",
        "running",
        "halted"
      ],
      "task": {
        "uuid": "110cb10e-20c2-b315-d8b9-50cc9b2311d9",
        "name_label": "Async.VM.pool_migrate",
        "name_description": "",
        "allowed_operations": [],
        "current_operations": {},
        "created": "20260910T13:23:08Z",
        "finished": "20260910T13:23:08Z",
        "status": "failure",
        "resident_on": "OpaqueRef:5e55d030-7245-0317-7463-174fc2c81848",
        "progress": 1,
        "type": "<none/>",
        "result": "",
        "error_info": [
          "VM_BAD_POWER_STATE",
          "OpaqueRef:3d062b96-e098-69c3-b77b-db727c06505f",
          "running",
          "halted"
        ],
        "other_config": {},
        "subtask_of": "OpaqueRef:NULL",
        "subtasks": [],
        "backtrace": "(((process xapi)(filename ocaml/xapi/xapi_vm_lifecycle.ml)(line 758))((process xapi)(filename ocaml/xapi/xapi_vm_helpers.ml)(line 1657))((process xapi)(filename fun.ml)(line 33))((process xapi)(filename fun.ml)(line 38))((process xapi)(filename ocaml/xapi/helpers.ml)(line 1825))((process xapi)(filename ocaml/xapi/xapi_vm_helpers.ml)(line 1656))((process xapi)(filename ocaml/xapi/message_forwarding.ml)(line 2519))((process xapi)(filename ocaml/xapi/rbac.ml)(line 228))((process xapi)(filename ocaml/xapi/rbac.ml)(line 238))((process xapi)(filename ocaml/xapi/server_helpers.ml)(line 78)))"
      },
      "message": "VM_BAD_POWER_STATE(OpaqueRef:3d062b96-e098-69c3-b77b-db727c06505f, running, halted)",
      "name": "XapiError",
      "stack": "XapiError: VM_BAD_POWER_STATE(OpaqueRef:3d062b96-e098-69c3-b77b-db727c06505f, running, halted)
        at XapiError.wrap (file:///opt/xo/xo-builds/xen-orchestra-202609011557/packages/xen-api/_XapiError.mjs:16:12)
        at default (file:///opt/xo/xo-builds/xen-orchestra-202609011557/packages/xen-api/_getTaskResult.mjs:13:29)
        at Xapi._addRecordToCache (file:///opt/xo/xo-builds/xen-orchestra-202609011557/packages/xen-api/index.mjs:1329:24)
        at file:///opt/xo/xo-builds/xen-orchestra-202609011557/packages/xen-api/index.mjs:1363:14
        at Array.forEach (<anonymous>)
        at Xapi._processEvents (file:///opt/xo/xo-builds/xen-orchestra-202609011557/packages/xen-api/index.mjs:1353:12)
        at Xapi._watchEvents (file:///opt/xo/xo-builds/xen-orchestra-202609011557/packages/xen-api/index.mjs:1560:14)"
    }
    
  • RE: Why are transfer sizes different between XO5 & XO6?

    I've confirmed the discrepancy when health checks are performed. Let's see what @Team-XO-Backend has to say about this.

  • RE: Why are transfer sizes different between XO5 & XO6?

    For those of you that are observing a difference in the reported transfer size between XO5 and XO6, can you please let us know if the affected backup jobs are performing health checks?

  • RE: Why are transfer sizes different between XO5 & XO6?

    I'm not seeing this discrepancy on either XOA 6.8.2 or XO from sources (commit a1dba). Does it occur with all backup jobs or only some of them?

    Also, I'm not sure that I understood your reference to the side panel. Are you not able to view it in XO6?

    Edit: Just saw your comment regarding health checks. This is certainly something to investigate.

Member List

borzelB borzel Group Owner
1,523 Posts 376 Reputation
Tristis OrisT Tristis Oris Group Owner
657 Posts 66 Reputation
nikadeN nikade Group Owner
767 Posts 146 Reputation
planedropP planedrop Group Owner
714 Posts 107 Reputation
T tuxen Group Owner
271 Posts 64 Reputation
J JeffBerntsen Group Owner
367 Posts 183 Reputation
K KPS Group Owner
369 Posts 55 Reputation
ronivayR ronivay Group Owner
80 Posts 36 Reputation
A abufrejoval Group Owner
123 Posts 22 Reputation
A Andrew Group Owner
1,487 Posts 632 Reputation
gskgerG gskger Group Owner
520 Posts 288 Reputation
DanpD Danp Group Owner
2,961 Posts 450 Reputation