Subcategories

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

    362 Topics
    3k Posts
    tjkreidlT
    @gb.123 I'm sure you can also find some NVIDIA "hoe to" guides that might be helpful. As mentioned before, I've only done server passthrough so that all VMs would get access, so sorry I can't provide more specifics. You can always try with one or the other option and add the other if it still doesn't work. I'm pretty sure, though, that you do need both enabled. Keep us posted!
  • ACLs, Self-service, Cloud-init, Load balancing...

    89 Topics
    763 Posts
    R
    I see your point. Thank you!
  • All XO backup features: full and incremental, replication, mirrors...

    366 Topics
    4k Posts
    J
    @SylvainB said in WORM Backups with XCP-ng / Xen Orchestra - Seeking Solutions & Experience: Hello everyone, I'm exploring options for implementing WORM (Write Once, Read Many) capabilities for my backups within my XCP-ng environment, specifically using Xen Orchestra. My current setup: XCP-ng Version: 8.3 Xen Orchestra Version: 5.106.4 (Stable) Intended Backup Target: Synology NAS My primary goal is to ensure that my backup data, once written, becomes immutable for a defined retention period, offering protection against accidental deletion or ransomware attacks. My questions are: Does Xen Orchestra offer any native WORM features or integrations that I might be overlooking for its backup jobs? If not directly, has anyone successfully implemented WORM backups with a similar perimeter (XCP-ng, Xen Orchestra, and potentially a Synology NAS or other storage solution)? I'm very interested in learning about your setup, the specific technologies you used (e.g., storage features, specific configurations), and any lessons learned or best practices. Any insights, architectural recommendations, or shared experiences would be highly valuable. Thank you in advance for your help! Best regards, SylvainB You can setup in the Synology its WriteOnce feature, then configure the appropriate configuration settings, including retention ones. This will prepare the appropriate WORM environment you’re looking for. It will work well due it being the equivalent to Vates solution and/or the S3 based one. https://kb.synology.com/en-in/search?tags[]=WriteOnce
  • Everything related to Xen Orchestra's REST API

    65 Topics
    496 Posts
    olivierlambertO
    Haha, glad it works now, that's what matters anyway
  • Terraform, Packer or any tool to do IaC

    33 Topics
    309 Posts
    I
    @olivierlambert @nathanael-h @Team-DevOps Please let me know if you have answers for any of the flollowing questions: Why JSON-RPC over websocket regularly returns not expected result for calls and what could be done with it? examples: method xo.getAllObjects sometimes returns empty result, but following: jsonrpc method params ------- ------ ------ 2.0 all @{type=enter; items=} On retry - everything is fine and we have all data jsonrpc result ------- ------ 2.0 @{bbdb1ed0-4c86-24ec-...=;..... method vm.copy sometimes returns only task with name_label host.get_server_certificate and no task async.vm.copy. Meanwhile copy operation is started in XEN Orchestra, so we have to separately search for the task currently running in all objects and if it is not there anymore suggest that it completed successfully. Afterwards we need to check if vm was copied and appeared in all objects. That is really frustrating as we have no info about successfully completed tasks in XEN - records just removed as nothing happen. most likely this happens due to other tasks being popped up in tasks at the same time and websocket call recives not its own responce, is it possible to workaround? What is correct syntax for JSON to run job.create method? Are there any article with supported methods for JSON-RPC calls and examples to use them? Calling for "system.getMethodsInfo" I can see "job.create": { "description": "Creates a new job from description object", "params": { "job": { "type": "object", "properties": { "userId": { "type": "string", "optional": true }, "name": { "type": "string", "optional": true }, "timeout": { "type": "number", "optional": true }, "type": { "type": "string" }, "key": { "type": "string" }, "method": { "type": "string" }, "paramsVector": { "type": "object", "properties": { "type": { "type": "string" }, "items": { "type": "array", "items": { "type": "object" } } }, "optional": true } } } }, "permission": "admin" }, But it is unclear what values should I provide to paramsVector and looking into the job created manually (in web interface) with method job.getall I can see 2 jobs [ { "type": "call", "name": "copyvm", "key": "generictask", "method": "vm.copy", "paramsvector": { "type": "crossproduct", "items": [ { "type": "set", "values": [ { "name": "nevm", "vm": "GUID", "sr": "GUID" } ] } ] }, "userid": "GUID", "id": "GUID" }, { "method": "vm.copy", "key": "vm.copy", "name": "copyvmjob", "type": "call", "userid": "GUID", "id": "GUID" } ] How can I create similar job myself if it is not possible to find out why vm.copy does not return async.vm.copy task info?
  • Updating Xen Orchestra from '13f2afb0d' to '943ad781c' STATS empty

    Solved
    7
    1
    1 Votes
    7 Posts
    486 Views
    W
    @manilx Nice was about to ask this too lol. Glad someone point this out already
  • Error When Trying to Create Backup Using NFS Remote

    Solved
    7
    2
    0 Votes
    7 Posts
    309 Views
    A
    @olivierlambert - Working now! Thanks!
  • Can't boot new VM "NO_HOSTS_AVAILABLE"

    11
    1 Votes
    11 Posts
    8k Views
    olivierlambertO
    Yes, that's the issue, the max vCPU in Advanced tab. It's probably at 42 while you only have 32 physical CPUs. Therefore, the VM won't boot. See an example screenshot: [image: 1726217639918-8728f260-893b-4601-b8b2-43b39b9d6806-image.png]
  • XOA setup on a completely offline system

    2
    0 Votes
    2 Posts
    854 Views
    olivierlambertO
    Hi, We offer air gap services to get you pre-bound XOA without the need for any Internet connection Otherwise, the workflow you used works too (configure XOA with a connected env and then export it). See https://xen-orchestra.com/docs/airgap.html for more details. Also, you can use our airgap deploy script in here: https://xen-orchestra.com/blog/xen-orchestra-5-95/#️-air-gap-features
  • How to add plugins like sdn-controller etc. to my XOA

    5
    1
    0 Votes
    5 Posts
    464 Views
    P
    ok thank you!
  • This topic is deleted!

    1
    0 Votes
    1 Posts
    6 Views
    No one has replied
  • Reset/Update statistics page fields

    3
    1
    0 Votes
    3 Posts
    220 Views
    S
    ah ok, thanks for the information.
  • Problems mounting NFS share

    13
    0 Votes
    13 Posts
    869 Views
    DanpD
    @rongage I don't know if anyone else has it working correctly on CentOS Stream 9. I know that it works on recent versions of Debian and Ubuntu, so why not try one of those?
  • Continue (vs restart) an interrupted backup

    7
    0 Votes
    7 Posts
    555 Views
    olivierlambertO
    With classical export (ie VHD and without NBD) you cannot "resume" a backup. Now it's possible (technically with NBD) but it's not done (yet). But we improved a lot the retry vs the original backups in VHD.
  • Deployment of XOA

    4
    0 Votes
    4 Posts
    673 Views
    J
    I don't "need" to deploy with xo-lite I just wanted to report it in case it was a bug with static ip configuration.
  • Replicating bare metal to VM

    6
    0 Votes
    6 Posts
    307 Views
    olivierlambertO
    In theory, like thinking on top of my head, an agent in the physical machine that will be able to replicate the VM files in the same format than the XO backup, with also the "machine metadata" (CPU, RAM etc.). Then, if something goes wrong, you could restore a backup as a VM from the real machine.
  • Windows template sysprep with cloudinit

    3
    0 Votes
    3 Posts
    349 Views
    J
    @olivierlambert thanks for the quick reply Olivier, We have cloudinit working for Linux as that is working like a charm, hopefully a MS cloudinit god will reply and will be able to help me out
  • Windows VM gets apipa from tagged network interface, no issues on Linux

    Solved
    3
    2
    0 Votes
    3 Posts
    167 Views
    J
    @Andrew it was related to a switch configuration mistake, thanks anyways.
  • Set Static Memory for VM in XOA

    9
    2
    0 Votes
    9 Posts
    350 Views
    olivierlambertO
    Yes, you can ignore static min, 99% of the time it's not relevant.
  • Ran XOA updater, got 'CANNOT GET /', web UI has stopped working.

    7
    0 Votes
    7 Posts
    963 Views
    W
    My apologies @Danp , I had misunderstood the comments on the other commands in that KB article. Good news, things are working, but it didn't seem like they would be. xoa run npm i -g --unsafe-perm https://xen-orchestra.com/xoa-updater.tgz Seemed to work. I was then able to run systemctl restart xoa-updater and xoa-updater --upgrade. After the upgrade command, this is the feedback: xoa:xoa$ xoa-updater --upgrade stable channel selected Downloading packages... xen-orchestra 5.95.2 . ok ✔ xo-server-telemetry 0.5.0 ...................................... ok ✔ xen-orchestra-web 0.0.3 ................................................... ok ✔ xo-server-xoa 0.29.0 .................................................................................................................. ok ✔ xo-web-free 5.147.0 ................................................................................................................................................................................................................................................................................................................................................................................................................................. ok ✔ xoa-cli 0.38.2 ...................................................................................................................................................................................................................... ok ✔ xen-orchestra-upload-ova 0.1.6 ........................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................ ok ✔ xo-server 5.145.0 ......................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................... ok ✔ Following packages will be removed: xoa-updater 0.50.0 Removing packages... Saving current updater version in /usr/local/lib/node_modules/xoa-updater-previous ...ok ✔ xoa-updater ✔ New versions available: node 18.20.2 (18.19.1 installed) npm 10.5.0 (10.2.4 installed) Downloading packages... node 18.20.2 ...... ok ✔ npm 10.5.0 .................................................................................................................................................................. ok ✔ Installing packages... Upgrading Node/npm failed, re-installing old packages Command failed with exit code 1: npm i -g --unsafe-perm --quiet /tmp/xoa-updater/node-18.20.2.tgz npm ERR! code 1 npm ERR! path /usr/local/lib/node_modules/node npm ERR! command failed npm ERR! command sh -c ./installer npm ERR! installing : node-v18.20.2 npm ERR! curl: (28) Failed to connect to nodejs.org port 443 after 261014 ms: Couldn't connect to server npm ERR! npm ERR! Error: download preflight failed for '18.20.2' (https://nodejs.org/dist/v18.20.2/node-v18.20.2-linux-x64.tar.xz) npm ERR! A complete log of this run can be found in: /tmp/.npm/_logs/2024-09-01T16_42_27_685Z-debug-0.log New packages available: xoa-updater 0.50.0 Downloading packages... Installing packages... xoa-updater ✔ xoa-updater ✔ ✖ { message: 'Command failed with exit code 1: npm i -g --unsafe-perm --quiet /tmp/xoa-updater/node-18.20.2.tgz\n' + 'npm ERR! code 1\n' + 'npm ERR! path /usr/local/lib/node_modules/node\n' + 'npm ERR! command failed\n' + 'npm ERR! command sh -c ./installer\n' + 'npm ERR! installing : node-v18.20.2\n' + "npm ERR! curl: (28) Failed to connect to nodejs.org port 443 after 261014 ms: Couldn't connect to server\n" + 'npm ERR! \n' + "npm ERR! Error: download preflight failed for '18.20.2' (https://nodejs.org/dist/v18.20.2/node-v18.20.2-linux-x64.tar.xz)\n" + '\n' + 'npm ERR! A complete log of this run can be found in: /tmp/.npm/_logs/2024-09-01T16_42_27_685Z-debug-0.log' } At this point I thought there was a failure - but then I was able to run systemctl restart xo-server.service and access both the current web UI and the v6 UI. I'm interested in trying the newer v6 features, so I just changed from the stable channel to latest using the web UI and ran upgrade - but it gave me an error: 9/1/2024, 1:02:48 PM: New versions available: 9/1/2024, 1:02:48 PM: xoa-updater 0.50.1 (0.50.0 installed) 9/1/2024, 1:02:48 PM: Downloading packages... 9/1/2024, 1:02:49 PM: xoa-updater 0.50.1 ....................................................................................................................................................................................... ok ✔ 9/1/2024, 1:02:49 PM: Installing packages... 9/1/2024, 1:03:02 PM: Saving current updater version in /usr/local/lib/node_modules/xoa-updater-previous ...ok ✔ 9/1/2024, 1:03:03 PM: xoa-updater ✔ 9/1/2024, 1:03:14 PM: xoa-updater ✔ 9/1/2024, 1:03:14 PM: Lost connection with xoa-updater 9/1/2024, 1:03:14 PM: xoa-updater could not be reached Using ssh I went back to the command line and ran xoa-updater --upgrade again and this time it is proceeding forward. And now it all works! Very weird. I think I'm in good shape now.
  • Health alerts/alarms

    14
    1 Votes
    14 Posts
    2k Views
    J
    @billcouper I 100% agree with you. I will add to this that it would be amazing if RX and TX nic/SFP errors could be made visible in the interface as well. reason why i mention this is we recently had a problem on one of our hosts storage links where due to a dirty fiber we had some problems (vm's going to read only, crashes, very poor IO). Due to how dom0 sits as a VM we could not get stats off a nic using ethtool or snmp. It took WAY to much trouble shooting to figure out that our issues was caused by a dirty fiber on the servers side. the more native/local self monitoring/alerting xcp-ng and XOA can do, the better.
  • Best Practices XO Location

    5
    0 Votes
    5 Posts
    504 Views
    J
    I do run XOA on its own dedicated host/dedicated pool, so the xcp-ng cpu scheduler does not cause issues with other busy production VM's while backup tasks are happening. this also allows XOA to use 100% of cpu cores making backups (especially with compression on) faster. xoa does DR back up to the primary pool in case something happens to the host its running on.
  • Full backup restore error: Stream_vdi.Invalid_checksum

    14
    0 Votes
    14 Posts
    642 Views
    olivierlambertO
    Yes, you can always export/import the config on a working install. So it's a problem on your build, it's really hard to tell where's the culprit (because you built it, you see why we distribute it via XOA for production/professional usage )
  • Is v6 preview not available on XO from source?

    Solved
    22
    2 Votes
    22 Posts
    5k Views
    A
    @olivierlambert Yes, this worked great! I’ll just keep both until v6 releases.
  • XOA Pricing Concerns

    3
    0 Votes
    3 Posts
    428 Views
    Marc.pezinM
    Hello @someone2b, Marc here, CMO of Vates. I wanted to provide some clarity on our new pricing structure and the reasoning behind these changes. Here are a few key points that led to our decision: In 2022, half of the support requests from Xen Orchestra customers were actually related to issues with the hypervisor layer, which aren't covered by standalone Xen Orchestra support. We've seen an increase in requests for XCP-ng support from users who only seek help after encountering issues in their infrastructure. XCP-ng and Xen Orchestra have become deeply integrated, making it increasingly challenging for our team to effectively support Xen Orchestra without also addressing the virtualization platform. We’ve also redesigned our business model to be more equitable, particularly for smaller infrastructures. For those with 10 hosts or fewer, the new pricing is actually lower than the previous cost of purchasing XCP-ng and Xen Orchestra separately. That being said, we didn't forgot as well all the remaining XenServer users out there and we are currently working on to have a secure and affordable path forward for them as well. If you have any questions or would like to discuss this further, please don’t hesitate to reach out to our sales team at sales@vates.tech. Marc