On Fri, Mar 18, 2011 at 03:34:20PM -0600, Tim Flink wrote:
> I was wondering about the progress towards dom0 support in F15. The
> feature page [1] hasn't been updated for a while, so I'm not clear on
> how close the feature is to completion.
> Specifically, I am looking to find out what kind of testing has been
> done or is being done for this new feature. As far as I know, the Fedora
> QA community is not very aware of xen dom0 support and it isn't a part
> of the test cases that we have been running.
> If dom0 support is likely to be complete in time for F15, we would
> certainly welcome assistance in writing test cases and/or helping out
> with the upcoming virtualization test day on 2011-04-14 [2].


Quick dom0 kernel status update:
        - upstream Linux 2.6.38 has core xen dom0 support, but no backend 
        - upcoming Linux 2.6.39 will have xen-netback driver (already merged 
        - xen-blkback is planned for 2.6.40.
        - xen-pciback (for pci passthru) is planned for 2.6.40.

That's the "afaik" list. There are also git branches available
with the not-yet-upstream drivers included in 2.6.38 / 2.6.39,
so those branches are usable as dom0 kernel.

If running *pure* upstream Linux 2.6.38 as Xen dom0 kernel 
then you can't launch domUs due to missing backend drivers.

When Linux 2.6.39 is released and used as dom0 kernel you 
can actually run domUs, *IF* running with Xen 4.1 hypervisor/tools, 
as Xen 4.1 contains userspace blkback driver 
(kind of a failback when kernel based xen-blkback is not available).

Based on the info/plans at the moment upcoming Linux 2.6.40
should have all the important backend drivers merged into the kernel.

I assume Fedora 15 will ship with 2.6.38 kernel?

There was some discussions earlier if we could add the various
xen backend drivers as additional patches for F15 kernel.. 
what was the end result of that discussion?

-- Pasi

> Thanks,
> Tim
> [1] http://fedoraproject.org/wiki/Features/XenPvopsDom0
> [2] https://fedoraproject.org/wiki/QA/Fedora_15_test_days

xen mailing list

Reply via email to