Subcategories

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

    363 Topics
    3k Posts
    dthenotD
    @Razor_648 While I was writing my previous message, I have been reminded that there are also issues with LVHDoISCSI SR and CBT, you should disable CBT on your backup job and on all VDI on the SR. It might help with the issue.
  • ACLs, Self-service, Cloud-init, Load balancing...

    90 Topics
    766 Posts
    D
    @Danp said in Advanced VM settings Logs: Hi Dustin, Yes... these types of actions are recorded in the Audit log (Settings > Audit) if you have access to this feature and have enabled it. Dan Perfect, thanks!
  • All XO backup features: full and incremental, replication, mirrors...

    370 Topics
    4k Posts
    C
    I have two remotes that I use for delta backups. One is on a 10Gbe network and the other only has a single 1Gbe port. Since XO writes those backups simultaneously, the backup takes a really long time and frequently randomly fails on random VMs. I was thinking it would be better if I have XO perform the backup to the 10Gbe remote running UNRAID then schedule an rsync job to mirror that backup to the 1Gbe remote on a Synology array. I've already NFS mounted the Synology share to UNRAID and confirmed I can rsync to it from a prompt, I just need to create a cron job to do it daily. In addition to, hopefully, preventing the random failures, it would let XO complete the backup a lot faster and my UNRAID server and Synology will take care of the rest, reducing the load on my main servers during the workday. The current backup takes long enough that it sometimes spills into the workday. I'm wondering if that will cause any restore problems. When XO writes to two remotes, does it write exactly the same files to both remote such that it can restore from the secondary even if it never wrote the files to that remote? I would assume they are all the same but want to make sure I don't create a set of backup files that won't be usable. Granted, I can, and will, test a restore from that other location but I don't want to destroy all the existing backups on that remote if this would be a known-bad setup. Note, I did a --dry-run with rsync and see quite a few files that it would delete and a bunch it would copy. That surprises me because that is still an active remote for the delta backups. I'm suspicious that the differences are due to previously failed backups.
  • Everything related to Xen Orchestra's REST API

    66 Topics
    502 Posts
    lsouai-vatesL
    @StephenAOINS This endpoint is not currently present in our REST API swagger, but we do plan to add it to the list of endpoints. We are currently finalizing the migration of existing endpoints, the next step will be adding new ones. We will keep you informed when it is available. Feel free to come back to us if you want to learn more and follow our blog posts. have a good day
  • Terraform, Packer or any tool to do IaC

    34 Topics
    319 Posts
    olivierlambertO
    No, it's fine, as long the issue contains all the relevant details it's fine
  • Acessing console on a remote VM

    8
    0 Votes
    8 Posts
    547 Views
    olivierlambertO
    If you proxy (or reverse proxy) any stuff, yes, you need to have a fixed address for the proxy.
  • display bond mode in Pool/network. New to xoa

    5
    2
    0 Votes
    5 Posts
    221 Views
    M
    @Andrew Yes, that offscreen was the problem..... Perhaps place it more to the left.
  • Updating Xen Orchestra from '13f2afb0d' to '943ad781c' STATS empty

    Solved
    7
    1
    1 Votes
    7 Posts
    494 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
    316 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
    875 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
    476 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
    229 Views
    S
    ah ok, thanks for the information.
  • Problems mounting NFS share

    13
    0 Votes
    13 Posts
    894 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
    562 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
    689 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
    321 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
    354 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
    172 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
    366 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
    985 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
    512 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
    650 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 )