1. Home
  2. Xen Orchestra

Subcategories

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

    381 Topics
    3k Posts
    D
    @Cygace Someone from the community may jump in and help troubleshoot this. The best approach would be to not modify the Dom0 installation by installing Zabbix via a community post, as you're customizing the installation. The vates team and XCP-ng specifically need to include these packages to ensure you're able to get support. Best of luck

  • ACLs, Self-service, Cloud-init, Load balancing...

    93 Topics
    790 Posts
    DustyArmstrongD
    @Berrick Ah cool, I was anticipating that doing it live would've caused boot issues but I think I've just got a bug in my head about how it actually works, I'm conflating two separate things based on an incorrect interpretation of a previous experience I had once with XCP. Thanks!

  • All XO backup features: full and incremental, replication, mirrors...

    389 Topics
    4k Posts
    A
    @florent Sep 15 10:00:01 xo1 xo-server[5582]: 2025-09-15T14:00:01.026Z xo:backups:worker INFO starting backup Sep 15 10:00:32 xo1 xo-server[5582]: 2025-09-15T14:00:32.794Z xo:xapi:xapi-disks INFO Error in openNbdCBT XapiError: SR_BACKEND_FAILURE_460(, Failed to calculate changed blocks for given VD Is. [opterr=Source and target VDI are unrelated], ) Sep 15 10:00:32 xo1 xo-server[5582]: at XapiError.wrap (file:///opt/xo/xo-builds/xen-orchestra-202509150942/packages/xen-api/_XapiError.mjs:16:12) Sep 15 10:00:32 xo1 xo-server[5582]: at default (file:///opt/xo/xo-builds/xen-orchestra-202509150942/packages/xen-api/_getTaskResult.mjs:13:29) Sep 15 10:00:32 xo1 xo-server[5582]: at Xapi._addRecordToCache (file:///opt/xo/xo-builds/xen-orchestra-202509150942/packages/xen-api/index.mjs:1073:24) Sep 15 10:00:32 xo1 xo-server[5582]: at file:///opt/xo/xo-builds/xen-orchestra-202509150942/packages/xen-api/index.mjs:1107:14 Sep 15 10:00:32 xo1 xo-server[5582]: at Array.forEach (<anonymous>) Sep 15 10:00:32 xo1 xo-server[5582]: at Xapi._processEvents (file:///opt/xo/xo-builds/xen-orchestra-202509150942/packages/xen-api/index.mjs:1097:12) Sep 15 10:00:32 xo1 xo-server[5582]: at Xapi._watchEvents (file:///opt/xo/xo-builds/xen-orchestra-202509150942/packages/xen-api/index.mjs:1270:14) Sep 15 10:00:32 xo1 xo-server[5582]: at process.processTicksAndRejections (node:internal/process/task_queues:105:5) { Sep 15 10:00:32 xo1 xo-server[5582]: code: 'SR_BACKEND_FAILURE_460', Sep 15 10:00:32 xo1 xo-server[5582]: params: [ Sep 15 10:00:32 xo1 xo-server[5582]: '', Sep 15 10:00:32 xo1 xo-server[5582]: 'Failed to calculate changed blocks for given VDIs. [opterr=Source and target VDI are unrelated]', Sep 15 10:00:32 xo1 xo-server[5582]: '' Sep 15 10:00:32 xo1 xo-server[5582]: ], Sep 15 10:00:32 xo1 xo-server[5582]: call: undefined, Sep 15 10:00:32 xo1 xo-server[5582]: url: undefined, Sep 15 10:00:32 xo1 xo-server[5582]: task: task { Sep 15 10:00:32 xo1 xo-server[5582]: uuid: '6265a41c-29c3-f4d9-5f0c-e52db6e0fcc9', Sep 15 10:00:32 xo1 xo-server[5582]: name_label: 'Async.VDI.list_changed_blocks', Sep 15 10:00:32 xo1 xo-server[5582]: name_description: '', Sep 15 10:00:32 xo1 xo-server[5582]: allowed_operations: [], Sep 15 10:00:32 xo1 xo-server[5582]: current_operations: {}, Sep 15 10:00:32 xo1 xo-server[5582]: created: '20250915T14:00:32Z', Sep 15 10:00:32 xo1 xo-server[5582]: finished: '20250915T14:00:32Z', Sep 15 10:00:32 xo1 xo-server[5582]: status: 'failure', Sep 15 10:00:32 xo1 xo-server[5582]: resident_on: 'OpaqueRef:65b7a047-094b-4c7a-a503-2823e92b9fe4', Sep 15 10:00:32 xo1 xo-server[5582]: progress: 1, Sep 15 10:00:32 xo1 xo-server[5582]: type: '<none/>', Sep 15 10:00:32 xo1 xo-server[5582]: result: '', Sep 15 10:00:32 xo1 xo-server[5582]: error_info: [ Sep 15 10:00:32 xo1 xo-server[5582]: 'SR_BACKEND_FAILURE_460', Sep 15 10:00:32 xo1 xo-server[5582]: '', Sep 15 10:00:32 xo1 xo-server[5582]: 'Failed to calculate changed blocks for given VDIs. [opterr=Source and target VDI are unrelated]', Sep 15 10:00:32 xo1 xo-server[5582]: '' Sep 15 10:00:32 xo1 xo-server[5582]: ], Sep 15 10:00:32 xo1 xo-server[5582]: other_config: {}, Sep 15 10:00:32 xo1 xo-server[5582]: subtask_of: 'OpaqueRef:NULL', Sep 15 10:00:32 xo1 xo-server[5582]: subtasks: [], Sep 15 10:00:32 xo1 xo-server[5582]: backtrace: '(((process xapi)(filename lib/backtrace.ml)(line 210))((process xapi)(filename ocaml/xapi/storage_utils.ml)(line 141))((process xapi)(fi lename ocaml/xapi/message_forwarding.ml)(line 141))((process xapi)(filename ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml)(line 24))((process xapi)(filename ocaml/libs/x api-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml)(line 39))((process xapi)(filename ocaml/xapi/rbac.ml)(line 188))((process xapi)(filename ocaml/xapi/rbac.ml)(line 197))((process xapi) (filename ocaml/xapi/server_helpers.ml)(line 77)))' Sep 15 10:00:32 xo1 xo-server[5582]: } Sep 15 10:00:32 xo1 xo-server[5582]: } Sep 15 10:00:35 xo1 xo-server[5582]: 2025-09-15T14:00:35.240Z xo:xapi:vdi WARN invalid HTTP header in response body { Sep 15 10:00:35 xo1 xo-server[5582]: body: 'HTTP/1.1 500 Internal Error\r\n' + Sep 15 10:00:35 xo1 xo-server[5582]: 'content-length: 318\r\n' + Sep 15 10:00:35 xo1 xo-server[5582]: 'content-type: text/html\r\n' + Sep 15 10:00:35 xo1 xo-server[5582]: 'connection: close\r\n' + Sep 15 10:00:35 xo1 xo-server[5582]: 'cache-control: no-cache, no-store\r\n' + Sep 15 10:00:35 xo1 xo-server[5582]: '\r\n' + Sep 15 10:00:35 xo1 xo-server[5582]: '<html><body><h1>HTTP 500 internal server error</h1>An unexpected error occurred; please wait a while and try again. If the problem persists, please contact your support representative.<h1> Additional information </h1>VDI_INCOMPATIBLE_TYPE: [ OpaqueRef:ec54186c-0ab5-0390-d244-64414e9d8887; CBT metadata ]</body></html>' Sep 15 10:00:35 xo1 xo-server[5582]: } Sep 15 10:00:35 xo1 xo-server[5582]: 2025-09-15T14:00:35.249Z xo:xapi:xapi-disks WARN can't compute delta OpaqueRef:888ccaa8-07c6-e6f0-3bfb-3e6b5ac4da2a from OpaqueRef:ec54186c-0ab5-0390-d2 44-64414e9d8887, fallBack to a full { Sep 15 10:00:35 xo1 xo-server[5582]: error: Error: invalid HTTP header in response body Sep 15 10:00:35 xo1 xo-server[5582]: at checkVdiExport (file:///opt/xo/xo-builds/xen-orchestra-202509150942/@xen-orchestra/xapi/vdi.mjs:36:19) Sep 15 10:00:35 xo1 xo-server[5582]: at process.processTicksAndRejections (node:internal/process/task_queues:105:5) Sep 15 10:00:35 xo1 xo-server[5582]: at async Xapi.exportContent (file:///opt/xo/xo-builds/xen-orchestra-202509150942/@xen-orchestra/xapi/vdi.mjs:244:5) Sep 15 10:00:35 xo1 xo-server[5582]: at async #getExportStream (file:///opt/xo/xo-builds/xen-orchestra-202509150942/@xen-orchestra/xapi/disks/XapiVhdStreamSource.mjs:123:20) Sep 15 10:00:35 xo1 xo-server[5582]: at async XapiVhdStreamSource.init (file:///opt/xo/xo-builds/xen-orchestra-202509150942/@xen-orchestra/xapi/disks/XapiVhdStreamSource.mjs:135:23) Sep 15 10:00:35 xo1 xo-server[5582]: at async #openExportStream (file:///opt/xo/xo-builds/xen-orchestra-202509150942/@xen-orchestra/xapi/disks/Xapi.mjs:128:7) Sep 15 10:00:35 xo1 xo-server[5582]: at async #openNbdStream (file:///opt/xo/xo-builds/xen-orchestra-202509150942/@xen-orchestra/xapi/disks/Xapi.mjs:81:22) Sep 15 10:00:35 xo1 xo-server[5582]: at async XapiDiskSource.openSource (file:///opt/xo/xo-builds/xen-orchestra-202509150942/@xen-orchestra/xapi/disks/Xapi.mjs:191:18) Sep 15 10:00:35 xo1 xo-server[5582]: at async XapiDiskSource.init (file:///opt/xo/xo-builds/xen-orchestra-202509150942/@xen-orchestra/disk-transform/dist/DiskPassthrough.mjs:28:41) Sep 15 10:00:35 xo1 xo-server[5582]: at async file:///opt/xo/xo-builds/xen-orchestra-202509150942/@xen-orchestra/backups/_incrementalVm.mjs:67:5 Sep 15 10:00:35 xo1 xo-server[5582]: }

  • Everything related to Xen Orchestra's REST API

    68 Topics
    530 Posts
    lsouai-vatesL
    @olivierlambert I am asking XO Team about this issue.

  • Terraform, Packer or any tool to do IaC

    35 Topics
    350 Posts
    J
    @manilx I have proposed to the IaC team of Vates, a MCP Server for Vates VMS. Which can be used by GitHub Copilot or similar, if used when doing IaC etc.
Log in to post
Load new posts
  • GriAleG

    invalid credentials in new installation from source

    9
    0 Votes
    9 Posts
    1k Views
    julien-fJ
    @GriAle Should be fixed: https://github.com/vatesfr/xen-orchestra/commit/ba03a4849831deecda7b8139374b5c43bf90d2b3 0 julien-f committed to vatesfr/xen-orchestra chore(xo-server): update to hashy@0.11.1 Fixes https://xcp-ng.org/forum/post/50866 Introduced by 49890a09b7a3c4bcbe7f462577c6d0a7da8b7006 Fixes argon2id support which is the new default algorithm since argon2@0.28.7
  • Spunky_SurveyorS

    XVA might be broken on Delta Backup

    4
    1
    0 Votes
    4 Posts
    778 Views
    Spunky_SurveyorS
    @julien-f It is likely a broken xva. I did interrupt those as they were exporting, however I was a bit confused as to why it was checked by a different backup task. In other words this screen clip is from a delta backup, not a xva export. I was more expecting it to show up on the XVA export backup task.
  • A

    Backup automatic retry

    7
    0 Votes
    7 Posts
    522 Views
    A
    @florent @olivierlambert Looking at failed S3 backup problems the retry should be easy. Currently on the job report there is a button to restart all failed VM backups in that job. Can you just add an option for automatic restart failed VM backups after job completion. It can even be a separate job (just as clicking the button is). It would just "click" the restart failed VMs button once (or a setting) after a few minutes (or a setting). Or it could start the new job as pending or delayed and start after a few minutes allowing for time to cancel it.
  • A

    Not seeing tasks any more (as admin)

    11
    0 Votes
    11 Posts
    1k Views
    T
    Thank you, that fix worked.
  • northportioN

    XO fails to backup 1 specific VM due to: Error: HTTP connection has timed out

    backup backups-reports delta
    14
    3
    1 Votes
    14 Posts
    2k Views
    M
    @olivierlambert i have created config.httpInactivityTimeout.toml in /opt/xen-orchestra/packages/xo-server with the content from above. Not sure how i can check if thats actually set. BTW: this is not a CR Backup Problem, i also dont see Tasks running for my "normal" Backup Job. I cant check "how far" the actual Backup runs and if that differs. https://github.com/vatesfr/xen-orchestra/pull/6315 Rajaa-BARHTAOUI opened this pull request in vatesfr/xen-orchestra closed fix(xo-web/tasks): tasks with no bound objects not displayed #6315
  • E

    how do i migrate VM storage to a different SR

    3
    0 Votes
    3 Posts
    3k Views
    E
    @olivierlambert thanks
  • GheppyG

    tasks not sowing in XOCE

    8
    0 Votes
    8 Posts
    830 Views
    rajaa-bR
    Hello, we will take a look into that and keep you posted.
  • Z

    Backup a VM with all its snapshots?

    14
    0 Votes
    14 Posts
    4k Views
    G
    @Zevgeny For a few snapshots it's fine - the issue comes when you have large numbers. Most of my first-hand experience with this specific issue comes from Hyper-V but the logic applies here. This is from VMware but the concept is the same and has some good reading on snapshots in general. Running a virtual machine on a snapshot for extended periods of time can cause instability and data loss. https://kb.vmware.com/s/article/1015180 The underlying issue stems from the nature of snapshots. With none you have a single VHD containing all of the data for the VM, once you take a snapshot a new delta VHD is created with all new data written going forward from the time of the snapshot. So, in order to have a complete VM you have the original VHD + the delta VHD. This is fine in smaller numbers, but once you start having 10, 15, 20+ snapshots, every one of those represents an additional VHD in the chain. This results in performance degradation because you're reading from multiple potential files as only new data is written to the deltas. This is actually from XO's blog: https://xen-orchestra.com/blog/xenserver-coalesce-detection-in-xen-orchestra/
  • J

    Xen Orchestra Community Edition - Registration

    xenorchestra
    14
    0 Votes
    14 Posts
    10k Views
    G
    Happy to do baby steps If / when you guys add some kind of "register" option to get a count on things I'd add my instance(s), as long as it doesn't break the existing install / upgrade scripts at least! Generally I have no issues with just clicking it away since I'm the only one that sees it. If it were a viable option sometime in the future, those would be my ideal "features". I've really enjoyed using XO coming from ESXi / vCenter at work and formerly running my home lab. Your vision of support is similar to Nutanix's which is partially why we went their route for our server overhaul and I think it's excellent. I'm hoping by the time we're due for a refresh the hyper-converged offering is fleshed out and production ready. Though I would miss my integrated firmware upgrades.
  • J

    Backup with USB passthru workaround?

    feature in backlog
    8
    0 Votes
    8 Posts
    2k Views
    J
    @olivierlambert Yes this is really great. I have a windows box where I experiment with bluetooth a bit and having backup on this machine at least once a week or so feels very good I think I think it also makes sense that a machine that needs to be taken down in order to make backup also probably will need another backup schedule.
  • D

    Best way to schedule backups hourly, daily, weekly, monthly without overlap?

    Solved
    3
    1
    0 Votes
    3 Posts
    813 Views
    D
    @ronivay very good point thank you! I guess hourly is excessive when snapshots are available. Will just schedule hourly snapshots instead as the main point is to be able to revert in the event of a breaking change.
  • A

    Strange backup error. false !== true

    11
    0 Votes
    11 Posts
    1k Views
    A
    @julien-f Restore showed that there were backups even when it said it failed.... I did not test one, sorry. I deleted the snapshots and old backup data which forced a full backup to S3 and XO was happy. A delta backup after that was also successful.
  • K

    Host Patch Installation Failure | "global name 'commmand' is not defined"

    Solved
    6
    0 Votes
    6 Posts
    1k Views
    K
    @olivierlambert Aaah, thanks Olivier. Still learning. Great product by the way. Hoping I can get comfortable with it enough to make a recommendation to my company.
  • MilitaryNerdM

    At a loss on network config chicken/egg

    3
    0 Votes
    3 Posts
    737 Views
    fohdeeshaF
    @MilitaryNerd Have you restarted the host since removing this bond? It's reporting that bond0 is still attached to an OVS bridge, so it may need a reboot. You can also ensure the bond is really gone by running xe bond-list, it should return nothing. You could also still have the bond PIF existing or other networks using the old bond, check that you don't have any PIFs with device ( RO): bond0 listed when running xe pif-list
  • Tristis OrisT

    unhealthy VDI chain

    21
    0 Votes
    21 Posts
    3k Views
    olivierlambertO
    Good news then
  • A

    New and exciting backup errors

    7
    0 Votes
    7 Posts
    1k Views
    A
    @andrewreid Not that this helps with your error, but my nightly S3 delta backups to Wasabi have been working just fine. I'm using XO source and keep mostly up to date with master. S3 and NFS are different backup formats so NFS working does not mean S3 will work. Sometimes Wasabi causes failures but not recently and not that last more than a few VMs in one night. The next backup run (manual restart or next nightly) seems to work correctly. I force a full backup every 3 months just to make sure I have a good checkpoint in case undetected corruption creeps into the delta data. Plus I have replication and other backups. I did have a problem once (not exactly yours) with a VM and just deleted the S3 backup data which forced a full backup again. Sucks because you don't have the weeks of deltas anymore. Error #3 (date-time) is strange. May be a backblaze issue. You could create a new S3 remote to backblaze (new bucket or directory) and test one failing VM backup to the new remote and see if it works (and works again for delta). You could set the retention low to test merge too. I have a setup like this with a local MinIO server for S3 testing and local backups.
  • mauzillaM

    Backups not starting after failed NFS mount

    4
    0 Votes
    4 Posts
    403 Views
    olivierlambertO
    haha that's exactly the purpose of the remote test button No grand mastery, just experience
  • K

    Moving backups to another remote?

    3
    0 Votes
    3 Posts
    511 Views
    K
    @olivierlambert I want to move them on NFS in order to be able to backup later from NFS to S3 in more granular way Generally, we are talking about XO - NFS. S3 would be out of XO.
  • S

    Register instance of XO Running on Hyper-V

    4
    0 Votes
    4 Posts
    683 Views
    julien-fJ
    @someone2b Just install this work-around xenstore-read with the following commands and hopefully it will work. sudo -s cd /usr/local/bin curl -O https://gist.githubusercontent.com/julien-f/a6f98de3bd5a775f3f04b2fa14a9a102/raw/xenstore-read chmod +x xenstore-read
  • K

    Second Pool Host Network 0 doesn't work for VMs

    1
    0 Votes
    1 Posts
    200 Views
    No one has replied