Then what would be the Dom0 kernel in Fedora 9?<br><br>Emre<br><br><div class="gmail_quote">On Thu, Mar 6, 2008 at 8:33 PM, Daniel P. Berrange <<a href="mailto:berrange@redhat.com">berrange@redhat.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><div></div><div class="Wj3C7c">On Thu, Mar 06, 2008 at 09:28:05PM +0200, Pasi K?rkk?inen wrote:<br>
> On Thu, Mar 06, 2008 at 03:29:17PM +0000, Mark McLoughlin wrote:<br>
> > Hi,<br>
> > Fedora's Xen hackers have been working hard towards switching<br>
> > our kernel-xen package from a forward-ported Xensource kernel tree to a<br>
> > state-of-the-art upstream, paravirt_ops based, kernel in Fedora 9 as<br>
> > described here:<br>
> ><br>
> > <a href="http://fedoraproject.org/wiki/Features/XenPvops" target="_blank">http://fedoraproject.org/wiki/Features/XenPvops</a><br>
> > <a href="http://www.redhat.com/archives/fedora-xen/2007-November/msg00106.html" target="_blank">http://www.redhat.com/archives/fedora-xen/2007-November/msg00106.html</a><br>
> ><br>
> > Some great progress has been made, and tomorrow's rawhide will<br>
> > have a kernel-xen update with:<br>
> ><br>
> > + A very recent 2.6.25-rc4 base<br>
> ><br>
> > + Xen paravirt_ops DomU from upstream<br>
> ><br>
> > + x86_64 Xen paravirt_ops DomU support<br>
> ><br>
> > + Paravirt framebuffer<br>
> ><br>
> > However, although the Dom0 paravirt_ops work is well advanced at<br>
> > this point, we still don't have backend drivers or x86_64 Dom0 working.<br>
> ><br>
> > With the feature freeze looming next week, we have make the<br>
> > difficult decision to focus the Fedora 9 efforts on DomU and postpone<br>
> > the inclusion of paravirt_ops Dom0 support.<br>
> ><br>
><br>
> First I'd like to thank you guys for doing this work. I think it's very<br>
> important to get good Xen support working and integrated into upstream kernel.<br>
><br>
> Was there some specific problem/bug about dom0 support (backend drivers and<br>
> x86-64), or just not enough time?<br>
<br>
</div></div>Simply lack of time - stability of DomU is of most importance because we<br>
can't change the $INSTALL_TREE/images/xen/{vmlinux,initrd.img} once F9<br>
is released. So we need to prioritize DomU support. Pushing out a new<br>
kernel to add Dom0 is trivial post-GA since it doesn't impact installer<br>
images.<br>
<br>
Dan.<br>
<font color="#888888">--<br>
|=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=|<br>
|=- Perl modules: <a href="http://search.cpan.org/%7Edanberr/" target="_blank">http://search.cpan.org/~danberr/</a> -=|<br>
|=- Projects: <a href="http://freshmeat.net/%7Edanielpb/" target="_blank">http://freshmeat.net/~danielpb/</a> -=|<br>
|=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|<br>
</font><div><div></div><div class="Wj3C7c"><br>
--<br>
Fedora-xen mailing list<br>
<a href="mailto:Fedora-xen@redhat.com">Fedora-xen@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/fedora-xen" target="_blank">https://www.redhat.com/mailman/listinfo/fedora-xen</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Emre Erenoglu<br><a href="mailto:erenoglu@gmail.com">erenoglu@gmail.com</a>