<![CDATA[Xen 4.17 on XCP-ng 8.3!]]>Xen 4.17

XenServer developers updated Xen from 4.13 to 4.17 in XenServer 8 recently. We decided to port this to XCP-ng 8.3 as soon as possible in order to let you take part in the tests really early.

We'll forward any feedback you give us to these developers (and to the Xen Project when useful).

It is a big version jump, that's why testing it on a wide range of hardware is a good idea.

How to install

We put the test packages in the xcp-ng-lab repository, which is already setup on XCP-ng 8.3 (albeit disabled).

Just run :

yum update --enablerepo=xcp-ng-lab

And reboot. That's it!

Keep us informed of how well it goes, and of any issues you may have that were not present with the 4.13 version.

How to downgrade

In case of issues, if your host is still bootable, you can downgrade with:

yum downgrade blktap forkexecd gpumon kexec-tools message-switch python2-xapi-storage qemu rrdd-plugins sm-cli squeezed varstored varstored-guard varstored-tools vhd-tool vncterm wsproxy xapi-core xapi-nbd xapi-rrd2csv xapi-storage-script xapi-tests xapi-xe xcp-clipboardd xcp-featured xcp-networkd xcp-rrdd xen-dom0-libs xen-dom0-tools xen-hypervisor xen-libs xen-tools xenopsd xenopsd-cli xenopsd-xc

(or use yum history to rollback the last transaction)

If you can't boot, well, first we'll try to help you overcome this issue, and if nothing works you can still boot the fifth entry in grub, which will boot using an older version of Xen. Then you can downgrade the packages.

After the installation

On a host running with this Xen 4.17 and packages rebuilt for it, don't install updates for the coming days/weeks unless I tell you to (and this will likely be another yum update --enablerepo=xcp-ng-lab operation).

What to test

Installing on as many different hardware specs you can, then at least a few operations on a VM, and then anything you want to test.

Besides testing manually, you can also:

  1. Run XTF: https://docs.xcp-ng.org/project/development-process/tests/#test-the-xen-hypervisor-itself
  2. Run xen-dom0-tests: https://docs.xcp-ng.org/project/development-process/tests/#xen-dom0-tests

In order not to flood this thread with your test results:

  • only share the output if there's an error, or when in doubt
  • you can quote errors here, but if you think it's useful to share the full output, then please use https://paste.vates.tech.

If you have extra hosts you can temporarily dedicate to this, even if you don't have any VMs to run on them, you can very well take part in the testing effort by installating XCP-ng 8.3 beta2, updating, installing Xen 4.17, and then running these automated tests.

The more diverse hardware we get to test, the better.

What this version of Xen changes

(courtesy of @gb.123)

Notable Features (filtered to x86-related changes only)

  • MISRA-C integration: The project has officially adopted four directives and 24 rules, added MISRA-C checker build integration, and defined how to document deviations. A number of MISRA-C violations have been fixed.
  • x86: IOMMU superpage support for all guest types; improving performance of PCI pass-through
  • x86: Security support hosts with up to 12 TiB of RAM
  • x86: Can now set cpuid parameters for dom0 at boot time
  • x86: mwait-idle support: Added SPR and ADL
  • x86: Improved speculative mitigation support, including VIRT_SSBD and MSR_SPEC_CTRL features to help guests know what speculative mitigations they don't need to be done (due to mitigations on the hypervisor side), and to control what kind of speculative mitigations the hypervisor performs on their behalf
  • Out-of-tree builds for the hypervisor now supported

Source : https://wiki.xenproject.org/wiki/Xen_Project_4.17_Feature_List

Also check changelogs for versions 4.14, 4.15 and 4.16.

]]>https://xcp-ng.org/forum/topic/8370/xen-4-17-on-xcp-ng-8-3RSS for NodeWed, 15 Apr 2026 01:21:20 GMTTue, 13 Feb 2024 17:27:11 GMT60<![CDATA[Reply to Xen 4.17 on XCP-ng 8.3! on Tue, 23 Apr 2024 15:16:32 GMT]]>@olivierlambert thanks for confirming!

]]>https://xcp-ng.org/forum/post/76051https://xcp-ng.org/forum/post/76051Tue, 23 Apr 2024 15:16:32 GMT<![CDATA[Reply to Xen 4.17 on XCP-ng 8.3! on Tue, 23 Apr 2024 15:08:13 GMT]]>You can imagine, as we are actively working on this, we tested that a long time ago. All Xen version are affected, including vanilla Xen upstream, XenServer and such.

]]>https://xcp-ng.org/forum/post/76046https://xcp-ng.org/forum/post/76046Tue, 23 Apr 2024 15:08:13 GMT<![CDATA[Reply to Xen 4.17 on XCP-ng 8.3! on Tue, 23 Apr 2024 14:52:07 GMT]]>Would be nice to see if Xen 4.17 fixes the slow network on EPYC servers.

]]>https://xcp-ng.org/forum/post/76042https://xcp-ng.org/forum/post/76042Tue, 23 Apr 2024 14:52:07 GMT<![CDATA[Reply to Xen 4.17 on XCP-ng 8.3! on Mon, 22 Apr 2024 21:48:54 GMT]]>@stormi None of the other things I tried fixed the problems with left over update artifacts but running a normal yum update after this did. Thanks!

]]>https://xcp-ng.org/forum/post/75987https://xcp-ng.org/forum/post/75987Mon, 22 Apr 2024 21:48:54 GMT<![CDATA[Reply to Xen 4.17 on XCP-ng 8.3! on Mon, 22 Apr 2024 20:32:55 GMT]]>The main update repositories for XCP-ng 8.3 beta now contain Xen 4.17, so the steps described in this thread to test it are not necessary anymore.

In theory, the transition will be automatic for you: just update normally.

]]>https://xcp-ng.org/forum/post/75984https://xcp-ng.org/forum/post/75984Mon, 22 Apr 2024 20:32:55 GMT<![CDATA[Reply to Xen 4.17 on XCP-ng 8.3! on Fri, 01 Mar 2024 17:20:25 GMT]]>@stormi
I've tried that and also yum-complete-transaction --enablerepo=xcp-ng-lab to see if that would make a difference but no change in the problem. I've also tried to revert the patches with the yum downgrade command from the first message here and see similar problems.

]]>https://xcp-ng.org/forum/post/72701https://xcp-ng.org/forum/post/72701Fri, 01 Mar 2024 17:20:25 GMT<![CDATA[Reply to Xen 4.17 on XCP-ng 8.3! on Fri, 01 Mar 2024 16:33:31 GMT]]>Can you run two different kernels in one pool? Can I test one host with 4.17 and then roll it back to 4.13 after testing completes without messing up my pool?

]]>https://xcp-ng.org/forum/post/72695https://xcp-ng.org/forum/post/72695Fri, 01 Mar 2024 16:33:31 GMT<![CDATA[Reply to Xen 4.17 on XCP-ng 8.3! on Fri, 01 Mar 2024 16:10:35 GMT]]>@JeffBerntsen This looks like a previous update was interrupted before the cleanup phase, which leaves a lot of duplicate RPMs in the RPM database. A Ctrl+C, or an early reboot maybe?

Try yum-complete-transaction before anything else?

]]>https://xcp-ng.org/forum/post/72690https://xcp-ng.org/forum/post/72690Fri, 01 Mar 2024 16:10:35 GMT<![CDATA[Reply to Xen 4.17 on XCP-ng 8.3! on Fri, 01 Mar 2024 16:07:18 GMT]]>Hmm. I'm getting the following errors when I try to install the update with the yum update --enablerepo=xcp-ng-lab command

Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
Excluding mirror: updates.xcp-ng.org
 * xcp-ng-base: mirrors.xcp-ng.org
Excluding mirror: updates.xcp-ng.org
 * xcp-ng-lab: mirrors.xcp-ng.org
Excluding mirror: updates.xcp-ng.org
 * xcp-ng-updates: mirrors.xcp-ng.org
Resolving Dependencies
--> Running transaction check
---> Package forkexecd.x86_64 0:23.31.0-1.1.xcpng8.3 will be updated
---> Package forkexecd.x86_64 0:23.31.0-1.1.0.xen417.2.xcpng8.3 will be updated
---> Package forkexecd.x86_64 0:23.31.0-1.6.0.xen417.0.xcpng8.3 will be an update
---> Package gpumon.x86_64 0:0.25.0-6.1.xcpng8.3 will be updated
---> Package gpumon.x86_64 0:0.25.0-6.1.0.xen417.1.xcpng8.3 will be updated
---> Package gpumon.x86_64 0:0.25.0-6.1.0.xen417.2.xcpng8.3 will be an update
---> Package libblkid.x86_64 0:2.23.2-52.el7_5.1 will be updated
---> Package libblkid.x86_64 0:2.23.2-52.1.xcpng8.3 will be an update
---> Package libmount.x86_64 0:2.23.2-52.el7_5.1 will be updated
---> Package libmount.x86_64 0:2.23.2-52.1.xcpng8.3 will be an update
---> Package libuuid.x86_64 0:2.23.2-52.el7_5.1 will be updated
---> Package libuuid.x86_64 0:2.23.2-52.1.xcpng8.3 will be an update
---> Package message-switch.x86_64 0:23.31.0-1.1.xcpng8.3 will be updated
---> Package message-switch.x86_64 0:23.31.0-1.1.0.xen417.2.xcpng8.3 will be updated
---> Package message-switch.x86_64 0:23.31.0-1.6.0.xen417.0.xcpng8.3 will be an update
---> Package python2-xapi-storage.x86_64 0:23.31.0-1.1.0.xen417.2.xcpng8.3 will be updated
---> Package python2-xapi-storage.x86_64 0:23.31.0-1.6.0.xen417.0.xcpng8.3 will be an update
---> Package rrdd-plugins.x86_64 0:23.31.0-1.1.0.xen417.2.xcpng8.3 will be updated
---> Package rrdd-plugins.x86_64 0:23.31.0-1.6.0.xen417.0.xcpng8.3 will be an update
---> Package sm.x86_64 0:3.0.12-6.1.xcpng8.3 will be updated
---> Package sm.x86_64 0:3.0.12-6.2.xcpng8.3 will be an update
---> Package sm-cli.x86_64 0:23.31.0-1.1.xcpng8.3 will be updated
---> Package sm-cli.x86_64 0:23.31.0-1.1.0.xen417.2.xcpng8.3 will be updated
---> Package sm-cli.x86_64 0:23.31.0-1.6.0.xen417.0.xcpng8.3 will be an update
---> Package squeezed.x86_64 0:23.31.0-1.1.0.xen417.2.xcpng8.3 will be updated
---> Package squeezed.x86_64 0:23.31.0-1.6.0.xen417.0.xcpng8.3 will be an update
---> Package util-linux.x86_64 0:2.23.2-52.el7_5.1 will be updated
---> Package util-linux.x86_64 0:2.23.2-52.1.xcpng8.3 will be an update
---> Package varstored-guard.x86_64 0:23.31.0-1.1.xcpng8.3 will be updated
---> Package varstored-guard.x86_64 0:23.31.0-1.1.0.xen417.2.xcpng8.3 will be updated
---> Package varstored-guard.x86_64 0:23.31.0-1.6.0.xen417.0.xcpng8.3 will be an update
---> Package vhd-tool.x86_64 0:23.31.0-1.1.xcpng8.3 will be updated
---> Package vhd-tool.x86_64 0:23.31.0-1.1.0.xen417.2.xcpng8.3 will be updated
---> Package vhd-tool.x86_64 0:23.31.0-1.6.0.xen417.0.xcpng8.3 will be an update
---> Package wsproxy.x86_64 0:23.31.0-1.1.xcpng8.3 will be updated
---> Package wsproxy.x86_64 0:23.31.0-1.1.0.xen417.2.xcpng8.3 will be updated
---> Package wsproxy.x86_64 0:23.31.0-1.6.0.xen417.0.xcpng8.3 will be an update
---> Package xapi-core.x86_64 0:23.31.0-1.1.xcpng8.3 will be updated
---> Package xapi-core.x86_64 0:23.31.0-1.1.0.xen417.2.xcpng8.3 will be updated
---> Package xapi-core.x86_64 0:23.31.0-1.6.0.xen417.0.xcpng8.3 will be an update
---> Package xapi-nbd.x86_64 0:23.31.0-1.1.xcpng8.3 will be updated
---> Package xapi-nbd.x86_64 0:23.31.0-1.1.0.xen417.2.xcpng8.3 will be updated
---> Package xapi-nbd.x86_64 0:23.31.0-1.6.0.xen417.0.xcpng8.3 will be an update
---> Package xapi-rrd2csv.x86_64 0:23.31.0-1.1.xcpng8.3 will be updated
---> Package xapi-rrd2csv.x86_64 0:23.31.0-1.1.0.xen417.2.xcpng8.3 will be updated
---> Package xapi-rrd2csv.x86_64 0:23.31.0-1.6.0.xen417.0.xcpng8.3 will be an update
---> Package xapi-storage-script.x86_64 0:23.31.0-1.1.xcpng8.3 will be updated
---> Package xapi-storage-script.x86_64 0:23.31.0-1.1.0.xen417.2.xcpng8.3 will be updated
---> Package xapi-storage-script.x86_64 0:23.31.0-1.6.0.xen417.0.xcpng8.3 will be an update
---> Package xapi-tests.x86_64 0:23.31.0-1.1.0.xen417.2.xcpng8.3 will be updated
---> Package xapi-tests.x86_64 0:23.31.0-1.6.0.xen417.0.xcpng8.3 will be an update
---> Package xapi-xe.x86_64 0:23.31.0-1.1.xcpng8.3 will be updated
---> Package xapi-xe.x86_64 0:23.31.0-1.1.0.xen417.2.xcpng8.3 will be updated
---> Package xapi-xe.x86_64 0:23.31.0-1.6.0.xen417.0.xcpng8.3 will be an update
---> Package xcp-networkd.x86_64 0:23.31.0-1.1.xcpng8.3 will be updated
---> Package xcp-networkd.x86_64 0:23.31.0-1.1.0.xen417.2.xcpng8.3 will be updated
---> Package xcp-networkd.x86_64 0:23.31.0-1.6.0.xen417.0.xcpng8.3 will be an update
---> Package xcp-ng-xapi-plugins.noarch 0:1.9.1-1.xcpng8.3 will be updated
---> Package xcp-ng-xapi-plugins.noarch 0:1.10.0-1.xcpng8.3 will be an update
---> Package xcp-rrdd.x86_64 0:23.31.0-1.1.0.xen417.2.xcpng8.3 will be updated
---> Package xcp-rrdd.x86_64 0:23.31.0-1.6.0.xen417.0.xcpng8.3 will be an update
---> Package xen-dom0-libs.x86_64 0:4.13.5-10.58.xcpng8.3 will be updated
--> Processing Dependency: libxenctrl.so.4.13()(64bit) for package: 1:kexec-tools-2.0.15-18.xcpng8.3.x86_64
--> Processing Dependency: libxenctrl.so.4.13()(64bit) for package: 2:qemu-4.2.1-5.2.4.xcpng8.3.x86_64
--> Processing Dependency: libxenguest.so.4.13()(64bit) for package: 2:qemu-4.2.1-5.2.4.xcpng8.3.x86_64
---> Package xen-dom0-libs.x86_64 0:4.17.3-1.0.xen417.1.xcpng8.3 will be updated
---> Package xen-dom0-libs.x86_64 0:4.17.3-3.0.xen417.0.xcpng8.3 will be an update
---> Package xen-dom0-tests.x86_64 0:4.13.5-10.58.xcpng8.3 will be updated
---> Package xen-dom0-tests.x86_64 0:4.17.3-1.0.xen417.1.xcpng8.3 will be updated
---> Package xen-dom0-tests.x86_64 0:4.17.3-3.0.xen417.0.xcpng8.3 will be an update
---> Package xen-dom0-tools.x86_64 0:4.13.5-10.58.xcpng8.3 will be updated
---> Package xen-dom0-tools.x86_64 0:4.17.3-1.0.xen417.1.xcpng8.3 will be updated
---> Package xen-dom0-tools.x86_64 0:4.17.3-3.0.xen417.0.xcpng8.3 will be an update
---> Package xen-hypervisor.x86_64 0:4.13.5-10.58.xcpng8.3 will be updated
---> Package xen-hypervisor.x86_64 0:4.17.3-1.0.xen417.1.xcpng8.3 will be updated
---> Package xen-hypervisor.x86_64 0:4.17.3-3.0.xen417.0.xcpng8.3 will be an update
---> Package xen-libs.x86_64 0:4.13.5-10.58.xcpng8.3 will be updated
--> Processing Dependency: libxenstore.so.3.0()(64bit) for package: blktap-3.54.6-2.1.xcpng8.3.x86_64
--> Processing Dependency: libxenstore.so.3.0()(64bit) for package: 2:qemu-4.2.1-5.2.4.xcpng8.3.x86_64
--> Processing Dependency: libxenstore.so.3.0()(64bit) for package: xcp-clipboardd-1.0.3-7.xcpng8.3.x86_64
--> Processing Dependency: libxenstore.so.3.0()(64bit) for package: vncterm-10.2.0-3.xcpng8.3.x86_64
---> Package xen-libs.x86_64 0:4.17.3-1.0.xen417.1.xcpng8.3 will be updated
---> Package xen-libs.x86_64 0:4.17.3-3.0.xen417.0.xcpng8.3 will be an update
---> Package xen-tools.x86_64 0:4.13.5-10.58.xcpng8.3 will be updated
---> Package xen-tools.x86_64 0:4.17.3-1.0.xen417.1.xcpng8.3 will be updated
---> Package xen-tools.x86_64 0:4.17.3-3.0.xen417.0.xcpng8.3 will be an update
---> Package xenopsd.x86_64 0:23.31.0-1.1.xcpng8.3 will be updated
---> Package xenopsd.x86_64 0:23.31.0-1.1.0.xen417.2.xcpng8.3 will be updated
---> Package xenopsd.x86_64 0:23.31.0-1.6.0.xen417.0.xcpng8.3 will be an update
---> Package xenopsd-cli.x86_64 0:23.31.0-1.1.xcpng8.3 will be updated
---> Package xenopsd-cli.x86_64 0:23.31.0-1.1.0.xen417.2.xcpng8.3 will be updated
---> Package xenopsd-cli.x86_64 0:23.31.0-1.6.0.xen417.0.xcpng8.3 will be an update
---> Package xenopsd-xc.x86_64 0:23.31.0-1.1.0.xen417.2.xcpng8.3 will be updated
---> Package xenopsd-xc.x86_64 0:23.31.0-1.6.0.xen417.0.xcpng8.3 will be an update
---> Package xsconsole.x86_64 0:10.1.14-2.1.xcpng8.3 will be updated
---> Package xsconsole.x86_64 0:10.1.14-2.2.xcpng8.3 will be an update
--> Running transaction check
---> Package xen-installer-files.x86_64 0:4.13.5-10.42.3.xcpng8.3 will be installed
---> Package xen-libs.x86_64 0:4.13.5-10.58.xcpng8.3 will be updated
--> Processing Dependency: libxenstore.so.3.0()(64bit) for package: blktap-3.54.6-2.1.xcpng8.3.x86_64
--> Processing Dependency: libxenstore.so.3.0()(64bit) for package: 2:qemu-4.2.1-5.2.4.xcpng8.3.x86_64
--> Processing Dependency: libxenstore.so.3.0()(64bit) for package: xcp-clipboardd-1.0.3-7.xcpng8.3.x86_64
--> Processing Dependency: libxenstore.so.3.0()(64bit) for package: vncterm-10.2.0-3.xcpng8.3.x86_64
--> Finished Dependency Resolution
Error: Package: vncterm-10.2.0-3.xcpng8.3.x86_64 (@xcp:main/$releasever)
           Requires: libxenstore.so.3.0()(64bit)
           Removing: xen-libs-4.13.5-10.58.xcpng8.3.x86_64 (@xcp-ng-base)
               libxenstore.so.3.0()(64bit)
           Updated By: xen-libs-4.17.3-3.0.xen417.0.xcpng8.3.x86_64 (xcp-ng-lab)
               Not found
           Available: xen-libs-4.13.4-10.27.xcpng8.3.x86_64 (xcp-ng-base)
               libxenstore.so.3.0()(64bit)
           Available: xen-libs-4.13.4-10.35.xcpng8.3.x86_64 (xcp-ng-base)
               libxenstore.so.3.0()(64bit)
           Available: xen-libs-4.13.4-10.36.xcpng8.3.x86_64 (xcp-ng-base)
               libxenstore.so.3.0()(64bit)
           Available: xen-libs-4.13.5-10.40.xcpng8.3.x86_64 (xcp-ng-base)
               libxenstore.so.3.0()(64bit)
           Available: xen-libs-4.13.5-10.42.xcpng8.3.x86_64 (xcp-ng-base)
               libxenstore.so.3.0()(64bit)
           Available: xen-libs-4.13.5-10.42.1.xcpng8.3.x86_64 (xcp-ng-base)
               libxenstore.so.3.0()(64bit)
           Available: xen-libs-4.13.5-10.42.3.xcpng8.3.x86_64 (xcp-ng-base)
               libxenstore.so.3.0()(64bit)
           Available: xen-libs-4.13.5-10.51.xcpng8.3.x86_64 (xcp-ng-base)
               libxenstore.so.3.0()(64bit)
           Removing: xen-libs-4.17.3-1.0.xen417.1.xcpng8.3.x86_64 (installed)
               Not found
           Updated By: xen-libs-4.17.3-3.0.xen417.0.xcpng8.3.x86_64 (xcp-ng-lab)
               Not found
           Available: xen-libs-4.17.3-2.0.xen417.1.xcpng8.3.x86_64 (xcp-ng-lab)
               Not found
Error: Package: xcp-clipboardd-1.0.3-7.xcpng8.3.x86_64 (@xcp:main/$releasever)
           Requires: libxenstore.so.3.0()(64bit)
           Removing: xen-libs-4.13.5-10.58.xcpng8.3.x86_64 (@xcp-ng-base)
               libxenstore.so.3.0()(64bit)
           Updated By: xen-libs-4.17.3-3.0.xen417.0.xcpng8.3.x86_64 (xcp-ng-lab)
               Not found
           Available: xen-libs-4.13.4-10.27.xcpng8.3.x86_64 (xcp-ng-base)
               libxenstore.so.3.0()(64bit)
           Available: xen-libs-4.13.4-10.35.xcpng8.3.x86_64 (xcp-ng-base)
               libxenstore.so.3.0()(64bit)
           Available: xen-libs-4.13.4-10.36.xcpng8.3.x86_64 (xcp-ng-base)
               libxenstore.so.3.0()(64bit)
           Available: xen-libs-4.13.5-10.40.xcpng8.3.x86_64 (xcp-ng-base)
               libxenstore.so.3.0()(64bit)
           Available: xen-libs-4.13.5-10.42.xcpng8.3.x86_64 (xcp-ng-base)
               libxenstore.so.3.0()(64bit)
           Available: xen-libs-4.13.5-10.42.1.xcpng8.3.x86_64 (xcp-ng-base)
               libxenstore.so.3.0()(64bit)
           Available: xen-libs-4.13.5-10.42.3.xcpng8.3.x86_64 (xcp-ng-base)
               libxenstore.so.3.0()(64bit)
           Available: xen-libs-4.13.5-10.51.xcpng8.3.x86_64 (xcp-ng-base)
               libxenstore.so.3.0()(64bit)
           Removing: xen-libs-4.17.3-1.0.xen417.1.xcpng8.3.x86_64 (installed)
               Not found
           Updated By: xen-libs-4.17.3-3.0.xen417.0.xcpng8.3.x86_64 (xcp-ng-lab)
               Not found
           Available: xen-libs-4.17.3-2.0.xen417.1.xcpng8.3.x86_64 (xcp-ng-lab)
               Not found
Error: Package: blktap-3.54.6-2.1.xcpng8.3.x86_64 (@xcp-ng-base)
           Requires: libxenstore.so.3.0()(64bit)
           Removing: xen-libs-4.13.5-10.58.xcpng8.3.x86_64 (@xcp-ng-base)
               libxenstore.so.3.0()(64bit)
           Updated By: xen-libs-4.17.3-3.0.xen417.0.xcpng8.3.x86_64 (xcp-ng-lab)
               Not found
           Available: xen-libs-4.13.4-10.27.xcpng8.3.x86_64 (xcp-ng-base)
               libxenstore.so.3.0()(64bit)
           Available: xen-libs-4.13.4-10.35.xcpng8.3.x86_64 (xcp-ng-base)
               libxenstore.so.3.0()(64bit)
           Available: xen-libs-4.13.4-10.36.xcpng8.3.x86_64 (xcp-ng-base)
               libxenstore.so.3.0()(64bit)
           Available: xen-libs-4.13.5-10.40.xcpng8.3.x86_64 (xcp-ng-base)
               libxenstore.so.3.0()(64bit)
           Available: xen-libs-4.13.5-10.42.xcpng8.3.x86_64 (xcp-ng-base)
               libxenstore.so.3.0()(64bit)
           Available: xen-libs-4.13.5-10.42.1.xcpng8.3.x86_64 (xcp-ng-base)
               libxenstore.so.3.0()(64bit)
           Available: xen-libs-4.13.5-10.42.3.xcpng8.3.x86_64 (xcp-ng-base)
               libxenstore.so.3.0()(64bit)
           Available: xen-libs-4.13.5-10.51.xcpng8.3.x86_64 (xcp-ng-base)
               libxenstore.so.3.0()(64bit)
           Removing: xen-libs-4.17.3-1.0.xen417.1.xcpng8.3.x86_64 (installed)
               Not found
           Updated By: xen-libs-4.17.3-3.0.xen417.0.xcpng8.3.x86_64 (xcp-ng-lab)
               Not found
           Available: xen-libs-4.17.3-2.0.xen417.1.xcpng8.3.x86_64 (xcp-ng-lab)
               Not found
Error: Package: 2:qemu-4.2.1-5.2.4.xcpng8.3.x86_64 (@xcp-ng-base)
           Requires: libxenstore.so.3.0()(64bit)
           Removing: xen-libs-4.13.5-10.58.xcpng8.3.x86_64 (@xcp-ng-base)
               libxenstore.so.3.0()(64bit)
           Updated By: xen-libs-4.17.3-3.0.xen417.0.xcpng8.3.x86_64 (xcp-ng-lab)
               Not found
           Available: xen-libs-4.13.4-10.27.xcpng8.3.x86_64 (xcp-ng-base)
               libxenstore.so.3.0()(64bit)
           Available: xen-libs-4.13.4-10.35.xcpng8.3.x86_64 (xcp-ng-base)
               libxenstore.so.3.0()(64bit)
           Available: xen-libs-4.13.4-10.36.xcpng8.3.x86_64 (xcp-ng-base)
               libxenstore.so.3.0()(64bit)
           Available: xen-libs-4.13.5-10.40.xcpng8.3.x86_64 (xcp-ng-base)
               libxenstore.so.3.0()(64bit)
           Available: xen-libs-4.13.5-10.42.xcpng8.3.x86_64 (xcp-ng-base)
               libxenstore.so.3.0()(64bit)
           Available: xen-libs-4.13.5-10.42.1.xcpng8.3.x86_64 (xcp-ng-base)
               libxenstore.so.3.0()(64bit)
           Available: xen-libs-4.13.5-10.42.3.xcpng8.3.x86_64 (xcp-ng-base)
               libxenstore.so.3.0()(64bit)
           Available: xen-libs-4.13.5-10.51.xcpng8.3.x86_64 (xcp-ng-base)
               libxenstore.so.3.0()(64bit)
           Removing: xen-libs-4.17.3-1.0.xen417.1.xcpng8.3.x86_64 (installed)
               Not found
           Updated By: xen-libs-4.17.3-3.0.xen417.0.xcpng8.3.x86_64 (xcp-ng-lab)
               Not found
           Available: xen-libs-4.17.3-2.0.xen417.1.xcpng8.3.x86_64 (xcp-ng-lab)
               Not found
 You could try using --skip-broken to work around the problem
** Found 28 pre-existing rpmdb problem(s), 'yum check' output follows:
blktap-3.54.6-2.1.0.xen417.1.xcpng8.3.x86_64 is a duplicate with blktap-3.54.6-2.1.xcpng8.3.x86_64
forkexecd-23.31.0-1.1.0.xen417.2.xcpng8.3.x86_64 is a duplicate with forkexecd-23.31.0-1.1.xcpng8.3.x86_64
gpumon-0.25.0-6.1.0.xen417.1.xcpng8.3.x86_64 is a duplicate with gpumon-0.25.0-6.1.xcpng8.3.x86_64
1:kexec-tools-2.0.15-18.0.xen417.1.xcpng8.3.x86_64 is a duplicate with 1:kexec-tools-2.0.15-18.xcpng8.3.x86_64
message-switch-23.31.0-1.1.0.xen417.2.xcpng8.3.x86_64 is a duplicate with message-switch-23.31.0-1.1.xcpng8.3.x86_64
2:qemu-4.2.1-5.2.4.0.xen417.1.xcpng8.3.x86_64 is a duplicate with 2:qemu-4.2.1-5.2.4.xcpng8.3.x86_64
sm-cli-23.31.0-1.1.0.xen417.2.xcpng8.3.x86_64 is a duplicate with sm-cli-23.31.0-1.1.xcpng8.3.x86_64
varstored-guard-23.31.0-1.1.0.xen417.2.xcpng8.3.x86_64 is a duplicate with varstored-guard-23.31.0-1.1.xcpng8.3.x86_64
varstored-tools-1.2.0-1.3.0.xen417.1.xcpng8.3.x86_64 is a duplicate with varstored-tools-1.2.0-1.3.xcpng8.3.x86_64
vhd-tool-23.31.0-1.1.0.xen417.2.xcpng8.3.x86_64 is a duplicate with vhd-tool-23.31.0-1.1.xcpng8.3.x86_64
vncterm-10.2.0-3.0.xen417.1.xcpng8.3.x86_64 is a duplicate with vncterm-10.2.0-3.xcpng8.3.x86_64
wsproxy-23.31.0-1.1.0.xen417.2.xcpng8.3.x86_64 is a duplicate with wsproxy-23.31.0-1.1.xcpng8.3.x86_64
xapi-core-23.31.0-1.1.0.xen417.2.xcpng8.3.x86_64 is a duplicate with xapi-core-23.31.0-1.1.xcpng8.3.x86_64
xapi-nbd-23.31.0-1.1.0.xen417.2.xcpng8.3.x86_64 is a duplicate with xapi-nbd-23.31.0-1.1.xcpng8.3.x86_64
xapi-rrd2csv-23.31.0-1.1.0.xen417.2.xcpng8.3.x86_64 is a duplicate with xapi-rrd2csv-23.31.0-1.1.xcpng8.3.x86_64
xapi-storage-script-23.31.0-1.1.0.xen417.2.xcpng8.3.x86_64 is a duplicate with xapi-storage-script-23.31.0-1.1.xcpng8.3.x86_64
xapi-xe-23.31.0-1.1.0.xen417.2.xcpng8.3.x86_64 is a duplicate with xapi-xe-23.31.0-1.1.xcpng8.3.x86_64
xcp-clipboardd-1.0.3-7.0.xen417.1.xcpng8.3.x86_64 is a duplicate with xcp-clipboardd-1.0.3-7.xcpng8.3.x86_64
xcp-featured-1.1.6-3.0.xen417.1.xcpng8.3.x86_64 is a duplicate with xcp-featured-1.1.6-3.xcpng8.3.x86_64
xcp-networkd-23.31.0-1.1.0.xen417.2.xcpng8.3.x86_64 is a duplicate with xcp-networkd-23.31.0-1.1.xcpng8.3.x86_64
xen-dom0-libs-4.17.3-1.0.xen417.1.xcpng8.3.x86_64 is a duplicate with xen-dom0-libs-4.13.5-10.58.xcpng8.3.x86_64
xen-dom0-tests-4.17.3-1.0.xen417.1.xcpng8.3.x86_64 is a duplicate with xen-dom0-tests-4.13.5-10.58.xcpng8.3.x86_64
xen-dom0-tools-4.17.3-1.0.xen417.1.xcpng8.3.x86_64 is a duplicate with xen-dom0-tools-4.13.5-10.58.xcpng8.3.x86_64
xen-hypervisor-4.17.3-1.0.xen417.1.xcpng8.3.x86_64 is a duplicate with xen-hypervisor-4.13.5-10.58.xcpng8.3.x86_64
xen-libs-4.17.3-1.0.xen417.1.xcpng8.3.x86_64 is a duplicate with xen-libs-4.13.5-10.58.xcpng8.3.x86_64
xen-tools-4.17.3-1.0.xen417.1.xcpng8.3.x86_64 is a duplicate with xen-tools-4.13.5-10.58.xcpng8.3.x86_64
xenopsd-23.31.0-1.1.0.xen417.2.xcpng8.3.x86_64 is a duplicate with xenopsd-23.31.0-1.1.xcpng8.3.x86_64
xenopsd-cli-23.31.0-1.1.0.xen417.2.xcpng8.3.x86_64 is a duplicate with xenopsd-cli-23.31.0-1.1.xcpng8.3.x86_64
]]>https://xcp-ng.org/forum/post/72689https://xcp-ng.org/forum/post/72689Fri, 01 Mar 2024 16:07:18 GMT<![CDATA[Reply to Xen 4.17 on XCP-ng 8.3! on Fri, 01 Mar 2024 13:38:51 GMT]]>I just pushed an update to the xcp-ng-lab repository, which updates Xen to a new build with a security fix and two other changes.

Changelog:

* Fri Feb 23 2024 Andrew Cooper <andrew.cooper3@citrix.com> - 4.17.3-3
- Fix for XSA-451 CVE-2023-46841.
- Fix the migration of VMs which had previously seen the CMP_LEGACY feature.
- Retire support to customise guest memory at the 1M boundary.
]]>https://xcp-ng.org/forum/post/72653https://xcp-ng.org/forum/post/72653Fri, 01 Mar 2024 13:38:51 GMT<![CDATA[Reply to Xen 4.17 on XCP-ng 8.3! on Fri, 01 Mar 2024 08:06:54 GMT]]>On an HP EliteDesk 800 G3 35W Mini i5 6500T

XTF:
with no-exec-sp:
All Test SKIP/SUCCESS

with exec-sp:
Hard Freeze.

dom0 Test all Tests passed.

]]>https://xcp-ng.org/forum/post/72634https://xcp-ng.org/forum/post/72634Fri, 01 Mar 2024 08:06:54 GMT<![CDATA[Reply to Xen 4.17 on XCP-ng 8.3! on Thu, 29 Feb 2024 13:46:45 GMT]]>Server:

Intel S5520UR Dual Xeon E5645

  • Dom0 all Tests passed
  • xtf selftest SUCCESS
  • xtf expected skip results SKIP/SUCCESS
  • except:
test-pv64-cpuid-faulting                 SKIP
test-pv64-pv-fsgsbase                    SKIP
with or without xl set-parameters ept=no-exec-sp
]]>https://xcp-ng.org/forum/post/72538https://xcp-ng.org/forum/post/72538Thu, 29 Feb 2024 13:46:45 GMT<![CDATA[Reply to Xen 4.17 on XCP-ng 8.3! on Wed, 28 Feb 2024 23:26:19 GMT]]>dell poweredge r720 with dual xeon e5-2670
all tests successful or skipped on xtf and dom0 (without setting no-exec-fp)

]]>https://xcp-ng.org/forum/post/72465https://xcp-ng.org/forum/post/72465Wed, 28 Feb 2024 23:26:19 GMT<![CDATA[Reply to Xen 4.17 on XCP-ng 8.3! on Mon, 26 Feb 2024 23:21:36 GMT]]>@Andrew said in Xen 4.17 on XCP-ng 8.3!:

xtf HARD system freeze at test-hvm64-xsa-304. (only XCP hard lockup I have seen)
xtf With ept=no-exec-sp, all tests SKIP/SUCCESS.

XSA-304 is https://www.intel.com/content/www/us/en/developer/articles/troubleshooting/software-security-guidance/technical-documentation/machine-check-error-avoidance-page-size-change.html

It's guest exploitable, and locks up the CPU so hard it doesn't even reset properly. It's also very expensive to work around, hence why it's not mitigated by default.

]]>https://xcp-ng.org/forum/post/72260https://xcp-ng.org/forum/post/72260Mon, 26 Feb 2024 23:21:36 GMT<![CDATA[Reply to Xen 4.17 on XCP-ng 8.3! on Fri, 23 Feb 2024 15:19:35 GMT]]>@gb-123 Thanks! I updated the first message.

]]>https://xcp-ng.org/forum/post/72092https://xcp-ng.org/forum/post/72092Fri, 23 Feb 2024 15:19:35 GMT<![CDATA[Reply to Xen 4.17 on XCP-ng 8.3! on Fri, 23 Feb 2024 15:14:16 GMT]]>@stormi

WHAT THIS VERSION OF XEN CHANGES

I must admit I haven't done my homework yet here. You can check the upstream changelogs at the Xen Project. I'll update this post if someone provides a useful bullet list.

Here you go :

Notable Features
This release has seen the increase in hardware support for both x86 and Arm, together with the addition of other improvements and features:

  • MISRA-C integration: The project has officially adopted four directives and 24 rules, added MISRA-C checker build integration, and defined how to document deviations. A number of MISRA-C violations have been fixed.
  • Static configuration options for ARM: In many embedded environments, we know ahead of time exactly what resources all guests will need at boot time. In constrained resource environments, allocation on use increases the possibility that the allocation will fail at runtime. With static configuration, resources are allocated statically when the hypervisor boots, removing the possibility of runtime failure. Resources which can be statically configured as of 4.17 include event channels, shared memory, and hypervisor heap.
  • ARM: Add “tech preview” implementation for VirtIO. Xen now includes full support for VirtIO on embedded systems, on ARM, for the virtio-mmio transport, allowing a wide range of VirtIO devices to be supported. This includes front-end support in Linux, toolstack (libxl/xl) and dom0less support, and a userspace backend. Currently, the following stand-alone backends are available and have been tested: virtio-disk, virtio-net, i2c, and gpio.
  • dom0less / Hyperlaunch: cpupools can be specified at boot using device tree. This allows the use of cpupools in dom0less / Hyperlaunch -style configurations; in particular, it makes it possible to assign different types of CPUs of an ARM big.LITTLE system to different cpupools at boot time.
  • dom0less / Hyperlaunch: PV frontend / backend connections can now be specified between guests, allowing statically booted guests with PV devices
  • On ARM, p2m structures are now allocated out of a pool of memory set aside at domain creation; this provides better isolation between guests against memory resource failures
  • ARM: Mitigations against Spectre-BHB
  • x86: IOMMU superpage support for all guest types; improving performance of PCI pass-through
  • x86: Security support hosts with up to 12 TiB of RAM
  • x86: Can now set cpuid parameters for dom0 at boot time
  • x86: mwait-idle support: Added SPR and ADL
  • x86: Improved speculative mitigation support, including VIRT_SSBD and MSR_SPEC_CTRL features to help guests know what speculative mitigations they don't need to be done (due to mitigations on the hypervisor side), and to control what kind of speculative mitigations the hypervisor performs on their behalf
  • Out-of-tree builds for the hypervisor now supported
  • ARM: Since addition of Zephyr RTOS guests support (Xen 4.15, Zephyr 3.1.0), work has been done on making it possible to run Zephyr in dom0 improving boot time, stability and paving the way for future safety certification for Xen-based systems

Source : https://wiki.xenproject.org/wiki/Xen_Project_4.17_Feature_List

]]>https://xcp-ng.org/forum/post/72089https://xcp-ng.org/forum/post/72089Fri, 23 Feb 2024 15:14:16 GMT<![CDATA[Reply to Xen 4.17 on XCP-ng 8.3! on Fri, 23 Feb 2024 13:05:19 GMT]]>@stormi
HP DL360p G8 (Xeon E5-2680) XCP 8.3 Xen version 4.17.3-2

  • Dom0 ALL TESTS PASSED.
  • xtf selftest SUCCESS.
  • xtf all tests SKIP/SUCCESS.

Intel NUC10 (i5-10210U) XCP 8.3 Xen version 4.17.3-2

  • Dom0 ALL TESTS PASSED.
  • xtf selftest SUCCESS.
  • xtf HARD system freeze at test-hvm64-xsa-304. (only XCP hard lockup I have seen)
  • xtf With ept=no-exec-sp, all tests SKIP/SUCCESS.
]]>https://xcp-ng.org/forum/post/72075https://xcp-ng.org/forum/post/72075Fri, 23 Feb 2024 13:05:19 GMT<![CDATA[Reply to Xen 4.17 on XCP-ng 8.3! on Fri, 23 Feb 2024 12:22:14 GMT]]>@stormi Never mind.... yum update --enablerepo=xcp-ng-lab is working now on that system...

]]>https://xcp-ng.org/forum/post/72074https://xcp-ng.org/forum/post/72074Fri, 23 Feb 2024 12:22:14 GMT<![CDATA[Reply to Xen 4.17 on XCP-ng 8.3! on Fri, 23 Feb 2024 12:16:41 GMT]]>@stormi I already installed 4.17 before, now doing today's update yum update --enablerepo=xcp-ng-lab wants to install from both lab and base, but they conflict because yum picks base. This happens for all of the updated lab packages, not just one in the example:

---> Package forkexecd.x86_64 0:23.31.0-1.1.0.xen417.2.xcpng8.3 will be updated
---> Package forkexecd.x86_64 0:23.31.0-1.5.xcpng8.3 will be an update
Updating:
 forkexecd                                         x86_64                              23.31.0-1.5.xcpng8.3                                   xcp-ng-base                              1.7 M

https://paste.vates.tech/?f4dea5fc787301a9#6XKfAJyxkRjuLVkrJVznRJpV3x1VQVL5NE2oaRLHKWA7

]]>https://xcp-ng.org/forum/post/72072https://xcp-ng.org/forum/post/72072Fri, 23 Feb 2024 12:16:41 GMT<![CDATA[Reply to Xen 4.17 on XCP-ng 8.3! on Fri, 23 Feb 2024 11:33:12 GMT]]>After the update, besides testing manually, there is another way you can contribute to the testing of Xen 4.17 for XCP-ng.

  1. Run XTF: https://docs.xcp-ng.org/project/development-process/tests/#test-the-xen-hypervisor-itself
  2. Run xen-dom0-tests: https://docs.xcp-ng.org/project/development-process/tests/#xen-dom0-tests

In order not to flood this thread with your test results:

  • only share the output if there's an error, or when in doubt
  • you can quote errors here, but if you think it's useful to share the full output, then please use https://paste.vates.tech.

If you have extra hosts you can temporarily dedicate to this, even if you don't have any VMs to run on them, you can very well take part in the testing effort by installating XCP-ng 8.3 beta2, updating, installing Xen 4.17, and then running these automated tests.

The more diverse hardware we get to test, the better.

]]>https://xcp-ng.org/forum/post/72065https://xcp-ng.org/forum/post/72065Fri, 23 Feb 2024 11:33:12 GMT<![CDATA[Reply to Xen 4.17 on XCP-ng 8.3! on Fri, 23 Feb 2024 11:26:19 GMT]]>New updates are available in xcp-ng-lab for Xen 4.17.

Update with:

yum update --enablerepo=xcp-ng-lab

Then reboot.

Here's the changelog, from XenServer's development repository for Xen:

 * Tue Feb 13 2024 Andrew Cooper <andrew.cooper3@citrix.com> - 4.17.3-2
- De-virtualise more function pointers, based on boot time configuration
- Improve the performance of IOMMU construction for dom0
- Fix a bug with the determination of IVMD memory regions
- Fix inefficiencies with XEN_{SYS,DOM}CTL_getdomaininfo{,list}
- Fix undefined behaviour in compat_set_timer_op()
- Fix the Raw CPU Policy rescan when CPUID Masking is active
]]>https://xcp-ng.org/forum/post/72063https://xcp-ng.org/forum/post/72063Fri, 23 Feb 2024 11:26:19 GMT<![CDATA[Reply to Xen 4.17 on XCP-ng 8.3! on Tue, 20 Feb 2024 17:01:54 GMT]]>@redakula That's a known issue that was due to 2 problems, and both are fixed for the end of the month

]]>https://xcp-ng.org/forum/post/71808https://xcp-ng.org/forum/post/71808Tue, 20 Feb 2024 17:01:54 GMT<![CDATA[Reply to Xen 4.17 on XCP-ng 8.3! on Tue, 20 Feb 2024 16:57:08 GMT]]>@stormi Intel 9th gen on C242 chipset if you are keeping track of hardware.

Not 100% sure if it is related (but i believe it was working before updating) but stats are unavailable in XOfor both host and VM's. Simply says "No stats."
XO from sources and fully up to date on the latest commit.

Can anyone else check if they have stats in XO?

]]>https://xcp-ng.org/forum/post/71806https://xcp-ng.org/forum/post/71806Tue, 20 Feb 2024 16:57:08 GMT<![CDATA[Reply to Xen 4.17 on XCP-ng 8.3! on Tue, 20 Feb 2024 15:01:16 GMT]]>ive been running it for 3 days so far with no issues, everything seems to be working fine

]]>https://xcp-ng.org/forum/post/71786https://xcp-ng.org/forum/post/71786Tue, 20 Feb 2024 15:01:16 GMT