Subcategories

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

    329 Topics
    2k Posts
    M
    @olivierlambert I have 9000 everywhere on the network so i set the MTU to that. I did notice in a previous POC that I used 1500 in XO/XCP-NG though.... Thoughts? How can I recover, just delete /re-install the hypervisor and reconnect?
  • ACLs, Self-service, Cloud-init, Load balancing...

    84 Topics
    707 Posts
    CyrilleC
    @ferrao Yes it is. At the end the task disappears unless there is an error / failure.
  • All XO backup features: full and incremental, replication, mirrors...

    337 Topics
    3k Posts
    olivierlambertO
    Thanks for your feedback, we'll discuss internally if there's any other possible approach (and I'm not sure).
  • Everything related to Xen Orchestra's REST API

    61 Topics
    476 Posts
    S
    @Studmuffn1134 I changed my link from ws:// to https:// and it now gives me this error File "Z:\Valera\School\Lakeland University\Finished\Programming 2\Python Programs\StudsPrograms.venv\Lib\site-packages\jsonrpc_base\jsonrpc.py", line 213, in parse_response raise ProtocolError(code, message, data) jsonrpc_base.jsonrpc.ProtocolError: (10, 'invalid parameters', {'error': {'message': 'invalid parameters', 'code': 10, 'data': {'errors': [{'instancePath': '/id', 'schemaPath': '#/properties/id/type', 'keyword': 'type', 'params': {'type': 'string'}, 'message': 'must be string'}]}}, 'id': '0a11ec72-9300-4030-a5d2-a5c0286f3811', 'jsonrpc': '2.0'})
  • Terraform, Packer or any tool to do IaC

    30 Topics
    279 Posts
    nathanael-hN
    Hello, I suggest you look also for Packer to build ready to use VM templates, with cloud-init, guest tools, and the softwares you'd need. There's a blog post for this https://xcp-ng.org/blog/2024/02/22/using-packer-with-xcp-ng/.
  • This topic is deleted!

    Solved
    2
    0 Votes
    2 Posts
    7 Views
  • Using tags or custom fields for VM placement

    25
    0 Votes
    25 Posts
    5k Views
    olivierlambertO
    The easiest way to guarantee it is to depend on a local resource (local SR or ISO).
  • Acessing console on a remote VM

    8
    0 Votes
    8 Posts
    378 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
    140 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
    379 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
    241 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
    641 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
    344 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
    116 Views
    S
    ah ok, thanks for the information.
  • Problems mounting NFS share

    13
    0 Votes
    13 Posts
    588 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
    454 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
    543 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
    224 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
    261 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
    134 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
    218 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
    777 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.