Subcategories

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

    431 Topics
    3k Posts
    itservicesI
    Hi @McHenry . You should obfuscate the IP address in your first screenshot. Also check your profile and private chat Hope everyone had a joyful Christmas and I wish everyone the best for 2026. Regards, Marc
  • ACLs, Self-service, Cloud-init, Load balancing...

    97 Topics
    818 Posts
    olivierlambertO
    October release fixed it
  • All XO backup features: full and incremental, replication, mirrors...

    444 Topics
    4k Posts
    A
    I have opened a support ticket and tunnel is open - Ticket#7749796 here is a section of the error log. I have rebooted XOA and rebooted the Proxy but yet the job still remains hung. Maybe i didn't reboot them in the correct order? As stated support ticket and tunnel are open. { "id": "1766901730734", "message": "snapshot", "start": 1766901730734, "status": "success", "end": 1766901734483, "result": "a995b25e-ab77-a217-fccd-7e8a1d06df57" }, { "data": { "id": "3022703c-5029-4ac3-bda1-3a76c6634a39", "isFull": true, "type": "remote" }, "id": "1766901734494", "message": "export", "start": 1766901734494, "status": "interrupted", "tasks": [ { "id": "1766901737246", "message": "transfer", "start": 1766901737246, "status": "interrupted" } ] } ], "infos": [ { "message": "Transfer data using NBD" } ] } ], "end": 1766901871318, "result": { "url": "https://10.120.20.119/api/v1", "message": "HTTP connection has timed out", "name": "Error", "stack": "Error: HTTP connection has timed out\n at ClientRequest.<anonymous> (/usr/local/lib/node_modules/xo-server/node_modules/http-request-plus/index.js:61:25)\n at ClientRequest.emit (node:events:518:28)\n at ClientRequest.patchedEmit [as emit] (/usr/local/lib/node_modules/xo-server/node_modules/@xen-orchestra/log/configure.js:52:17)\n at TLSSocket.emitRequestTimeout (node:_http_client:849:9)\n at Object.onceWrapper (node:events:632:28)\n at TLSSocket.emit (node:events:530:35)\n at TLSSocket.patchedEmit [as emit] (/usr/local/lib/node_modules/xo-server/node_modules/@xen-orchestra/log/configure.js:52:17)\n at TLSSocket.Socket._onTimeout (node:net:595:8)\n at listOnTimeout (node:internal/timers:581:17)\n at processTimers (node:internal/timers:519:7)" schedule.runSequence { "schedules": [ "3a677031-4eb9-427a-99fc-22afa411b745", "cadef7b9-2541-4850-9bfd-871d9602c6bb", "599d9321-7081-4840-9617-d31762d4764c", "828b5e60-4302-455c-94f1-479a8001f955" ] } { "url": "https://10.120.20.119/api/v1", "message": "HTTP connection has timed out", "name": "Error", "stack": "Error: HTTP connection has timed out at ClientRequest.<anonymous> (/usr/local/lib/node_modules/xo-server/node_modules/http-request-plus/index.js:61:25) at ClientRequest.emit (node:events:518:28) at ClientRequest.patchedEmit [as emit] (/usr/local/lib/node_modules/xo-server/node_modules/@xen-orchestra/log/configure.js:52:17) at TLSSocket.emitRequestTimeout (node:_http_client:849:9) at Object.onceWrapper (node:events:632:28) at TLSSocket.emit (node:events:530:35) at TLSSocket.patchedEmit [as emit] (/usr/local/lib/node_modules/xo-server/node_modules/@xen-orchestra/log/configure.js:52:17) at TLSSocket.Socket._onTimeout (node:net:595:8) at listOnTimeout (node:internal/timers:581:17) at processTimers (node:internal/timers:519:7)" backupNg.runJob { "id": "bb0adfc7-93b9-45c9-a90f-7aa327f95a05", "schedule": "3a677031-4eb9-427a-99fc-22afa411b745", "vms": [ "4c2fb974-f2d5-b0fb-7385-1683e0275ef2", "025f71ff-ecb2-9d0c-7692-f7005d22c659", "78aecc3d-4817-a11c-04b4-9d0f49f8736e", "9f36a8c5-c988-8546-b0f9-30ac9d0a5015", "db89c6f0-3330-7180-b5e4-7f2f36a241e6", "e5c656bb-8bb2-461e-a801-402ae150d022" ] } { "code": -32000, "data": { "jobId": "bb0adfc7-93b9-45c9-a90f-7aa327f95a05", "stack": "Error: job is already running at file:///usr/local/lib/node_modules/@xen-orchestra/proxy/app/mixins/backups.mjs:96:25 at file:///usr/local/lib/node_modules/@xen-orchestra/proxy/app/mixins/backups.mjs:114:20 at processTicksAndRejections (node:internal/process/task_queues:95:5)" },
  • Everything related to Xen Orchestra's REST API

    75 Topics
    571 Posts
    F
    @MathieuRA Thank you, perfect Br,
  • Terraform, Packer or any tool to do IaC

    45 Topics
    427 Posts
    CyrilleC
    Terraform provider release v0.37.0 Enables the secure boot parameter for the VM resource Terraform provider release: https://github.com/vatesfr/terraform-provider-xenorchestra/releases/tag/v0.37.0
  • Feature request: Highlight full backups

    feature in backlog
    6
    1
    0 Votes
    6 Posts
    689 Views
    julien-fJ
    I agree it makes sense. Ping @pdonias
  • Clarification on an Advanced setting

    5
    0 Votes
    5 Posts
    1k Views
    stormiS
    @jedimarcus said in Clarification on an Advanced setting: @eangulus With MaxCPU you can do the increase WITHOUT shutting down... I'll complete this with an example: create a VM with 4 vCPUs and Max vCPU = 8. you can now change the number of vCPUs from anything between 1 and 8 without shutting the VM down
  • S3 / Wasabi Backup

    47
    0 Votes
    47 Posts
    22k Views
    olivierlambertO
    It's also explained very clearly here: https://xen-orchestra.com/docs/community.html (in the first point) Always update to latest code available before reporting a problem
  • Full Backup Problem

    6
    1
    0 Votes
    6 Posts
    859 Views
    N
    @danp i couldnt get the log from command line, sorry But i was able to complete the backup to another remote, so i think the main problem is the remote im using
  • XOA from Source Limitation

    11
    0 Votes
    11 Posts
    2k Views
    J
    @harajukakei I dont use it but it does work for me (XO build from Source), although not from my android phone (the hosts don't move across to the Available list), so could it be browser related?
  • Cannot add ip or edit to existing network

    Solved
    4
    1
    0 Votes
    4 Posts
    700 Views
    M
    @andy you're welcome!
  • XO tree view

    8
    1 Votes
    8 Posts
    2k Views
    ForzaF
    @julien-f Thank you for explaining your plans. I am very eager to see the new XO 6! Perhaps a Christmas present for all of us? I just realised I have one more "peeve" with XOA. That is the console view which does not work well with Swedish keyboard layout. For example pressing Alt-Gr+2 to get at-sign '@' doesn't work. It also crashes the keyboard input so it doesn't release the alt-key. This always works correctly in XCP-ng center. The problem is in both Linux and Windows guests.
  • Switch to XOA free

    5
    0 Votes
    5 Posts
    6k Views
    olivierlambertO
    Have you checked our guide to install Windows drivers? Check https://xcp-ng.org/docs/guests.html#windows If you still have issues, with your current XOA account in trial, you can open support tickets already so we can take a look remotely (https://support.vates.fr)
  • Xen Motion Network

    3
    3
    0 Votes
    3 Posts
    1k Views
    brezlordB
    Feature request oped https://github.com/vatesfr/xen-orchestra/issues/5391 brezlord created this issue in vatesfr/xen-orchestra closed Set pool wide Xen Motion Network #5391
  • 1 Votes
    2 Posts
    461 Views
    BenjiReisB
    @naeemarsalan Good catch, It will be added to the cloudinit script creating the master and the nodes. This will save one reboot to everyone.
  • How to set ip for storage on each server?

    2
    1
    0 Votes
    2 Posts
    2k Views
    jedimarcusJ
    It's a little different, but if in Xen Orchestra you go: Home => Hosts => <host> => Network there I can see my storage IP addresses comparable to that "IP Address Configuration" part. Except that here, all the networks are listed in the same list. Can you see if that's what you are looking for?
  • Import VM from VirtualBox to XO

    4
    0 Votes
    4 Posts
    1k Views
    olivierlambertO
    Is there a way to access your OVA so we can try to reproduce?
  • XCP-ng high availability & xoSAN basic quesstions

    2
    0 Votes
    2 Posts
    2k Views
    olivierlambertO
    Existing HA level is at VM level. It means, if the VM is down (or the host on the VM is running is down), it will be booted on a working host in that pool. For hyperconvergence, it's far from being a miracle solution. It costs a lot of thinking, planning and maintenance (and careful usage of it). Like HA in the end. So before asking for advanced features, it's good to think about what you really need.
  • XOA import issue

    4
    0 Votes
    4 Posts
    872 Views
    olivierlambertO
    He also said there's a fix coming for the next release.
  • Delta Backups & Continous Replication of Empty Drives

    14
    4
    0 Votes
    14 Posts
    2k Views
    S
    @olivierlambert Thanks, I tried running fstrim but it returned "the discard operation is not supported" on this NFS SR mount. I also tried running on SSD mounts which do support TRIM and they all returned the same message about "discard...not supported." The VM OS (CentOS 7.8) does support TRIM in kernel so not sure if xcp-ng or xenserver is the reason why the VM can't issue fstrim on the NFS SR mount or the SSD SR mounts. [image: 1605283613178-85b94dd0-b129-45ec-9ee2-bc4b7dd92b5e-image.png]
  • XOA always does a full backup if VDI was moved between storage

    2
    0 Votes
    2 Posts
    273 Views
    olivierlambertO
    When you migrate a VDI to another SR, its UUID is changed. So it's like a "new VDI". However, there's an issue opened a while ago: https://github.com/vatesfr/xen-orchestra/issues/2896 We did not have a priority on this because not a lot of people asked for it. I think it could be a good optional feature in a job. snimmerjahn created this issue in vatesfr/xen-orchestra closed [Delta Backup] Avoid full export after VDI migrate #2896
  • XO disconnects regularly, freezing the console

    6
    0 Votes
    6 Posts
    1k Views
    olivierlambertO
    It's in our documentation, please read https://xen-orchestra.com/docs/configuration.html#https
  • Problem with ZSTD compressed backup

    7
    0 Votes
    7 Posts
    1k Views
    M
    So far, I noticed this problem for three VMs. Each time I am trying to perform a backup with zstd compression through XO, the backup is marked as successful, but output XVA file is damaged (incomplete). The backup works fine for all other VMs, and I cannot pinpoint what is special about these faulty VMs.
  • xoa-updater --upgrade fails and configuration questions

    2
    0 Votes
    2 Posts
    776 Views
    olivierlambertO
    Hi, It failed because you changed the npm version manually. You can indeed re-deploy a fresh XOA, export the configuration and import it on the new one.
  • XO - change control domain memory?

    4
    0 Votes
    4 Posts
    2k Views
    olivierlambertO
    I'm not against exposing this in the UI, it might be not that difficult. However, more traction will obviously make it possible