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

    Warm migration stuck at 0%

    Scheduled Pinned Locked Moved Solved Xen Orchestra
    12 Posts 7 Posters 618 Views 4 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.
    • DanpD Online
      Danp Pro Support Team
      last edited by

      What commit are you using in your XO VM? Have you tried with XOA?

      J 1 Reply Last reply Reply Quote 0
      • Tristis OrisT Offline
        Tristis Oris Top contributor
        last edited by

        same with cf5db. Looks it yet one problem after bfb8d3b.

        1 Reply Last reply Reply Quote 0
        • J Offline
          jdias14 @Danp
          last edited by

          Danp
          Currently I'm using:

          • Xen Orchestra commit 1d912
          • Master commit cf5db

          I tried with XOA and it works.

          DanpD 1 Reply Last reply Reply Quote 0
          • DanpD Online
            Danp Pro Support Team @jdias14
            last edited by

            jdias14 There are known issues with some recent commits. You can revert to 51f95b3 or keep using XOA for the moment.

            J 1 Reply Last reply Reply Quote 1
            • s-masterS Offline
              s-master
              last edited by

              I'm experiencing the same issue with the latest commit in XO from the sources.
              I reverted back to an older version, and it worked again.

              1 Reply Last reply Reply Quote 0
              • J Offline
                jdias14 @Danp
                last edited by

                Thank you all for the feedback!!

                Danp Is there any prediction to the fix of this bug?

                DanpD 1 Reply Last reply Reply Quote 0
                • DanpD Online
                  Danp Pro Support Team @jdias14
                  last edited by

                  jdias14 Another release of XOA is scheduled for the end of March, so I would expect this be be resolved this week.

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

                    Also, if you are using it into production, time to think about XOA that's not affected 😉 But yes, we'll fix it ASAP (probably a matter of hours now, days at worse)

                    julien-fJ 1 Reply Last reply Reply Quote 0
                    • julien-fJ Offline
                      julien-f Vates 🪐 Co-Founder XO Team @olivierlambert
                      last edited by

                      Hello everyone,

                      Please test the fix-putResource, it should fix this issue, please keep me posted 🙂

                      1 Reply Last reply Reply Quote 1
                      • tjkreidlT Offline
                        tjkreidl Ambassador @jdias14
                        last edited by

                        jdias14 Make sure you have at least double the available disk storage space on the target.

                        J 1 Reply Last reply Reply Quote 0
                        • J Offline
                          jdias14 @tjkreidl
                          last edited by

                          Currently in commit 2f962 and it's working. Thanks you all

                          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