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
  • Can I replicate between 2 different versions

    4
    0 Votes
    4 Posts
    513 Views
    mauzillaM
    The XO team is also bringing the magic!
  • Replication Backup failure

    3
    2
    0 Votes
    3 Posts
    555 Views
    GheppyG
    It's more work, but... you have to stop the VM and export them, delete the current SR (Local Storage), recreate SR (Local Storage) as local ext4 format import the VM back In this way you switch from LVM to ext4 and the space it needs will be small, not double the space
  • 0 Votes
    6 Posts
    1k Views
    DarkbeldinD
    @BigHeadBighetti Just make a snapshot And yes I know I already discuss this with XOA team to have a more obvoious warnin but you already have a "Are you sure you want to shutdown this VM?" even without the box checked
  • Control domain of Xcp-ng

    16
    1
    0 Votes
    16 Posts
    3k Views
    olivierlambertO
    https://xcp-ng.org/docs/troubleshooting.html is a good start to read. In your case, it's likely inside /var/log/SMlog
  • Troubleshooting Backups (in general)

    7
    2
    0 Votes
    7 Posts
    1k Views
    daveD
    @olivierlambert Yes, i will update and have a look if it changes the behaviour anyhow. "For the rest, it's hard to answer without digging more." That`t exactly was i was looking for: Any Information where i can dig deeper? I`m looking for logs or traces of errors or so. It is not that i just wan`t this particular problem to be solved In my limited understanding of interal processes i think somehow a backup process dies and xo-server does not report or recognize this. But shouldn`t it somehow?
  • ISO Import to Local Storage via XO Not Working

    5
    0 Votes
    5 Posts
    2k Views
    K
    @olivierlambert Oh nice, hope it's not too cold over there. It's 9AM over here in Maryland and a bit nippy but not too cold. Nope, no host or pool logs available (both are empty). Then again, I cleared all the alerts from the dashboard earlier this morning, so not sure if that's what wiped all the logs. I'm not too worried, as this is a testing environment so I'm using this host to do a lot of learning.
  • backup using http instead of https

    23
    0 Votes
    23 Posts
    6k Views
    florentF
    @KPS that is a second bug I will look into it this afternoon. edit : confirmed, I'm working on it
  • XOCE limit ?

    27
    2
    0 Votes
    27 Posts
    7k Views
    florentF
    @Gheppy I am not an expert on the network part but I can help on the NBD part We added some info in this PR https://github.com/vatesfr/xen-orchestra/pull/6596, it should be merged in this form or another in master in a few days. It will give the user more info on the NBD usage and the cause (misconfiguration, or network error) Then if XO ( or the proxy) can't connect to the host through the NBD (for example with a network filtering/ routing), it will fall back to the reliable (but non parallelizable) api call Finally , the backup done with NBD or the legacy api call will produce exactly the same data so they are compatibles, but using the same target (as in the same directory , same remote and same VMs) for multiple job can lead to complex support tickets with interesting race conditions. I would advise to only use the same remote/directory only if the backups jobs does not concern the same VMs fbeauchamp opened this pull request in vatesfr/xen-orchestra closed feat(@xen-orchestra/backups): more information on nbd backups #6596
  • S3 Remote with encryption: VHDFile implementation is not compatible

    11
    0 Votes
    11 Posts
    2k Views
    florentF
    @cdbessig that's strange Since S3 remote are only able to store blocks, the option is enforced on save ( without any uI) I tested locally and the options seems to be there. Can you show me a screenshot of the backup job configuration ?
  • Base Copy (No active VDI)

    vdi base copy remove
    4
    1
    0 Votes
    4 Posts
    2k Views
    olivierlambertO
    Remember that the point of pro support (to help and guide you to run this setup confidently in production).
  • VM won't start with internal error

    7
    0 Votes
    7 Posts
    1k Views
    DanpD
    What is your process for provisioning a VM? What template are you using?
  • XO reports wrong number of backups

    Solved
    11
    0 Votes
    11 Posts
    2k Views
    codesmakerC
    @julien-f Thanks a lot for the fast answer. I'll update to the latest version and test.
  • Importing OVA - “Device Already Exists”

    24
    0 Votes
    24 Posts
    8k Views
    planedropP
    @trent234 Interesting, good to know. I do know that XCP-ng only officially supports 7 network interfaces, so not really surprised by that. It supports more VHDs though so feel like I shouldn't be seeing this error.
  • XOCE - Config path

    10
    0 Votes
    10 Posts
    1k Views
    K
    @Gheppy I found my issue... The changes, I wanted to test have not been committed to "master-branch". After changing the branch, everything is clear... Thank you for your help!
  • 0 Votes
    7 Posts
    1k Views
    olivierlambertO
    +1, that's the way to go
  • error -104

    21
    0 Votes
    21 Posts
    8k Views
    P
    @tuxen No GPUs were removed. only 2 were added. The only PCIE item removed was a NIC but I didn't remove it from dom0 or assign it to any VMs, it was just in the system.
  • [XO-CE] job.Sequence error - invalid parameters

    xoce jobs
    3
    7
    0 Votes
    3 Posts
    819 Views
    julien-fJ
    I believe this is a known issue (https://github.com/vatesfr/xen-orchestra/issues/5973) that is unlikely to be fixed in XO5. We'll need to wait for @pdonias to be back from holidays to have more info on this. just-333 created this issue in vatesfr/xen-orchestra closed Error on vm.set from Jobs tab in XO web GUI #5973
  • Deleting snapshots and base copies

    18
    1
    0 Votes
    18 Posts
    6k Views
    S
    @sumansaha In summary , I've deleted Orphan VDIs from Dashboard->health . But in deletion, I've maintained the sequence of their age.It has taken 6 hours, though that depends on the VM size.
  • Show me your backup performance

    11
    0 Votes
    11 Posts
    950 Views
    olivierlambertO
    If you do a full every time, it's fine (use no retention or full every time)
  • How to delete unmanaged disks in local storage

    7
    0 Votes
    7 Posts
    4k Views
    olivierlambertO
    You can't delete a base copy. You need to understand how it works before doing dangerous operations. A base copy exists if there's a snapshot. If you have 0 snap and still base copy, it could be either: because the coalesce isn't finished because the coalesce doesn't work In both case, you have to take a look at your SMlog. If you have no idea about it, you should either get pro support or start to read the doc in more details You can start here: https://xcp-ng.org/docs/storage.html#coalesce