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
    19 Posts 3 Posters 402 Views 3 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 Online
      farokh
      last edited by

      The VM I'm looking to import is running on ESXi 7.0u3, and the storage is on local VMFS storage.

      I have a backup, which is what I used to restore it last night, so I'm good that way.

      Just so I'm clear, do I have to do anything in order to prep before starting the import?

      Thanks.

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

        I don't think so (at least from the top of my head)

        1 Reply Last reply Reply Quote 0
        • F Online
          farokh
          last edited by

          OK, so I started the import. These are screenshots from the XO and the ESXi.
          Screenshot 2025-08-30 at 11.58.52.png
          Screenshot 2025-08-30 at 12.00.24.png
          So, I started the process, and on the ESXi side, it powered off the VM, and then nothing else (as per the task list).
          I left it alone until now, and at some point, the import screen on XO went away, and it shows the imported VM.

          However, this time, when I powered up the original VM on the ESXi host, it did power up without giving me an error.

          When I checked the event log on the ESXi host, I found the following:
          Screenshot 2025-08-30 at 12.40.59.png
          So, the XO machine clearly downloaded files, but there was nothing at all displayed on the import screen with a status.

          So, other than abruptly powering off the VM, it appears to have worked.

          I'll post more once I've played with the imported the VM, but I guess there's still the issue where it's powering off the VM (not even doing a shutdown).

          florentF 1 Reply Last reply Reply Quote 0
          • F Online
            farokh
            last edited by

            Another thing to note, the original VM had 5 total network interfaces, and the imported machine has 5 network interfaces, but all 5 were connected to the same interface (which was the only one selectable during the import).

            1 Reply Last reply Reply Quote 0
            • F Online
              farokh
              last edited by

              Starting to play with the imported VM, and there are 2 snapshots, both from the import process. I'm going run the VM with them for now and then try deleting them once I see it's working.

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

                @farokh If my understanding it correct : it migrated the source VM correctly , without breaking anything on esxi side, but it would be better if the V2V gives more feedback to the user ?
                Also, you would like to be able to select different networks as target ?

                F 1 Reply Last reply Reply Quote 0
                • F Online
                  farokh @florent
                  last edited by farokh

                  @florent That's a good summary, however, V2V did power off the VM before starting the import, which defeats the point of a warm migration, and the power off is abrupt, not allowing the OS to cleanly shutdown, which means that there's a potential for data loss.

                  Thank you.

                  Edit: I was just looking at the blog post for 5.110 and I noticed this:
                  The interface has been polished as well. There’s now a progress bar visible from the start of the migration, speed metrics are recorded in the VDI, and snapshots are created at each step. This allows the process to pause and resume safely without needing to create multiple VMs. Finally, UEFI VMs are no longer forced into Secure Boot mode, avoiding previous boot issues.

                  I guess I'm confused as to why I didn't see any of this?

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

                    @farokh do you have at least one snapshot on the source ? The data migrated while the VM is running are the data before the last snapshot

                    The power off is effectively a call to powerOff, is there a better alternative (that can work with or without the vmware tools installed) ?

                    the progress bar are visible in the task view, or on the disk tab on the VM being imported ( not yet in the form , this will probably wait for the XO6 version of this page )

                    F 1 Reply Last reply Reply Quote 0
                    • F Online
                      farokh @florent
                      last edited by

                      @florent Yes, I made sure that I had a snapshot.

                      I guess my main question is why the VM is being powered off? It's supposed to be a warm migration, meaning the VM is running while the data is migrated, correct?

                      But, assuming that you have to power the VM down, and I haven't done any programming or scripting with ESXi, but I can tell you that the web interface can tell if the VM has the tools installed. If the tools are installed, you should be able to send a Shutdown request, which should shut the machine down gracefully, allowing the OS to perform tasks prior to powering off. You can wait a few minutes and if the machine hasn't powered off yet, you could then issue the power off command to stop it.

                      Next time I test a migration, I'll check the task and/or disk to see the status.

                      Thanks.

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

                        Hi, just wondering if there's any update on why the VMs are being shutdown for the migration.

                        Thanks.

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

                          We made a patch release of XOA, improving some aspects. Have you tried it?

                          F 1 Reply Last reply Reply Quote 0
                          • F Online
                            farokh @olivierlambert
                            last edited by

                            @olivierlambert No, I wasn't aware. I'll take a look.
                            Thanks.

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

                              Is there a blog or forum post about the updates? I can't seem to find anything.

                              Thanks.

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