Subcategories

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

    462 Topics
    4k Posts
    K
    @dinhngtu Thanks for the fast response, as always.
  • 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
  • XOA import script failing silently

    6
    0 Votes
    6 Posts
    1k Views
    olivierlambertO
    Hi! The new standard way to import is here: https://xen-orchestra.com/#!/xoa Let me know if you have any issue. It's still in beta yet, and we got one small issue to fix (it won't fetch the XO username/password, so it's still admin@admin.net / admin)
  • What is miss in XO and What i like and What I like to have ;-)

    3
    0 Votes
    3 Posts
    563 Views
    A
    THX Oliver I will try it soon more like XO-CLI
  • XOSAN - few questions :)

    4
    0 Votes
    4 Posts
    2k Views
    olivierlambertO
    Technically everything is possible (even adding disk) but not with the XOSAN UI. If you want more flexibility, I suggest you wait for XOSANv2.
  • Migrate VM with a private network to another host.

    7
    0 Votes
    7 Posts
    3k Views
    olivierlambertO
    Advanced tab of the VM view, "Start on…" button. Cross server private network will be a Xen Orchestra plugin for our next release.
  • After started CR backup I cannot open XOA web page

    5
    1
    0 Votes
    5 Posts
    702 Views
    julien-fJ
    @olivierlambert If you're talking about the merge, yes it's done in separate threads.
  • Continous replication - testing - start replicated VM

    2
    2
    0 Votes
    2 Posts
    396 Views
    olivierlambertO
    That's normal. If you boot the replicated VMs, then blocks will be changed. It mean no further delta replication will work on this VM. Force boot it if you lost the original VM and you don't care about delta toward the copy anymore. If you just want to test the VM without doing a new full (breaking the delta chain), boot with a copy. I think I explained that in this video: https://www.youtube.com/watch?v=FfUqIwT8KzI That's a display glitch.
  • Wrong time on XOA

    7
    0 Votes
    7 Posts
    5k Views
    olivierlambertO
    It's tzdata
  • host.call_plugin?

    2
    0 Votes
    2 Posts
    1k Views
    olivierlambertO
    It's everytime a XAPI plugin is called. Eg the update plugin is called regularly and there is other plugins. So it's OK
  • Error when migrate with XOA

    3
    0 Votes
    3 Posts
    1k Views
    olivierlambertO
    Ah yes, when you migrate, unmount your CD drive, sometimes it causes issues!
  • This topic is deleted!

    2
    0 Votes
    2 Posts
    2 Views
    No one has replied
  • Importing VMs all with same mac-address

    Moved
    7
    0 Votes
    7 Posts
    2k Views
    ?
    @borzel sweet.
  • This topic is deleted!

    1
    1
    0 Votes
    1 Posts
    4 Views
    No one has replied
  • "Cannot GET /" Error after update

    11
    1
    0 Votes
    11 Posts
    4k Views
    P
    In case someone ran into the same problem here is how I solved it. I had a feeling this was http mounts issue. I checked and looks like during update process the .xo-server.toml got deleted. I copied the sample one from the /opt/xen-orchestra/packages/xo-server/sample.config.toml , edited the http.mount and bob's your uncle. I have a feeling this has something to do with the format of that file change. When I originally built from source the file has a slightly different syntax and it was called .xo-server.yaml. At least according tot he directions I used to build. In any case its all back to normal now. Thanks you everyone for your help.
  • Try to import .ova

    26
    0 Votes
    26 Posts
    11k Views
    olivierlambertO
    Thanks, this way we'll have a way to understand what's wrong with this OVA, if it's something really specific or a VMWare way to make something we didn't expected
  • Self-Service not showing assigned IP pool

    1
    0 Votes
    1 Posts
    312 Views
    No one has replied
  • xoa, xoa-updater ignore LC variables

    utf8 xoa-updater xoa
    9
    0 Votes
    9 Posts
    2k Views
    julien-fJ
    Yes, I know this is not exclusive to C, but there are some facilities to handle this, that are, as far as I know, not available in Node.
  • 0 Votes
    2 Posts
    1k Views
    borzelB
    @MajorTom I saw it on my XenOrchestra's and wondered also
  • Self-Service moving VMs from one to the other

    2
    0 Votes
    2 Posts
    467 Views
    borzelB
    @hitechhillbilly yes it does you can do it live or with a shutdown VM
  • free space of backup drive reported incorrect

    5
    0 Votes
    5 Posts
    2k Views
    P
    that's relatively easy to explain, only the naming is doubled: the backup-hdd are local disks raid1 in xcp-ng and there brought to xcp-ng as a local "vmbackup" volume, called vmbackup on xcp-ng-volume a disk is created with the name "backup_raid1_1tb" and connected as 2nd disk (xvdb) to XO [image: 1559158139829-ab68fa1c-49a8-4d15-afcf-ecdc8bcd9d04-grafik-resized.png] to make the disk available for backup-usage the disk xvdb is mounted via "remote" as a local now usage for backup-ng is possible, but the usage is not xo_disks
  • Deleting old delta backups.

    2
    0 Votes
    2 Posts
    1k Views
    olivierlambertO
    Yes, you can safely remove them.