Subcategories

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

    427 Topics
    3k Posts
    P
    In case anyone wonders how this played out. At the end of the day, I shutdown the host with the running workloads on it, kept it at BIOS boot so the 8.3 installer would upgrade it cleanly, and then booted it back up. For reasons related to my particular setup, the down time was more than 60 minutes. But that's not related to XCP-ng. The XCP-ng installer was maybe 10 of that. 20 of that was 3 reboots on a server that takes ages to boot. One thing that is a bit difficult is that the 8.3 installer doesn't notice ZFS volumes or help with ZFS. So after the upgrade, I have to follow a modified set of these instructions (modified because the package names have changed over time) to install ZFS and its components into the system. So the sequence is: Shutdown Install via ISO Reboot to single user mode Run yum update to pull in all the updates Run the ZFS commands to install ZFS on the host Reboot again Run normally Of course, I ended up rebooting more than just those 2 times, because I forgot that I would need to install ZFS (even though I did it on 2 different hosts already ) So now the pool is fully upgraded, everybody is happy. I'm now working on creating shared storage across the nodes. It's amateur hour over here. I appreciate all the help.
  • 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...

    440 Topics
    4k Posts
    A
    Yesterday I upgraded to the most recent version of XCP-NG 8.3 via yum update. Last night's backup is full of this error using the following: Xen Orchestra, commit 8448b Xen Orchestra, commit 1de60 I looked at the logs and they pointed to a snapshot error. For the heck of it , I tried running a snapshot on any of the VM's. Each one fails with this error: vm.snapshot { "id": "0b65cf83-8309-3dcc-fa94-a511c77c96bd" } { "code": "NOT_SUPPORTED_DURING_UPGRADE", "params": [], "task": { "uuid": "71b630bb-d299-bab2-c2e9-065cd4bfef5c", "name_label": "Async.VM.snapshot", "name_description": "", "allowed_operations": [], "current_operations": {}, "created": "20251219T14:33:39Z", "finished": "20251219T14:33:39Z", "status": "failure", "resident_on": "OpaqueRef:3ea53cca-30d6-7c19-3f77-3f7eb26c6675", "progress": 1, "type": "<none/>", "result": "", "error_info": [ "NOT_SUPPORTED_DURING_UPGRADE" ], "other_config": {}, "subtask_of": "OpaqueRef:NULL", "subtasks": [], "backtrace": "(((process xapi)(filename ocaml/xapi/xapi_vm_lifecycle.ml)(line 755))((process xapi)(filename ocaml/xapi/xapi_vm_helpers.ml)(line 1653))((process xapi)(filename fun.ml)(line 33))((process xapi)(filename fun.ml)(line 38))((process xapi)(filename ocaml/xapi/helpers.ml)(line 1788))((process xapi)(filename ocaml/xapi/xapi_vm_helpers.ml)(line 1652))((process xapi)(filename ocaml/xapi/message_forwarding.ml)(line 1740))((process xapi)(filename ocaml/xapi/rbac.ml)(line 229))((process xapi)(filename ocaml/xapi/rbac.ml)(line 239))((process xapi)(filename ocaml/xapi/server_helpers.ml)(line 78)))" }, "message": "NOT_SUPPORTED_DURING_UPGRADE()", "name": "XapiError", "stack": "XapiError: NOT_SUPPORTED_DURING_UPGRADE() at Function.wrap (file:///opt/xo/xo-builds/xen-orchestra-202512190914/packages/xen-api/_XapiError.mjs:16:12) at default (file:///opt/xo/xo-builds/xen-orchestra-202512190914/packages/xen-api/_getTaskResult.mjs:13:29) at Xapi._addRecordToCache (file:///opt/xo/xo-builds/xen-orchestra-202512190914/packages/xen-api/index.mjs:1078:24) at file:///opt/xo/xo-builds/xen-orchestra-202512190914/packages/xen-api/index.mjs:1112:14 at Array.forEach (<anonymous>) at Xapi._processEvents (file:///opt/xo/xo-builds/xen-orchestra-202512190914/packages/xen-api/index.mjs:1102:12) at Xapi._watchEvents (file:///opt/xo/xo-builds/xen-orchestra-202512190914/packages/xen-api/index.mjs:1275:14)" I've tried restarting the toolstack on the pool master as well as the hosts. Any ideas?
  • 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
  • How to see the real progress of a backup

    4
    0 Votes
    4 Posts
    521 Views
    olivierlambertO
    We will discuss that internally Thanks for your feedback
  • User cannot see any servers - how to edit permissions

    6
    1
    0 Votes
    6 Posts
    1k Views
    olivierlambertO
    @kent You can ask for a trial so you can do it the time you need If you use XO from the sources, you will have the feature for free (but without support/updater and such)
  • XOA - VM-console on iPhone - no keyboard

    7
    0 Votes
    7 Posts
    1k Views
    MathieuRAM
    At first glance, it does not seem so easy. First, we will implement this feature in XO Lite (soon). We will then see if there is a trivial way to adapt the changes in XO5
  • Missing vhd after a possibly failed migration

    4
    1
    0 Votes
    4 Posts
    786 Views
    G
    This was ultimately traced to a currupted metadata on the VHD and to a stuck tapdisk process on the host where the VM was running. Solved thanks to a very persistent member of support. Thanks Jon!
  • Want to compare insecure_nbd but doesn't seem to work (secure does)

    26
    0 Votes
    26 Posts
    11k Views
    florentF
    @sluflyer06 the warning on XO is to discourage the mass. But you can really try you can make a config.toml file in ~/.config/xo-server/config.*.toml , it should be loaded , and won't be changed by an XO update . https://github.com/JsCommunity/app-conf
  • Google Sign-in stopped working "internal server error" (log attached)

    Solved
    12
    0 Votes
    12 Posts
    1k Views
    S
    @HeMaN this may have actually worked... In etc/network/interfaces The primary network interface allow-hotplug eth0 iface eth0 inet dhcp This is an autoconfigured IPv6 interface iface eth0 inet6 auto post-up route add default via 10.10.10.1 dev eth0 auto eth1 iface eth1 inet static address 10.10.5.188 post-up route del default dev eth1
  • How to configure Teleport App service for XO web UI?

    8
    0 Votes
    8 Posts
    2k Views
    olivierlambertO
    Then I don't see why it would be a XO problem FYI, we use JSON-RPC over websockets. Hopefully, someone at Teleport community would be able to pinpoint the problem
  • SR not working: stale NFS handle

    2
    0 Votes
    2 Posts
    437 Views
    I
    @djingo Have you made any config changes to unraid? That will often make nfs go stale.
  • Template usage doc

    2
    0 Votes
    2 Posts
    153 Views
    olivierlambertO
    Hi, In XO Hub, you already have a Debian 11 which is Cloudinit ready This is more a Cloudinit question BTW, you should ask their community. Frankly, Cloudinit doc isn't great and many things changed a lot
  • VM console borks with "Alt Gr" key

    8
    0 Votes
    8 Posts
    3k Views
    K
    @olivierlambert I can confirm: This issue is solved in XO Lite, but still present in XOA.
  • What are these 34+ tasks - going 5+ hours

    4
    1
    0 Votes
    4 Posts
    423 Views
    K
    Restarting the toolstack on AHP101 (which was the pool master) cleared the tasks. Hopefully no long term side effects
  • Changing the backup name

    6
    0 Votes
    6 Posts
    923 Views
    julien-fJ
    @mauzilla There is no easy way to achieve that, it requires updating a number of other_config entries manually. If you have a paid subscription, open a support ticket and I'll take care of it for you
  • Delta backups: Restore issue

    Solved
    4
    0 Votes
    4 Posts
    695 Views
    A
    @MrNaz It merges the past delta backup into the past full backup. Then it does a delta backup..... then you repeat.... Since you only keep one copy it just keeps merging the delta into the full backup. The delta backup depends on the old full backup existing and being correct. When it does a "full backup", it does a full backup of the data not just a delta (the changes). That way it does not merge the new full backup into the old full backup (or depend upon any old backups). Doing a full backup is a good checkpoint in case the old data (full or deltas) is corrupted. So having the retention set to 1 basically means you only have the most current backup saved. With backups every 12 hours you might want to set the retention to 20 so you have about 10 days of backups and every 5 days (10 backups) it will do a full backup. Or set it higher if you have more backup space.
  • 0 Votes
    7 Posts
    515 Views
    T
    @Danp Thanks RAM was problem. There was only 1.5GB, which was default value with XCP-ng center. Now it compiled successfully with 4GB. [image: 1684340422417-28e1c460-9d67-44b4-b018-96d1b9531bc7-obraz.png]
  • Remove/Reset TOTP 2FA

    mfa 2fa totp
    5
    0 Votes
    5 Posts
    932 Views
    DanpD
    Another option is to add a new admin user using xo-cli. Then login to XO as the new user and clear the OTP for the existing user.
  • Advanced Live Telemetry - Cluster-Wide

    2
    0 Votes
    2 Posts
    352 Views
    olivierlambertO
    Hi, No easily, no (at XCP-ng level at least). Maybe in the future with Open metrics everywhere. You can already track a VM metrics whatever they move to by having VM metrics from within the VM itself (eg VM is sending its metrics via netdata to a central netdata that will store them in Prometheus for example).
  • Boot after restore - excluded swap

    6
    0 Votes
    6 Posts
    532 Views
    olivierlambertO
    XO doesn't have access to the VM content so it's not possible at the moment.
  • Cannot use cloudConfig while creating VM with RPC call

    Solved
    23
    0 Votes
    23 Posts
    7k Views
    TheiLLeniumStudiosT
    @julien-f The problem seems to be fixed now! Thank you for the fix
  • Xen-Orchestra broken after rollback

    8
    0 Votes
    8 Posts
    2k Views
    M
    So I'm very very sorry for digging this up; I had this XO installation halted for a while wanted to come back to it. In the meanwhile the resolution for the error presented on the initial post: 2022-09-22T10:50:18.823Z xo:xo-server ERROR unhandled error event { error: Error: connect ECONNREFUSED ::1:6379 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16) at TCPConnectWrap.callbackTrampoline (node:internal/async_hooks:130:17) { errno: -111, code: 'ECONNREFUSED', syscall: 'connect', address: '::1', port: 6379 } } Solution: Edit /etc/redis.conf; Comment the bind directive; Save, restart redis, done.
  • Unable to convert VM to Template in Xen Orchestra ( VBD_IS_EMPTY )

    Solved
    11
    0 Votes
    11 Posts
    2k Views
    julien-fJ
    @josh383451 The bug was fixed 3 days ago: https://github.com/vatesfr/xen-orchestra/commit/73d88cc5f1a5458c68e6935a9d5a9240616007b1 0 julien-f committed to vatesfr/xen-orchestra fix(xo-server/vm.convertToTemplate): handle VBD_IS_EMPTY (#6808) Fixes https://xcp-ng.org/forum/post/61653