XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login
    • Profile
    • Following 0
    • Followers 2
    • Topics 2
    • Shares 0
    • Posts 811
    • Groups 3
    florentF Offline
    1. Home
    2. florent

    florent

    @florent

    Vates πŸͺ XO Team
    315
    Reputation
    189
    Profile views
    811
    Posts
    2
    Followers
    0
    Following
    Joined
    Last Online
    Email florent.beauchamp@vates.fr

    florent Unfollow Follow
    Team - XO Backend Vates πŸͺ XO Team
    • RE: backup mail report says INTERRUPTED but it's not ?

      On tomorrow 's release we will:

      • reduce the polling for the patches list
      • add more debug to know exactly what request go through the xo6 api (rest api)

      following this we will add core xo metrics to the openmetrics ( prometheus) export to allow users and support to dig through real world data when needed

      posted in Backup
      florentF
      florent
    • RE: Mirror backup: Progress status and ETA

      @Forza

      Cancelling a backup run is also on our roadmap ,as soon as we have done reworking the tasks to use xo-task on the full chain, and not an hybrid of various iteration of the tasks objects

      better tracking of the backup run is also on our roadmap , this is also linked to the task changes plus are some issues with the size on the remote before being able to do this

      In any case, both are on our backlog

      posted in Backup
      florentF
      florent
    • RE: πŸ›°οΈ XO 6: dedicated thread for all your feedback!

      Hi everyone πŸ‘‹

      V2V just landed in the XO 6 UI, and it's more than a port of the XO 5 form:

      • Reworked step-by-step wizard
      • Network, storage and template picked per VM, not once for the whole batch
      • Start VM after migration
      • Auto-pilot docking (experimental): XO boots the imported VM on a small live ISO that fixes it before its first boot on XCP-ng. Xen PV drivers in the initramfs, VMware Tools out, guest tools in, static IPs and MACs kept. No more INACCESSIBLE_BOOT_DEVICE πŸ˜…

      Your VMware VM stays untouched as a fallback, and a failed docking never fails the import.

      All the details (supported OSes, how it works, how to test) are on a topic next to this one : https://xcp-ng.org/forum/topic/12583/v2v-in-xo-6-a-brand-new-migration-wizard-with-auto-pilot-docking

      We're especially looking for weird setups: old distros, exotic partitioning, multi-NIC Windows with static IPs… Feedback welcome, here or on the forum! πŸ™‚

      posted in Xen Orchestra
      florentF
      florent
    • RE: Veeam backup with XCP NG

      @Pilow said in Veeam backup with XCP NG:

      @olivierlambert I get you.

      Same in veeam and synthetic fulls, it's only between the server/proxy and the repository.
      but we get a progressing percentage while the job sits while doing the synthetic full.

      would be cool to "see" the progress of merging.
      why ? bad habits from previous technologies used I guess.

      Giving better observability is something we are working actively on , this is tightly coupled with being able to stop a task, and I hope we will be able to show the progress soon

      posted in Backup
      florentF
      florent
    • RE: Question on Mirror backups

      @manilx yes, that's it

      we should change the "full backup interval" to "base/complete backup interval", to clarify what is a full . And we will do it.

      posted in Backup
      florentF
      florent
    • RE: Cannot Import VMDK Through Import > Disk (migrating from ESXi, all methods not working)

      we are reworking the import code , along the new backup code ( https://xcp-ng.org/forum/topic/10664/our-future-backup-code-test-it ) to unify the differetn disk transformation path

      For now:

      • V2V handles flat, cowd, sesparse, stream optimized vmdk in the format "metadata.vmdk and a data file ) and ova ( for VSAN)
      • disk import support monolithic vmdk ( cowd, sesparse, streamoptimized )
      • ova improt support only stream ova with streamoptimzed vmdk inside
      posted in Xen Orchestra
      florentF
      florent
    • RE: Backblaze B2 as a backup remote

      @andrewreid Yes, I can't wait to share it with everybody.

      posted in Xen Orchestra
      florentF
      florent
    • RE: Continuous Replication isnt deleting old Replikas anymore since Update

      @AlexD2006 thanks for signaling this, we just merged a fix, that fix it on our labs
      can you test it on your side ?
      https://github.com/vatesfr/xen-orchestra/pull/9202

      posted in Backup
      florentF
      florent
    • RE: Continuous Replication isnt deleting old Replikas anymore since Update

      @AlexD2006 this looks like the right issue, we will look into it immediately ( yesterday was a public holiday in France)

      posted in Backup
      florentF
      florent
    • RE: Continuous Replication jobs creates full backups every time since 2025-09-06 (xo from source)

      @Andrew then again, with such a precise report, the fix is easier

      the fix should join master soon

      posted in Backup
      florentF
      florent
    • RE: πŸ›°οΈ XO 6: dedicated thread for all your feedback!

      @coolsport00 the monthly blog post are the easiest way to follow what is going on.

      the https://github.com/vatesfr/xen-orchestra/blob/master/CHANGELOG.unreleased.md or the open PR are showing what is merged but not yes released in xoa, and what we are working on, but it's quite hard to read now that the teams are up to speed and the tools ready
      (note that we are still only the 18 , we have ~10 more days to push feature before the end of the month)

      posted in Xen Orchestra
      florentF
      florent
    • RE: V2V in XO 6: a brand new migration wizard, with Auto-pilot docking πŸ›¬

      @jr-m4 yes, the global counter is updated only when the VM has finished the docking and is completely done

      thank you for testing it.
      Are you using windows or liinux VMs ? which flavors ?

      posted in Xen Orchestra
      florentF
      florent
    • RE: V2V in XO 6: a brand new migration wizard, with Auto-pilot docking πŸ›¬

      @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

      posted in Xen Orchestra
      florentF
      florent
    • RE: V2V in XO 6: a brand new migration wizard, with Auto-pilot docking πŸ›¬

      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/...

      posted in Xen Orchestra
      florentF
      florent
    • RE: πŸ›°οΈ XO 6: dedicated thread for all your feedback!

      Hi everyone πŸ‘‹

      V2V just landed in the XO 6 UI, and it's more than a port of the XO 5 form:

      • Reworked step-by-step wizard
      • Network, storage and template picked per VM, not once for the whole batch
      • Start VM after migration
      • Auto-pilot docking (experimental): XO boots the imported VM on a small live ISO that fixes it before its first boot on XCP-ng. Xen PV drivers in the initramfs, VMware Tools out, guest tools in, static IPs and MACs kept. No more INACCESSIBLE_BOOT_DEVICE πŸ˜…

      Your VMware VM stays untouched as a fallback, and a failed docking never fails the import.

      All the details (supported OSes, how it works, how to test) are on a topic next to this one : https://xcp-ng.org/forum/topic/12583/v2v-in-xo-6-a-brand-new-migration-wizard-with-auto-pilot-docking

      We're especially looking for weird setups: old distros, exotic partitioning, multi-NIC Windows with static IPs… Feedback welcome, here or on the forum! πŸ™‚

      posted in Xen Orchestra
      florentF
      florent
    • V2V in XO 6: a brand new migration wizard, with Auto-pilot docking πŸ›¬

      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! πŸ™‚

      posted in Xen Orchestra
      florentF
      florent
    • RE: Full backup failure when upgrading XOce

      @ph7 can you try with node 24 ?
      are there any logs ?

      posted in Backup
      florentF
      florent
    • RE: Xen Orchestra web UI becomes unresponsive when an NFS backup remote goes offline

      when a NFS munt in hard mount mode fails, it is quite tricky to handle on user land, and falling back to a soft mount means we accept to loose data without knowing

      To unstuck a XO with a brken NFS , we added a cli tool that allow you to disable a remote here https://github.com/vatesfr/xen-orchestra/pull/10587

      posted in Xen Orchestra
      florentF
      florent
    • RE: Incremental Backup Question

      @Velocity1192 If you can wait a little, we are atively working on the new XO6 backup job uI, that will come with some changes : one schedule per job, but with conditionnal actions

      You will run an incremental job, and will be able to define that the schedule of sunday is a full,and even run a healthcheck on it

      The ETA is on 6.11 ( next month release )

      posted in Backup
      florentF
      florent
    • RE: Troubleshooting "TCP: out of memory" - Possible memory leak?

      @jr-m4 you can export the heap memory of the nodeJS process by doing kill -SIGUSER2 <xoserverpid>

      onte that this will increase a lot the memory consumed by the xo process even when its done exporting the memory . This will help us know what xo is doing at the moment

      posted in Xen Orchestra
      florentF
      florent