XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login
    • Profile
    • Following 0
    • Followers 0
    • Topics 50
    • Posts 532
    • Groups 0
    acebmxerA Online
    1. Home
    2. acebmxer

    acebmxer

    @acebmxer

    172
    Reputation
    41
    Profile views
    532
    Posts
    0
    Followers
    0
    Following
    Joined
    Last Online
    Website forums.pozzatech.com
    Location New Jersey, United States

    acebmxer Unfollow Follow
    • Migration from VMware to XCP-NG complete.

      Finally just finished our migration from VMware to XCP-NG.

      VMs - 34 mix windows server and ubuntu linux.
      Pools - 3
      Host - 6
      Dell R660 - 2
      Dell R640 - 4

      Screenshot_20260218_193945.png

      posted in Share your setup!
      acebmxerA
      acebmxer
    • RE: XCP-ng 8.3 updates announcements and testing

      @gleh

      Installed...

      Updated:
        blktap.x86_64 0:3.55.5-9.4.xcpng8.3                forkexecd.x86_64 0:26.1.16-1.2.xcpng8.3                
        message-switch.x86_64 0:26.1.16-1.2.xcpng8.3       qcow-stream-tool.x86_64 0:26.1.16-1.2.xcpng8.3         
        rrdd-plugins.x86_64 0:26.1.16-1.2.xcpng8.3         sm.x86_64 0:3.2.12-23.5.xcpng8.3                       
        sm-cli.x86_64 0:26.1.16-1.2.xcpng8.3               sm-fairlock.x86_64 0:3.2.12-23.5.xcpng8.3              
        squeezed.x86_64 0:26.1.16-1.2.xcpng8.3             varstored-guard.x86_64 0:26.1.16-1.2.xcpng8.3          
        vhd-tool.x86_64 0:26.1.16-1.2.xcpng8.3             wsproxy.x86_64 0:26.1.16-1.2.xcpng8.3                  
        xapi-core.x86_64 0:26.1.16-1.2.xcpng8.3            xapi-nbd.x86_64 0:26.1.16-1.2.xcpng8.3                 
        xapi-rrd2csv.x86_64 0:26.1.16-1.2.xcpng8.3         xapi-storage-script.x86_64 0:26.1.16-1.2.xcpng8.3      
        xapi-tests.x86_64 0:26.1.16-1.2.xcpng8.3           xapi-xe.x86_64 0:26.1.16-1.2.xcpng8.3                  
        xcp-networkd.x86_64 0:26.1.16-1.2.xcpng8.3         xcp-rrdd.x86_64 0:26.1.16-1.2.xcpng8.3                 
        xenopsd.x86_64 0:26.1.16-1.2.xcpng8.3              xenopsd-cli.x86_64 0:26.1.16-1.2.xcpng8.3              
        xenopsd-xc.x86_64 0:26.1.16-1.2.xcpng8.3
      
      posted in News
      acebmxerA
      acebmxer
    • RE: XCP-ng 8.3 updates announcements and testing

      @rzr said:

      We pushed the tested packages along a xen security update to the xcp-ng-updates repository, check blog post for summary and related advisories:
      https://xcp-ng.org/blog/2026/07/28/july-2026-updates-1-for-xcp-ng-8-3-lts/

      Just updated my homelab hosts.

      [10:45 xcp-ng-disjqdnc ~]# yum clean metadata
      Loaded plugins: fastestmirror
      Cleaning repos: xcp-ng-base xcp-ng-updates
      6 metadata files removed
      4 sqlite files removed
      0 metadata files removed
      [10:45 xcp-ng-disjqdnc ~]# yum update
      Loaded plugins: fastestmirror
      Loading mirror speeds from cached hostfile
      Excluding mirror: updates.xcp-ng.org
       * xcp-ng-base: mirrors.xcp-ng.org
      Excluding mirror: updates.xcp-ng.org
       * xcp-ng-updates: mirrors.xcp-ng.org
      xcp-ng-base/signature                                                                                                |  473 B  00:00:00     
      xcp-ng-base/signature                                                                                                | 3.0 kB  00:00:00 !!! 
      xcp-ng-updates/signature                                                                                             |  473 B  00:00:00     
      xcp-ng-updates/signature                                                                                             | 3.0 kB  00:00:00 !!! 
      (1/2): xcp-ng-base/primary_db                                                                                        | 3.9 MB  00:00:00     
      (2/2): xcp-ng-updates/primary_db                                                                                     | 1.6 MB  00:00:01     
      Resolving Dependencies
      --> Running transaction check
      ---> Package xen-dom0-libs.x86_64 0:4.17.6-9.3.xcpng8.3 will be updated
      ---> Package xen-dom0-libs.x86_64 0:4.17.6-9.3.1.xcpng8.3 will be an update
      ---> Package xen-dom0-tools.x86_64 0:4.17.6-9.3.xcpng8.3 will be updated
      ---> Package xen-dom0-tools.x86_64 0:4.17.6-9.3.1.xcpng8.3 will be an update
      ---> Package xen-hypervisor.x86_64 0:4.17.6-9.3.xcpng8.3 will be updated
      ---> Package xen-hypervisor.x86_64 0:4.17.6-9.3.1.xcpng8.3 will be an update
      ---> Package xen-libs.x86_64 0:4.17.6-9.3.xcpng8.3 will be updated
      ---> Package xen-libs.x86_64 0:4.17.6-9.3.1.xcpng8.3 will be an update
      ---> Package xen-tools.x86_64 0:4.17.6-9.3.xcpng8.3 will be updated
      ---> Package xen-tools.x86_64 0:4.17.6-9.3.1.xcpng8.3 will be an update
      --> Finished Dependency Resolution
      
      Dependencies Resolved
      
      ============================================================================================================================================
       Package                          Arch                     Version                                   Repository                        Size
      ============================================================================================================================================
      Updating:
       xen-dom0-libs                    x86_64                   4.17.6-9.3.1.xcpng8.3                     xcp-ng-updates                   704 k
       xen-dom0-tools                   x86_64                   4.17.6-9.3.1.xcpng8.3                     xcp-ng-updates                   2.0 M
       xen-hypervisor                   x86_64                   4.17.6-9.3.1.xcpng8.3                     xcp-ng-updates                   2.4 M
       xen-libs                         x86_64                   4.17.6-9.3.1.xcpng8.3                     xcp-ng-updates                    66 k
       xen-tools                        x86_64                   4.17.6-9.3.1.xcpng8.3                     xcp-ng-updates                    47 k
      
      Transaction Summary
      ============================================================================================================================================
      Upgrade  5 Packages
      
      Total download size: 5.2 M
      Is this ok [y/d/N]: y
      Downloading packages:
      Delta RPMs disabled because /usr/bin/applydeltarpm not installed.
      (1/5): xen-dom0-tools-4.17.6-9.3.1.xcpng8.3.x86_64.rpm                                                               | 2.0 MB  00:00:00     
      (2/5): xen-dom0-libs-4.17.6-9.3.1.xcpng8.3.x86_64.rpm                                                                | 704 kB  00:00:00     
      (3/5): xen-libs-4.17.6-9.3.1.xcpng8.3.x86_64.rpm                                                                     |  66 kB  00:00:00     
      (4/5): xen-hypervisor-4.17.6-9.3.1.xcpng8.3.x86_64.rpm                                                               | 2.4 MB  00:00:00     
      (5/5): xen-tools-4.17.6-9.3.1.xcpng8.3.x86_64.rpm                                                                    |  47 kB  00:00:00     
      --------------------------------------------------------------------------------------------------------------------------------------------
      Total                                                                                                       2.9 MB/s | 5.2 MB  00:00:01     
      Running transaction check
      Running transaction test
      Transaction test succeeded
      Running transaction
        Updating   : xen-libs-4.17.6-9.3.1.xcpng8.3.x86_64                                                                                   1/10 
        Updating   : xen-hypervisor-4.17.6-9.3.1.xcpng8.3.x86_64                                                                             2/10 
        Updating   : xen-dom0-libs-4.17.6-9.3.1.xcpng8.3.x86_64                                                                              3/10 
        Updating   : xen-tools-4.17.6-9.3.1.xcpng8.3.x86_64                                                                                  4/10 
        Updating   : xen-dom0-tools-4.17.6-9.3.1.xcpng8.3.x86_64                                                                             5/10 
        Cleanup    : xen-dom0-tools-4.17.6-9.3.xcpng8.3.x86_64                                                                               6/10 
        Cleanup    : xen-tools-4.17.6-9.3.xcpng8.3.x86_64                                                                                    7/10 
        Cleanup    : xen-dom0-libs-4.17.6-9.3.xcpng8.3.x86_64                                                                                8/10 
        Cleanup    : xen-hypervisor-4.17.6-9.3.xcpng8.3.x86_64                                                                               9/10 
        Cleanup    : xen-libs-4.17.6-9.3.xcpng8.3.x86_64                                                                                    10/10 
        Verifying  : xen-dom0-tools-4.17.6-9.3.1.xcpng8.3.x86_64                                                                             1/10 
        Verifying  : xen-dom0-libs-4.17.6-9.3.1.xcpng8.3.x86_64                                                                              2/10 
        Verifying  : xen-hypervisor-4.17.6-9.3.1.xcpng8.3.x86_64                                                                             3/10 
        Verifying  : xen-libs-4.17.6-9.3.1.xcpng8.3.x86_64                                                                                   4/10 
        Verifying  : xen-tools-4.17.6-9.3.1.xcpng8.3.x86_64                                                                                  5/10 
        Verifying  : xen-libs-4.17.6-9.3.xcpng8.3.x86_64                                                                                     6/10 
        Verifying  : xen-dom0-tools-4.17.6-9.3.xcpng8.3.x86_64                                                                               7/10 
        Verifying  : xen-hypervisor-4.17.6-9.3.xcpng8.3.x86_64                                                                               8/10 
        Verifying  : xen-tools-4.17.6-9.3.xcpng8.3.x86_64                                                                                    9/10 
        Verifying  : xen-dom0-libs-4.17.6-9.3.xcpng8.3.x86_64                                                                               10/10 
      
      Updated:
        xen-dom0-libs.x86_64 0:4.17.6-9.3.1.xcpng8.3 xen-dom0-tools.x86_64 0:4.17.6-9.3.1.xcpng8.3 xen-hypervisor.x86_64 0:4.17.6-9.3.1.xcpng8.3
        xen-libs.x86_64 0:4.17.6-9.3.1.xcpng8.3      xen-tools.x86_64 0:4.17.6-9.3.1.xcpng8.3
      
      posted in News
      acebmxerA
      acebmxer
    • RE: XCP-ng 8.3 updates announcements and testing

      @rzr

      Updates applied...

      Updated:
        forkexecd.x86_64 0:26.1.11-1.2.xcpng8.3                         kexec-tools.x86_64 1:2.0.15-21.1.xcpng8.3                           
        message-switch.x86_64 0:26.1.11-1.2.xcpng8.3                    qcow-stream-tool.x86_64 0:26.1.11-1.2.xcpng8.3                      
        rrdd-plugins.x86_64 0:26.1.11-1.2.xcpng8.3                      sm-cli.x86_64 0:26.1.11-1.2.xcpng8.3                                
        squeezed.x86_64 0:26.1.11-1.2.xcpng8.3                          varstored-guard.x86_64 0:26.1.11-1.2.xcpng8.3                       
        vhd-tool.x86_64 0:26.1.11-1.2.xcpng8.3                          wsproxy.x86_64 0:26.1.11-1.2.xcpng8.3                               
        xapi-core.x86_64 0:26.1.11-1.2.xcpng8.3                         xapi-nbd.x86_64 0:26.1.11-1.2.xcpng8.3                              
        xapi-rrd2csv.x86_64 0:26.1.11-1.2.xcpng8.3                      xapi-storage-script.x86_64 0:26.1.11-1.2.xcpng8.3                   
        xapi-tests.x86_64 0:26.1.11-1.2.xcpng8.3                        xapi-xe.x86_64 0:26.1.11-1.2.xcpng8.3                               
        xcp-networkd.x86_64 0:26.1.11-1.2.xcpng8.3                      xcp-rrdd.x86_64 0:26.1.11-1.2.xcpng8.3                              
        xenopsd.x86_64 0:26.1.11-1.2.xcpng8.3                           xenopsd-cli.x86_64 0:26.1.11-1.2.xcpng8.3                           
        xenopsd-xc.x86_64 0:26.1.11-1.2.xcpng8.3                       
      
      Complete!
      

      Will continue to test.

      posted in News
      acebmxerA
      acebmxer
    • RE: XCP-ng 8.3 updates announcements and testing

      @rzr Installed latest update and no issues to report. I dont hvae any 2tb+ drives in my vms. converting from vhd to qcow2 and backups all working.

      posted in News
      acebmxerA
      acebmxer
    • RE: XCP-ng 8.3 updates announcements and testing

      @rzr

      installed updates will report back.

      Update - I had migrated vms back over to vhd prior to update release. I have migrated 2 vms back over to qcow2 and the initial backup ran successfull. Ran a second delta backup and that as well was successful with out issues. Backups happen very quickly now. But it appears the % and progress bar are working.

      When CBT is enabled on the vm vdi. They show up as needing to be coalesced. VMs without CBT enabled the vdis are coalesced.

      Screenshot 2026-04-23 143142.png

      Will continue to monitor.

      Once the coalesence hits 2 for the vm. The vm is skipped form future backups until cleared. (shutting down the vm will allow the coalescence to happen.
      2026-04-23T19_52_34.694Z - backup NG.txt

      Screenshot 2026-04-23 155432.png

      Screenshot 2026-04-23 155727.png

      posted in News
      acebmxerA
      acebmxer
    • RE: XCP-ng 8.3 updates announcements and testing

      @olivierlambert Created new topic.

      posted in News
      acebmxerA
      acebmxer
    • RE: XCP-ng 8.3 updates announcements and testing

      @rzr

      Updated my to AMD Ryzen host in my home lab. No issues with update will monitor and report back any issues.

      posted in News
      acebmxerA
      acebmxer
    • RE: 🛰️ XO 6: dedicated thread for all your feedback!

      @julienXOvates

      Ok that was in xo from sources and yes issue is fixed...

      Confirmed is working in XOA in 6.4.1

      Screenshot 2026-05-05 083337.png

      posted in Xen Orchestra
      acebmxerA
      acebmxer
    • Install XO from sources.

      While this project is more for myself it is open to others to use. Please use at your own risk. As always review the script before using in a production environment. Please leave any feedback or suggestions. https://github.com/acebmxer/install_xen_orchestra/
      https://forums.pozzatech.com - You can read more about this project and other things over in my personal forums.

      Automated installation and management of Xen Orchestra from source.

      Update 5/15/26 - This update only applies to anyone using older version of script. See note. Also added option to Adjust Xen Orchestra Memory Allocation. It will look at the system memory and suggest setting for XO based off the official documentation.

      ⚠️ Upgrading from an earlier version of this script? Read this first.
      This version bumps the config schema to v2 (adds PUBLIC_URL and ENCRYPT_REDIS_CREDENTIALS) and corrects two config.toml generation bugs. Your xo-config.cfg is migrated automatically and non-destructively, but the corrected /etc/xo-server/config.toml is only written by --reconfigure.
      
      Run --reconfigure once before resuming normal updates:
      
      ./install-xen-orchestra.sh --reconfigure
      This regenerates config.toml with the fixes (your old file is backed up first; data in /var/lib/xo-server is untouched). It is strongly recommended if you set both REDIRECT_TO_HTTPS=true and REVERSE_PROXY_TRUST — that combination previously produced a duplicate [http] section and silently dropped one of the settings.
      
      Afterwards, run --update as normal for routine XO updates — --update does not need to be preceded by --reconfigure again.
      

      Available Functions

      Function CLI Flag Description
      Install --install Fresh install of Xen Orchestra
      Update --update Update existing installation (with backup)
      Restore --restore Restore from a previous backup
      Rebuild --rebuild Fresh clone + clean build, preserves settings
      Reconfigure --reconfigure Apply config changes without rebuilding
      XO Proxy --proxy Deploy XO Proxy to a Xen pool master
      Edit Config (menu only) Open xo-config.cfg in your preferred editor
      Rename Config (menu only) Rename sample-xo-config.cfg to xo-config.cfg

      Running without flags launches an interactive menu. All flags also work directly:

      ./install-xen-orchestra.sh           # interactive menu
      ./install-xen-orchestra.sh --update  # run update directly
      ./install-xen-orchestra.sh --help    # show all options
      

      Interactive Menu

      Running the script with no arguments opens a two-column menu with keyboard navigation:

        ╔══════════════════════════════════════════════════════════════════════════════════╗
        ║              Install Xen Orchestra from Sources Setup and Update                 ║
        ╚══════════════════════════════════════════════════════════════════════════════════╝
      
                              Current Script Commit : 693f4 (Branch: main)
                              Master Script Commit  : 693f4 (Branch: main)
                              Current XO Commit     : a1b2c (Branch: master)
                              Master XO Commit      : d4e5f (Branch: master)
                              Current Node          : v24.15.0
      
        ──────────────────────────────────────────────────────────────────────────────────
      
        ▸ [✓] Install Xen Orchestra                   [ ] Reconfigure Xen Orchestra
          [ ] Update Xen Orchestra                    [ ] Rebuild Xen Orchestra
          [ ] Rename Sample-xo-config.cfg             [ ] Edit xo-config.cfg
          [ ] Install XO Proxy                        [ ]  Restore Backup
                               [ ] Adjust Xen Orchestra Memory Allocation
      
        ──────────────────────────────────────────────────────────────────────────────────
      
        Selected: 1
      
        ↑↓←→ Navigate   SPACE Select/Deselect   ENTER Confirm   Q Quit
      

      Select one or more items with SPACE, then press ENTER to run them.

      Quick Start

      git clone https://github.com/acebmxer/install_xen_orchestra.git
      cd install_xen_orchestra
      cp sample-xo-config.cfg xo-config.cfg
      nano xo-config.cfg   # edit to your liking
      ./install-xen-orchestra.sh
      

      Do NOT run with sudo. Run as a normal user with sudo privileges — the script handles sudo internally.

      If xo-config.cfg doesn't exist, it will be created automatically from the sample.

      Configuration

      All settings live in xo-config.cfg. See sample-xo-config.cfg for full documentation of every option.

      Key settings:

      Option Default Description
      HTTP_PORT 80 HTTP port
      HTTPS_PORT 443 HTTPS port
      INSTALL_DIR /opt/xen-orchestra Installation directory
      GIT_BRANCH master Git branch or tag
      NODE_VERSION 24.15.0 Node.js version
      SERVICE_USER xo-service Service user (set to root for VMware V2V import)
      BACKUP_KEEP 5 Number of backups to retain
      BIND_ADDRESS 0.0.0.0 Bind address
      REVERSE_PROXY_TRUST false Trust X-Forwarded headers from proxy IP

      Note on BACKUP_KEEP rotation: The retention policy only applies to backups created by the current version of the script. Backups made by older script versions may use a different naming convention and will not be counted or pruned by the rotation logic. If you are upgrading from an older version, manually review your backup directory (BACKUP_DIR in config, default /var/lib/xo-backups) and remove any legacy-named archives you no longer need.

      Default Credentials

      After installation, access the web interface at https://your-server-ip.

      • Username: admin@admin.net
      • Password: admin

      Change the default password immediately after first login.

      Supported Operating Systems

      • Debian 10/11/12/13
      • Ubuntu (all supported versions)
      • RHEL / CentOS / AlmaLinux / Rocky
      • Fedora

      Running Task Detection (Update Safety)

      Before applying an update, the script queries the Xen Orchestra REST API for active tasks (e.g. running backups, VM exports). If any are found, the update is aborted to prevent data loss or corruption.

      Authentication

      Only admin-level XO accounts can access the REST API. Authentication is resolved in priority order:

      Priority Method Source
      1 Auth token XO_TASK_CHECK_TOKEN in xo-config.cfg
      2 Credentials XO_TASK_CHECK_USER / XO_TASK_CHECK_PASS in xo-config.cfg
      3 Interactive Prompted at runtime (press Enter to skip)

      Recommended: Dedicated XO Account

      It is recommended to create a dedicated XO web UI account solely for the task check (e.g. task-checker@local.net). This account:

      • Must have Admin privileges (required by the REST API)
      • Exists only within the XO web interface — no shell access, SSH keys, or OS-level permissions are needed
      • Provides a clear audit trail separate from personal accounts
      • Prevents shared credentials from being used for unrelated actions

      You are free to use any admin account you choose, but a dedicated account is the safest approach.

      Using an Auth Token (Recommended)

      Tokens are more secure than storing a password — they can be revoked independently and expire after 30 days by default.

      1. Log into the XO web UI with the dedicated account
      2. Generate a token:
        curl -X POST -u 'task-checker@local.net:yourpassword' \
          https://localhost/rest/v0/users/me/authentication_tokens -k
        
      3. Copy the id field from the response
      4. Add to xo-config.cfg:
        XO_TASK_CHECK_TOKEN=UlTBEnFeL12XocK-7Qx-DKvOYbPn0eG7Z2oMvOniNjg
        

      Using Credentials

      Alternatively, store the account credentials directly:

      XO_TASK_CHECK_USER=task-checker@local.net
      XO_TASK_CHECK_PASS=changeme
      

      If neither token nor credentials are configured, the script will prompt interactively during each update.

      Environment Variables

      Variable Description
      XO_DEBUG=1 Enable debug mode (set -x)
      XO_NO_SELF_UPDATE=1 Skip automatic script self-update

      Troubleshooting

      Check service logs:

      sudo journalctl -u xo-server -n 50
      

      If the build is broken, rebuild (takes a backup first):

      ./install-xen-orchestra.sh --rebuild
      

      Build fails with OOM / out-of-memory error

      The Yarn build is memory-intensive. On hosts with less than 2 GB RAM the Node.js process can be killed by the kernel OOM killer mid-build, leaving an incomplete install.

      Add or increase swap to give the build room:

      sudo fallocate -l 2G /swapfile
      sudo chmod 600 /swapfile
      sudo mkswap /swapfile
      sudo swapon /swapfile
      

      Re-run the install or --rebuild after the swap is active. To make it permanent across reboots, add /swapfile none swap sw 0 0 to /etc/fstab.

      NodeSource GPG key failure (air-gapped / offline hosts)

      On hosts without internet access (or with strict egress firewall rules) the NodeSource repository setup script fails because it cannot reach keyserver.ubuntu.com or deb.nodesource.com.

      Option A — pre-download and import the key manually, then copy the .deb/.rpm packages to the host.

      Option B — set NODE_VERSION to a specific patch version (e.g. 24.15.0) in xo-config.cfg. The script will then download a pre-built binary directly from nodejs.org instead of using the NodeSource package repository.

      git reports "dubious ownership" and exits

      Recent versions of Git refuse to operate on a repository owned by a different user than the one running the command. This can happen when sudo is used inconsistently or when the install directory was created by root but the script is run as a normal user.

      Fix it by resetting ownership to match your SERVICE_USER:

      sudo chown -R xo-service:xo-service /opt/xen-orchestra
      

      Replace xo-service with the value of SERVICE_USER in xo-config.cfg. Re-running the script afterwards will resolve the rest.

      RedHat / Rocky / AlmaLinux: SELinux denials or systemd capability errors

      On SELinux-enforcing systems the xo-server service may fail to bind ports or access network resources. Check for AVC denials:

      sudo ausearch -m avc -ts recent | grep xo-server
      

      If denials are present, generate and apply a local policy module:

      sudo ausearch -m avc -ts recent | audit2allow -M xo-server-local
      sudo semodule -i xo-server-local.pp
      

      Alternatively, set the service to permissive mode while investigating:

      sudo semanage permissive -a xo_server_t
      

      audit2allow and semanage are provided by the policycoreutils-python-utils package on RHEL/Rocky/Alma.

      License

      This project is licensed under the MIT License. Xen Orchestra itself is licensed under AGPL-3.0.

      Credits

      • Xen Orchestra by Vates
      • Installation Documentation
      posted in Xen Orchestra
      acebmxerA
      acebmxer
    • RE: Install XO from sources.

      install_xen_orchestra v0.5.0 — build your own cloud-init VM templates

      As I am sure most of you know that XOA Hub is not accessible from Xen Orchestra from sources.

      So v0.5.0 of my install script adds a VM Template Library — a new
      --build-templates flag (and menu entry) that builds the equivalent on your own pool, from each distribution's own published cloud image.

      ./install-xen-orchestra.sh --build-templates
      

      It runs from your workstation over SSH against the pool master, like --deploy does. Nothing is installed locally and your XO install isn't touched.

      What you get

      A sealed template that shows up next other vm templates you have, with:

      • cloud-init — supply an SSH key or a full cloud-config at VM creation.
      • XCP-ng guest tools, installed from guest-tools.iso on the pool. Without these XO never reports the VM's IP. On Debian 13 there's no
        xe-guest-utilities package, and a failed package install doesn't stop cloud-init, so an apt-first approach silently gives you a template that looks fine and is useless. The ISO is what the XCP-ng docs prescribe anyway.
      • A scrubbed identity — machine-id, SSH host keys, cloud-init state and logs are all wiped before sealing, so clones don't collide on DHCP leases or share an SSH fingerprint.
      • growroot, so the disk size you ask for at creation is actually filled.
      • One template for both BIOS and UEFI — the Debian generic images carry an ESP and a BIOS boot partition, so you just flip "Boot firmware" in XO's advanced settings. The build itself isn't prompted for storage or network —
        it uses your pool's default SR (or the emptiest one, if you haven't set a default) and the management network. Both are just build-time choices; you pick whatever you want when you actually create a VM from the template.

      Images are pulled from the distribution's own mirror (nothing redistributed), downloaded onto the pool master so the ~3 GB never crosses your workstation's link, and verified against the origin's published SHA512SUMS at build time
      —so new upstream releases get picked up without me editing anything.

      Allow roughly five to ten minutes per template; it has to boot the VM once to
      install the guest agent and run the scrub.

      Distros

      Debian 13 (Trixie) is the only one for now. That's a starting point, not the limit — the catalogue is a table with one row per distro, and adding another is a row in that table, not a change to the build.

      So: comment here if there's a specific distro you'd want to see sooner rather than later and I'll prioritise accordingly.

      Repo: https://github.com/acebmxer/install_xen_orchestra
      Docs for this feature: https://github.com/acebmxer/install_xen_orchestra/blob/main/docs/templates.md

      posted in Xen Orchestra
      acebmxerA
      acebmxer
    • RE: XOA 6.8 Pool Metadata backup

      @flakpyro The patch was pushed though to XO from Sources. Hasnt hit XOA yet i dont beleive.

      https://github.com/vatesfr/xen-orchestra/commit/003cc6f9cc7de6bff9eaee9fa0bc14a1f7b64cc0

      I am not seeing this error after patch applied to XOA...

      fix(proxy): fetch failed  (#10346)
      * fix(backups): fetch failed
      
      disable compresion between xoa on proxy on xoa side
      
      * fix(xo-proxy): disable compression on the proxy
      
      it was disable with hrp, replaced by #10038 since it was never
      sending accept-encoding header
      
      compression can be put back later on a route by route basis after
      careful checks ( for example : file restore, backup listing )
      
      posted in Backup
      acebmxerA
      acebmxer
    • RE: Install XO from sources.

      v0.4.1 and v0.4.2 are out.

      v0.4.1 — mostly credential encryption (ENCRYPT_REDIS_CREDENTIALS)

      • The preflight check now catches a Xen guest that's missing xenstore-read / xenstore-write. Before, that guest passed the systemd-detect-virt check and then failed later at xo-server startup, because there was nowhere to store the XenStore half of the key. It now names the missing tools and the package that provides them.
      • --backup now warns that it contains neither half of the encryption key, and points at the passphrase-protected XO config export as the actual recovery artifact.
      • --uninstall warns before deleting this host's on-disk key half — doing so while leaving Redis in place turns the stored records into unreadable ciphertext.
      • The docs (README, sample config, generated config.toml comments) now explain why the XAPI credential in Redis is stored reversibly instead of hashed: it's replayed on every connect and auto-reconnect, so it can't be a hash. They also spell out the recovery caveats — the key is split between XenStore and /var/lib/xo-server/data, and losing either half while encryption is on makes the records permanently undecryptable.
      • Also flagged in the sample config: pointing REDIS_URI at an off-host Redis sends the pool credentials over the network in cleartext.

      v0.4.2 — docs and packaging only, no behaviour change:

      • The README had grown past 700 lines, with the --deploy walkthrough alone taking up a third of it. The large reference sections moved out to docs/deployment.md, docs/configuration.md, docs/authentication.md and docs/troubleshooting.md; the README is back to ~330 lines with a table pointing at them. Nothing was removed.
      • Expanded the badge row — release tag, last commit, open issues, unit-test count, number of distros the CI container matrix covers, and ShellCheck status.

      Where the project's got to

      I started this in February as a script to save myself doing the from-source install by hand every time I rebuilt my homelab. Seven months and twelve tagged releases later it's grown into something a fair bit bigger:

      • --install does the from-source build on whatever distro you run it on — the Debian/Ubuntu, RHEL/Alma/Rocky/CentOS and Fedora families, eight distributions in all, each one smoke-tested in CI alongside 118 unit tests.
      • --deploy (added in v0.3.0) starts a step earlier: point it at a XCP-ng / XenServer pool and it builds the VM, pulls a Debian cloud image straight onto the pool, seeds it with cloud-init and runs the install inside it. It's there for people who have a pool but no Linux VM to put XO on.
      • --proxy deploys an XO Proxy VM the same way — that one came straight out of requests in this thread.
      • Around that: a config file so nothing needs editing in the script itself, --update / --rebuild with a local build cache, --backup / --restore / --uninstall, non-root operation with encrypted Redis credentials, firewall handling, and a lot of --deploy security work in v0.4.0 — image checksums, pool host-key pinning, the deploy SSH key destroyed at the end of the run, a required admin password, passwordless sudo revoked once the install finishes.

      Since the v0.3.0 / v0.4.0 post a couple of weeks ago the repo has had 263 clones from 49 unique cloners.

      Thanks

      To everyone in this thread who's installed it, tested it and come back with feedback — genuinely, thank you. The proxy support, the credential-encryption questions that turned into proper docs, the config-file suggestions, the distro edge cases on systems I don't run myself: several of the releases above have something in them that started as a post here. Keep it coming.

      Repo: https://github.com/acebmxer/install_xen_orchestra
      Changelog: https://github.com/acebmxer/install_xen_orchestra/blob/main/CHANGELOG.md

      posted in Xen Orchestra
      acebmxerA
      acebmxer
    • RE: 🛰️ XO 6: dedicated thread for all your feedback!

      @pdonias said:

      Hello everyone! We need you!

      We're currently designing the XO 6 UI for non-admin users, and some choices are genuinely hard to make. If you'd like to give us your opinion, here's a 30-second survey with 2 questions we couldn't settle ourselves: https://survey.vates.tech/s/cms4nrqb4005wrw01021ru6dy

      Thanks! 🙂

      Thank you with presenting us with a choice. I have made my comments and offered a 3rd option.

      posted in Xen Orchestra
      acebmxerA
      acebmxer
    • RE: XOA 6.8 causes backup / replication failure

      To sum up... It appears the patch has worked for me but has shed some light on miss configuration with the network design at this remote location, that I will need to take a real closer look at.

      @florent thank you very much for your continue assistance with my issues.

      posted in Backup
      acebmxerA
      acebmxer
    • RE: XOA 6.8 causes backup / replication failure

      @florent

      Backups ran after patch applied...

      1 pool had zero issues on backup 100% complete...
      Other pool while it complete did have some errors...

      Started a second backup on same pool and giving same results.

      {
        "data": {
          "mode": "delta",
          "reportWhen": "always",
          "backupReportTpl": "compactMjml",
          "hideSuccessfulItems": true
        },
        "id": "1788428437610",
        "jobId": "c0e31730-7d45-4f3a-8733-8cea444b127d",
        "jobName": "Salem - Delta Backups",
        "message": "backup",
        "proxyId": "7840039e-a3cb-41ed-acee-3690f89a1426",
        "scheduleId": "ce3c801c-4384-4726-bda1-f6bae788e2f4",
        "start": 1788428437610,
        "status": "success",
        "tasks": [
          {
            "id": "0mtlc477z-gdvpj68kva",
            "start": 1788428438927,
            "status": "success",
            "tasks": [
              {
                "id": "0mtlc478f-guqsurb38qa",
                "start": 1788428438943,
                "status": "success",
                "end": 1788428440120,
                "result": {
                  "merge": false,
                  "size": 0
                },
                "message": "clean-vm"
              },
              {
                "id": "0mtlc48cx-c1y79k93vl",
                "start": 1788428440401,
                "status": "success",
                "end": 1788428442225,
                "result": "67677eec-494b-6ab6-0447-ac4dba8932a1",
                "message": "snapshot"
              },
              {
                "id": "0mtlc49rm-ou0nslm2c7l",
                "start": 1788428442227,
                "status": "success",
                "tasks": [
                  {
                    "id": "0mtlc724s-62ae1bzdupa",
                    "start": 1788428572300,
                    "status": "success",
                    "end": 1788428932605,
                    "result": {
                      "size": 20385362944
                    },
                    "message": "transfer",
                    "data": {
                      "progress": 99
                    }
                  },
                  {
                    "id": "0mtlceupa-f476k7iq2u4",
                    "start": 1788428935918,
                    "status": "success",
                    "tasks": [
                      {
                        "id": "0mtlceutz-yztgqk0sv0c",
                        "start": 1788428936087,
                        "status": "success",
                        "end": 1788429285986,
                        "result": {
                          "size": 20380123136,
                          "id": "5fb5f6f1-709b-b149-4aa6-31514ef2c7f2"
                        },
                        "message": "transfer"
                      },
                      {
                        "id": "0mtlcmctg-8z00dmmisds",
                        "start": 1788429285988,
                        "status": "success",
                        "end": 1788429291289,
                        "message": "vmstart"
                      }
                    ],
                    "end": 1788429296722,
                    "message": "health check"
                  },
                  {
                    "id": "0mtlcml5b-ywe7qa02f7q",
                    "start": 1788429296783,
                    "status": "success",
                    "end": 1788429300723,
                    "result": {
                      "merge": false,
                      "size": 0
                    },
                    "message": "clean-vm"
                  }
                ],
                "end": 1788429300727,
                "message": "export",
                "data": {
                  "id": "19270323-baaa-4a7b-bf1f-e152ae44f263",
                  "isFull": false,
                  "type": "remote"
                }
              }
            ],
            "warnings": [
              {
                "message": "can't compute delta OpaqueRef:afcf0af9-64c9-845d-207c-789c9c5de78f from OpaqueRef:13ce290f-2194-280e-72c5-9e16271505df, fall back to a full"
              },
              {
                "message": "can't connect through NBD, fall back to stream export"
              },
              {
                "message": "Backup fell back to a full"
              }
            ],
            "infos": [
              {
                "message": "will delete snapshot data"
              },
              {
                "data": {
                  "vdiRef": "OpaqueRef:afcf0af9-64c9-845d-207c-789c9c5de78f"
                },
                "message": "Snapshot data has been deleted"
              }
            ],
            "end": 1788429300728,
            "message": "backup VM",
            "data": {
              "id": "0618e9fe-854e-7f01-1f22-6fb1667806d4",
              "type": "VM",
              "name_label": "Salem XO-CE",
              "progress": 0
            }
          },
          {
            "id": "0mtlc4783-s6m3pnf32pl",
            "start": 1788428438931,
            "status": "success",
            "tasks": [
              {
                "id": "0mtlc478g-epd65nptnrn",
                "start": 1788428438944,
                "status": "success",
                "end": 1788428439927,
                "result": {
                  "merge": false,
                  "size": 0
                },
                "message": "clean-vm"
              },
              {
                "id": "0mtlc486t-mq755lvlxi",
                "start": 1788428440181,
                "status": "success",
                "end": 1788428443614,
                "result": "d52e8853-1102-8bcd-b588-adbe5b411a6b",
                "message": "snapshot"
              },
              {
                "id": "0mtlc4au7-q4va6ntph6c",
                "start": 1788428443615,
                "status": "success",
                "tasks": [
                  {
                    "id": "0mtlc9pax-xyje1fo25lf",
                    "start": 1788428695641,
                    "status": "success",
                    "end": 1788429704445,
                    "result": {
                      "size": 44032329216
                    },
                    "message": "transfer",
                    "data": {
                      "progress": 100
                    }
                  },
                  {
                    "id": "0mtlcvdy1-pxmgi1rx7tk",
                    "start": 1788429707353,
                    "status": "success",
                    "tasks": [
                      {
                        "id": "0mtlcvdzc-uodtj65grrn",
                        "start": 1788429707400,
                        "status": "success",
                        "end": 1788430481457,
                        "result": {
                          "size": 44021317632,
                          "id": "ed4d4ce7-2685-a35a-b1e4-c54a1385364e"
                        },
                        "message": "transfer"
                      },
                      {
                        "id": "0mtldbz96-dsndwbb93hv",
                        "start": 1788430481466,
                        "status": "success",
                        "end": 1788430486658,
                        "message": "vmstart"
                      }
                    ],
                    "end": 1788430492516,
                    "message": "health check"
                  },
                  {
                    "id": "0mtldc7vt-oopf5wcg74e",
                    "start": 1788430492649,
                    "status": "success",
                    "end": 1788430501065,
                    "result": {
                      "merge": false,
                      "size": 0
                    },
                    "message": "clean-vm"
                  }
                ],
                "end": 1788430501070,
                "message": "export",
                "data": {
                  "id": "19270323-baaa-4a7b-bf1f-e152ae44f263",
                  "isFull": false,
                  "type": "remote"
                }
              }
            ],
            "warnings": [
              {
                "message": "can't compute delta OpaqueRef:82b55a23-b13e-df37-c9f7-11373a42c40b from OpaqueRef:9824e8f1-0199-885c-e69a-d9275cd62d2a, fall back to a full"
              },
              {
                "message": "can't connect through NBD, fall back to stream export"
              },
              {
                "message": "Backup fell back to a full"
              }
            ],
            "infos": [
              {
                "message": "will delete snapshot data"
              },
              {
                "data": {
                  "vdiRef": "OpaqueRef:82b55a23-b13e-df37-c9f7-11373a42c40b"
                },
                "message": "Snapshot data has been deleted"
              }
            ],
            "end": 1788430501071,
            "message": "backup VM",
            "data": {
              "id": "64476a1a-20f5-32a4-6352-47916b2162d8",
              "type": "VM",
              "name_label": "Salem UnifiOS",
              "progress": 0
            }
          },
          {
            "id": "0mtlcmo92-ezud8mmu26",
            "start": 1788429300806,
            "status": "success",
            "tasks": [
              {
                "id": "0mtlcmoaf-ah3ohsdoy7r",
                "start": 1788429300855,
                "status": "success",
                "end": 1788429304315,
                "result": {
                  "merge": false,
                  "size": 0
                },
                "message": "clean-vm"
              },
              {
                "id": "0mtlcmrdk-xm266uwj1ni",
                "start": 1788429304856,
                "status": "success",
                "end": 1788429307794,
                "result": "dd0d0918-efdd-1a1d-ce94-85afbf0fd25c",
                "message": "snapshot"
              },
              {
                "id": "0mtlcmtn7-clidkdhy2ht",
                "start": 1788429307795,
                "status": "success",
                "tasks": [
                  {
                    "id": "0mtlcs7g8-3k59s9tshcf",
                    "start": 1788429558968,
                    "status": "success",
                    "end": 1788430829213,
                    "result": {
                      "size": 43868711424
                    },
                    "message": "transfer",
                    "data": {
                      "progress": 100
                    }
                  },
                  {
                    "id": "0mtldjhbz-rfnh54dr3y",
                    "start": 1788430831487,
                    "status": "success",
                    "tasks": [
                      {
                        "id": "0mtldjhd9-g6rihy05ec7",
                        "start": 1788430831533,
                        "status": "success",
                        "end": 1788431285549,
                        "result": {
                          "size": 43857739776,
                          "id": "e3215b6b-9b5a-0d49-3392-491cc39c19e4"
                        },
                        "message": "transfer"
                      },
                      {
                        "id": "0mtldt7ox-r81abwrax4",
                        "start": 1788431285553,
                        "status": "success",
                        "end": 1788431290565,
                        "message": "vmstart"
                      }
                    ],
                    "end": 1788431296314,
                    "message": "health check"
                  },
                  {
                    "id": "0mtldtg0h-8kvnbox5dg3",
                    "start": 1788431296337,
                    "status": "success",
                    "end": 1788431297610,
                    "result": {
                      "merge": false,
                      "size": 0
                    },
                    "message": "clean-vm"
                  }
                ],
                "end": 1788431297611,
                "message": "export",
                "data": {
                  "id": "19270323-baaa-4a7b-bf1f-e152ae44f263",
                  "isFull": false,
                  "type": "remote"
                }
              }
            ],
            "warnings": [
              {
                "message": "can't compute delta OpaqueRef:4b3d9930-d795-03f8-c887-f8b7d2a95524 from OpaqueRef:894ead1a-dae6-f156-d8c7-c7f5ba2200ef, fall back to a full"
              },
              {
                "message": "can't connect through NBD, fall back to stream export"
              },
              {
                "message": "Backup fell back to a full"
              }
            ],
            "infos": [
              {
                "message": "will delete snapshot data"
              },
              {
                "data": {
                  "vdiRef": "OpaqueRef:4b3d9930-d795-03f8-c887-f8b7d2a95524"
                },
                "message": "Snapshot data has been deleted"
              }
            ],
            "end": 1788431297611,
            "message": "backup VM",
            "data": {
              "id": "ddf296c8-20a0-6aa9-0d74-ebc029d0d1b3",
              "type": "VM",
              "name_label": "Salem UnifiOS",
              "progress": 0
            }
          }
        ],
        "end": 1788431297621,
        "infos": [
          {
            "data": {
              "vms": [
                "0618e9fe-854e-7f01-1f22-6fb1667806d4",
                "64476a1a-20f5-32a4-6352-47916b2162d8",
                "ddf296c8-20a0-6aa9-0d74-ebc029d0d1b3"
              ]
            },
            "message": "vms"
          }
        ]
      }
      
      posted in Backup
      acebmxerA
      acebmxer
    • RE: XOA 6.8 causes backup / replication failure

      @florent I sent pm with support tunnel. Are you able to apply patch or will patch be pushed live soon?

      posted in Backup
      acebmxerA
      acebmxer
    • RE: XOA 6.8 causes backup / replication failure

      @florent Yes you may deploy a patch thought the support tunnel.

      posted in Backup
      acebmxerA
      acebmxer
    • RE: XOA 6.8 causes backup / replication failure

      @pierrebrunet

      v6 dahsboard is now connected and working.

      Both Proxies are connected and vms are visible from the remote pools...

      Backup job still fails. same error.

      How and why does it have to many conections? To where XOA? to the Proxy? to the Backup remote?

      I did recently have two seperate issues each different at both remote sites recenlty but the inital backup error seemed similar to the OP. And all backups worked until recent updates.

      Edit -

      This is soemthing new....

      THis is still an active tranfer when the job reported failed....
      Reran backup again. It does appear to be doing the backup but it stil fails after creating snapshots or around that point. Once the job fails the backup is still happening and health checks happening.

      Screenshot 2026-09-02 100207.png

      posted in Backup
      acebmxerA
      acebmxer
    • RE: XOA 6.8 causes backup / replication failure

      @pierrebrunet

      My post this morning after that update.

      I see the same error in task view prior to the update but under the scheduled task as it was the actual backup job not me tring.

      API call: schedule.runSequence
      

      I am starting a fresh backup instead of retrying the last failed backup.

      Edit - From fresh backup....

      Also i have support ticket up about v6 dash board not loading and support tunnel open if you want to look. Ticket#7763637

      {
        "data": {
          "mode": "delta",
          "reportWhen": "always",
          "backupReportTpl": "mjml",
          "hideSuccessfulItems": true
        },
        "id": "1788347692784",
        "jobId": "bb0adfc7-93b9-45c9-a90f-7aa327f95a05",
        "jobName": "Tilton - Delta Backups",
        "message": "backup",
        "proxyId": "9d22fb88-8bdd-44d3-a3a3-9ff5401f95df",
        "scheduleId": "249a8339-da2b-4031-b85d-dc3d9526efa5",
        "start": 1788347692784,
        "status": "failure",
        "end": 1788347752961,
        "result": {
          "message": "fetch failed",
          "name": "TypeError",
          "stack": "TypeError: fetch failed\n    at node:internal/deps/undici/undici:14976:13\n    at AsyncResource.runInAsyncScope (node:async_hooks:214:14)\n    at cb (/usr/local/lib/node_modules/xo-server/node_modules/bluebird/js/release/util.js:355:42)\n    at tryCatcher (/usr/local/lib/node_modules/xo-server/node_modules/bluebird/js/release/util.js:16:23)\n    at Promise._settlePromiseFromHandler (/usr/local/lib/node_modules/xo-server/node_modules/bluebird/js/release/promise.js:547:31)\n    at Promise._settlePromise (/usr/local/lib/node_modules/xo-server/node_modules/bluebird/js/release/promise.js:604:18)\n    at Promise._settlePromise0 (/usr/local/lib/node_modules/xo-server/node_modules/bluebird/js/release/promise.js:649:10)\n    at Promise._settlePromises (/usr/local/lib/node_modules/xo-server/node_modules/bluebird/js/release/promise.js:725:18)\n    at _drainQueueStep (/usr/local/lib/node_modules/xo-server/node_modules/bluebird/js/release/async.js:93:12)\n    at _drainQueue (/usr/local/lib/node_modules/xo-server/node_modules/bluebird/js/release/async.js:86:9)\n    at Async._drainQueues (/usr/local/lib/node_modules/xo-server/node_modules/bluebird/js/release/async.js:102:5)\n    at Immediate.Async.drainQueues (/usr/local/lib/node_modules/xo-server/node_modules/bluebird/js/release/async.js:15:14)\n    at processImmediate (node:internal/timers:484:21)\n    at process.callbackTrampoline (node:internal/async_hooks:130:17)"
        }
      }
      
      posted in Backup
      acebmxerA
      acebmxer