1. Home
  2. Xen Orchestra

Subcategories

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

    455 Topics
    3k Posts
    J
    I've got my OPNsense (FreeBSD) router running in a VM on XCP, and it does have the xe-guest-utilities installed. I'm trying to figure out an issue on one of the interfaces, and I noticed a weird discrepancy in XO with this VM. The MAC addresses and such for the interfaces being used by the VM are all off. It seems that VIF #0 is the only one coming up correctly. Unfortunately, I don't think the FreeBSD or OPNsense teams have a maintainer for the xe-guest-utilities package, and so what they distribute is showing as 6.2.1-76888 in XO. [image: 1773276971518-xoa_guest_discrepancies.png] I don't know if this is what is causing my network issue, but I thought it strange.

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

    101 Topics
    840 Posts
    olivierlambertO
    That's a very good question, let me ask internally. Ping @pdonias he might know the answer

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

    475 Topics
    5k Posts
    P
    I did a rollback to 5bdd7 and got the date back and also delta

  • Everything related to Xen Orchestra's REST API

    82 Topics
    613 Posts
    K
    After updating to XCP-ng 8.3 (March 2026), IPMI / iDRAC information fails in both XO5 stable and XO6 stable (built from sources). It is thrown a XENAPI_PLUGIN_FAILURE log line for failure of the "ipmitool lan print" which works fine on the (DELL) node(s). These are old PowerEdge R430 and R810 with iDRAC versions 6 and 8 and worked well before the upgrade, so I guess tihis may be due to a XAPI command failing. Worth mentioning for this nice-to have feature.

  • 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
  • ?

    Importing VMs all with same mac-address

    Moved
    7
    0 Votes
    7 Posts
    2k Views
    ?
    @borzel sweet.
  • SoarinS

    This topic is deleted!

    1
    1
    0 Votes
    1 Posts
    4 Views
    No one has replied
  • P

    "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
  • H

    Self-Service not showing assigned IP pool

    1
    0 Votes
    1 Posts
    298 Views
    No one has replied
  • MajorTomM

    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.
  • MajorTomM

    xo-server: Warning: connect.session() MemoryStore is not designed for a production environment, as it will leak memory, and will not scale past a single process.

    memory leak xoa
    2
    0 Votes
    2 Posts
    1k Views
    borzelB
    @MajorTom I saw it on my XenOrchestra's and wondered also
  • H

    Self-Service moving VMs from one to the other

    2
    0 Votes
    2 Posts
    442 Views
    borzelB
    @hitechhillbilly yes it does you can do it live or with a shutdown VM
  • P

    free space of backup drive reported incorrect

    5
    0 Votes
    5 Posts
    1k 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
  • D

    Deleting old delta backups.

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

    xoa - host restart, random DR vms are UP!

    7
    1
    0 Votes
    7 Posts
    1k Views
    akurzawaA
    I've replied on github. For sure the VMs should not boot. Of course the source vm has autopower on parameter becouse it's needed. The problem is big: DR copy of Second Active Directory server is up.... for sure I can expect AD problems in a while... [image: 1558999805954-724808f6-fc82-4487-9f87-4d0291fc3e92-image.png] Autopower on is set up: [image: 1558999897310-e4b71a2e-17cd-4e5f-a863-77f693249847-image.png]
  • B

    XOA Update patches fails

    Solved
    9
    1
    0 Votes
    9 Posts
    3k Views
    olivierlambertO
    That's why I thought. NEVER enable base repo. If you want a package from their, just enable it during the yum install command line.
  • B

    Stuck on Importing XOA VM....

    Solved
    4
    1
    0 Votes
    4 Posts
    2k Views
    olivierlambertO
    Okay thanks. Note that with XCP-ng 8.0, it will be even easier to deploy XOA, directly from the host HTTP URL "mini website".
  • D

    XO from the sources - Something in the pages is missing

    19
    1
    0 Votes
    19 Posts
    3k Views
    DanpD
    @pdonias Thanks for confirming that this issue wasn't caused by the use of a 3rd party script.
  • J

    Backup-NG daily delta issue: footer1 !== footer2

    2
    0 Votes
    2 Posts
    487 Views
    olivierlambertO
    Hi, Before reporting on issues when you use XO from the sources, you must always fetch the latest code available on GitHub. Because it's likely some issues are fixed since then. Please upgrade, and come back if the problem persists
  • akurzawaA

    No manifest found for stable channel.

    4
    0 Votes
    4 Posts
    464 Views
    pdoniasP
    We're deploying support for the incoming release channels and there was an issue with that.
  • bradtriemB

    A Big Thank You

    2
    9 Votes
    2 Posts
    547 Views
    olivierlambertO
    Hi Brad, From the whole team: thanks a LOT. It's really cool to hear your feedback Enjoy XOA/XCP-ng!
  • akurzawaA

    xoa password change bug - to verify

    10
    0 Votes
    10 Posts
    2k Views
    akurzawaA
    Will do. Done.
  • ForzaF

    Moved a VDI to a new SR, but something is left behind?

    8
    1
    0 Votes
    8 Posts
    2k Views
    olivierlambertO
    Likely orphaned VDIs. Removing them should fix coalesce.
  • akurzawaA

    Backup: IMPORT_ERROR_PREMATURE_EOF()

    6
    0 Votes
    6 Posts
    1k Views
    olivierlambertO
    Okay so maybe there is a race condition somewhere with zstd (gut feeling, about premature EOF and using ZSTD). @johnelse what do you think? Do you need better logs?