XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Warm Migration HOST_CANNOT_ATTACH_NETWORK

    Scheduled Pinned Locked Moved Xen Orchestra
    3 Posts 2 Posters 117 Views 2 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • J Offline
      johnd
      last edited by Danp

      Trying to do a warm migration and I keep getting this error. When I do the warm migration, it does not give me the option to select the network on the other server to use once it migrates and should power on. Not sure what to do to get it to use the correct network on the other host and be automated.

      {
        "id": "0m4xfy0oj",
        "properties": {
          "method": "vm.warmMigration",
          "params": {
            "deleteSourceVm": false,
            "sr": "b0781787-2950-154c-c46f-226496c26f2e",
            "startDestinationVm": true,
            "vm": "bfcda45b-2bb9-3143-2c3b-44f7cee3c1f6"
          },
          "name": "API call: vm.warmMigration",
          "userId": "44b6805c-13da-4a50-b672-c132945a2e19",
          "type": "api.call"
        },
        "start": 1734740904691,
        "status": "failure",
        "updatedAt": 1734743781539,
        "end": 1734743781538,
        "result": {
          "errors": [
            "V1D1-31: HOST_CANNOT_ATTACH_NETWORK(OpaqueRef:e1cc46c3-0db7-4951-8adf-749d29b05e29, OpaqueRef:87880122-ca71-488c-bfd5-0e4eeb06fb3d)"
          ],
          "code": "NO_HOSTS_AVAILABLE",
          "params": [],
          "message": "NO_HOSTS_AVAILABLE()",
          "name": "Error",
          "stack": "Error: NO_HOSTS_AVAILABLE()\n    at Xapi._startVm (file:///opt/xo/xo-builds/xen-orchestra-202411230402/packages/xo-server/src/xapi/index.mjs:926:11)\n    at Xapi.startVm (file:///opt/xo/xo-builds/xen-orchestra-202411230402/packages/xo-server/src/xapi/index.mjs:965:7)\n    at MigrateVm.warmMigrateVm (file:///opt/xo/xo-builds/xen-orchestra-202411230402/packages/xo-server/src/xo-mixins/migrate-vm.mjs:102:7)\n    at Xo.warmMigration (file:///opt/xo/xo-builds/xen-orchestra-202411230402/packages/xo-server/src/api/vm.mjs:613:3)\n    at Task.runInside (/opt/xo/xo-builds/xen-orchestra-202411230402/@vates/task/index.js:172:22)\n    at Task.run (/opt/xo/xo-builds/xen-orchestra-202411230402/@vates/task/index.js:156:20)\n    at Api.#callApiMethod (file:///opt/xo/xo-builds/xen-orchestra-202411230402/packages/xo-server/src/xo-mixins/api.mjs:469:18)"
        }
      }
      
      nick.lloydN 1 Reply Last reply Reply Quote 0
      • nick.lloydN Offline
        nick.lloyd @johnd
        last edited by

        @johnd Can you make sure the networks show as "Connected" on the host you're trying to migrate to? I've run into a few issues where I can't migrate VMs after a host reboot because the networks aren't connected

        J 1 Reply Last reply Reply Quote 0
        • J Offline
          johnd @nick.lloyd
          last edited by

          @nick-lloyd So looked at the network ports on the host it is going to. They show disconnected due to they are in a bond lacp so the 2 network ports show as disconnected but the bond shows as connected. Also have other VMs running on the receiving host so know the bond is working.

          1 Reply Last reply Reply Quote 0
          • First post
            Last post