I am trying to work out whether it is practical to propose Dom0 xen
support as a feature for Fedora 15.
The kernel situation is that Domain 0 has been accepted upstream for
2.6.37. Assuming a 3 month kernel release cycle, F15 will most likely ship
with a 2.6.37.x kernel, with 2.6.38 coming out either after the F15
release or just before but too late to be included. If the plan to get key
xen drivers into 2.6.38 succeeds, then F15 may be become usable as a
Domain 0 system at some point during its lifetime as the kernel package in
a Fedora version typically has one major update.
If the kernel team accept backported patches then it might just be
possible to ship F15 with usable Domain 0 support but the timescale for
that would be very tight.
The other thing we would need to consider is what needs to be done to make
xen friendly enough to be usable by an ordinary user. The page
https://fedoraproject.org/wiki/Features/XenPvopsDom0 contains plans from
when dom0 xen support was expected to make a quick return to Fedora, but
they are a couple of years old now so probably need updating.
I think as a minimum we would need a way to add a dom0 enabled grub entry
for a kernel, rather than requiring the user to hand edit the grub file.
We should also make sure that xen works with the other Fedora
What do others think about this? For example is it achievable as a
feature, is it too early and better to wait for F16, and what else should
we aim to do to make xen usable in Fedora?
I have built another test kernel (2.6.37-0.1.rc1.git0.xendom0.fc15) to
play with at http://koji.fedoraproject.org/koji/taskinfo?taskID=2581020 .
As with the previous kernel this is entirely based on the upstream kernel
and Fedora kernel patches, and is probably close to what the Fedora 15
kernel will look like soon. I haven't tested it yet.
I just completed some updates of https://fedoraproject.org/wiki/Features/XenPvopsDom0.
I would like to submit this to the Fedora Feature Wranglers on Wednesday
as a proposed feature for Fedora 15. If you are interested, please review
the document and provide feedback. If you are a previous editor of the
page, I hope you don't mind me trying to move this forward. I will
appreciate any comments.
As far as I can tell, Fedora's grubby does not yet support the GRUB
syntax required by Xen, e.g.,
title Fedora (184.108.40.206-170.1.xendom0.fc12.x86_64)
==> module /vmlinuz-220.127.116.11-170.1.xendom0.fc12.x86_64 ...
==> module /initramfs-18.104.22.168-170.1.xendom0.fc12.x86_64.img
I don't think it supports multiple "module" keywords.
I am presently working on extending grubby to allow something like the
following (note that the --add-kernel parameter name might change):
grubby --add-multiboot=/boot/xen.gz --mbargs="[xen arguments]" \
--args="[kernel arguments]" \
Does this make sense?
How could we tie this into anaconda kernel upgrades? I am thinking of
adding something to /etc/sysconfig/kernel that new-kernel-pkg would
look for. If the flag is present, then new-kernel-pkg could use the
extended grubby syntax. The Fedora Wiki's XenPvopsDom0 document mentions
/etc/sysconfig/xen instead, is this up to date? Should we use this
instead of /etc/sysconfig/kernel?
I hope this isn't too off-topic. :)
I'm trying to recompile Michael Young's F12 dom0 kernel on RHEL 6.
I've run into a small issue that I could probably push through, but I
wanted to ask for opinions here.
The source RPM depends on 'asciidoc', which isn't in the main Red Hat
repository (at least, not that I could find). I was wondering what,
exactly, needs asciidoc and if it would be safe/easy/possible/advisable
to remove that dependency.
Node Assassin: http://nodeassassin.org