@bogikornel As discussed in the thread, pygrub doesn't work. (It might be fixable, because copying kernel and initrd to dom-0 and directly setting PV-kernel, PV-ramdisk and PV-args works, which is basically what pygrub is supposed to do. But I stopped investigating as pvhgrub is a much better option which acually works.) You have 3 options copy kernel and initrd do dom-0 and configure xe vm-param-set uuid=... domain-type=pvh xe vm-param-set uuid=... PV-kernel=/dom-0/path/to/kernel xe vm-param-set uuid=... PV-ramdisk=/dom-0/path/to/initrd xe vm-param-set uuid=... PV-args="root=... ro console=hvc0 ..." xe vm-param-clear uuid=... param-name=PV-bootloader Not a very practical option, just PoC. use pvh-ovmf, but this requires UEFI-enabled VM (ie. GPT disk layout with EFI partition and some EFI bootloader or kernel directly in EFI with proper config (or as UKI) use pvhgrub. You need a recent grub2 to build the image for i386-xen_pvh target. Or just get the blob - this one is from Alpine package curl https://dl-cdn.alpinelinux.org/alpine/edge/main/x86_64/grub-xenhost-2.12-r8.apk | tar -xzf - --strip-components=3 usr/lib/grub-xen/grub-i386-xen_pvh.bin Save it to dom-0 (e.g. to /var/lib/xcp/guest/grub-i386-xen_pvh.bin) and configure the VM xe vm-param-set uuid=... domain-type=pvh xe vm-param-set uuid=... PV-kernel=/var/lib/xcp/guest/grub-i386-xen_pvh.bin xe vm-param-clear uuid=... param-name=PV-ramdisk xe vm-param-clear uuid=... param-name=PV-args xe vm-param-clear uuid=... param-name=PV-bootloader If the VM has valid grub2 config, it should work. Of course, you need a linux kernel with CONFIG_XEN_PVH enabled.

@ronan-a Thanks! I've installed the plugin, and configured it. Now to wait until the next power outage. (or until I get time this weekend to test it and annoy my family)

Upon further testing, it seems that initiating a rescan of the 0 byte SR fixes the size issue. However, I should not be having to do this but at least it appears to be more easily dealt with than I previously assessed.

@TeddyAstie I ran iperf3 tests between two VMs on Xeon E5-2680v2 and average results were within 2% of each other with the patch being slower. Peak speed was 14.5 vs. 13.7 Gbits/sec.

@gduperrey Got it, thank you for your assistance, this is super helpful.

@olivierlambert Fabulous! This is great news!

@LonnieTC Don't try to install XCP-ng as if it's any other Linux OS. It's an appliance, you need to download the XCP-ng ISO directly, install this to your hardware and then setup your management interface (Xen Orchestra). Xen Orchestra is installable to Ubuntu.

@kevdog @yann said in New Rust Xen guest tools: @kevdog great news, looking forward for this PKGBUILD! Wouldn't it make sense to build from release packages rather than from Git? The CI scripts should give you some guidance. For dependencies you should have a list at https://gitlab.com/xen-project/xen-guest-agent#build-requirements. Not sure why you would want python-setuptools? Hey all, I put together PKGBUILD for Arch which pulls the latest git. It seems to be working fine for me. You'll need to install xen package on AUR. https://aur.archlinux.org/packages/xen-guest-agent-git It's my first attempt at submitting something on AUR. I look forward to any feedback.

@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.

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.