https://wiki.xenproject.org/index.php?title=Special:NewPages&feed=atom&hideredirs=1&limit=50&offset=&namespace=0&username=&tagfilter=&size-mode=max&size=0Xen - New pages [en]2024-03-28T14:28:16ZFrom XenMediaWiki 1.31.3https://wiki.xenproject.org/wiki/Xen_Project_4.18_Feature_ListXen Project 4.18 Feature List2023-11-17T11:29:30Z<p>Dunlapg: /* Notable Features */</p>
<hr />
<div>= Notable Features =<br />
<br />
This release has seen the increase in hardware support for both x86 and Arm, together with the addition of other improvements and features:<br />
<br />
* ARM: The Scalable Vector Extension (SVE) is now merged in upstream Xen as a tech preview. <br />
* ARM: The Arm Firmware Framework for Arm A-profile (FF-A) framework support is now merged in upstream Xen as a tech preview. <br />
* ARM: The memory subsystem in Xen on Arm64 is now more compliant with the Arm Arm.<br />
x86<br />
* x86: On all Intel systems, MSR_ARCH_CAPS is now visible in guests, and controllable from the VM's config file. For CPUs from ~2019 onwards, this allows guest kernels to see details about hardware fixes for speculative mitigations.<br />
* x86: Support for features new in AMD Genoa CPUs:<br />
* x86: CPUID_USER_DIS (CPUID Faulting) used by Xen to control PV guest's view of CPUID data.<br />
* x86: Support for features new in Intel Sapphire Rapids CPUs:<br />
** PKS (Protection Key Supervisor) available to HVM/PVH guests<br />
** VM-Notify used by Xen to mitigate certain micro-architectural pipeline livelocks, instead of crashing the entire server<br />
** Bus-lock detection, used by Xen to mitigate (by rate-limiting) the systemwide impact of a guest misusing atomic instructions<br />
* x86: Support for features new in Intel Granite Rapids CPUs: AVX512-FP16<br />
* x86: Add Intel Hardware P-States (HWP) cpufreq driver<br />
* x86: Support for enforcing system-wide operation in Data Operand Independent Timing Mode<br />
* Initial RISC-V port, with Gitlab-CI doing "Early printk" (i.e., "Hello world" implementation)<br />
* Initial Power port, with Gitlab-CI doing "Early printk" (i.e., "Hello world" implementation)<br />
* The project has officially adopted more MISRA-C rules, from four directives and 24 rules in 4.17 to 6 directives and 65 rules of MISRA-C<br />
* xl/libxl can customize SMBIOS strings for HVM guests<br />
* On Arm, experimental support for dynamic addition/removal of Xen device tree nodes using a device tree overlay binary (.dtbo)<br />
* Introduced two new hypercalls to map the vCPU runstate and time areas by physical rather than linear/virtual addresses<br />
<br />
= Ongoing activities =<br />
<br />
The Xen community has several interesting initiatives, where work is ongoing and is expected to bear fruit in forthcoming releases. Some of the highlights:<br />
<br />
== ARM MPU and vPCI ==<br />
<br />
On Arm, the upstream MPU (memory protection unit) support and PCI-passthrough work is ongoing, including some refactoring and improvements of the existing code. Both works will be included in the next few releases. <br />
<br />
== RISC-V ==<br />
<br />
On RISC-V, some refactoring and improvements of the existing code have been done. BUG/WARN macros, temporary printk, and decode_cause() functions to print the reason for a trap have been introduced. In the next few releases, identity mapping, full Xen build, and trap handling will be introduced.<br />
<br />
== POWER ==<br />
<br />
On PowerPC, initial support for the ppc64le architecture was added to Xen, specifically targeting Power ISA 3.0B and later. As of 4.18, an early-stage Xen image can be built that boots on bare metal PowerNV systems. Current ongoing work focuses on handling printing to the OPAL serial console, as well as some basic Radix MMU page table initialization.<br />
<br />
<br />
[[Category:Xen]] <br />
[[Category:Users]]<br />
[[Category:Xen 4.18]]</div>Dunlapghttps://wiki.xenproject.org/wiki/Xen_Project_4.18_Release_NotesXen Project 4.18 Release Notes2023-11-17T10:31:58Z<p>Dunlapg: </p>
<hr />
<div><br />
= Overview =<br />
<br />
Xen Project 4.18.0 was released on 17th of November 2023.<br />
<br />
Xen Project 4.18.0 is the work of 11 months of development.<br />
<br />
= New Feature Highlights =<br />
The list of new features can be found on the following page: [[Xen Project 4.18 Feature List]]<br />
<br />
You can find information on support status (including security support) for various features in [https://xenbits.xenproject.org/docs/4.18-testing/SUPPORT.html SUPPORT.md] and [https://xenbits.xen.org/docs/unstable/support-matrix.html Hypervisor Support Matrix].<br />
<br />
Documentation is available online: [https://xenbits.xen.org/docs/4.18-testing Xen 4.18 Documentation]<br />
<br />
= Build Requirements =<br />
<br />
Xen requires gcc v4.1.2 or later (x86), gcc 4.9 or later (arm32), or gcc 5.1 or later (arm64).<br />
<br />
= Build =<br />
First of all you will have to get the Xen 4.18 source code, which you can either download through our release tarball (including signature) from our [https://downloads.xenproject.org/release/xen/4.18.0 download page]. Alternatively, you can get the source in the following way:<br />
<br />
* With a recent enough git (&gt;= 1.7.8.2) just clone and checkout the proper tag (RELEASE-4.18.0) from the [https://xenbits.xenproject.org/gitweb/?p=xen.git;a=summary xen.git] repo directly:<br />
git clone -b RELEASE-4.18.0 https://xenbits.xenproject.org/git-http/xen.git<br />
<br />
Build instructions can be found at [[Compiling Xen From Source]] or [[Compiling Xen From Source on NetBSD]].<br />
<br />
= Changes affecting downstreams and users =<br />
<br />
In general, our aim is to keep old guests working on new versions of Xen, and to allow live migration from the previous Xen major version.<br />
<br />
* The old qemu-xen-traditional stubdomain device model (ioemu-stubdom) is deprecated and no longer built by default.<br />
<br />
* The old pv-grub Xen fork is also deprecated and no longer built by default. Support to run in PV mode has been added to upstream Grub project.<br />
<br />
= Known issues =<br />
<br />
While we do the utmost to make the release perfect, there are always fixes which are not quite complete on time. We will add those here. So if you run into trouble, please check this section.<br />
<br />
Currently known issues are:<br />
<br />
* Cpupools: when moving a domain from a cpupool with the credit2 scheduler to another cpupool, the host will crash.<br />
<br />
* Livepatching: Attempting to apply a livepatch will crash the hypervisor.<br />
<br />
[[Category:Xen]] <br />
[[Category:Release Notes]] <br />
[[Category:Users]]<br />
[[Category:Xen 4.18]]</div>Dunlapg