[Pkg-xen-devel] Re: Packaing Xen 3.0 etc for Debian [signed]

Jeremy T. Bouse [c] jbouse at debian.org
Fri Feb 24 18:00:18 UTC 2006


    What can I say gang, but "WOW!"... Just made it into work and seems
the list had a wild fire while I was commuting. It seems to me Bastian
had his own plans that he didn't make known and is apparently the only
one on the kernel team, that I've seen, wanting to completely manage
Xen. I can see his point about using -unstable rather than -testing and
it would seem that what we have in place could easily be transitioned to
work with it instead. Do we want to tag what we have now that works with
-testing and get any changes made to support -unstable done before we
release any packaging?

    Maybe try a lil harder to get Bastian to join our efforts and
support from the kernel team side as we do really need that support and
it seems foolish to me to split hairs over this. Xen is complex and
needs more than one person to support it properly IMHO. Without any
kernel team support we will have trouble getting pre-built base Xen
kernel images (dom0 or domU) into the archive.

    I'm going to draft an email and try to get Bastian to communicate
with me and see if I can't get him to see our point better. From the
others that had responded that are not on the xen team, it seems they
agree that it shouldn't mean disbanding this team and that the kernel
team doesn't have the desire to maintain xen as well. Any thoughts?

    Regards,
    Jeremy

Guido Trotter wrote:

>On Fri, Feb 24, 2006 at 06:06:22PM +0100, Bastian Blank wrote:
>
>Hi,
>
>  
>
>>It is a sort of kernel.
>>    
>>
>
>Yeah, it's a sort of kernel, but it's not the linux kernel... And it seems the
>kernel team is about the linux kernel, not just any kernel, isn't it?
>
>  
>
>>Just to say, how connected xen to linux is:
>>
>>For example: There are three kernel trees of xen:
>>- from xen-3.0-testing, 2.6.12
>>- from linux-2.6-xen, 2.6.16-rc4
>>- from linux-2.6-merge, 2.6.16-rc3
>>All of them have different needs from xen.
>>
>>The kernels from xen-3.0-testing and linux-2.6-merge works with a 3.0
>>and unstable hypervisor.
>>
>>The 3.0 utils only works on the kernel from xen-3.0-testing. The
>>unstable utils with the other. But with both hypervisors.
>>
>>    
>>
>
>That's I think because xen is still young, and is starting just now its
>distribution integration, and probably will happen a lot less when it will be
>integrated with Linux (Linus' tree) and the development of xenolinux will
>proceed at a different pace than the hypervisor. Then probably it will just be
>that any xen version will have a minimum linux version needed, just as now a lot
>of other stuff does, and there will be nothing special in it, except the fact
>that it needs a kernel compiled for the appropriate subarch).
>
>  
>
>>I won't reject the help of volunteers but I strongly think that the
>>kernel team needs to have its hands on them.
>>
>>    
>>
>
>What do other people in the kernel team think? If the majority of them agree
>fine, otherwise are you sure it's not counterproductive to force xen in the
>kernel team hands if most of them don't want to touch it, and on the other hand
>to risk driving away other people who just cannot follow the whole linux
>business but could work on the xen hypervisor and tools, help coordinate with
>xen's upstream, debian glibc and d-i, etc! Especially if you and other people
>who would do both can still do it! :)
>
>Guido
>
>
>_______________________________________________
>Pkg-xen-devel mailing list
>Pkg-xen-devel at lists.alioth.debian.org
>http://lists.alioth.debian.org/mailman/listinfo/pkg-xen-devel
>
>  
>


--
------------------------ [ SECURITY NOTICE ] ------------------------
To: pkg-xen-devel at lists.alioth.debian.org.
For your security, jbouse at debian.org
digitally signed this message on 24 February 2006 at 18:00:24 UTC.
Verify this digital signature at http://www.ciphire.com/verify.
------------------- [ CIPHIRE DIGITAL SIGNATURE ] -------------------
Q2lwaGlyZSBTaWcuAjhwa2cteGVuLWRldmVsQGxpc3RzLmFsaW90aC5kZWJpYW4ub3JnA
Gpib3VzZUBkZWJpYW4ub3JnAGVtYWlsIGJvZHkAMwsAAHwAfAAAAAEAAAC4Sf9DMwsAAP
4CAAIAAgACACBbbe/kx8tpUyJhmgvpubSxgZmn0dxD/KgljpsTpsvZVQEAJLQlVT52rnd
nqox8AzyHB09mthbDWqsaMF1UXyCm8B69Woft5nTmknn1KMOKU+cNpU8ek4SQf7N68WFL
2/7OHF7TNorRU2lnRW5k
--------------------- [ END DIGITAL SIGNATURE ] ---------------------




More information about the Pkg-xen-devel mailing list