Subcategories

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

    470 Topics
    4k Posts
    andrewperryA
    @Danp I was going to do the upgrade over the December / January Christmas break in Australia but that is when this issue became apparent so we didn't want to be making major changes until it was resolved. I note @anthoineb noted the first report was late August / September 2025 which was just before 8.2.1 reached EOL, so it would be a shame not to have a fix for it tested on 8.2.1 as it seems an upgrade to 8.3 would be unwise while we still have this issue?
  • ACLs, Self-service, Cloud-init, Load balancing...

    104 Topics
    861 Posts
    olivierlambertO
    Question for @julienxovates (and @florent likely )
  • All XO backup features: full and incremental, replication, mirrors...

    505 Topics
    5k Posts
    G
    @Rod-G These have 9.4.2-xxxx and I need to go through and update everything now that I see how far behind I am. the second VM completed fine after its reboot, something was just stuck in a dirty state and got in the way of the import or health check.
  • Everything related to Xen Orchestra's REST API

    85 Topics
    633 Posts
    DustyArmstrongD
    @florent OK cool, thank you for the info.
  • 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
  • Windows template sysprep with cloudinit

    3
    0 Votes
    3 Posts
    924 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
    462 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
    1k 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
    3k 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
    5k 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
    1k 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
    2k 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 )
  • XOA Pricing Concerns

    3
    0 Votes
    3 Posts
    883 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
  • Xenserver 8 Support

    Solved
    4
    0 Votes
    4 Posts
    760 Views
    olivierlambertO
    The doc is now updated: https://xen-orchestra.com/docs/supported_hosts.html
  • Autostart VMs doesn't work

    6
    0 Votes
    6 Posts
    1k Views
    krakenredseaK
    what about xcp center v20, after enabling the checkbox, it can't work like if we enable power_on:true via command line? is xcp center not patched?
  • after a major crash and reload sr introduce

    2
    0 Votes
    2 Posts
    467 Views
    olivierlambertO
    The SR won't store the metadata. Maybe you have a metadata backup saved for this pool?
  • Automatic startup and shutdows VMs at the specified time

    Solved
    10
    0 Votes
    10 Posts
    2k Views
    julien-fJ
    @abudef Indeed, the delay is in milliseconds.
  • SR_BACKEND_FAILURE_140

    Solved
    13
    1
    0 Votes
    13 Posts
    2k Views
    J
    Hi @BenjiReis, Yes. Problem solved by adding the following lines to the resolv.conf file: domain Mydoamin.com search Mydoamin.com
  • Cannot import VHD disks while VMDK can

    Solved
    9
    2
    0 Votes
    9 Posts
    2k Views
    A
    qemu-img convert disk_image_fixed.vhd -O vpc -o subformat=dynamic disk_image_dynamic.vhd
  • Cannot find the link between virtual machine and virtual disk

    14
    0 Votes
    14 Posts
    3k Views
    P
    @julien-f Maybe we do not differentiate "attaching" a disk and "connecting" a disk. I just created a new disk then went to a VM to attach it, then did the same on another VM without problem on XO UI. BUT it seems that I cannot "connect" it on both VMs, which is not a problem, I only need to know what's possible, and what's not to be able to handle it. Regards
  • How to update the XO from the source code?

    Solved
    3
    0 Votes
    3 Posts
    572 Views
    J
    Thank you @olivierlambert.
  • Build from sources error -- EISDIR: illegal operation on a directory, read

    Solved
    9
    0 Votes
    9 Posts
    9k Views
    planedropP
    @planedrop Ignore me, I did make a dumb mistake, all is working now.
  • Xen Orchestra from source with Let's Encrypt certificates

    15
    2 Votes
    15 Posts
    9k Views
    gskgerG
    Having XO from source or XOA act as a certification authority for the XCP-ng hosts is for sure a good approach. Would be great if that could include the VMs running on the XCP-ng hosts, which is my main goal (apart from being able to HTTPS into XO from source of course).
  • Tips on installing XO

    97
    0 Votes
    97 Posts
    47k Views
    P
    I've acctually got a PR to help solve the documentation regarding the yarn forever part. Since I never could get that to work, I implemented a systemd variant instead. #7848 Ping @olivierlambert for visibility
  • Can't access XOA - stuck at grub

    1
    0 Votes
    1 Posts
    305 Views
    No one has replied