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

    V2V in XO 6: a brand new migration wizard, with Auto-pilot docking πŸ›¬

    Scheduled Pinned Locked Moved Xen Orchestra
    10 Posts 3 Posters 84 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.
    • florentF
      florent Vates πŸͺ XO Team
      last edited by

      V2V in XO 6: a brand new migration wizard, with Auto-pilot docking πŸ›¬

      Hi everyone πŸ‘‹

      V2V is now in the XO 6 UI! We didn't just port the XO 5 form: we rebuilt it, and it comes with a big new feature, VMs Auto-pilot docking, so your VMware VMs are ready for XCP-ng before their first boot.

      image.jpeg
      image.jpeg
      image.jpeg
      image.jpeg
      image.jpeg

      What's new compared to XO 5

      • A reworked wizard: step by step, from connecting to your vCenter/ESXi to the final review. Clearer, and harder to get wrong.
      • Choices per VM: network, storage and template are picked for each VM, not once for the whole batch. Your Windows Server and your Debian web server don't have to land the same way anymore. The template matters too: it gives the VM the right settings for its OS on the XCP-ng side.
      • Start VM after migration: the VM is started once the import is done, no need to come back and click.
      • Auto-pilot docking: one checkbox, details below πŸ‘‡
      • Readable tasks: each VM shows the progress of every step. If something goes wrong, the task tells you what and why.

      Auto-pilot docking: why?

      Moving disks from VMware to XCP-ng is now the easy part. The real pain comes at the first boot: Windows blue screens with INACCESSIBLE_BOOT_DEVICE, a Linux initramfs without the Xen drivers, VMware Tools still running, NICs renamed and static IPs gone… You know the drill πŸ˜…

      How it works

      Once the import is complete, XO boots the VM on a small live ISO, inside the target VM, so the ISO sees the real XCP-ng virtual hardware.

      1. Diagnose: the ISO reads the guest disks without touching anything and reports what it plans to do, plus anything blocking.
      2. Dock: it applies the changes offline (Xen PV drivers in the initramfs, VMware Tools disabled, XCP-ng guest tools installed, network configuration carried over), then powers the VM off.
      3. First boot: XO starts the VM and follows it through, including the Windows driver and agent install. It also turns Secure Boot back on when the source had it.

      What about static IPs?

      They're kept, and so are the MAC addresses, so DHCP reservations keep working too.

      • Linux: your network configuration is never modified. The ISO only pins the old interface name to the NIC with the same MAC: ens192 stays ens192 instead of becoming enX0.
      • Windows: the ISO captures the static configuration and the first boot reapplies it to the new PV adapter with the matching MAC. With several NICs, XO uses what VMware Tools reported to match addresses and adapters. If it can't, the adapters stay in DHCP and the task tells you so.

      A few things we care about

      • Your VMware VM stays your safe fallback. It is left untouched, apart from Changed Block Tracking, which XO enables to speed up the transfer. Stop source is your call, and it's a clean guest shutdown. If anything goes wrong, just power it back on.
      • No guest credentials needed, and nothing is installed in the source OS.
      • A failed docking never fails the import. The VM is left halted, the task explains why, and the snapshot taken at the end of the import is your rollback on the XCP-ng side.

      What's supported

      • Linux: Debian 10/11/12/13, Ubuntu 22.04 / 24.04, the RHEL family (CentOS 7.3, Rocky 8/9/10, Oracle Linux with UEK and RHCK), SLES 15 SP7 / 16, openSUSE Leap 15.6, and Arch (experimental). BIOS and UEFI, LVM across several disks, btrfs with snapper, SELinux enforcing…
      • Windows: Server 2016, 2019, 2022 and 2025.
      • Older Windows (7 SP1, 2012 R2): docked, but they run without PV drivers.
      • Not docked: encrypted system volumes (LUKS, BitLocker), dynamic disks, hibernated VMs or Fast Startup, and no OS found (BSD…).

      How to test

      Docking is experimental and off by default.

      • XO 6: available in [XO from sources / XOA X.Y]. Open the V2V wizard, pick your VMs, then tick Auto-pilot docking and/or Start VM after migration.
      • REST API: the docking and startVm options of POST /rest/v0/pools/:id/actions/import_vms_from_vmware.
      • The docking ISO must be in an ISO SR of the target pool: link to the ISO. For the most curious, the build system is in @xen-orchestra/autopilot-docking/scripts/build.sh (building it from a CI needs a privileged runner).

      All the details are in PR #10621 and in the V2V migration guide.

      We need you!

      Weird setups are exactly what we want: exotic partitioning, old distros, multi-NIC Windows with static IPs… And of course, any feedback on the new wizard is welcome. If something goes wrong, the import task holds the full report, so please share it here.

      Feel free to react or ask questions! πŸ™‚

      J 1 Reply Last reply
      Reply Quote 0
      • florentF florent referenced this topic
      • J
        jr-m4 @florent
        last edited by

        @florent

        I'm going to be testing this more extensively during the week.

        Quick question.
        When/If I choose to remember the connection. Will that save my credentials as well? If so, then I would like to propose that splitting that up to being able to save the connection host/target e.g. vcenter.contoso.lan, and the credentials separately.

        But in my first try-run.

        Docking failed: (I'm surely doing something wrong)
        no docking ISO vates-autopilot-docking-<YYYYMMDDTHHMMSSZ>-<commit or version>.iso in the pool

        Error: no docking ISO vates-autopilot-docking-<YYYYMMDDTHHMMSSZ>-<commit or version>.iso in the pool
            at findDockingIso (file:///opt/xen-orchestra/packages/xo-server/src/xo-mixins/vmware/_docking.mjs:48:19)
            at MigrateVm.migrationfromEsxi (file:///opt/xen-orchestra/packages/xo-server/src/xo-mixins/vmware/index.mjs:344:7)
            at file:///opt/xen-orchestra/@xen-orchestra/rest-api/dist/v2v/v2v.service.mjs:69:38
            at Task.runInside (/opt/xen-orchestra/@vates/task/index.js:204:22)
            at Task.run (/opt/xen-orchestra/@vates/task/index.js:188:20)
            at asyncEach.concurrency.concurrency (file:///opt/xen-orchestra/@xen-orchestra/rest-api/dist/v2v/v2v.service.mjs:67:17)
        

        And thanks for enabling auto-start of the VM after the migration has completed!

        florentF 1 Reply Last reply
        Reply Quote 0
        • florentF
          florent Vates πŸͺ XO Team @jr-m4
          last edited by florent

          both are saved at the same time in your browser, but we could split the UI

          @jr-m4 yes, you need to deploy the iso http://xoa.io/vates-autopilot-docking-20261116T173627Z-8c206149.iso on the pool that will receive the migration

          automatic boot is really useful after docking, most of the VM don't really like to be booted automatically without changing network / drivers/...

          J 2 Replies Last reply
          Reply Quote 0
          • J
            jr-m4 @florent
            last edited by

            @florent
            As another suggestion. Maybe we could pre-populate a default list with source-hosts as well?

            Reason is that I really don't want to save credentials in browser. But if I can get away from typing the host of vcenter each time, then that would be absolutely lovely.

            Thanks for pointing out the iso to download. I missed that download link unfortunately. Merci!

            1 Reply Last reply
            Reply Quote 0
            • J
              jr-m4 @florent
              last edited by

              @florent
              Could I bother to have a checksum of the ISO as well, please?

              florentF 1 Reply Last reply
              Reply Quote 0
              • olivierlambertO
                olivierlambert Vates πŸͺ Co-Founder CEO
                last edited by olivierlambert

                @jr-m4 sha256sum is d7eb1b569afe93e3c5a4a07fa889ffcc1df4dff56732f334fef69f062d2e7c05 vates-autopilot-docking-20261116T173627Z-8c206149.iso

                1 Reply Last reply
                Reply Quote 1
                • florentF
                  florent Vates πŸͺ XO Team @jr-m4
                  last edited by

                  This post is deleted!
                  1 Reply Last reply
                  Reply Quote 0
                  • J
                    jr-m4
                    last edited by

                    I'm having very fun testing this out. And you've really got something with extreme potential here. And I am very impressed. Thank you!

                    So far I've noticed a couple of things, both very small and medium in size. And I've tried to collect my initial thoughts below.

                    v2v xo6 thought

                    • "next: mapping" is far down, when browsing "ALL". Could be remedied with placing it up at the top. With the header fixed at the top as well.

                    • Consider showing what networks are attached in the VM-list.

                      • Further suggestion could be to look into some smart-mapping. A simple (not saying the implementation would be easy, but the matching algorithm), that matches source-VLAN vs target-VLAN.
                    • Have a V2V settings page, where many defaults could be set. Examples are:

                      • Tags: Although you can click into each VM that is supposed to be migrated. Doing so for hundreds of VMs would be tedious very quickly. So an on-masse applying of tags would be great. (yes I'm aware there is a notice specifically about tags.
                      • Deciding what would be the active default. Such as example deciding if Docking and "Start the VM on XCP-ng" would be pre-checked or not (current default).
                      • Concurrent VMs
                    • Incorporate an option to set if a VM should be booted with BIOS or UEFI. Perhaps be able to match with vmware-source?

                    • When creating a migration, there is no way to discard already existing list, except for continuing with existing list and clear it inside.

                    • When a migration is underway. It would be nice if the migration task for that VM would show up under the Tasks-tab for that particular VM as well. Not just in the "Tasks-section for XO"

                    Questions:

                    • When importing a VM. The task for that particular VM has a percentage counter for its import. This does not seem to work. So my question is, what is the percentage of completion based on?
                    florentF 1 Reply Last reply
                    Reply Quote 0
                    • florentF
                      florent Vates πŸͺ XO Team @jr-m4
                      last edited by

                      @jr-m4

                      I will a colleague from the front team for the UI/UX question

                      • vlan mapping : we hve the same quesiton for migration between xcp-ng, but have yet to find the right approach

                      • tags : should be available soon

                      • docking by default : we are waiting for more tester before enabling this

                      • concurrent VM is already possible ( even in XO5) , by default I think it's 2 VMs

                      • it should match the source , at least it did in my tests

                      • you have a clear button on the top of the VM list

                      • this is planned

                      on a VM , there is a per disk counter ( that rely on the disk size ) . The global progress bar at the root of the task is the number of vm done Vs the total number of VM to migrate

                      J 1 Reply Last reply
                      Reply Quote 1
                      • J
                        jr-m4 @florent
                        last edited by

                        @florent

                        "you have a clear button on the top of the VM list":
                        Yes, but you have to click into that VM-list first. My suggestion is that you could have a clear-list option prior to that. See screenshot:
                        image.jpeg

                        Regarding having a V2V Settings page. Here is an extremely rough mockup
                        image.jpeg

                        Again. Great thanks to implementing this to begin with. I will also report back if I find any problems.

                        1 Reply Last reply
                        Reply Quote 0

                        Hello! It looks like you're interested in this conversation, but you don't have an account yet.

                        Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

                        With your input, this post could be even better πŸ’—

                        Register Login
                        • First post
                          Last post