1. Home
  2. Xen Orchestra

Subcategories

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

    473 Topics
    4k Posts
    olivierlambertO
    Hi, IP conflict?

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

    104 Topics
    863 Posts
    laszlobortelL
    @florent Thanks for your reply! We have started to migrate thousands of VMs, so disk transfer speed is important for us.. We will also do our detailed tests soon with different threads setting and publish it here. I think threads=1 is a good and logical default, but not efficient. Others might complain if you set it to a higher value. Configuration option would be a real good solution.

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

    512 Topics
    5k Posts
    P
    Hello forum! I recently begun mirroring my full backups to backblaze and I've been getting the error "maximum size allowed is (your minPartSize for the chunk)" [image: 1782755451515-e9df4605-45a6-494e-912c-6e48f50615ab-image.jpeg] This error was supposed to be fixed, earlier this year, but I'm still getting it. Actually PR #9396 might only fix direct backups and not mirror backups... I'm running xo built last week. Object lock is set to 0 at backblaze for the time being, but I plan to turn it whenr this problem is over. This may be caused because I'm mirroring from a local nfs remote (not encripted) to backcblaze remote (encripted) ? Maybe this scenario wasn't tested. Anyway, everytime I run the mirror job the larger VMs would fail and all VMs would show warnings about issues checking XVA: [image: 1782755859883-97d973ab-83b9-4981-917e-efb374c879c2-image.jpeg] I've just bumped minPartSize to 100 000 000 (following the recomendation from Backblaze and hope that the maximum size allowed error goes away, though the warnings will still be there. Thank you, Pedro

  • Everything related to Xen Orchestra's REST API

    86 Topics
    645 Posts
    J
    Hello I'm pulling stats for all VMs to understand CPU usage. We're a bit behind the curve in terms of XO versions, but these questions hopefully are still relevant. If using a granularity of days, the interval is set to 86400 (understandably) but the endTimestamp varies. Running this on June 9th @ ~1740 we get timestamps for both Mon Jun 8 01:00:00 AM BST 2026 and Tues Jun 9 01:00:00 AM BST 2026. Does this average across the day? Why is the timestamp 0100? Why would there be different timestamps between VMs (all are running) and does that mean that the figures are misaligned in the results? These are retrieved via curl and a bash script, a bit hacky, but for clarity the request is: ++ curl -X GET -s -H accept:application/json -b authenticationToken=[[REDACTED]] -o [[REDACTED]] 'https://[[REDACTED]]/rest/v0/vms/[[REDACTED]]/stats?granularity=days' Really keen to know if we can control the start and endtime, as well as provide a manual interval, as well as the aggregation strategy (min, max, average). Are any of these possible? Lastly, is cpuUsage the percentage as per the dashboard, but averaged over all CPUs? Thanks so much in advance. James

  • Terraform, Packer or any tool to do IaC

    51 Topics
    471 Posts
    poddingueP
    The Kubernetes CSI driver for Xen Orchestra just hit v0.4.0, and we want it on more real clusters before it reaches a stable release candidate. If you run Kubernetes on XCP-ng VMs, this is a good time to give it a proper workout. What's new in v0.4.0: Local-storage support Automatic pool-discovery fallback Kubernetes metadata now lives in Xen Orchestra VDI tags instead of the deprecated other_config. That change also drops the old requirement for Xen Orchestra 6.4 or newer, so the driver runs on more deployments now. ️ Read this before you upgrade. v0.4.0 is a breaking change. The Kubernetes metadata moved from other_config to VDI tags, so you must migrate before upgrading from v0.3.0. Do not upgrade in place: follow the v0.3.0 to v0.4.0 migration guide in the release notes, then move to v0.4.0. What helps us most is hearing how it behaves on your own setup: what works, what breaks, which storage backend you use, and which flavour of Kubernetes you run (k3s, full k8s, or something else). Edge cases on real clusters are the ones we don't see in our own testing. Where to report: start right here in this thread. It keeps everything visible to the community and lets others on the same setup jump in. If something turns out to be a reproducible bug, we'll move it to a GitHub issue on the repo so the team can track it to a fix. Release notes and migration guide: https://github.com/vatesfr/xenorchestra-csi-driver/releases/tag/v0.4.0
Log in to post
Load new posts
  • IndyJI

    Backing up to NFS share on ZFS

    9
    0 Votes
    9 Posts
    3k Views
    IndyJI
    @indyj The file restore issue was due to installing XO on FreeBSD (fine for VM restores, not file extraction). I then installed XO on Ubuntu 20, and this worked for restoring files from Linux VMs but not Windows VMs. Then I installed on CentOS 8 and had the same problem as Ubuntu. I then installed on Fedora 34 and everthing works fine.
  • A

    Backblaze B2 as a backup remote

    7
    0 Votes
    7 Posts
    2k Views
    olivierlambertO
    Just hold on for this month release
  • sheridancomputeS

    Automatic backup verification

    feature in backlog
    11
    1 Votes
    11 Posts
    3k Views
    julien-fJ
    Yes, it should be safe enough to try importing the backup, then starting the VM without network (ie VIFs) and see if it stays up for a few minutes. I think we could start by adding a manual feature and then see in a second step how we could automate it.
  • W

    XOCE Integration with OpenLDAP

    41
    0 Votes
    41 Posts
    18k Views
    olivierlambertO
    Also, the user will be created only on first connection. Maybe you are thinking about the plugin in a way that's not how it behave.
  • C

    Restored Backups Do Not Boot

    backup
    8
    0 Votes
    8 Posts
    2k Views
    olivierlambertO
    Sure, please keep us posted on your experiments If it's a bug, we'll have more info to be able to work on it!
  • A

    XOA Report

    3
    0 Votes
    3 Posts
    855 Views
    A
    @olivierlambert many thanks for the very quick response, it is indeed XO from sources. I think the burst explanation makes sense. Also, thanks for you and your teams continued development and support with both XCP-NG and XO.
  • tsettleT

    Backups failed after changing masters?

    6
    0 Votes
    6 Posts
    1k Views
    olivierlambertO
    Source: https://github.com/vatesfr/xen-orchestra/issues/5969 olivierlambert created this issue in vatesfr/xen-orchestra closed Save all associated host IPs to a pool and use them as fallback for XAPI connection #5969
  • B

    Lots of Tasks: Xapi#getResource /rrd_updates (on **masterhost**) 0%

    19
    0 Votes
    19 Posts
    4k Views
    stormiS
    And the IRC channel is #xcp-ng on oftc.net if you prefer IRC.
  • F

    Usage of job.run.Sequence

    6
    0 Votes
    6 Posts
    1k Views
    F
    Hi, thank you for your support. I was out of Office for two weeks and will test this soon. I will give you feedback. Regards, Torsten
  • D

    Jobs

    Solved
    5
    0 Votes
    5 Posts
    1k Views
    D
    Thank you for your help this is the solution i was searching for, I appriciate this much.
  • D

    Missing information in XOA 5.64 blog post

    4
    0 Votes
    4 Posts
    972 Views
    olivierlambertO
    What do you mean "how it works"? It's the same thing than before, just "isolated" from the rest, working in a... worker. And yes, the long run objective is the ability to run it as a service on the remote directly, reducing a lot the merge time (because latency is the worst enemy of merging).
  • ForzaF

    Backup does not work if one host in the pool is offline

    12
    0 Votes
    12 Posts
    2k Views
    ForzaF
    @olivierlambert said in Backup does not work if one host in the pool is offline: When you connect to a working, machine, yes it does But XAPI connection isn't persistent: it means, when the pool is disconnected, XO has no recollection whatsoever on who was the "real" master the last time it was connected. The only info we store is the IP address you entered in Settings/server. I agree, functionally speaking, it can be limiting in your case. A viable option would be to save all existing hosts IPs in the XO database, as fallback if we can't connect to the IP you entered. This is not a very common case, that's why it wasn't done before Looks like a good suggestion. Thanks. In my case I migrated everything from the poolmaster to the second host, then changed the second host to pool master, waited an hour and then shut down the old pool master (now just a pool member). XOA was online during the entire process and I had forgotten to check the server list.
  • V

    Overview of a logical allocation of thin provisioned SRs

    6
    2
    0 Votes
    6 Posts
    1k Views
    olivierlambertO
    That's because the effort to change this will be taken into account in XO 6 Alternatively, you can indeed contribute, this will be very welcome!
  • M

    Delta backup fails for specific vm with VDI chain error

    79
    0 Votes
    79 Posts
    28k Views
    M
    Hi ! We are experiencing these kind of problems because we activated Continous Replication and frequency was way too low. Now I want to eliminate all those files in the chain, can I do it manually from XCP-NG Center or XOA ? Thanks !!! [image: 1635327169557-c2aa1fb3-2ed2-41cf-b242-e2a23e6832e4-image.png]
  • T

    continuous replication job - no progress

    Solved
    21
    0 Votes
    21 Posts
    8k Views
    olivierlambertO
    Ping @julien-f and/or @fohdeesha
  • jedimarcusJ

    Netbox Debugging

    Solved
    9
    1
    0 Votes
    9 Posts
    3k Views
    jedimarcusJ
    @pdonias I did an update to Netbox 2.11.12 and it works now, so I don't need to tamper with my XOA.
  • P

    XCP host rebooted: VM's wont start anymore :-(

    40
    0 Votes
    40 Posts
    13k Views
    olivierlambertO
    It can't be done by XO, because XO is using XAPI to make all calls (there's no XAPI command to rename a file on the SR, also XO isn't connected via SSH, so there's 0 change it was caused by XO). So it was done manually at some point (check your host bash history).
  • C

    Clip Board Not Copying Text (Linux) Tools installed [Xen Orchestra]

    bugs in backlog
    6
    0 Votes
    6 Posts
    3k Views
    pdoniasP
    Thanks @cookie-eater2000, we'll take a look.
  • mauzillaM

    Allowing replicated server to start

    4
    0 Votes
    4 Posts
    748 Views
    olivierlambertO
    There's no issue nor restriction to replicate a shutdown VM. CR will work as long as the destination VM never booted (otherwise destination blocks will be modified, so you understand now why we should block boot except if you really know what you do )
  • M

    Error: footer1 !== footer2

    10
    0 Votes
    10 Posts
    2k Views
    M
    @julien-f said in Error: footer1 !== footer2: @markhewitt1978 In that case, please open a support ticket there and then, open a support tunnel for us to investigate Thanks. I shall run it one more time manually to make sure. And if it fails I’ll open a ticket Thanks.