Change:
If you experience any issues, please report them. The original Perl script can still be used for now by setting `system.switch.enableNg` to `false`. <ins> - The [Xen Hypervisor](https://xenproject.org) is once again available as a virtualisation option under [`virtualisation.xen`](#opt-virtualisation.xen.enable). - This release includes Xen [4.17.5](https://wiki.xenproject.org/wiki/Xen_Project_4.17_Release_Notes), [4.18.3](https://wiki.xenproject.org/wiki/Xen_Project_4.18_Release_Notes) and [4.19.0](https://wiki.xenproject.org/wiki/Xen_Project_4.19_Release_Notes), as well as support for booting the hypervisor on EFI systems. ::: {.warning} Booting into Xen through a legacy BIOS bootloader or with the legacy script-based Stage 1 initrd have been **deprecated**. Only EFI booting and the new systemd-based Stage 1 initrd are supported. ::: - There are two flavours of Xen available by default: `xen`, which includes all built-in components, and `xen-slim`, which replaces the built-in components with their Nixpkgs equivalents. - The `qemu-xen-traditional` component has been deprecated by upstream Xen, and is no longer available in any of the Xen packages. - The OCaml-based Xen Store can now be configured using  [`virtualisation.xen.store.settings`](#opt-virtualisation.xen.store.settings). - The `virtualisation.xen.bridge` options have been deprecated in this release cycle. Users who need network bridges are encouraged to set up their own networking configurations. </ins> ## New Modules {#sec-release-24.11-new-modules} - [TaskChampion Sync-Server](https://github.com/GothenburgBitFactory/taskchampion-sync-server), a [Taskwariror 3](https://taskwarrior.org/docs/upgrade-3/) sync server, replacing Taskwarrior 2's sync server named [`taskserver`](https://github.com/GothenburgBitFactory/taskserver).

Discussion:
I am unable to get xen working on my system following the advise from with and without: the system and expect failure to boot due to the kernel panic in domain0 (?) Please run and paste the result. !
CC
I haven't been using Xen for a while now so I have no idea if it's broken now. But AFAIK you can't use both Xen and KVM together, so your config shouldn't work in any case.
I marked this as stale due to inactivity. &rarr;

Describe the bug Xen package does not build on EFI systems even while support was in Add support for booting as Xen dom0 on EFI systems. To Reproduce Enable Xen in on a system with EFI boot: Expected behavior Xen packages are built and enabled. Log Error message is given to the user as nix configuration fails to build. Related to , failed assertion. Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Xen maintainers Metadata Using with EFI boot Maintainer information:
I marked this as stale due to inactivity. &rarr;
Shouldn't this just work since ?
I'm interested in this working. Is anyone working on it? Can I help in some way?
i looked into this couple of months ago and it looked to me like it just didnt work because of assertions left over before xen supported efi but im not knowledgeable enough on the subject to confirm if that is the only thing needed to fix
I have removed the assertion, but I cannot activate. There is a bug where if you are running on a non-Xen system, enable Xen, and attempt to activate, you get an error because Xen-stored (or something) service cannot read . If one ignores this, and reboots, at boot time, there is an error due to "xenfs" kmod not loading. I find that my currently booted system has a "" in but it fails to insert. It depends on which is also there and which also fails to load. I am currently nixing (is that a verb?) on I cloned today (in order to fix the EFI assertion) so perhaps that is an issue. I will see if I can checkout the 23.05 commit, but don't expect much luck there. Xen seems to be pretty much dead, which is sad. Yes, i know Qubes-OS uses it. And boots with UEFI with no problems, FWIW, here is an of an attempt to load the : Nothing to .
maybe add both to availableKernelModules and nixos-rebuild boot?
Had those set. No difference.

On reflection, given that what I have so far does not appear to boot first, I suspect the kmods fail to load because they reject being loaded in a non-Xen-booted kernel. Just checked the source. Will only register the filesystem if returns non-zero, implying not running on bare metal. I might get around to scrounging up the requisite boot stages for the EFI boot and build myself a kernel to load. a few months ago I installed dom0 FreeBSD despite all the "xen can't boot EFI" history, and it came up without a hitch and ran, so that would be a good place to look as a reference. Or I could just look at my system.... Latest for was 4.15.1. I think they are up to 4.18 or so, so perhaps I will start with overlaying 4.18 just to get my feet wet with what is needed to build the kernel.
are u using the xen kernel variant (pkgs.linuxPackagesxendom0)?
Was not. Am now. Makes no difference. The infrastructure is not being deployed. In particular, the is not being installed. Need to boot Xen first, then load the dom0 kernel. I'm sort of interested in getting to the bottom of this (ie: getting it to work) but there is so much other stuff to learn / play with / ...
yeah i get that - ill ask around a bit on the nixos discord to see if anyone there is a bit more knowledgeable on this
Great. Thanks.
posted the question on there but nobody was answering :/ idk how else to help - xen feels like a deep rabbit hole to go down and i don't wanna do that right now hopefully someone in the future responds with steps on how to solve this
anything i can do to help with this ?
Xen now works on EFI. Required compilation changes to and a custom boot builder script.