New pages
From Xen
Jump to navigationJump to search
- 15:27, 4 March 2025 Xen Project 4.20 Feature List (hist | edit) [1,916 bytes] Olkur (talk | contribs) (Created page with "= 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: * ARM: Support for LLC (Last Level Cache) coloring. * ARM: Experimental support for Armv8-R. * ARM: Support for NXP S32G3 Processors Family and NXP LINFlexD UART driver. * ARM: Basic handling for SCMI requests over SMC using Shared Memory, by allowing forwarding the calls to EL3 FW if coming from hwdom. * x86:...")
- 15:16, 4 March 2025 Xen Project 4.20 Release Notes (hist | edit) [2,325 bytes] Olkur (talk | contribs) (Created page with "= Overview = Xen Project 4.20.0 was released on 5th of March 2025. Xen Project 4.20.0 is the work of 7 months of development. = New Feature Highlights = The list of new features can be found on the following page: Xen Project 4.20 Feature List You can find information on support status (including security support) for various features in [https://xenbits.xenproject.org/docs/4.20-testing/SUPPORT.html SUPPORT.md] and [https://xenbits.xen.org/docs/unstable/support-...")
- 10:12, 11 February 2025 NUMA node affinity in the Xen hypervisor (hist | edit) [788 bytes] Bernhard.Kaindl (talk | contribs) (Created page with "= Setting a Domain’s node affinity = == Hypercall: <code>XEN_DOMCTL_setnodeaffinity</code> == It can be called from <code>libxenctrl</code> and <code>libxl</code> === <code>libxenctrl</code>: <code>xc_domain_node_setaffinity()</code> === This call requires the <code>domid</code> of the created domain and an <code>xc_nodemap_t</code>: <source lang="c">int xc_domain_node_setaffinity(xc_interface *xch, uint32_t domid,...")
- 11:37, 5 February 2025 Walkthrough: VM build using xenguest (hist | edit) [9,384 bytes] Bernhard.Kaindl (talk | contribs) (Created page with "= xenguest is used by xenopsd to start domains = See https://xapi-project.github.io/new-docs/xenopsd/walkthroughs/VM.start for more details on what how xenopsd does at the start of the the VM.start task and how it works in detail. When Xenopsd receives the request to start a VM, it adds it to the appropriate per-VM queue via the function [https://github.com/xapi-project/xenopsd/blob/524d57b3c70/lib/xenops_server.ml#L1744 queue_operation]. In the case of <code>VM_start...")
- 15:08, 30 January 2025 NUMA node-specifc memory allocation (hist | edit) [14,694 bytes] Bernhard.Kaindl (talk | contribs) (Created page with "__NOTOC__ {{sidebar | name = Content | outertitlestyle = text-align: left; | headingstyle = text-align: left; | contentstyle = text-align: left; | content1 = __TOC__ }} = NUMA node-specific memory allocation in X86 meminit_hvm() = == Entry point: <code>xenguest --mode hvm_build</code> == <code>xenguest --mode hvm_build</code>: It calls [https://github.com/xenserver-next/xen/blob/xenguest/tools/xenguest/xenguest.c#L499|<code>do_hvm_build()</code>], which cal...")