@guiand888 Thank you for the feedback. Just a note: before running XenClean, please turn off the "Manage Citrix PV drivers via Windows Update" option; otherwise, Windows will try to reinstall Citrix drivers as soon as it's rebooted. For the storage perf, Xen PV does fluctuate a lot at I/O performance (both network and storage), so the real performance would be better seen with long benchmark runs (depending on your I/O backend).

xe is a XAPI client, like XO is a XAPI client too. The issue with this, is if you have 1 pool it's OK. If you have many pools, it's a lot better to use XO API.

@yann here you are : https://gitlab.com/xen-project/xen-guest-agent/-/issues/22

FYI and for what it's worth - In my experience as of Jan 2025, the process aligns with RHEL and appears to have no issues. From a fresh install of Alma 9.5: sudo dnf install epel-release sudo dnf install xe-guest-utilities-latest sudo systemctl enable --now xe-inux-distribution graphs and other Xen Orchestra behaviours work as expected.

No specific plans as this kind of feature isn't really useful in Datacenters. However, if there's a way that's relatively universal, it's doable with the help of the community (ie contributions are very welcome and we'll review it seriously)

turned out that this is not necessary. An easier option is to simply add the bootparameter aacraid.numacb=1000 before booting into xcp-ng. As of my current understanding this makes sure that the xen-specific larger management fib size of 16 is taken into account (the driver default is 8). Only tested on Version 8.2.1

@john-c said in USB Passthrough Override Script - to ensure usb-policy.conf consistency: This is no longer needed if you have Xen Orchestra version 5.93 or later, alternatively if using in home lab and from source then any commit dated after 29th March 2024 (or current head on GitHub Main - Master). The reason being that Xen Orchestra from version 5.93 has official support for USB Passthrough and later from version 5.95 you can do PCI Passthrough. This is unfortunately still needed, as otherwise the XO simply does not show the PUSB in the host, so it cannot be assigned as a VUSB for the VM. @zeropointer thanks for the idea, this seems to be the most pragmatic solution.

Everything told here is already in our (huge) backlog

CCing @bleader too. @sapcode said in openssl 1.1.1 update or manual build in XCP 8.2.1 possible ?: Would it be safe to run yum remove openssl as the first step or would this break the XCP installation: The second option. And actually it's not openssl you're looking for, it's openssl-libs, and removing it will not even work, as it attempts to remove yum and systemd which depend on it and are protected. Note that we do offer openssl 1.1.1 through the xs-openssl-libs package, and that is what XAPI uses for communication instead of the system one. However you'd have to patch and rebuild curl or wget so that they use it, and this definitely voids your warranty. You are going on a journey that is far more difficult than you initially expected, I fear. So I'd start questioning the initial needs again. Why do you need to contact websites such as ssl-tools.net from dom0? Can't you do it from a VM?

@olivierlambert said in Redhad CoreOS and Guest Tools installation: Have you tried with the new Rust guest tools? Sorry for the delay in replying, I have not. I'll see if I can find them and install them.

@olivierlambert Thanks

@probain As @olivierlambert said, Redis is used to story very little data, and we are already thinking about migrating away from it. We would like to use a simpler solution that would not require users to manage it like an SQLite database. For the time being, we will likely keep Redis as long as it's available in open source distributions like Debian but we are keeping an eye on it

@cg Those HDD's will take their fair time to rebuild. Always stressful looking how far along it is while crossing your fingers that another drive wont pop during the process.

@julien-f I can confirm that the fix worked! Snapshots are back and working. I am impressed at how quick you managed to fix it too. Thanks!

@wolfmon You have this documentation https://xenbits.xen.org/docs/unstable/man/xl.1.html But be careful, most operations of xl are not officially supported in XCP-ng.

@CJ yum update from 8.3 beta to 8.3 will be possible, but I still recommend using the ISO. In a perfect world, yum update would give you exactly the same result, but in reality there are always corner cases where files or packages are left behind (we have no sane way to tell yum/rpm to remove an installed RPM, unless making another RPM obsolete it and thus make it impossible to reinstall later if someone needs it for a good reason).

@mohammadm i think for nfs you should handle that from the kubernetes side. i.e. use an nfs-provisioner or the built-in nfs storageclass