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

    Help moving VMs from XenServer 6.0.2 to XCP-ng 8.3

    5
    0 Votes
    5 Posts
    960 Views
    olivierlambertO
    Excellent news! Keep us posted
  • J

    error @vates/generator-toolbox@1.0.1: The engine "node" is incompatible with this module. Expected version ">=20.18". Got "18.20.3"

    5
    0 Votes
    5 Posts
    2k Views
    A
    @jasonnix Update to nodejs 22.x. It should be good for a while. Nodejs 24 will be out soon but not required yet.
  • planedropP

    Cannot Import VMDK Through Import > Disk (migrating from ESXi, all methods not working)

    30
    1
    1 Votes
    30 Posts
    16k Views
    florentF
    we are reworking the import code , along the new backup code ( https://xcp-ng.org/forum/topic/10664/our-future-backup-code-test-it ) to unify the differetn disk transformation path For now: V2V handles flat, cowd, sesparse, stream optimized vmdk in the format "metadata.vmdk and a data file ) and ova ( for VSAN) disk import support monolithic vmdk ( cowd, sesparse, streamoptimized ) ova improt support only stream ova with streamoptimzed vmdk inside
  • E

    XO update fails

    4
    1
    0 Votes
    4 Posts
    892 Views
    olivierlambertO
    @AtaxyaNetwork said in XO update fails: @edisoninfo Hi, What's xo-install.sh ? It's a third party script ? Very likely indeed Those scripts really needs to make sure to provide the URL of the repo to report issues in a very visible way.
  • ?

    IMPORT_ERROR - Tar.Header.Checksum_mismatch

    Unsolved
    3
    0 Votes
    3 Posts
    452 Views
    ?
    @Danp No sir, I have not. I have, however, exported the same VM in the OVA format. Ended up being about 47 GiB, however, I was able to import it into XOA without any issues, and the import took just under 10 minutes to complete.
  • C

    Ldap plugin : filter to allow only specific group to login ?

    2
    0 Votes
    2 Posts
    295 Views
    ?
    @Chico008 Seems like you're duplicating your inquiries. As I suggested in the previous thread, I think your memberOf is missing the full DN of the group.
  • C

    "Download System logs" tgz-file does not work

    17
    0 Votes
    17 Posts
    3k Views
    P
    @gthvn1 Yeah, that works. I can get the logs both from the same host and from the other one in the pool.
  • A

    Windows VMGuest changing network cause the guest to crash

    14
    1
    0 Votes
    14 Posts
    3k Views
    olivierlambertO
    @dinhngtu said in Windows VMGuest changing network cause the guest to crash: This is a driver bug that we fixed in XCP-ng Windows tools v9.0.9030 but hasn't been integrated by Citrix yet. You can try it out if you're not running a production system. Gosh, we are now officially faster than Citrix to detect and fix bugs even in the Windows PV driver
  • X

    GPN GRE/VxLAN Tunnel - connect/access from other Devices?

    1
    0 Votes
    1 Posts
    279 Views
    No one has replied
  • love2scootL

    Upgrade to XO v5.105 seems broken

    9
    2 Votes
    9 Posts
    2k Views
    I
    @ph7 Thank you. It seems to work like that. I'll wait for this fix.
  • P

    XO CE 82ed2 and 5c390 update.

    4
    0 Votes
    4 Posts
    981 Views
    olivierlambertO
    Note: just do a yarn && yarn build and it will work. The XO 6 build might be broken, but that's not surprising, it could happens.
  • I

    SQL Database support and XO HA

    7
    0 Votes
    7 Posts
    1k Views
    I
    @olivierlambert Happy to hear
  • S

    Just an idea :) - (SATA controller passthrough)

    3
    0 Votes
    3 Posts
    814 Views
    lsouai-vatesL
    @ScarfAntennae hello, and thanks for the suggestion. I am discussing it with the XO Team to add it to our next features. Have a good day!
  • V

    Bonded interface viewing support in XO

    23
    1 Votes
    23 Posts
    9k Views
    lsouai-vatesL
    @flakpyro yes, indeed that exactly what I was talking about. The XO6 new interface will provide more information, but I am noting the missing type of bound to discuss it with XO team for next feature.
  • TheNorthernLightT

    With qcow2 format support coming, could we then import KVM vm's ?

    3
    0 Votes
    3 Posts
    1k Views
    I
    Works with .raw at the moment. If you disconnect it from the vm and migrate it to another SR its converter to vhd.
  • I

    resourceSet issues

    4
    7
    0 Votes
    4 Posts
    845 Views
    I
    @olivierlambert ack.
  • Y

    Trial period extension for on-going tests

    3
    1
    0 Votes
    3 Posts
    728 Views
    Y
    @Danp Hi, Thanks for quick support.
  • Y

    How to deploy XO on ESXi

    5
    0 Votes
    5 Posts
    1k Views
    D
    @yzgulec said in How to deploy XO on ESXi: I just used VMware Converter for V2V (seems more practical for me) Installing from Source or using an installation script from the community is also very straight-forwards. Maybe 10 minutes worth of setup for the OS and then for at least my github it's a single line installation.
  • A

    Simulating network cable disconnect

    11
    0 Votes
    11 Posts
    4k Views
    O
    @splastunov I realize this thread is old, but I think there is important info to keep connected to this thread for future readers. The IP locking trick doesn't seem to prevent all traffic -- it only prevents traffic that has an IP that isn't 255.255.255.255 (and possibly others as well). That is, I can still successfully acquire a DHCP IP even when the IP locking mechanism is engaged. I think this is important for others to know since it doesn't fully isolate VMs like the OP wanted. UPDATE: Setting the locking mode to "disabled" is what you want -- not "locked". Disabled will drop all traffic; locked simply checks if the set of IPs in the VM is permitted. Source: https://docs.xenserver.com/en-us/citrix-hypervisor/networking/manage.html#vif-locking-mode-states
  • I

    host connection error

    3
    1
    0 Votes
    3 Posts
    482 Views
    P
    @irtaza9 Sometimes when I have been tinkering with a host, I get a red triangle. Then just pressing Enabled and then Disabled can get rid of the triangle and the host back in business again.