1. Home
  2. Xen Orchestra

Subcategories

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

    463 Topics
    4k Posts
    P
    @delacosta456 said: the pool host maximum limit is 3200% right right

  • ACLs, Self-service, Cloud-init, Load balancing...

    102 Topics
    853 Posts
    I
    @simonp - Can you reshare the dashboards. The link says json is not available for any of these dashboards,

  • All XO backup features: full and incremental, replication, mirrors...

    497 Topics
    5k Posts
    A
    So the scheduled backup at 1pm this afternoon ran with no issue. As stated previously the Coalesces are adding now now show 2 for vm. edit - Apr 21 11:22:55 xo-ce xo-server[15617]: }, Apr 21 11:22:55 xo-ce xo-server[15617]: summary: { duration: '6m', cpuUsage: '4%', memoryUsage: '29.01 MiB' } Apr 21 11:22:55 xo-ce xo-server[15617]: } Apr 21 13:00:00 xo-ce xo-server[16924]: 2026-04-21T17:00:00.320Z xo:backups:worker INFO starting backup Apr 21 13:00:00 xo-ce sudo[16938]: xo-service : PWD=/opt/xen-orchestra/packages/xo-server ; USER=root ; COMMAND=/usr/bin/mount -o -t nf> Apr 21 13:00:00 xo-ce sudo[16938]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=996) Apr 21 13:00:00 xo-ce sudo[16938]: pam_unix(sudo:session): session closed for user root Apr 21 13:00:06 xo-ce xo-server[16924]: 2026-04-21T17:00:06.941Z xo:backups:MixinBackupWriter INFO deleting unused VHD { Apr 21 13:00:06 xo-ce xo-server[16924]: path: '/xo-vm-backups/138538a8-ef52-4d0a-4433-5ebb31d7e152/vdis/9f7daac4-80a1-41f9-8af0-99b6fe> Apr 21 13:00:06 xo-ce xo-server[16924]: } Apr 21 13:00:19 xo-ce xo-server[16924]: 2026-04-21T17:00:19.536Z xo:backups:MixinBackupWriter INFO deleting unused VHD { Apr 21 13:00:19 xo-ce xo-server[16924]: path: '/xo-vm-backups/6d733582-0728-b67c-084b-56abe6047bfc/vdis/9f7daac4-80a1-41f9-8af0-99b6fe> Apr 21 13:00:19 xo-ce xo-server[16924]: } Apr 21 13:01:23 xo-ce xo-server[16924]: 2026-04-21T17:01:23.971Z xo:backups:worker INFO backup has ended Apr 21 13:01:23 xo-ce sudo[16971]: xo-service : PWD=/opt/xen-orchestra/packages/xo-server ; USER=root ; COMMAND=/usr/bin/umount /run/xo-> Apr 21 13:01:23 xo-ce sudo[16971]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=996) Apr 21 13:01:23 xo-ce sudo[16971]: pam_unix(sudo:session): session closed for user root Apr 21 13:01:24 xo-ce xo-server[16924]: 2026-04-21T17:01:24.029Z xo:backups:worker INFO process will exit { Apr 21 13:01:24 xo-ce xo-server[16924]: duration: 83708608, Apr 21 13:01:24 xo-ce xo-server[16924]: exitCode: 0, Apr 21 13:01:24 xo-ce xo-server[16924]: resourceUsage: { Apr 21 13:01:24 xo-ce xo-server[16924]: userCPUTime: 31147905, Apr 21 13:01:24 xo-ce xo-server[16924]: systemCPUTime: 14319055, Apr 21 13:01:24 xo-ce xo-server[16924]: maxRSS: 65888, Apr 21 13:01:24 xo-ce xo-server[16924]: sharedMemorySize: 0, Apr 21 13:01:24 xo-ce xo-server[16924]: unsharedDataSize: 0, Apr 21 13:01:24 xo-ce xo-server[16924]: unsharedStackSize: 0, Apr 21 13:01:24 xo-ce xo-server[16924]: minorPageFault: 367979, Apr 21 13:01:24 xo-ce xo-server[16924]: majorPageFault: 1, Apr 21 13:01:24 xo-ce xo-server[16924]: swappedOut: 0, Apr 21 13:01:24 xo-ce xo-server[16924]: fsRead: 5648, Apr 21 13:01:24 xo-ce xo-server[16924]: fsWrite: 16101272, Apr 21 13:01:24 xo-ce xo-server[16924]: ipcSent: 0, Apr 21 13:01:24 xo-ce xo-server[16924]: ipcReceived: 0, Apr 21 13:01:24 xo-ce xo-server[16924]: signalsCount: 0, Apr 21 13:01:24 xo-ce xo-server[16924]: voluntaryContextSwitches: 65983, Apr 21 13:01:24 xo-ce xo-server[16924]: involuntaryContextSwitches: 7745 Apr 21 13:01:24 xo-ce xo-server[16924]: }, Apr 21 13:01:24 xo-ce xo-server[16924]: summary: { duration: '1m', cpuUsage: '54%', memoryUsage: '64.34 MiB' } Apr 21 13:01:24 xo-ce xo-server[16924]: } lines 617-656/656 (END)

  • Everything related to Xen Orchestra's REST API

    84 Topics
    630 Posts
    K
    @olivierlambert & @mathieura thanks for the speedy response. Duly noted, very much appreciated.

  • Terraform, Packer or any tool to do IaC

    49 Topics
    463 Posts
    dalemD
    Version 1.4.0 is released: https://codeberg.org/NiXOA/system/releases/tag/v1.4.0 It includes significant changes and improvements, including: dedicated getting started section, migration to valkey, only needing to clone system, and helper scripts. the xen-orchestra-ce nixpkg now references the libvhdi nixpkg, and the core flake now references and pulls from the xen-orchestra-ce repo as an overlay. System (the user input flake) now uses the Core repo as an overlay, reducing the need to clone both locally AND allowing system to pull new updates and releases from core. XO, and libvhdi as needed. The next goal is: Make an xsconsole-like TUI Automate package updates for libvhdi and xen-orchestra-ce using CI/CD pipelines Submit libvhdi and xen-orchestra-ce as official nixpkgs
Log in to post
Load new posts
  • NoidenN

    Metadata Backup to Backblaze S3 compatible will not work

    5
    0 Votes
    5 Posts
    1k Views
    I
    Having the same issue here with metadata backups, tried Backblaze bucket and Amazon. Also the vm backups to S3 are failing usually with VDI_IO_ERROR(Device I/O errors) or "Error calling AWS.S3.upload: socket hang up" (but working to NAS). Is there somebody who made backups to S3 to work somehow?
  • capeschoolsC

    Location of Backups?

    3
    0 Votes
    3 Posts
    888 Views
    capeschoolsC
    @olivierlambert Thanks!
  • capeschoolsC

    Update Failed : Command failed: npm uninstall -g --silent xen-orchestra-upload-ova

    5
    0 Votes
    5 Posts
    971 Views
    capeschoolsC
    @olivierlambert Okay no problem!
  • S

    Move VM to a host containing a CR vm

    6
    0 Votes
    6 Posts
    1k Views
    DanpD
    @shorian No worries. I just figured the full error log would be beneficial to @olivierlambert and team if they review this thread. Edit: This thread seems related
  • P

    Kuberenets cluster recipe not happy

    49
    0 Votes
    49 Posts
    27k Views
    olivierlambertO
    Thanks for the feedback @mathiashedberg !
  • M

    New install some people can't login

    1
    0 Votes
    1 Posts
    527 Views
    No one has replied
  • M

    New install can't add remote NFS

    Solved
    3
    0 Votes
    3 Posts
    919 Views
    M
    That was it you're awesome. You can mark it as solved.
  • M

    XOCE Yarn Start Error code 1

    Solved
    13
    0 Votes
    13 Posts
    2k Views
    M
    Again thanks everyone. you can mark this as solved. The step I was missing was the config step. $ cd packages/xo-server $ mkdir -p ~/.config/xo-server $ cp sample.config.toml ~/.config/xo-server/config.toml
  • L

    XO Installation on an offline system

    17
    0 Votes
    17 Posts
    5k Views
    L
    @olivierlambert Thanks
  • D

    Scheduled snapshots only visible to self-service user when they're an admin *

    5
    0 Votes
    5 Posts
    815 Views
    pdoniasP
    @duxepu Ok, this is weird, I'm not able to reproduce that and I don't see how it's possible. Could you check a few things? from an admin point of view, at the bottom of the VM's advanced tab, please check that the user has Admin ACLs on the VM from the user's point of view, when you're on the snapshots tab, open the browser console (press F12 > Console tab) and check if there are any errors do you have this issue with all the users of all your Self Service groups or is it more specific? Thanks!
  • X

    Bizarre Error during backup process (from the sources, 20.04)

    12
    0 Votes
    12 Posts
    2k Views
    DanpD
    Yesterday I updated to the latest sources and my backup ran successfully, so it appears that this issue is resolved. @carlosfrederico You'll need to switch back to the master branch before your normal update routine will work.
  • S

    Debian cloud template for XenServer Default Password

    6
    0 Votes
    6 Posts
    5k Views
    olivierlambertO
    There's no root password. Use sudo -s
  • grapesmcG

    Server can no longer connect after crash

    Solved pool server
    5
    0 Votes
    5 Posts
    1k Views
    grapesmcG
    @olivierlambert FYI turned out to be a networking issue that had nothing to do with the server itself. I'm still getting to the bottom of what exactly the cause was, and will update here once I do just in case someone else runs into this. Thanks again. And thanks for the awesome software. ! -Rob
  • pwasonP

    Uncertain state of VM tools

    7
    0 Votes
    7 Posts
    1k Views
    olivierlambertO
    No, there's no need to upgrade VM tools when you upgrade the host. You can keep old tools, it will work fine.
  • D

    VDI is not available Error

    4
    0 Votes
    4 Posts
    3k Views
    F
    @dan2462 Did you get a resolution to your VDI issue? I have a similar problem as it seems hosts are locking up the VDI's on my shared iscsi storage and if they are shutdown and I try to boot them on an alternate host, I get the VDI not available error.
  • M

    HOST_NOT_ENOUGH_FREE_MEMORY

    9
    0 Votes
    9 Posts
    3k Views
    M
    @olivierlambert Thanks for the quick feedback!
  • X

    What ordering does XO trigger backups in?

    3
    0 Votes
    3 Posts
    664 Views
    badrAZB
    Hi @xo-g , We don't use any specific order to pick the VMs to backup.
  • iverlaekI

    How to implement the perfect backup strategy with Xen Orchestra?

    1
    0 Votes
    1 Posts
    2k Views
    No one has replied
  • M

    Single backup job two locations

    2
    0 Votes
    2 Posts
    460 Views
    olivierlambertO
    You can have one job with 2 remotes. Or a job with backup and DR at the same time.
  • M

    SAML, automatic user generation

    5
    0 Votes
    5 Posts
    2k Views
    pdoniasP
    @mrbaz Thanks for the detailed feedback! If XO had a way of pulling the user's group information and only allowing those in a certain group to have authorization to XO to have their accounts automatically generated, that would work too. That wouldn't be trivial to implement with our current plugin system. But as you said, a user that logs into XO isn't able to do anything without granting them permissions first. Also, if this is still a concern for you, you can disable user auto-generation in xo-server configuration by adding this line: createUserOnFirstSignin = false However, you'd then have to create the users manually before they can log in. the issue still stands that I can't put a user into a group or assign ACLs until after they have signed in for the first time. I agree but I'm not sure what a good solution to this would be. If we add an option to import all the users at once, it could mean importing a lot of users for some companies, even if many of those users would never actually log in later.