> "The release must boot successfully as Xen DomU with releases providing > a functional, supported Xen Dom0 and widely used cloud providers > utilizing Xen." I am a long time Xen/Fedora user. In fact, I rely on Fedora as my Dom0. I acknowledge that there are not too many of us, and I further acknowledge that mandatory testing often goes unperformed. The Fedora Xen mailing list is exceedingly low-volume. Michael Young has in the past done a lot of the heavy lifting surrounding Xen support, and I am very grateful for his work. Xen Dom0 is particularly tenuous. Dropping (for a good reason) GRUB's multiboot2 module left Xen unable to boot under EFI [e.g., 1]. All of that said, there are good reasons to choose Xen over KVM. Xen's architecture and full support for libvmi come to mind. (Of course, there are good reasons to choose KVM too.) Perhaps we could go one more release with the status quo to give the Xen/Fedora community a last chance to rally and demonstrate a willingness to perform the necessary testing and maintenance. I suspect we are all quite busy, so we might find ourselves admitting that broader Xen support will be relegated to the standard means of maintenance rather than rising to the status of blockers. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1703872 -- Mike :wq _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
