Subcategories

  • VMs, hosts, pools, networks and all other usual management tasks.

    472 Topics
    4k Posts
    johnnezeroJ
    UPDATE: Tag-Based-Automation Plugin WHAT: The xo-tag-automation plugn is a native xo-server plugin that enforces VM performance tiers, manages group permissions, and synchronizes VM metadata -- all driven by VM tags and NFS-hosted CSV files (see below for more details). FEATURES PERFORMANCE SYNC Automatically applies CPU weights and IO priorities (sched-pri) based on VM performance tier tags: 0-core -- CPU weight: 2048 IO priority: 7 1-high -- CPU weight: 1024 IO priority: 7 2-normal -- CPU weight: 512 IO priority: 5 3-low -- CPU weight: 256 IO priority: 2 All tier weights and IO priorities are fully configurable in the plugin UI. An optional pool-specific tag suffix (e.g. -1=POOL1, -2=POOL2, etc.) allows you to manage multiple pools from a single XO instance without tag collisions. PERMISSION SYNC VM tags ending in -Admin, -Operator, or -Viewer (e.g. "Dept1-Operator", "Dept2-Admin", etc.) automatically trigger appropriate XO Group creation and ACL assignments for the designated VM. CSV PERMISSION MANAGEMENT FILES Two CSV files on your NFS share drive the workflow: current-vms.csv A live export of your entire VM inventory. Contains UUID, Name, CurrentTags, NewTags, CurrentNotes, and NewNotes columns. Edit the NewTags and NewNotes columns and run the plugin (e.g. push the [Test plugin] button) to apply changes in bulk. The CSV auto-refreshes after each run. A staleness warning fires if the CSV has not been updated within a configurable number of days. preload-vms.csv Pre-stage tag and notes configurations for VMs that do not exist yet -- before they are migrated or created. The moment a VM matching a preload entry appears in XO, the plugin applies (on next scheduled interval) its tags and notes automatically and removes the entry from the preload file. PERMISSION AUTOPILOT Designed for active migration and onboarding projects. Automatically applies permission settings on scheduled interval, based on preload-vms.csv contents. Note: Should be disabled when not actively involved in migration projects. DRY-RUN / EXPORT-CSV MODE When Dry-Run is ON (the default), the plugin previews all changes in the XO logs without applying any changes, and simultaneously exports a fresh copy of all VM metadata to current-vms.csv with blank NewTags and NewNotes columns ready to fill in. Turn Dry-Run OFF to apply changes for real. RUN NOW (e.g. The [Test plugin] button) Trigger a full enforcement cycle instantly from the XO plugin UI without waiting for the next scheduled run. NFS LOGGING All activity is written to structured log files on your NFS share: xo-tag-automation.log -- full run log (auto-rotates at 2MB) xo-tag-automation.log.1 -- previous log backup xo-tag-automation-summary.log -- run summary entries only daily-summary.log -- nightly VM count and new VM report Logs are also available via xo-cli API methods (see below). LEGACY MIGRATION If you have an existing vm_metadata.csv from an older version, the plugin automatically renames it to current-vms.csv on first run. No manual migration needed. SECURITY -- PLEASE READ CAREFULLY This plugin automates infrastructure changes. Security is not optional. Please take both of the following seriously before enabling Permission Sync or Autopilot. -- REST API SERVICE ACCOUNT -- The plugin uses the XO JSON-RPC API internally. Use a dedicated service account -- never your personal admin credentials. Recommended setup (generic -- adapt to your environment): Create a dedicated XO user account for the service (e.g. a non-admin account with only the minimal access permissions required) Generate a scoped API token via xo-cli: xo-cli --register xo-cli token.create Store the token securely -- treat it like a password! Refer to the official Vates REST API documentation for full token management guidance: https://xen-orchestra.com/docs/restapi.html -- NFS SHARE SECURITY -- The NFS share hosts your CSV files and logs. Anyone with write access to the share can modify VM tags and permissions. STRONGLY RECOMMENDED Run the NFS share from a dedicated VM -- not a general-purpose NFS server. Restrict NFS exports to the XOA IP address only: /srv/nfs/share<XOAIP>/32(rw,sync,no_subtree_check,no_root_squash) Do NOT expose the NFS share to the general network or to end-user access. Admins who need to edit CSV files can SCP them to/from the XOA: EXAMPLE: Download CSV from XOA to your workstation scp <xoa-user>@<xoa-ip>:/path/to/current-vms.csv ./ Upload edited CSV back to XOA scp ./current-vms.csv <xoa-user>@<xoa-ip>:/path/to/current-vms.csv Use firewall rules to enforce NFS access at the network level in addition to the exports configuration Failure to secure the NFS share is a serious security risk. UPGRADING FROM THE STANDALONE SCRIPT If you installed the old standalone set-performance.sh script, you can remove it before enabling the plugin as follows: Remove the script: sudo rm /usr/local/bin/set-performance.sh Remove the crontab entry: crontab -e (delete the line referencing set-performance.sh) Note: The plugin handles its own scheduling via the XO UI. No manual cron configuration is required. INSTALLATION Download the latest airgap release tarball from GitHub: https://github.com/johnezero/xo-tag-automation_plugin/releases SCP the tarball to your XOA: scp xo-tag-automation-airgap-vX.X.X.tar.gz <xoa-user>@<xoa-ip>:/tmp/ Create the plugin folder: sudo mkdir -p /usr/local/lib/node_modules/xo-server-tag-automation Extract directly into the plugin directory: sudo tar -xzvf /tmp/xo-tag-automation-airgap-vX.X.X.tar.gz -C /usr/local/lib/node_modules/xo-server-tag-automation/ --strip-components=1 Restart xo-server: sudo systemctl restart xo-server Verify registration: sudo journalctl -u xo-server -n 100 --no-pager | grep -A3 "tag-automation" You should see: [INFO] xo-tag-automation: Plugin factory called -- xo context: YES [INFO] xo-tag-automation: Plugin loaded -- waiting for core started. xo:plugin INFO successfully register tag-automation Enable and configure the plugin options in XO: Settings -> Plugins -> tag-automation -> Enable XO-CLI API METHODS The plugin exposes several API methods accessible via xo-cli: xo-cli xo-server-tag-automation.exportCsv Export current VM inventory to current-vms.csv xo-cli xo-server-tag-automation.downloadCsvApi Print CSV content to stdout xo-cli xo-server-tag-automation.uploadCsvApi content@./current-vms.csv Push an edited CSV back to the NFS share xo-cli xo-server-tag-automation.getLog lines=100 View the last N lines of the plugin log xo-cli xo-server-tag-automation.getDailySummary View the nightly VM count summary xo-cli xo-server-tag-automation.getFilePaths Show all configured file paths LINKS GitHub: https://github.com/johnezero/xo-tag-automation_plugin Vates REST API docs: https://xen-orchestra.com/docs/restapi.html STANDARD DISCLAIMER HERE This software is provided "AS-IS" without any express or implied warranty. While this plugin is being used in a production environment managing live VMs, you should always review the code and test it in a non-production environment before full deployment. Note: The plugin is designed to ONLY take action on VMs with specific tags assigned (e.g. untagged VMs are never modified). Use Dry-Run mode to preview all changes (via log file output) before applying them. That said, as always - your mileage may vary... [image: 1780884996846-johnezero-logo.jpg]
  • ACLs, Self-service, Cloud-init, Load balancing...

    104 Topics
    863 Posts
    laszlobortelL
    @florent Thanks for your reply! We have started to migrate thousands of VMs, so disk transfer speed is important for us.. We will also do our detailed tests soon with different threads setting and publish it here. I think threads=1 is a good and logical default, but not efficient. Others might complain if you set it to a higher value. Configuration option would be a real good solution.
  • All XO backup features: full and incremental, replication, mirrors...

    509 Topics
    5k Posts
    A
    @florent Ubuntu LVM file restore is working! (commit 38931) Now for another important issue I noticed with file restore (not directly LVM). Symbolic links don't show up. They should be restorable alone, but more importantly you need to be able to see and follow them for directories. For example. In Ubuntu, /bin is a link to /usr/bin. It is important to be able to click on /bin as a link to /usr/bin so files can be found in the backup. Another example is /vmlinuz that is a link to boot/vmlinuz-5.10.0-44-amd64. At worst the file restore should show a link (and it's destination), even if I can't restore the link. This is not just a LVM issue.
  • Everything related to Xen Orchestra's REST API

    85 Topics
    642 Posts
    1
    @poddingue Confirmed working, thank you so much for the heads-up, this made my day! Got it wired into the n8n flow and it's running perfectly. One gotcha for anyone else landing here, name_description gets rejected with a 422 "excess property", it has to be nameDescription. Working body: { "nameDescription": "nginx, app-1, app-2 | 2026-06-01" }
  • Terraform, Packer or any tool to do IaC

    50 Topics
    470 Posts
    CyrilleC
    Kubernetes CSI Driver for XO new release v0.3.0 Stable CSI Volume Identity: This decouples Kubernetes volume identity from backend storage lifecycle events (e.g. VDI migration between Storage Repositories) Topology-Aware Volume Provisioning: Dynamic provisioning now supports topology-aware pool selection. ️ Migration required from v0.2.0 to v0.3.0 Full release note: https://github.com/vatesfr/xenorchestra-csi-driver/releases/tag/v0.3.0
  • Authentication via Active Directory

    3
    0 Votes
    3 Posts
    2k Views
    B
    @deoccultist Sadly, none of this seemed to make any difference.
  • Can Network be selected for Backups?

    4
    1
    0 Votes
    4 Posts
    1k Views
    olivierlambertO
    See my answer in the other thread.
  • Support for XO in docker container

    21
    0 Votes
    21 Posts
    13k Views
    olivierlambertO
    We are investigating an elegant solution called RunX. Basically, it might be able to transparently any standard "container stack" (Docker and/or k8s). See https://www.youtube.com/watch?v=9m95hojMtsU There's some work to adapt that to XAPI, but it might be doable. This means XCP-ng could be "container" native while having very good level of isolation with very small VMs (only few MiB overhead).
  • Add rescan ISO SR from VM menu

    6
    1
    0 Votes
    6 Posts
    1k Views
    pdoniasP
    This is simple enough so we'll implement it in XO 5. Thanks for the feedback!
  • Wasabi just wont work...

    9
    0 Votes
    9 Posts
    2k Views
    K
    5.79.3 / 5.81.0 All of my backups work (now), and speeds range between 5 MB/s to 20 MB/s. Most of my VM's are smaller (zstd helps a lot), though the largest archive is about 80 GB. Also, all of my backups are sequential -- I seem to remember a previous note where somebody had problems with concurrent uploads. My XOCE VM runs with 12 GB, which was the number that "just works" according to some of my earlier problems (and I haven't bothered to chase down or fine tune further).
  • This topic is deleted!

    3
    0 Votes
    3 Posts
    4 Views
  • backblaze b2 / amazon s3 as remote in xoa

    59
    2
    0 Votes
    59 Posts
    31k Views
    S
  • Migrating VM fails with DUPLICATE_VM error

    12
    0 Votes
    12 Posts
    3k Views
    I
    @olivierlambert having exactly the same issue as wcom939 reported. What did you mean by "Can you try with xe command to see if you have the same error?" ? Migrate using CLI? there are too many options:)
  • Alpine Linux from HUB: xe-daemon: CollectOS error

    9
    0 Votes
    9 Posts
    2k Views
    olivierlambertO
    @fohdeesha let's work on another clean Alpine template.
  • Task aborted before completion

    3
    0 Votes
    3 Posts
    460 Views
    mauzillaM
    @danp thank you, but in our case the 2nd remote is a hypervisor? I dont know how we should run the backup first then copy the VHD files to the the 2nd hypervisor as continuous replication also creates a VM? I am sure that if I can limit the amount of VM's that is exported once (it's currently 2) then the backups for the large VM should complete. Is there a setting available for this?
  • Can't edit XO metatata backup config

    Solved
    12
    2
    0 Votes
    12 Posts
    2k Views
    olivierlambertO
    Thanks @badrAZ for the fix!
  • Is there a feature to auto start a VM?

    4
    0 Votes
    4 Posts
    821 Views
    mauzillaM
    Thanks both, agreed, in hindsight this should be configured on the VM itself as it could lead to unexpected issues (like maintenance and having VM's start by themselves) Thanks for the input
  • VM Memory Limits Question

    2
    0 Votes
    2 Posts
    3k Views
    olivierlambertO
    Here is a good explanation: https://docs.citrix.com/en-us/xencenter/7-1/dmc-about.html Static can only be set while the VM is offline. Dynamic can be changed in live. When you'll live migrate a VM, it will be decreased to the dynamic min. So take care to use a value that's higher than your VM operating system minimum RAM usage.
  • This topic is deleted!

    1
    0 Votes
    1 Posts
    3 Views
    No one has replied
  • Creating network bonds in XO

    5
    0 Votes
    5 Posts
    1k Views
    olivierlambertO
    You can change the bond name yes.
  • Offline host vm removal

    Solved
    6
    0 Votes
    6 Posts
    2k Views
    olivierlambertO
    I just did
  • Backups & CR of same VM - Storage impact

    Solved
    5
    0 Votes
    5 Posts
    724 Views
    olivierlambertO
    That's a way to do it. Use smart backup on tags. Eg a tag called "delta only" and a tag "delta+CR", so you'll be sure to assign the right tag to your VM
  • LICENSE_RESTRICTION (PCI_device_for_auto_update)

    Solved
    15
    0 Votes
    15 Posts
    4k Views
    olivierlambertO
    Ahh finally!! Enjoy saying goodbye to Citrix We'll be delighted to get you on board (as a user or even as a contributor via our pro support!)
  • New XOA Remote not Working from previous install

    4
    0 Votes
    4 Posts
    576 Views
    olivierlambertO
    No. The parent folder. XO will search for the folder xo-vm-backups directly edit: if your share was previously <NFS_IP>:/myshare, then you should use this very same one, and NOT <NFS_IP>:/myshare/xo-vm-backups
  • Stuck tasks within XO (rrd_updates)?

    32
    1
    0 Votes
    32 Posts
    15k Views
    olivierlambertO
    That's why I don't know, I don't have any answer without digging more and sadly I can't If there's other people around to assist, go ahead