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
    789 Posts
    P
    I did stick to version: 1 in my working configuration [image: 1757959695876-01998ae9-bb3f-4a3c-b3f6-b1d34ae23704-image.png] Had to rename my "Ethernet 2" nic name to Ethernet2 without the space You have to put the exact template nic name for this to work.
  • 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.
  • Disaster Recovery backup auto-starting VMs (but shouldn't)

    15
    2
    0 Votes
    15 Posts
    3k Views
    olivierlambertO
    That's the issue. Why they don't have it is the problem/mystery. Try to check if new replicated VMs got it. If not, I would check if you are correctly up to date.
  • When VM has changes from latest snapshot?

    feature in backlog
    12
    0 Votes
    12 Posts
    2k Views
    MathieuRAM
    Hello @Zevgeny . Finally, we won't be able to display if the vm has changed since the snapshot.
  • Import VHD

    7
    0 Votes
    7 Posts
    2k Views
    stormiS
    @joearnon The browser javascript logs may give you useful information about what issue happened during the import as seen from XO's side. However the disappearing SR issue makes me think you should look at XCP-ng logs, in particular /var/log/SMLog for storage-related logs and /var/log/daemon.log.
  • OS for Xo

    3
    0 Votes
    3 Posts
    471 Views
    DanpD
    @jsawyer77 Did you follow the documentation when building XO? If not, then what process did you use? Also, check to see if libvhdi-utils is installed and which version.
  • What is Stored in a Template?

    Solved
    7
    0 Votes
    7 Posts
    3k Views
    kdmK
    @olivierlambert You inadvertently solved this one, too, n parallel with @tony . So, basically, as suspected, a template is nothing more than populating stuff that's in the basic and advanced webforms on Orchestra, anyway.
  • xo-server/bin doesn't exist after updating with yarn build.

    Solved
    25
    0 Votes
    25 Posts
    8k Views
    A
    I had same issue. doing: git clean -d -f and then running yarn build again helped.
  • Updates not showing up in XOA

    5
    0 Votes
    5 Posts
    559 Views
    pdoniasP
    There's a 1 min cache on XO's side. So if the updates weren't showing up for more than 1 minute, then it might be something else.
  • Warnings showing in system logs following each backup job

    4
    0 Votes
    4 Posts
    721 Views
    ForzaF
    @julien-f said in Warnings showing in system logs following each backup job: We'll see how many reports we get regarding this One more from me. But it was actually your tech support that discovered them in conjunction with a ticket we have open.
  • Backup failure: HTTP request has been canceled

    5
    2
    0 Votes
    5 Posts
    420 Views
    ForzaF
    @olivierlambert said in Backup failure: HTTP request has been canceled: It's a problem when XO tries to get address from your srv02.xxx.com. It just makes no sense that DNS would be an issue on this network. I guess if XO momentarilly looses connection during DNS lookup it could cause this problem. I've noticed sometimes that the webui of XOA sometimes can show red ? if I start live several live migrations. Maybe unrelated?
  • 100% load in XOA, but none in DomU

    14
    0 Votes
    14 Posts
    882 Views
    F
    @olivierlambert I created a ticket out of this request. Maybe continue there?
  • 0 Votes
    4 Posts
    1k Views
    R
    @olivierlambert Thanks.
  • Backup speed

    7
    1
    1 Votes
    7 Posts
    1k Views
    olivierlambertO
    That's probably since using more your cores (now there's a dedicated thread backup job).
  • Restart VM after SR available

    8
    0 Votes
    8 Posts
    1k Views
    C
    @gskger, supermicro requires -I open as they don't support RMCP+.
  • Backup Architecture

    Solved
    3
    0 Votes
    3 Posts
    444 Views
    C
    @olivierlambert Haha, it's so obvious! Didn't even think to select both at the same time. Genious, thanks.
  • console page tabs

    Solved
    3
    0 Votes
    3 Posts
    271 Views
    J
    Thanks for the response I got it working John
  • NFS SR not mounting

    8
    0 Votes
    8 Posts
    7k Views
    fohdeeshaF
    @thorcraftit seems like perhaps a permissions error, what does your share properties on truenas look like for this host? Is the allowed IP or denied IP boxes populated at all? Attach a screenshot if you can. Here's what mine looks like: [image: 1625573743330-f76ebeef-c5cf-452e-8a43-28144d9a8c94-image.png] Note that the mapall user and group must have permissions on the shared folder, I typically create a user on the freenas system just for xen shares, and give it ownership of the folder/dataset that's being shared. this ensures you don't have any weird permissions issues. I think in your case the key boxes to examine are the authorized networks however. What does your Services > NFS > Settings look like? here's mine: [image: 1625573851182-3ccf191c-575c-4094-b91f-b4e12e6a4091-image.png] Lastly and perhaps most importantly, can you run "yum install nmap" and then "nmap 172.16.60.200" on both a working host, and then this non-working host? Paste the results of both here - if they differ, for instance if the non-working server doesn't see any RPC services running like I suspect, that will heavily point towards a firewall/network/ACL issue
  • Config Password when exporting from 5.41.0 to 5.80

    7
    0 Votes
    7 Posts
    570 Views
    julien-fJ
    @cfm56 The error was probably due to https://github.com/vatesfr/xen-orchestra/issues/5836 This did not impact the import of the config though, anyway it should be fixed now trader418 created this issue in vatesfr/xen-orchestra closed Config restore error #5836
  • WORM / immutable backups

    2
    0 Votes
    2 Posts
    598 Views
    olivierlambertO
    But what about merging delta backup? This require write access. Except if we completely "move" the merge logic in the storage itself (which will be possible in few months)
  • Backup - Bypass XOA

    2
    0 Votes
    2 Posts
    360 Views
    olivierlambertO
    That's because of XCP-ng/XenServer design. The host isn't pushing data, it's only exposing an HTTP handler to pull from it. You can use XO Proxies if you prefer: https://xen-orchestra.com/docs/proxy.html
  • Clear Filters by Default

    Solved
    3
    0 Votes
    3 Posts
    535 Views
    kdmK
    @darkbeldin Thank you. That was just off the bottom of the screen and I did scroll past it a few times, but being a little lonely icon, when all the other items have text, it didn't even register as a thing!