1. Home
  2. Xen Orchestra

Subcategories

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

    476 Topics
    4k Posts
    A
    @pkgw Planning an RPU as a whole is a nice idea in theory, but it's inherently designed to co-exist with normal pool management operations (you should still be able to migrate VMs between hosts B and C during it, or start new ones), we are not "pre-booking" memory and other resources for groups of VMs, otherwise it can quickly make the rest of the pool hard to manage while some VM migrations could still be far away. Regarding the narrower case - I'll note this down and see if we can improve things, thank you!

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

    105 Topics
    864 Posts
    M
    Is a centralized XOA server "managing" two remote Proxy-fronted XCP clusters supported with the SDN Controller Plugin? We are looking to deploy an architecture similar to this blog post from 2022: https://xen-orchestra.com/blog/xo-proxy-a-concrete-guide/

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

    515 Topics
    5k Posts
    poddingueP
    Thanks for checking. That's useful, even if it points away from where I was looking. Clocks within a second of each other means drift probably isn't your problem, and I'd guess the MST/UTC difference is just how dom0 displays it, though I'm not sure. What I keep coming back to is that your full backups fail while the delta jobs on the same hosts never do. That's the same split in https://github.com/vatesfr/xen-orchestra/issues/9181, where full backups hit BodyTimeoutError on VMs with big disks or a lot of free space and the deltas are fine. If your failing VMs look like that, your dates and the MST/UTC detail would do more good on that issue than buried in here. MajorP93 created this issue in vatesfr/xen-orchestra open Full backup fails on large VMs / VMs with lots of free disk space #9181

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

    What are these 34+ tasks - going 5+ hours

    4
    1
    0 Votes
    4 Posts
    651 Views
    K
    Restarting the toolstack on AHP101 (which was the pool master) cleared the tasks. Hopefully no long term side effects
  • mauzillaM

    Changing the backup name

    6
    0 Votes
    6 Posts
    1k Views
    julien-fJ
    @mauzilla There is no easy way to achieve that, it requires updating a number of other_config entries manually. If you have a paid subscription, open a support ticket and I'll take care of it for you
  • M

    Delta backups: Restore issue

    Solved
    4
    0 Votes
    4 Posts
    943 Views
    A
    @MrNaz It merges the past delta backup into the past full backup. Then it does a delta backup..... then you repeat.... Since you only keep one copy it just keeps merging the delta into the full backup. The delta backup depends on the old full backup existing and being correct. When it does a "full backup", it does a full backup of the data not just a delta (the changes). That way it does not merge the new full backup into the old full backup (or depend upon any old backups). Doing a full backup is a good checkpoint in case the old data (full or deltas) is corrupted. So having the retention set to 1 basically means you only have the most current backup saved. With backups every 12 hours you might want to set the retention to 20 so you have about 10 days of backups and every 5 days (10 backups) it will do a full backup. Or set it higher if you have more backup space.
  • T

    xo-web build from source, FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed

    Solved
    7
    1
    0 Votes
    7 Posts
    865 Views
    T
    @Danp Thanks RAM was problem. There was only 1.5GB, which was default value with XCP-ng center. Now it compiled successfully with 4GB. [image: 1684340422417-28e1c460-9d67-44b4-b018-96d1b9531bc7-obraz.png]
  • SchmalzTechS

    Remove/Reset TOTP 2FA

    mfa 2fa totp
    5
    0 Votes
    5 Posts
    1k Views
    DanpD
    Another option is to add a new admin user using xo-cli. Then login to XO as the new user and clear the OTP for the existing user.
  • K

    Advanced Live Telemetry - Cluster-Wide

    2
    0 Votes
    2 Posts
    460 Views
    olivierlambertO
    Hi, No easily, no (at XCP-ng level at least). Maybe in the future with Open metrics everywhere. You can already track a VM metrics whatever they move to by having VM metrics from within the VM itself (eg VM is sending its metrics via netdata to a central netdata that will store them in Prometheus for example).
  • K

    Boot after restore - excluded swap

    6
    0 Votes
    6 Posts
    771 Views
    olivierlambertO
    XO doesn't have access to the VM content so it's not possible at the moment.
  • sMteXS

    Cannot use cloudConfig while creating VM with RPC call

    Solved
    23
    0 Votes
    23 Posts
    9k Views
    TheiLLeniumStudiosT
    @julien-f The problem seems to be fixed now! Thank you for the fix
  • M

    Xen-Orchestra broken after rollback

    8
    0 Votes
    8 Posts
    3k Views
    M
    So I'm very very sorry for digging this up; I had this XO installation halted for a while wanted to come back to it. In the meanwhile the resolution for the error presented on the initial post: 2022-09-22T10:50:18.823Z xo:xo-server ERROR unhandled error event { error: Error: connect ECONNREFUSED ::1:6379 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16) at TCPConnectWrap.callbackTrampoline (node:internal/async_hooks:130:17) { errno: -111, code: 'ECONNREFUSED', syscall: 'connect', address: '::1', port: 6379 } } Solution: Edit /etc/redis.conf; Comment the bind directive; Save, restart redis, done.
  • brodiecyberB

    Unable to convert VM to Template in Xen Orchestra ( VBD_IS_EMPTY )

    Solved
    11
    0 Votes
    11 Posts
    3k Views
    julien-fJ
    @josh383451 The bug was fixed 3 days ago: https://github.com/vatesfr/xen-orchestra/commit/73d88cc5f1a5458c68e6935a9d5a9240616007b1 0 julien-f committed to vatesfr/xen-orchestra fix(xo-server/vm.convertToTemplate): handle VBD_IS_EMPTY (#6808) Fixes https://xcp-ng.org/forum/post/61653
  • bullerwinsB

    Continuous Replication health check fails

    Solved
    7
    2
    0 Votes
    7 Posts
    2k Views
    bullerwinsB
    Just updated to lastest commit https://github.com/vatesfr/xen-orchestra/commit/4bd5b38aeb9d063e9666e3a174944cbbfcb92721 It's fixed now. Working wonderfully. Thanks! [image: 1683882828176-603fbea0-1c07-45b8-a005-54c100a74663-image.png] 0 fbeauchamp committed to vatesfr/xen-orchestra fix(backups): fix health check task during CR (#6830) Fixes https://xcp-ng.org/forum/post/62073 `healthCheck` is launched after `cleanVm`, therefore it should be closing the parent task, not `cleanVm`.
  • S

    Cannot export OVAs

    Solved
    64
    0 Votes
    64 Posts
    27k Views
    olivierlambertO
    Thanks for your feedback lads!
  • escape222E

    Option to Create Host only Private Network

    4
    1
    0 Votes
    4 Posts
    2k Views
    olivierlambertO
    Then it's a bug Pinging @pdonias or @julien-f
  • dumarjoD

    Import from vmware esxi 6.0 or 6.5

    13
    0 Votes
    13 Posts
    3k Views
    M
    @florent Tunnel ID sent via chat. Thank you for your help.
  • bullerwinsB

    XOA Proxy Error when updating

    5
    1
    0 Votes
    5 Posts
    2k Views
    bullerwinsB
    @julien-f said in XOA Proxy Error when updating: @bullerwins XO Proxy Appliance deployment is not supported in XO built from sources. my bad, it used to work a few months back I believe @olivierlambert said in XOA Proxy Error when updating: I missed that in the original message, indeed FYI @bullerwins there's no such thing as XOA built from sources, you have either: XOA is Xen Orchestra virtual Appliance, that's the VM we distribute with pro support and QA/stable channel, updater and such XO from the sources is from Github, without pro support but community support, no QA no stable version, no udpater and such Thanks, I got confused with the naming, I'm using the second option. As a workaround I used a VPN to manage the remote XCP-ng host, thanks!
  • F

    Kubernetes cluster recipes not seeing nodes

    43
    0 Votes
    43 Posts
    31k Views
    F
    @Raymondello you right, the issue is from the storage and I am looking into that. Thank you for sharing the UAT Testing, I didn't know about it
  • N

    Fail2Ban for failed Xo-Web-Logins

    Solved
    16
    0 Votes
    16 Posts
    3k Views
    konsultanerK
    Found the issue. I used the service from the repo like this: But I had to replace @BINDIR@ to /usr/bin. [Unit] Description=Fail2Ban Service Documentation=man:fail2ban(1) After=network.target iptables.service firewalld.service ip6tables.service ipset.service nftables.service PartOf=iptables.service firewalld.service ip6tables.service ipset.service nftables.service [Service] Type=simple Environment="PYTHONNOUSERSITE=1" ExecStartPre=/bin/mkdir -p /run/fail2ban ExecStart=/usr/bin/fail2ban-server -xf start # if should be logged in systemd journal, use following line or set logtarget to sysout in fail2ban.local # ExecStart=/usr/bin/fail2ban-server -xf --logtarget=sysout start ExecStop=/usr/bin/fail2ban-client stop ExecReload=/usr/bin/fail2ban-client reload PIDFile=/run/fail2ban/fail2ban.pid Restart=on-failure RestartPreventExitStatus=0 255 [Install] WantedBy=multi-user.target
  • E

    Unable to create NFS SR with truenas after rebuilding truenas

    Solved
    5
    1
    0 Votes
    5 Posts
    2k Views
    E
    @iLix That worked! I guess i forgot to enable NFSv4 after rebuilding it.
  • HolgiBH

    Samba Timeout - How to configure timeout limit / possible issues ?

    4
    0 Votes
    4 Posts
    5k Views
    olivierlambertO
    I can't follow what's done in 3rd party scripts, and it might be not trivial to find problems with them (if it's a problem due to the script or not). But before pointing any finger (I don't like that ) I would prefer to check with a fully up to date XOA on latest release channel and see if you have the same issue. At least, we'll be able to compare the behavior
  • K

    how to launch ec2 instance as disaster recovery from s3 using xen orchestra backup.

    2
    0 Votes
    2 Posts
    400 Views
    olivierlambertO
    Hi, I'm not aware of such feature on our side, you should ask AWS on how to import a XenServer/XCP-ng VM into EC2.