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

    FIX to XCP-ng

    Scheduled Pinned Locked Moved Development
    17 Posts 4 Posters 2.3k 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.
    • _danielgurgel_ Offline
      _danielgurgel @olivierlambert
      last edited by

      @olivierlambert Yes, all VMs have ejected CD.

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

        Ideally, we could make a patch a see if it fixes your issue.

        1 Reply Last reply Reply Quote 0
        • stormiS Offline
          stormi Vates 🪐 XCP-ng Team
          last edited by

          I've built xenopsd with that patch.

          You can download the xenopsd and xenopsd-xc packages (both need to be updated) there:

          • https://koji.xcp-ng.org/kojifiles/work/tasks/362/10362/xenopsd-0.101.0-2.0.1.xcpng8.0.x86_64.rpm
          • https://koji.xcp-ng.org/kojifiles/work/tasks/362/10362/xenopsd-xc-0.101.0-2.0.1.xcpng8.0.x86_64.rpm

          I believe a toolstack restart is enough afterwards.

          _danielgurgel_ 1 Reply Last reply Reply Quote 3
          • M Offline
            maxcuttins
            last edited by

            What amazing support ♥

            1 Reply Last reply Reply Quote 0
            • _danielgurgel_ Offline
              _danielgurgel @stormi
              last edited by

              @stormi After applying the new patch, migrations are no longer failing. We just tested on a new cluster with 20 servers.

              Thank you so much for your help.
              This patch be including as official update?

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

                We can do that yes.

                1 Reply Last reply Reply Quote 0
                • stormiS Offline
                  stormi Vates 🪐 XCP-ng Team
                  last edited by stormi

                  Did the patch fix migrations that were failing before, for the same VMs? Else we're not sure that the issue you had previously was fixed by it.

                  Your error message was
                  Caught Xenops_interface.Xenopsd_error([S(Storage_backend_error);[S(SR_BACKEND_FAILURE_46);[S();S(The VDI is not available [opterr=VDI e3222f55-10ce-4d85-b6a8-a7c81f1a5a1d not detached cleanly]);S()]]])

                  In the commit message the error message that the patch fixes is:
                  Caught Xs_protocol.Enoent("directory")

                  1 Reply Last reply Reply Quote 0
                  • stormiS Offline
                    stormi Vates 🪐 XCP-ng Team
                    last edited by stormi

                    Note: the patch only fixes migration for VMs without any network interface. Was that the case for you?

                    Edit: looks like this patch could be a fix for https://github.com/xcp-ng/xcp/issues/269

                    elialum created this issue in xcp-ng/xcp

                    closed live migration failed - Xenops_interface.Does_not_exist #269

                    1 Reply Last reply Reply Quote 0
                    • _danielgurgel_ Offline
                      _danielgurgel
                      last edited by

                      @stormi it seems to be the same problem.

                      Sorry, it may have been the "placebo effect" but after applying the update we no longer had the error when making the migrate.

                      I'm going to continue the tests... and with VMs without network card, as described in the link.

                      1 Reply Last reply Reply Quote 0
                      • _danielgurgel_ Offline
                        _danielgurgel
                        last edited by

                        Before applying the patch, in a new pool (during the CH8 update process to XCP8), when moving any VM to the updated host I received the error below.

                        After installing the patch on the master host and restarting the toolstack on the host master and the source host, we no longer notice error, with the migrate process successfully completing.

                        The error condition was the failed shutdown of the VM in the live migrate process. So I think the patch made available actually solves the problem in question. (for VMs with and without network interfaces)

                        Nov 30 12:54:48 SECH82 xapi: [error|SECH82|946189 ||backtrace] Async.VM.pool_migrate R:29b4b31d74de failed with exception Server_error(INTERNAL_ERROR, [ xenopsd internal error: Device_common.QMP_Error(135, "{\"error\":{\"class\":\"GenericError\",\"desc\":\"Unable to open /dev/fdset/0: No such file or directory\",\"data\":{}},\"id\":\"qmp-000029-135\"}") ])
                        Nov 30 12:54:48 SECH82 xapi: [error|SECH82|946189 ||backtrace] Raised Server_error(INTERNAL_ERROR, [ xenopsd internal error: Device_common.QMP_Error(135, "{\"error\":{\"class\":\"GenericError\",\"desc\":\"Unable to open /dev/fdset/0: No such file or directory\",\"data\":{}},\"id\":\"qmp-000029-135\"}") ])
                        Nov 30 12:54:48 SECH82 xapi: [error|SECH82|946189 ||backtrace] 1/1 xapi @ SECH82 Raised at file (Thread 946189 has no backtrace table. Was with_backtraces called?, line 0
                        Nov 30 12:54:48 SECH82 xapi: [error|SECH82|946189 ||backtrace]
                        
                        1 Reply Last reply Reply Quote 0
                        • First post
                          Last post