XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login
    1. Home
    2. Popular
    Log in to post
    • All Time
    • Day
    • Week
    • Month
    • All Topics
    • New Topics
    • Watched Topics
    • Unreplied Topics

    • All categories
    • florentF

      V2V in XO 6: a brand new migration wizard, with Auto-pilot docking 🛬

      Watching Ignoring Scheduled Pinned Locked Moved Xen Orchestra
      14
      5
      0 Votes
      14 Posts
      168 Views
      J
      Small thing I noticed: I have set the job to import 4 VMs. (2 concurrent) The Global counter is listing 3, as it has completed 1 and therefore gone up from 2->3.. However, the global counter-circle is listing 3. But the tracking percentage is counting the overall job. So in this case, the percentage tracker, is the correct one. Whereas the acctual counter is not showing the acctual amount of VMs that are in the job. [image: image.jpeg]
    • olivierlambertO

      🛰️ XO 6: dedicated thread for all your feedback!

      Watching Ignoring Scheduled Pinned Locked Moved Xen Orchestra
      332
      7 Votes
      332 Posts
      227k Views
      julienXOvatesJ
      @coolsport00 said: Is there the ability to Add a Host to a Pool in v6 yet? When I click on the Pool, in the default Dashboard view, there is no 'Add Host' option in the upper right; just Add VM option. Would be beneficial to have that there, as well as a Quick Action item in the navigation tree on the left: [image: image.jpeg] I can add this as a suggestion if desired as well. Thanks! @coolsport00 yes we do have this on roadmap, but we'd like to make it more friendly and smarter than in XO5, so to speak we think of a new panel with the following actions: add a secondary/slave host rename a hostname update host credentials remove a slave host change master host (when HA disabled) That's why it's not there yet. But I agree it's missing, so we can consider having "add a secondary/slave host" in a quicker way in the meantime !
    • P

      Full backup failure when upgrading XOce

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved Backup
      13
      0 Votes
      13 Posts
      250 Views
      P
      @acebmxer said: So when you used my script it worked aside from the backup hiccup? Yes, so far what I have tested. Seems like You put some effort int this one, keeping my fingers crossed It' using node v24.22.3
    • B

      Missing vdi which is a base for a delta

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved Backup
      13
      0 Votes
      13 Posts
      830 Views
      poddingueP
      Glad you got a clean run out of it, and thanks for coming back to say what worked. If I'm reading the mirror code right, it checks that the parent disk of each delta is already on every target, and stops with this exact error when one isn't there. How a chain ends up without its key in the first place, I can't tell you. Which remote were those chains on, Ark or one of the mirror targets? And before you wipe everything and start over, could you jot down which VMs had them? I think that's what someone would need to chase the cause.
    • acebmxerA

      Backups in OX v6

      Watching Ignoring Scheduled Pinned Locked Moved Backup
      2
      3
      0 Votes
      2 Posts
      66 Views
      poddingueP
      I don't think the manual run part is a bug. XO 6 has its own message for it ("This backup job has multiple schedules"), so it looks like a deliberate limit for now, though I don't know the reasoning behind it. On the chains, if I'm reading the backup code right, an incremental job only looks for its parent disks in a folder named after the job's ID. If that's right, splitting into two jobs would give you two separate chains on the remote, each starting with its own full. If the Full Backups schedule is there to restart the chain every so often, the docs describe the full backup interval setting on the delta job as the way to do that within one job: https://docs.xen-orchestra.com/backups-and-dr/backup-types/incremental_backups#key-backup-interval I haven't tried switching a running job over to it myself. @Team-XO-Frontend can probably say what the split advice has in mind.
    • F

      New Tools 9.2.445 update failure

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved Management
      5
      1
      0 Votes
      5 Posts
      158 Views
      F
      @dinhngtu I will mention that the package was deployed via windows SCCM deployment tools so that may have also played a part in leaving the old product code behind. After running the above script we were able to deploy 9.2.445 via SCCM without issue and no old product codes were left behind.
    • P

      xoa kernel update crash the VM ! linux-image-6.1.0-55

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved Management
      4
      1 Votes
      4 Posts
      71 Views
      poddingueP
      Thanks for the heads-up, @Pilow. In case someone finds this later, Debian tracks it as bug #1154101, an ext4 regression in kernel 6.1.192-1, which installs as -55. They marked it fixed in 6.1.192-2 on 16 November. That one installs as linux-image-6.1.0-56-amd64, so it's the -56 in your proxy screenshot. The XOA in my test lab never picked up -55, and apt-cache policy there already offers 6.1.192-2 as the next kernel. I think unattended-upgrades will jump straight to the fixed one, but I haven't watched it do that. If you put the hold in place, you'll want sudo apt-mark unhold linux-image-amd64 once you're on -56. Otherwise, if I understand holds correctly, the box stops getting kernel updates, including the security ones. It might be worth a mention to @Team-XO-Backend too, since XOA installs these kernels on its own.
    • B

      New project - XenAdminQt - a cross-platform GNU/Linux, macOS, Windows native thick client

      Watching Ignoring Scheduled Pinned Locked Moved News
      60
      1
      9 Votes
      60 Posts
      18k Views
      C
      @benapetr That's fantastic - thank you! Thanks @bvitnik for the better screenshots .