1. Home
  2. Xen Orchestra

Subcategories

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

    363 Topics
    3k Posts
    dthenotD
    @Razor_648 While I was writing my previous message, I have been reminded that there are also issues with LVHDoISCSI SR and CBT, you should disable CBT on your backup job and on all VDI on the SR. It might help with the issue.

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

    90 Topics
    766 Posts
    D
    @Danp said in Advanced VM settings Logs: Hi Dustin, Yes... these types of actions are recorded in the Audit log (Settings > Audit) if you have access to this feature and have enabled it. Dan Perfect, thanks!

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

    368 Topics
    4k Posts
    olivierlambertO
    So that explains it then Free BSD boots and since the kernel loads successfully the PV drivers, it's fine by us.

  • Everything related to Xen Orchestra's REST API

    66 Topics
    502 Posts
    lsouai-vatesL
    @StephenAOINS This endpoint is not currently present in our REST API swagger, but we do plan to add it to the list of endpoints. We are currently finalizing the migration of existing endpoints, the next step will be adding new ones. We will keep you informed when it is available. Feel free to come back to us if you want to learn more and follow our blog posts. have a good day

  • Terraform, Packer or any tool to do IaC

    33 Topics
    310 Posts
    A
    Hi, I'm currently testing deployments with pulumi using packer templates. So far the basics work as expected but I'm stuck on a setting issue that seems to affect both pulumi and terraform providers. As far as I know there is no way to set the memory as static or changing memory_min when creating a VM from a template. The template was created with 1cpu and 2GB of RAM [image: 1752573420785-screenshot-2025-07-15-at-11.56.01.png] The VM created from this template using pulumi was assigned 2cpus and 4GB of RAM, however this only sets memory_max [image: 1752573490942-screenshot-2025-07-15-at-11.56.21.png] I found the following post that talks about this: https://xcp-ng.org/forum/topic/5628/xenorchestra-with-terraform and also the folllowing github issue https://github.com/vatesfr/terraform-provider-xenorchestra/issues/211 Manually setting the memory limits after VM creation defeats the purpose of automation. I suppose that implementing those settings in the relevant providers is a core feature. In most cases, VMs need static memory limits. In the meantime, is there any workaround that I should investigate or anything that I missed ? slax81 created this issue in vatesfr/terraform-provider-xenorchestra open Dynamic memory control #211
Log in to post
Load new posts
  • akurzawaA

    Continous replication - testing - start replicated VM

    2
    2
    0 Votes
    2 Posts
    222 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.
  • akurzawaA

    Wrong time on XOA

    7
    0 Votes
    7 Posts
    4k Views
    olivierlambertO
    It's tzdata
  • ?

    host.call_plugin?

    2
    0 Votes
    2 Posts
    888 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
    751 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
    1k 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
    3k 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
    8k 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
    248 Views
    No one has replied
  • MajorTomM

    xoa, xoa-updater ignore LC variables

    utf8 xoa-updater xoa
    9
    0 Votes
    9 Posts
    1k 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
    926 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
    334 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
    956 Views
    olivierlambertO
    Yes, you can safely remove them.
  • akurzawaA

    xoa - host restart, random DR vms are UP!

    7
    1
    0 Votes
    7 Posts
    620 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
    2k 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
    2k 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
    338 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