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

    Migrate failed

    Scheduled Pinned Locked Moved Xen Orchestra
    24 Posts 3 Posters 5.4k Views 1 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.
    • olivierlambertO Offline
      olivierlambert Vates 🪐 Co-Founder CEO
      last edited by

      How do you try to migrate? Is the VM offline?

      I 1 Reply Last reply Reply Quote 0
      • I Offline
        Ivan @olivierlambert
        last edited by

        @olivierlambert yes. VM is offline.

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

          Can you try to boot it, and then migrate?

          Or just boot it once, then shutdown, then migrate?

          I 1 Reply Last reply Reply Quote 0
          • I Offline
            Ivan @olivierlambert
            last edited by

            @olivierlambert said in Migrate failed:

            r just boot it once, then shutdown, then migrate?

            tried both options, result is the same(

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

              Hmm that's weird 🤔

              Can you check detailed logs on the source host?

              I 1 Reply Last reply Reply Quote 0
              • I Offline
                Ivan @olivierlambert
                last edited by

                @olivierlambert said in Migrate failed:

                Can you check detailed logs on the source host?

                yes. which of log file are you recomend to check?

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

                  /var/log/xensource.log

                  I 1 Reply Last reply Reply Quote 0
                  • I Offline
                    Ivan @olivierlambert
                    last edited by

                    @olivierlambert
                    xenlog.txt

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

                      So I took some time to read the error in details.

                      It's a problem/bug in your current XenServer 7.2.

                      Indeed, in 7.2, they locked Xen Storage Motion feature as a paid feature. So you can't migrate a VMs with its storage to another SR/pool, unless you pay for it. The message is pretty clear:

                      Raised Server_error(LICENCE_RESTRICTION, [ Storage_motion ])
                      

                      There's is multiple workarounds, but as you can see, it's a very dick move from someone at Citrix who decided that 😛

                      I 1 Reply Last reply Reply Quote 0
                      • I Offline
                        Ivan @olivierlambert
                        last edited by

                        @olivierlambert
                        thank you for your help. Upgrade from 7.6 to 8.2(is it safely?) help to take off this containts.

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

                          You can indeed upgrade your host "locally" from XS to XCP-ng. Just read carefully our official doc on this 🙂

                          https://xcp-ng.org/docs/upgrade.html#upgrade-from-xenserver

                          I 1 Reply Last reply Reply Quote 0
                          • I Offline
                            Ivan @olivierlambert
                            last edited by

                            @olivierlambert
                            @olivierlambert said in Migrate failed:

                            You can indeed upgrade your host "locally" from XS to XCP-ng. Just read carefully our official doc on this

                            okay. we'll read that carefully and try to do at the not critical servers. but before start of upgrading procedure we'd like to make sure that migration between xcp-ng(8.2) server is working.
                            I've tried to migrate VM(from xcp-ng 8.2 to 8.2) and caught another error:

                            vm.migrate
                            {
                              "vm": "2c837cb0-fcf3-6a09-ac47-b939e90869aa",
                              "mapVifsNetworks": {},
                              "migrationNetwork": "8ad97115-d285-1be6-7738-acd1e7554b3e",
                              "sr": "d4f35636-0125-5318-b915-479bef1ba8c7",
                              "targetHost": "07e1d99b-5dcc-4e78-be88-69e04d625f2b"
                            }
                            {
                              "code": 21,
                              "data": {
                                "objectId": "2c837cb0-fcf3-6a09-ac47-b939e90869aa",
                                "code": "INTERNAL_ERROR"
                              },
                              "message": "operation failed",
                              "name": "XoError",
                              "stack": "XoError: operation failed
                                at factory (/usr/local/lib/node_modules/xo-server/node_modules/xo-common/src/api-errors.js:21:32)
                                at /usr/local/lib/node_modules/xo-server/src/api/vm.js:487:15
                                at runMicrotasks (<anonymous>)
                                at processTicksAndRejections (internal/process/task_queues.js:93:5)
                                at runNextTicks (internal/process/task_queues.js:62:3)
                                at processImmediate (internal/timers.js:434:9)
                                at Object.migrate (/usr/local/lib/node_modules/xo-server/src/api/vm.js:474:3)
                                at Api.callApiMethod (/usr/local/lib/node_modules/xo-server/src/xo-mixins/api.js:304:20)"
                            }
                            
                            1 Reply Last reply Reply Quote 0
                            • olivierlambertO Offline
                              olivierlambert Vates 🪐 Co-Founder CEO
                              last edited by

                              Errors in CAPS means an error from the host.

                              Check host logs, also check dynamic min memory == dynamic max

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