1. Home
  2. Xen Orchestra

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 plugin 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). In general only apply one performance and/or permission action tag per VM. Currently XO only allows one ACL assignment per VM (e.g. assigning "Dept1-Operator", and" Dept3-Admin" to the same VM does not work). 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. Note: Under normal conditions these performance settings do not affect anything. It's only when system resources are under high-load that the tiering levels ensure important VMs get priority over non-critical workloads, etc. 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
Log in to post
Load new posts
  • S

    Is supermicro IPMI data display planned?

    32
    0 Votes
    32 Posts
    5k Views
    ForzaF
    HPE ProLiant DL325 Gen10 # xe host-call-plugin host-uuid=54f5f83a-a80f-40e9-82ed-30dd335b8d88 plugin=ipmitool.py fn=get_all_sensors [{"name": "UID", "value": "0x00", "event": "ok"}, {"name": "SysHealth_Stat", "value": "0x00", "event": "ok"}, {"name": "01-Inlet Ambient", "value": "29 degrees C", "event": "ok"}, {"name": "02-CPU 1", "value": "40 degrees C", "event": "ok"}, {"name": "03-P1 DIMM 1-8", "value": "34 degrees C", "event": "ok"}, {"name": "04-P1 DIMM 9-16", "value": "38 degrees C", "event": "ok"}, {"name": "05-HD Max", "value": "35 degrees C", "event": "ok"}, {"name": "06-Exp Bay Drive", "value": "disabled", "event": "ns"}, {"name": "07-VR P1", "value": "50 degrees C", "event": "ok"}, {"name": "08-VR P1 Mem 1", "value": "45 degrees C", "event": "ok"}, {"name": "09-VR P1 Mem 2", "value": "45 degrees C", "event": "ok"}, {"name": "10-Stor Batt", "value": "35 degrees C", "event": "ok"}, {"name": "11-BMC", "value": "64 degrees C", "event": "ok"}, {"name": "12-BMC Zone", "value": "39 degrees C", "event": "ok"}, {"name": "13-Battery Zone", "value": "36 degrees C", "event": "ok"}, {"name": "14-System Board", "value": "34 degrees C", "event": "ok"}, {"name": "15-PCI 1", "value": "disabled", "event": "ns"}, {"name": "16-PCI 2", "value": "disabled", "event": "ns"}, {"name": "17-PCI 3", "value": "disabled", "event": "ns"}, {"name": "18-PCI 1 Zone", "value": "33 degrees C", "event": "ok"}, {"name": "19-PCI 2 Zone", "value": "33 degrees C", "event": "ok"}, {"name": "20-PCI 3 Zone", "value": "disabled", "event": "ns"}, {"name": "22-HD Cntlr Zone", "value": "40 degrees C", "event": "ok"}, {"name": "23-LOM Card", "value": "disabled", "event": "ns"}, {"name": "24-I/O Zone 1", "value": "34 degrees C", "event": "ok"}, {"name": "25-I/O Zone 2", "value": "40 degrees C", "event": "ok"}, {"name": "27-P/S 1 Inlet", "value": "37 degrees C", "event": "ok"}, {"name": "28-P/S 2 Inlet", "value": "disabled", "event": "ns"}, {"name": "29-P/S 1", "value": "55 degrees C", "event": "ok"}, {"name": "30-P/S 2", "value": "disabled", "event": "ns"}, {"name": "31-P/S Zone", "value": "40 degrees C", "event": "ok"}, {"name": "33-AHCI HD Max", "value": "disabled", "event": "ns"}, {"name": "34-CPU 1 PkgTmp", "value": "52 degrees C", "event": "ok"}, {"name": "Fan 1", "value": "Not Readable", "event": "ns"}, {"name": "Fan 1 DutyCycle", "value": "disabled", "event": "ns"}, {"name": "Fan 1 Presence", "value": "0x00", "event": "ok"}, {"name": "Fan 2", "value": "0x00", "event": "ok"}, {"name": "Fan 2 DutyCycle", "value": "51.35 percent", "event": "ok"}, {"name": "Fan 2 Presence", "value": "0x00", "event": "ok"}, {"name": "Fan 3", "value": "0x00", "event": "ok"}, {"name": "Fan 3 DutyCycle", "value": "51.35 percent", "event": "ok"}, {"name": "Fan 3 Presence", "value": "0x00", "event": "ok"}, {"name": "Fan 4", "value": "0x00", "event": "ok"}, {"name": "Fan 4 DutyCycle", "value": "51.35 percent", "event": "ok"}, {"name": "Fan 4 Presence", "value": "0x00", "event": "ok"}, {"name": "Fan 5", "value": "0x00", "event": "ok"}, {"name": "Fan 5 DutyCycle", "value": "51.35 percent", "event": "ok"}, {"name": "Fan 5 Presence", "value": "0x00", "event": "ok"}, {"name": "Fan 6", "value": "0x00", "event": "ok"}, {"name": "Fan 6 DutyCycle", "value": "51.35 percent", "event": "ok"}, {"name": "Fan 6 Presence", "value": "0x00", "event": "ok"}, {"name": "Fan 7", "value": "Not Readable", "event": "ns"}, {"name": "Fan 7 DutyCycle", "value": "disabled", "event": "ns"}, {"name": "Fan 7 Presence", "value": "0x00", "event": "ok"}, {"name": "Power Supply 1", "value": "0x00", "event": "ok"}, {"name": "PS 1 Input", "value": "180 Watts", "event": "ok"}, {"name": "Power Supply 2", "value": "0x00", "event": "ok"}, {"name": "PS 2 Input", "value": "disabled", "event": "ns"}, {"name": "Power Meter", "value": "180 Watts", "event": "ok"}, {"name": "Fans", "value": "0x00", "event": "ok"}, {"name": "Megacell Status", "value": "0x00", "event": "ok"}, {"name": "Memory Status", "value": "0x00", "event": "ok"}, {"name": "Intrusion", "value": "Not Readable", "event": "ns"}, {"name": "CPU Utilization", "value": "0 unspecified", "event": "ok"}, {"name": "PS 1 Output", "value": "150 Watts", "event": "ok"}, {"name": "PS_Volt_Out_01", "value": "12 Volts", "event": "ok"}, {"name": "PS_Volt_In_01", "value": "231 Volts", "event": "ok"}, {"name": "PS_Curr_Out_01", "value": "12.50 Amps", "event": "ok"}, {"name": "PS_Curr_In_01", "value": "0.70 Amps", "event": "ok"}, {"name": "PS 2 Output", "value": "disabled", "event": "ns"}, {"name": "PS_Volt_Out_02", "value": "disabled", "event": "ns"}, {"name": "PS_Volt_In_02", "value": "disabled", "event": "ns"}, {"name": "PS_Curr_Out_02", "value": "disabled", "event": "ns"}, {"name": "PS_Curr_In_02", "value": "disabled", "event": "ns"}, {"name": "21.1-HD Controll", "value": "48 degrees C", "event": "ok"}, {"name": "21.2-HD Controll", "value": "58 degrees C", "event": "ok"}, {"name": "21.3-HD Controll", "value": "47 degrees C", "event": "ok"}, {"name": "NIC_Link_01P1", "value": "Not Readable", "event": "ns"}, {"name": "NIC_Link_01P2", "value": "Not Readable", "event": "ns"}, {"name": "Dr_Stat_1I1_B001", "value": "0x00", "event": "ok"}, {"name": "Dr_Stat_1I1_B002", "value": "0x00", "event": "ok"}, {"name": "Dr_Stat_1I1_B003", "value": "0x00", "event": "ok"}, {"name": "Dr_Stat_1I1_B004", "value": "0x00", "event": "ok"}, {"name": "Dr_Stat_2I1_B005", "value": "0x00", "event": "ok"}, {"name": "Dr_Stat_2I1_B006", "value": "0x00", "event": "ok"}, {"name": "Dr_Stat_2I1_B007", "value": "0x00", "event": "ok"}, {"name": "Dr_Stat_2I1_B008", "value": "0x00", "event": "ok"}, {"name": "CPU_Stat_C1", "value": "0x00", "event": "ok"}] Pretty printed: [ { "name": "UID", "value": "0x00", "event": "ok" }, { "name": "SysHealth_Stat", "value": "0x00", "event": "ok" }, { "name": "01-Inlet Ambient", "value": "29 degrees C", "event": "ok" }, { "name": "02-CPU 1", "value": "40 degrees C", "event": "ok" }, { "name": "03-P1 DIMM 1-8", "value": "34 degrees C", "event": "ok" }, { "name": "04-P1 DIMM 9-16", "value": "38 degrees C", "event": "ok" }, { "name": "05-HD Max", "value": "35 degrees C", "event": "ok" }, { "name": "06-Exp Bay Drive", "value": "disabled", "event": "ns" }, { "name": "07-VR P1", "value": "50 degrees C", "event": "ok" }, { "name": "08-VR P1 Mem 1", "value": "45 degrees C", "event": "ok" }, { "name": "09-VR P1 Mem 2", "value": "45 degrees C", "event": "ok" }, { "name": "10-Stor Batt", "value": "35 degrees C", "event": "ok" }, { "name": "11-BMC", "value": "64 degrees C", "event": "ok" }, { "name": "12-BMC Zone", "value": "39 degrees C", "event": "ok" }, { "name": "13-Battery Zone", "value": "36 degrees C", "event": "ok" }, { "name": "14-System Board", "value": "34 degrees C", "event": "ok" }, { "name": "15-PCI 1", "value": "disabled", "event": "ns" }, { "name": "16-PCI 2", "value": "disabled", "event": "ns" }, { "name": "17-PCI 3", "value": "disabled", "event": "ns" }, { "name": "18-PCI 1 Zone", "value": "33 degrees C", "event": "ok" }, { "name": "19-PCI 2 Zone", "value": "33 degrees C", "event": "ok" }, { "name": "20-PCI 3 Zone", "value": "disabled", "event": "ns" }, { "name": "22-HD Cntlr Zone", "value": "40 degrees C", "event": "ok" }, { "name": "23-LOM Card", "value": "disabled", "event": "ns" }, { "name": "24-I/O Zone 1", "value": "34 degrees C", "event": "ok" }, { "name": "25-I/O Zone 2", "value": "40 degrees C", "event": "ok" }, { "name": "27-P/S 1 Inlet", "value": "37 degrees C", "event": "ok" }, { "name": "28-P/S 2 Inlet", "value": "disabled", "event": "ns" }, { "name": "29-P/S 1", "value": "55 degrees C", "event": "ok" }, { "name": "30-P/S 2", "value": "disabled", "event": "ns" }, { "name": "31-P/S Zone", "value": "40 degrees C", "event": "ok" }, { "name": "33-AHCI HD Max", "value": "disabled", "event": "ns" }, { "name": "34-CPU 1 PkgTmp", "value": "52 degrees C", "event": "ok" }, { "name": "Fan 1", "value": "Not Readable", "event": "ns" }, { "name": "Fan 1 DutyCycle", "value": "disabled", "event": "ns" }, { "name": "Fan 1 Presence", "value": "0x00", "event": "ok" }, { "name": "Fan 2", "value": "0x00", "event": "ok" }, { "name": "Fan 2 DutyCycle", "value": "51.35 percent", "event": "ok" }, { "name": "Fan 2 Presence", "value": "0x00", "event": "ok" }, { "name": "Fan 3", "value": "0x00", "event": "ok" }, { "name": "Fan 3 DutyCycle", "value": "51.35 percent", "event": "ok" }, { "name": "Fan 3 Presence", "value": "0x00", "event": "ok" }, { "name": "Fan 4", "value": "0x00", "event": "ok" }, { "name": "Fan 4 DutyCycle", "value": "51.35 percent", "event": "ok" }, { "name": "Fan 4 Presence", "value": "0x00", "event": "ok" }, { "name": "Fan 5", "value": "0x00", "event": "ok" }, { "name": "Fan 5 DutyCycle", "value": "51.35 percent", "event": "ok" }, { "name": "Fan 5 Presence", "value": "0x00", "event": "ok" }, { "name": "Fan 6", "value": "0x00", "event": "ok" }, { "name": "Fan 6 DutyCycle", "value": "51.35 percent", "event": "ok" }, { "name": "Fan 6 Presence", "value": "0x00", "event": "ok" }, { "name": "Fan 7", "value": "Not Readable", "event": "ns" }, { "name": "Fan 7 DutyCycle", "value": "disabled", "event": "ns" }, { "name": "Fan 7 Presence", "value": "0x00", "event": "ok" }, { "name": "Power Supply 1", "value": "0x00", "event": "ok" }, { "name": "PS 1 Input", "value": "180 Watts", "event": "ok" }, { "name": "Power Supply 2", "value": "0x00", "event": "ok" }, { "name": "PS 2 Input", "value": "disabled", "event": "ns" }, { "name": "Power Meter", "value": "180 Watts", "event": "ok" }, { "name": "Fans", "value": "0x00", "event": "ok" }, { "name": "Megacell Status", "value": "0x00", "event": "ok" }, { "name": "Memory Status", "value": "0x00", "event": "ok" }, { "name": "Intrusion", "value": "Not Readable", "event": "ns" }, { "name": "CPU Utilization", "value": "0 unspecified", "event": "ok" }, { "name": "PS 1 Output", "value": "150 Watts", "event": "ok" }, { "name": "PS_Volt_Out_01", "value": "12 Volts", "event": "ok" }, { "name": "PS_Volt_In_01", "value": "231 Volts", "event": "ok" }, { "name": "PS_Curr_Out_01", "value": "12.50 Amps", "event": "ok" }, { "name": "PS_Curr_In_01", "value": "0.70 Amps", "event": "ok" }, { "name": "PS 2 Output", "value": "disabled", "event": "ns" }, { "name": "PS_Volt_Out_02", "value": "disabled", "event": "ns" }, { "name": "PS_Volt_In_02", "value": "disabled", "event": "ns" }, { "name": "PS_Curr_Out_02", "value": "disabled", "event": "ns" }, { "name": "PS_Curr_In_02", "value": "disabled", "event": "ns" }, { "name": "21.1-HD Controll", "value": "48 degrees C", "event": "ok" }, { "name": "21.2-HD Controll", "value": "58 degrees C", "event": "ok" }, { "name": "21.3-HD Controll", "value": "47 degrees C", "event": "ok" }, { "name": "NIC_Link_01P1", "value": "Not Readable", "event": "ns" }, { "name": "NIC_Link_01P2", "value": "Not Readable", "event": "ns" }, { "name": "Dr_Stat_1I1_B001", "value": "0x00", "event": "ok" }, { "name": "Dr_Stat_1I1_B002", "value": "0x00", "event": "ok" }, { "name": "Dr_Stat_1I1_B003", "value": "0x00", "event": "ok" }, { "name": "Dr_Stat_1I1_B004", "value": "0x00", "event": "ok" }, { "name": "Dr_Stat_2I1_B005", "value": "0x00", "event": "ok" }, { "name": "Dr_Stat_2I1_B006", "value": "0x00", "event": "ok" }, { "name": "Dr_Stat_2I1_B007", "value": "0x00", "event": "ok" }, { "name": "Dr_Stat_2I1_B008", "value": "0x00", "event": "ok" }, { "name": "CPU_Stat_C1", "value": "0x00", "event": "ok" } ] # ipmitool sensor UID | 0x0 | discrete | 0x0180| na | na | na | na | na | na SysHealth_Stat | 0x0 | discrete | 0x0180| na | na | na | na | na | na 01-Inlet Ambient | 28.000 | degrees C | ok | na | na | na | na | 42.000 | 47.000 02-CPU 1 | 40.000 | degrees C | ok | na | na | na | na | 75.000 | na 03-P1 DIMM 1-8 | 34.000 | degrees C | ok | na | na | na | na | 90.000 | na 04-P1 DIMM 9-16 | 38.000 | degrees C | ok | na | na | na | na | 90.000 | na 05-HD Max | 35.000 | degrees C | ok | na | na | na | na | 60.000 | na 06-Exp Bay Drive | na | | na | na | na | na | na | 60.000 | na 07-VR P1 | 50.000 | degrees C | ok | na | na | na | na | 115.000 | 120.000 08-VR P1 Mem 1 | 45.000 | degrees C | ok | na | na | na | na | 115.000 | 120.000 09-VR P1 Mem 2 | 45.000 | degrees C | ok | na | na | na | na | 115.000 | 120.000 10-Stor Batt | 35.000 | degrees C | ok | na | na | na | na | 60.000 | na 11-BMC | 64.000 | degrees C | ok | na | na | na | na | 110.000 | 115.000 12-BMC Zone | 39.000 | degrees C | ok | na | na | na | na | 75.000 | 80.000 13-Battery Zone | 36.000 | degrees C | ok | na | na | na | na | 75.000 | 80.000 14-System Board | 34.000 | degrees C | ok | na | na | na | na | 75.000 | 80.000 15-PCI 1 | na | | na | na | na | na | na | 100.000 | na 16-PCI 2 | na | | na | na | na | na | na | 100.000 | na 17-PCI 3 | na | | na | na | na | na | na | 100.000 | na 18-PCI 1 Zone | 33.000 | degrees C | ok | na | na | na | na | 70.000 | 75.000 19-PCI 2 Zone | 33.000 | degrees C | ok | na | na | na | na | 70.000 | 75.000 20-PCI 3 Zone | na | | na | na | na | na | na | 70.000 | 75.000 22-HD Cntlr Zone | 40.000 | degrees C | ok | na | na | na | na | 70.000 | 75.000 23-LOM Card | na | | na | na | na | na | na | 100.000 | na 24-I/O Zone 1 | 34.000 | degrees C | ok | na | na | na | na | 70.000 | 75.000 25-I/O Zone 2 | 40.000 | degrees C | ok | na | na | na | na | 70.000 | 75.000 27-P/S 1 Inlet | 37.000 | degrees C | ok | na | na | na | na | na | na 28-P/S 2 Inlet | na | | na | na | na | na | na | na | na 29-P/S 1 | 55.000 | degrees C | ok | na | na | na | na | na | na 30-P/S 2 | na | | na | na | na | na | na | na | na 31-P/S Zone | 40.000 | degrees C | ok | na | na | na | na | 75.000 | 80.000 33-AHCI HD Max | na | | na | na | na | na | na | 60.000 | na 34-CPU 1 PkgTmp | 53.000 | degrees C | ok | na | na | na | na | na | na Fan 1 | na | discrete | na | na | na | na | na | na | na Fan 1 DutyCycle | na | | na | na | na | na | na | na | na Fan 1 Presence | 0x0 | discrete | 0x0180| na | na | na | na | na | na Fan 2 | 0x0 | discrete | 0x0180| na | na | na | na | na | na Fan 2 DutyCycle | 51.352 | percent | ok | na | na | na | na | na | na Fan 2 Presence | 0x0 | discrete | 0x0280| na | na | na | na | na | na Fan 3 | 0x0 | discrete | 0x0180| na | na | na | na | na | na Fan 3 DutyCycle | 51.352 | percent | ok | na | na | na | na | na | na Fan 3 Presence | 0x0 | discrete | 0x0280| na | na | na | na | na | na Fan 4 | 0x0 | discrete | 0x0180| na | na | na | na | na | na Fan 4 DutyCycle | 51.352 | percent | ok | na | na | na | na | na | na Fan 4 Presence | 0x0 | discrete | 0x0280| na | na | na | na | na | na Fan 5 | 0x0 | discrete | 0x0180| na | na | na | na | na | na Fan 5 DutyCycle | 51.352 | percent | ok | na | na | na | na | na | na Fan 5 Presence | 0x0 | discrete | 0x0280| na | na | na | na | na | na Fan 6 | 0x0 | discrete | 0x0180| na | na | na | na | na | na Fan 6 DutyCycle | 51.352 | percent | ok | na | na | na | na | na | na Fan 6 Presence | 0x0 | discrete | 0x0280| na | na | na | na | na | na Fan 7 | na | discrete | na | na | na | na | na | na | na Fan 7 DutyCycle | na | | na | na | na | na | na | na | na Fan 7 Presence | 0x0 | discrete | 0x0180| na | na | na | na | na | na Power Supply 1 | 0x0 | discrete | 0x0180| na | na | na | na | na | na PS 1 Input | 160.000 | Watts | ok | na | na | na | na | na | na Power Supply 2 | 0x0 | discrete | 0x0080| na | na | na | na | na | na PS 2 Input | na | | na | na | na | na | na | na | na Power Meter | 160.000 | Watts | ok | na | na | na | na | na | na Fans | 0x0 | discrete | 0x0180| na | na | na | na | na | na Megacell Status | 0x0 | discrete | 0x0480| na | na | na | na | na | na Memory Status | 0x0 | discrete | 0x4080| na | na | na | na | na | na Intrusion | na | discrete | na | na | na | na | na | na | na CPU Utilization | 0.000 | unspecified | ok | na | na | na | na | na | na PS 1 Output | 150.000 | Watts | ok | na | na | na | na | na | na PS_Volt_Out_01 | 12.000 | Volts | ok | na | na | na | na | na | na PS_Volt_In_01 | 231.000 | Volts | ok | na | na | na | na | na | na PS_Curr_Out_01 | 12.500 | Amps | ok | na | na | na | na | na | na PS_Curr_In_01 | 0.700 | Amps | ok | na | na | na | na | na | na PS 2 Output | na | | na | na | na | na | na | na | na PS_Volt_Out_02 | na | | na | na | na | na | na | na | na PS_Volt_In_02 | na | | na | na | na | na | na | na | na PS_Curr_Out_02 | na | | na | na | na | na | na | na | na PS_Curr_In_02 | na | | na | na | na | na | na | na | na 21.1-HD Controll | 48.000 | degrees C | ok | na | na | na | 75.000 | 80.000 | 85.000 21.2-HD Controll | 58.000 | degrees C | ok | na | na | na | 98.000 | 103.000 | 108.000 21.3-HD Controll | 47.000 | degrees C | ok | na | na | na | 73.000 | 78.000 | 83.000 NIC_Link_01P1 | na | discrete | na | na | na | na | na | na | na NIC_Link_01P2 | na | discrete | na | na | na | na | na | na | na Dr_Stat_1I1_B001 | 0x0 | discrete | 0x0180| na | na | na | na | na | na Dr_Stat_1I1_B002 | 0x0 | discrete | 0x0180| na | na | na | na | na | na Dr_Stat_1I1_B003 | 0x0 | discrete | 0x0180| na | na | na | na | na | na Dr_Stat_1I1_B004 | 0x0 | discrete | 0x0180| na | na | na | na | na | na Dr_Stat_2I1_B005 | 0x0 | discrete | 0x0180| na | na | na | na | na | na Dr_Stat_2I1_B006 | 0x0 | discrete | 0x0180| na | na | na | na | na | na Dr_Stat_2I1_B007 | 0x0 | discrete | 0x0180| na | na | na | na | na | na Dr_Stat_2I1_B008 | 0x0 | discrete | 0x0180| na | na | na | na | na | na CPU_Stat_C1 | 0x0 | discrete | 0x8080| na | na | na | na | na | na
  • G

    Rename Networks on XO Hosts

    27
    0 Votes
    27 Posts
    9k Views
    G
    @olivierlambert Thanks. --rename isn't mentioned in the KB. If I don't see something in the next week or two, I might be able to test it in a lab and then propose an update via a github fork.
  • B

    Async.VBD.eject always gets stuck

    6
    0 Votes
    6 Posts
    678 Views
    B
    Additional info: uuid ( RO) : 127a8a7b-e277-27dc-802f-7f779676e18e name-label ( RO): Async.VBD.eject name-description ( RO): subtask_of ( RO): <not in database> subtasks ( RO): resident-on ( RO): 74e89397-c334-43f5-8322-5331c31ae368 status ( RO): pending progress ( RO): 0.000 type ( RO): <none/> result ( RO): created ( RO): 20251106T19:44:14Z finished ( RO): 19700101T00:00:00Z error_info ( RO): allowed_operations ( RO): current_operations ( RO): other-config (MRW): debug_info:cancel_points_seen: 1
  • planedropP

    What Are You All Doing for Disaster Recovery of XOA Itself?

    11
    0 Votes
    11 Posts
    2k Views
    W
    @MajorP93 Thank you i appreciate. im not in a hurry , take your time
  • M

    VM exports sometimes invalid / truncated

    3
    0 Votes
    3 Posts
    539 Views
    florentF
    @olivierlambert the tar stream is passed as is is there any warning in the relevant backup job log ?
  • planedropP

    Migrating Powered Off VM Results In VDI_CBT_ENABLED Failure Error

    Solved
    10
    0 Votes
    10 Posts
    1k Views
    planedropP
    @olivierlambert Oh yeah good point, that makes sense. Well I think I've got all my answers now, thank you!
  • P

    XOv6, New VM not same as XO-Lite

    6
    2
    0 Votes
    6 Posts
    831 Views
    lsouai-vatesL
    @ph7 that's fine, keep on testing our new XO-6, we are very happy with all our community feedback
  • K

    Self-service and sharing

    2
    0 Votes
    2 Posts
    391 Views
    olivierlambertO
    Hi, Pinging @pdonias about this
  • O

    Unable to update XOA

    4
    0 Votes
    4 Posts
    702 Views
    olivierlambertO
    Have you read the link I've sent? It explains exactly the reasons and answer your question You can imagine that if we have hundreds of 3rd party scripts, each doing their own way to install, it means we'll have to de facto support them all, despite it's unrelated to Xen Orchestra itself. Which means spending resources instead of working on Xen Orchestra directly (or fixing XO bugs). That's why it's preferable to open a ticket in the Github repo of the script creator, because that's exactly there you'll find the right answer, and also making sure the script creator could even fix their scripts if needed. If you need community support in here, you have to install it by following the official documentation: https://docs.xen-orchestra.com/installation#from-the-sources
  • C

    XO Community Edition - Ldap Plugin not working ?

    56
    0 Votes
    56 Posts
    18k Views
    C
    Just a reminder for myself, or other people in need in the future thanks again for all people who helped me understanding this Had to reinstall my entire XCP system, and almost forget how to configure Ldap plugin to only allow my admin accout to login So here's my Ldap plugin conf, to allow only admin user (member of specific group) to login. my AD is a windows 2K19 server with active directory without ssl. URI : ldap://dc.domain.net:389 no certificate info base : dc=domain,dc=net Credential : Fill = tick DN = full DN of service user (CN=xen,OU=service_account,DC=domain,DC=net) password = password of this account it's a simple account with no specific right, can only read AD and login User Filter, where it can stuck (&(sAMAccountName={{name}})(memberOf=CN=SG-XCP_Admin,OU=service_account,DC=domain,DC=net)) in real my OU have spaces inside their name, it work anyway. SG-XCP_Admin is a security group having my admin users inside ID Attribute : sAMAccountName and that's all.
  • J

    Building from source fails with commit cb96de6

    Solved
    12
    1
    0 Votes
    12 Posts
    2k Views
    J
    @Andrew many thanks. As do I. See my OP. A failed build doesn't break XO. It leaves the previous successful build in place. My post wasn't to ask how to fix my problem, but to point out the issue to others who might care to know (see my last post). Cheers.
  • R

    Unknown error - this pool is already connected

    15
    0 Votes
    15 Posts
    5k Views
    P
    This is an old thread, but I ran into this myself recently. While there is a link to deleting the entire XO configuration, I think I fixed it with a less drastic solution. Remember: I'm just a random dude on the internet posting dangerous commands to try. It worked for me, but your mileage might vary. I run Xen Orchestra in a container (Xen Orchestra, commit e8733 at the time of writing). So I got a command line in the container with: docker exec -it xoa bash Then I ran redis-cli to get a redis command prompt. I typed KEYS * to get a list of keys. One key I saw was: 7) xo:server_host:172.30.0.214". That's the IP of the host I was trying to join (the master of a single-host pool). So I ran: del xo:server_host:172.30.0.214 Then I restarted my container with docker restart xoa. After that, I was able to successfully add the host to Xen Orchestra. Maybe this will help someone else. It got me working again.
  • J

    freepbx import from esxi wont boot correctly

    12
    0 Votes
    12 Posts
    2k Views
    J
    @jsox79 No I did not. Disclaimer - I inherited this FreePBX system and don't know a whole lot about it. Once I got it to boot, I tested by calling my cell from a desk phone and making a page, and both worked as expected so I'm considering everything to be working. Didn't realize re-registering modules was something I may have needed to do.
  • K

    Nordic languages AltGr+<key>

    3
    0 Votes
    3 Posts
    423 Views
    K
    OK, thanks for the quick response
  • TheNorthernLightT

    The emulator required to run this VM failed to start..?

    14
    0 Votes
    14 Posts
    12k Views
    M
    Bit of a necro-post, but we're mid migration of storage/VM hosts/pools. I have a single win11 VM that's UEFI (not secure boot). It runs just fine on our old 8.1 server that we're migrating off of. If I provision a new UEFI VM on the new pool and point it at the shared storage VHD, it refuses to boot with the same "The emulator required to run this VM..." error OP posted. I've tried restarting the toolstack and "updating the Secure Boot certs" on the host server. Any guidance very much welcomed, I was unaware that this VM wasn't booting on the new pool (the VM is off a lot of the time), and we're a couple weeks from this project completing (and the old server being WEEEd).
  • BytevenidosB

    XOA w/ secure boot and uefi mode

    4
    1
    0 Votes
    4 Posts
    777 Views
    olivierlambertO
    Not with XOA then (yet). We might switch XOA to UEFI in the future for that. If you are using XO from the source, sure, you can do that
  • tc-atworkT

    [Request] Improve XO6 tags display functionality

    8
    2
    1 Votes
    8 Posts
    1k Views
    tc-atworkT
    @lsouai-vates those look great! @Pilow hey I’m just happy that @olivierlambert officially 100% promised and fully committed to a December 2025 initial release of XO6 on the monthly blog
  • B

    Update Templates

    13
    1 Votes
    13 Posts
    2k Views
    G
    @olivierlambert The only thing I can think of from newer kernels is NFS options like nconnect=xx for hopefully more speed in the day to day range of duties. As of the pre-LTS, this still wasn't in 8.3. I haven't checked after LTS.
  • K

    ECONNREFUSED when creating SDN network

    5
    0 Votes
    5 Posts
    829 Views
    K
    @bleader Hi, After a restart of the entire host, port 6640 is now listed when I trigger ss. But, unfortunatly, tunnels are not working, every VM on this host loose connection to other in the same sdn network. Exemple with an ping between two hosts : 2025-10-09T12:22:54.781Z|00026|tunnel(handler1)|WARN|receive tunnel port not found (arp,tun_id=0x1f1,tun_src=192.0.0.1,tun_dst=192.0.0.3,tun_ipv6_src=::,tun_ipv6_dst=::,tun_gbp_id=0,tun_gbp_flags=0,tun_tos=0,tun_ttl=64,tun_erspan_ver=0,gtpu_flags=0,gtpu_msgtype=0,tun_flags=key,in_port=33,vlan_tci=0x0000,dl_src=56:30:10:5c:4d:ad,dl_dst=ff:ff:ff:ff:ff:ff,arp_spa=192.168.10.10,arp_tpa=192.168.10.20,arp_op=1,arp_sha=56:30:10:5c:4d:ad,arp_tha=00:00:00:00:00:00) 2025-10-09T12:22:54.781Z|00027|ofproto_dpif_upcall(handler1)|INFO|Dropped 61 log messages in last 59 seconds (most recently, 1 seconds ago) due to excessive rate 2025-10-09T12:22:54.781Z|00028|ofproto_dpif_upcall(handler1)|INFO|received packet on unassociated datapath port 33 If I migrate the VM on the third host to another, network came back. This is very strange, because the network I've choose to test it is one of firt of all created, not last one, so it have worked before, and not now. I don't understand why and what to do...
  • J

    XCP-NG & XOA Trial extend

    2
    1
    0 Votes
    2 Posts
    217 Views
    olivierlambertO
    Hi, As the message said, please reach out to us, you can use the contact form https://vates.tech/contact We'll be happy to discuss and assist in your evaluation