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

    Xen Orchestra 5.110 V2V not working

    Scheduled Pinned Locked Moved Migrate to XCP-ng
    49 Posts 5 Posters 1.4k 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.
    • F Offline
      farokh @DustinB
      last edited by

      @DustinB That's my point. The "Warm Migration" powers off the running machine.

      D 1 Reply Last reply Reply Quote 0
      • D Offline
        DustinB @farokh
        last edited by

        @farokh said in Xen Orchestra 5.110 V2V not working:

        @DustinB That's my point. The "Warm Migration" powers off the running machine.

        Are you stating that it forcibly powers the VM off, or does it gracefully execute a shutdown, IE "Start > Shutdown"?

        F 1 Reply Last reply Reply Quote 0
        • F Offline
          farokh @DustinB
          last edited by

          @DustinB It forcibly powers off the VM.

          D 1 Reply Last reply Reply Quote 0
          • florentF Offline
            florent Vates 🪐 XO Team @farokh
            last edited by

            @farokh In case you need to ensure that the VM is powered off manually :

            • do the first migration without "stop source"
            • stop the VM properly
            • launch the migration . It will only transfer the data from the snapshot
            florentF 1 Reply Last reply Reply Quote 1
            • florentF Offline
              florent Vates 🪐 XO Team @florent
              last edited by florent

              gracefully powering down a VM may need to go inside the VM ( through ssh/powershell) and that is something we try not to do, especially since we do not know anything on the os inside

              It can be easily scripted if you know what is the type of VM running and how to authenticate inside them

              1 Reply Last reply Reply Quote 1
              • D Offline
                DustinB @farokh
                last edited by

                @farokh said in Xen Orchestra 5.110 V2V not working:

                @DustinB It forcibly powers off the VM.

                You'd have to do what Florent is saying in this case. But I question why should it matter as long as the migration completes successfully and the VM boots on your new pool...

                F 2 Replies Last reply Reply Quote 0
                • F Offline
                  farokh @DustinB
                  last edited by

                  @DustinB Because I was led to believe that I could leave my VM running while the initial transfer is occurring and only have it shutdown for the final bit to be copied. I have VMs that I'd rather not shut down for some number of hours if I can avoid doing that.

                  D 1 Reply Last reply Reply Quote 0
                  • D Offline
                    DustinB @farokh
                    last edited by

                    @farokh said in Xen Orchestra 5.110 V2V not working:

                    @DustinB Because I was led to believe that I could leave my VM running while the initial transfer is occurring and only have it shutdown for the final bit to be copied. I have VMs that I'd rather not shut down for some number of hours if I can avoid doing that.

                    You would do what florent said, transfer the VM without shutting down the original VM on ESXi. Once the migration is completed you'd then power off the ESXi VM and power on the XCP-ng.

                    1 Reply Last reply Reply Quote 0
                    • F Offline
                      farokh @DustinB
                      last edited by

                      @DustinB When I tried to do that the first thing the migration process did was to power off the VM.

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