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

    Migration failled

    Scheduled Pinned Locked Moved Solved Xen Orchestra
    6 Posts 2 Posters 241 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.
    • RashidR Offline
      Rashid
      last edited by olivierlambert

      Re: Trying to migrate

      I tried to migrate VM from host1 to host2 it failed. the error message in log is:

      vm.migrate
      {
        "vm": "08e2baeb-0e58-c037-0e63-97b3cf41871a",
        "mapVifsNetworks": {
          "cbc74384-2167-a72f-f707-52d7179b76c3": "fab39b68-c54e-d23a-2e21-9e905f6dbbe9"
        },
        "migrationNetwork": "b0123e39-89e2-0fd6-47dc-5509552d1615",
        "sr": "bf8ec472-f0d5-1a0f-946f-97b854c6f82d",
        "targetHost": "5e57c2a7-5894-4116-bfbe-241eba3e9da3"
      }
      {
        "code": 21,
        "data": {
          "objectId": "08e2baeb-0e58-c037-0e63-97b3cf41871a",
          "code": "HOST_NOT_ENOUGH_PCPUS"
        },
        "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:578:15
          at Xo.migrate (file:///usr/local/lib/node_modules/xo-server/src/api/vm.mjs:564:3)
          at Api.#callApiMethod (file:///usr/local/lib/node_modules/xo-server/src/xo-mixins/api.mjs:445:20)"
      }
      
      1 Reply Last reply Reply Quote 0
      • RashidR Offline
        Rashid @olivierlambert
        last edited by

        @olivierlambert Thanks a lot.
        The Max vCPU was larger than the Physical CPU. Now it migrates successfully.

        1 Reply Last reply Reply Quote 1
        • olivierlambertO Offline
          olivierlambert Vates 🪐 Co-Founder CEO
          last edited by

          Hi!

          Take time to read the error code: HOST_NOT_ENOUGH_PCPUS

          "P" is for physical. So you are trying to migrate a VM with more vCPUs than you have physical CPUs on the destination host.

          RashidR 1 Reply Last reply Reply Quote 0
          • RashidR Offline
            Rashid @olivierlambert
            last edited by

            This post is deleted!
            1 Reply Last reply Reply Quote 0
            • RashidR Offline
              Rashid
              last edited by

              Thanks for your quick response.
              My host has 4 vCPU and the VM is just 1 vCPU as shown in the screenshot.

              Screenshot 2024-01-16 132705.png Screenshot 2024-01-16 132734.png

              1 Reply Last reply Reply Quote 0
              • olivierlambertO Offline
                olivierlambert Vates 🪐 Co-Founder CEO
                last edited by

                Check your VM max vCPU in the Adanvced tab.

                RashidR 1 Reply Last reply Reply Quote 0
                • RashidR Offline
                  Rashid @olivierlambert
                  last edited by

                  @olivierlambert Thanks a lot.
                  The Max vCPU was larger than the Physical CPU. Now it migrates successfully.

                  1 Reply Last reply Reply Quote 1
                  • olivierlambertO olivierlambert marked this topic as a question on
                  • olivierlambertO olivierlambert has marked this topic as solved on
                  • First post
                    Last post